[Webkit-unassigned] [Bug 45973] New: Wrong exposure of list item markers with non-inline objects inside the items
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Fri Sep 17 10:31:28 PDT 2010
https://bugs.webkit.org/show_bug.cgi?id=45973
Summary: Wrong exposure of list item markers with non-inline
objects inside the items
Product: WebKit
Version: 528+ (Nightly build)
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: Normal
Priority: P2
Component: Accessibility
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: msanchez at igalia.com
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 :-)
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list