Bug 45973 - Wrong exposure of list item markers with non-inline objects inside the items
Summary: Wrong exposure of list item markers with non-inline objects inside the items
Status: UNCONFIRMED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Accessibility (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC Linux
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-17 10:31 PDT by Mario Sanchez Prada
Modified: 2013-10-23 16:34 PDT (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mario Sanchez Prada 2010-09-17 10:31:28 PDT
I've observed the following behavior which I found strange when exposing list items to accessible technologies.

Take the following HTML:

 <ul>
   <li>Item with just plain text</li>
   <li><a href="http//foo.bar.baz">Item with an inline item (a link)</a></li>
   <li><p>Item with a non-inline item (a paragraph)</p></li>
 </ul>

I've checked the accessible hierarchy (AccessibleObject's) generated for the first two items is something like this, from the POV of the roles:

 ListRole
   |---> ListItemRole
   |            `---> ListMarkerRole (bullet)
   |
   |---> ListItemRole
   |            |---> ListMarkerRole (bullet)
   |            `---> LinkRole
  ...

As you can see the marker is exposed as a child of the item, and as far as I understood it so far, this is correct and the expected behaviour in WebCore.

However I find the following exposure about the third item (with a non inline item) strange:

  ...
   `---> ListItemRole
                `---> GroupRole (the paragraph)
                             `---> ListMarkerRole (bullet)

What I would have expected is more something like this:

  ...
   `---> ListItemRole
                |---> ListMarkerRole (bullet)
                `---> GroupRole (the paragraph)

Hence filing this bug as I'm not sure whether this should be the expected behaviour. If instead it's the expected behaviour please accept my apologies and resolve the bug, although I must say I'd appreciate an brief explanation on the topic if that was the case :-)
Comment 1 Mario Sanchez Prada 2010-09-17 10:34:29 PDT
Adding some people to CC that I think could be interested on this topic.

Chris, perhaps you're the one here best knowing the answer to this topic or, at least, to decide whether this is actually a bug or an expected behaviour.

Opinions?
Comment 2 James Craig 2013-10-23 16:34:20 PDT
This probably is a bug, but not a terribly serious one.