Closed
Bug 157183
Opened 23 years ago
Closed 23 years ago
Even though XUL Element Tree is focusable, Both the inspect tool and API return wrong value
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: dsirnapalli, Assigned: yuanyi21)
Details
Attachments
(1 file)
1.00 KB,
patch
|
mozilla
:
review+
jag+mozilla
:
superreview+
asa
:
approval+
|
Details | Diff | Splinter Review |
<tree seltype="single" flex="1">
<treecols>
<treecol id="sender" label="Sender" flex="1"/>
<treecol id="subject" label="Subject" flex="2"/>
</treecols>
<treechildren>
<treeitem>
<treerow>
<treecell label="joe@somewhere.com"/>
<treecell label="Top secret plans"/>
</treerow>
</treeitem>
<treeitem>
<treerow>
<treecell label="mel@whereever.com"/>
<treecell label="Lets do lunch"/>
</treerow>
</treeitem>
</treechildren>
</tree>
Enter the above code in xul file and open it in mozilla. Open Inspect tool and
click on "Show Hightlight Rectangle". Now Click somewhere on mozilla and tab
until the focus is on Tree Node. We get the focus on to the tree node. That
means Tree Element is focusable. Check the Inspect tool, you see only "read
only" for state. It should be "read only, focused, focusable".
If i made mistake correct me.
This was working ok previously.
Yes, it's my fault. I disabled the focusable state for tree in my last patch.
Will correct soon.
Status: NEW → ASSIGNED
Comment 4•23 years ago
|
||
Comment on attachment 91309 [details] [diff] [review]
added focused and focusable state to tree
r=jgaunt
Attachment #91309 -
Flags: review+
Comment 5•23 years ago
|
||
Comment on attachment 91309 [details] [diff] [review]
added focused and focusable state to tree
sr=jag
Attachment #91309 -
Flags: superreview+
Comment 6•23 years ago
|
||
Comment on attachment 91309 [details] [diff] [review]
added focused and focusable state to tree
a=asa (on behalf of drivers) for checkin to 1.1
Attachment #91309 -
Flags: approval+
checked into trunk!
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•