[Webkit-unassigned] [Bug 123568] New: AX: Children Nodes for Canvas objects are not equal to Render Objects
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Thu Oct 31 07:04:04 PDT 2013
https://bugs.webkit.org/show_bug.cgi?id=123568
Summary: AX: Children Nodes for Canvas objects are not equal to
Render Objects
Product: WebKit
Version: 528+ (Nightly build)
Platform: All
OS/Version: All
Status: UNCONFIRMED
Severity: Normal
Priority: P2
Component: Canvas
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: a.moryc at samsung.com
CC: jdiggs at igalia.com, mario at webkit.org
There is a difference in children nodes taken into account for RenderObject and for NodeObject types.
Text nodes are eliminated in the AccessibilityRenderObject::computeAccessibilityIsIgnored() method but in
AccessibilityNodeObject::computeAccessibilityIsIgnored() are not considered and therefore are always added to the m_children vector.
In Mac behaviour is similar but the test canvas-accessibilitynodeobject.html passes since the text nodes are not focusable which result in
having equal number of children nodes for the RenderObject and NodeObject types. But for efl/gtk there was a bug created
https://bugs.webkit.org/show_bug.cgi?id=27048 according to which the text nodes are required to be focusable.
The question is how to adjust the canvas-accessibilitynodeobject.html test to the needs of efl/gtk ports?
The first idea could be to eliminate the text node in AccessibilityNodeObject::computeAccessibilityIsIgnored() respectively as for RenderObjects.
Which result in that these objects have the same number of children nodes and the test passes without causing any regression so far.
Although it is wondering whether this approach is fully correct?
--
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