[Webkit-unassigned] [Bug 25678] [GTK] Implement ROLE_COMBO_BOX

Sun Nov 29 22:22:57 PST 2009

https://bugs.webkit.org/show_bug.cgi?id=25678

--- Comment #1 from Joanmarie Diggs <joanmarie.diggs at gmail.com>  2009-11-29 22:22:57 PST ---
I started hacking at this over the weekend, and made quite a bit of progress.
But it turns out to be somewhat more involved than I would have originally
thought. So before I continue and start proposing patches, here's the deal...

Given this:

  <body>
    <select id="component" name="component" size="1">
      <option value="Accessibility">Accessibility</option>
      <option value="CSS">CSS</option>
      <option selected value="Evangelism">Evangelism</option>
      <option value="Forms">Forms</option>
    </select>
  </body>

DRT gives us this:

  layer at (0,0) size 118x83
    RenderView at (0,0) size 62x83
  layer at (0,0) size 118x83
    RenderBlock {HTML} at (0,0) size 62x83
      RenderBody {BODY} at (8,8) size 46x67
        RenderMenuList {SELECT} at (2,2) size 106x28 [bgcolor=#FFFFFF]
          RenderBlock (anonymous) at (4,4) size 81x20
            RenderText at (0,0) size 74x20
              text run at (0,0) width 74: "Evangelism"
        RenderText {#text} at (0,0) size 0x0
        RenderText {#text} at (0,0) size 0x0
        RenderText {#text} at (0,0) size 0x0

We expect this:

  -> Document Frame
     -> Evangelism (Combo Box)
        -> Evangelism (Menu)
           -> Accessibility (Menu Item)
           -> CSS (Menu Item)
           -> Evangelism (Menu Item)
           -> Forms (Menu Item)

Associated problems:

  1. Hierarchy's in the wrong order w.r.t. options. We need to either
     swap the render objects associated with the impacted accessibles
     or render the objects in the expected order somehow.

  2. No *easy/immediate* way (that I've found) to go from what seems
     to be a stub RenderText object to the associated String. (I am
     able to re-create things via SelectElement and OptionElement...)

In other words, WebKitGtk's rendering w.r.t. HTML combo boxes doesn't mesh all
that well with what we need/expect.

In addition: VoiceOver seems to deal with this object in its collapsed form
strictly as a pop up button rather than as a combo box. So what other a11y
platforms need/expect doesn't mesh all that well with what we need/expect.

I am managing to hack around these things, but it's starting to get ugly. Any
brilliant insights would welcome. Otherwise, I'll try to get some patches up
before too long which more concretely illustrate the issues.

Thanks!

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.