Closed
Bug 320395
Opened 20 years ago
Closed 20 years ago
Accessible text caret offset is unreliable when tabbing between links
Categories
(Firefox :: Disability Access, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: wwalker, Assigned: ginnchen+exoracle)
References
(
URL
)
Details
Attachments
(1 file)
|
18.84 KB,
text/x-python
|
Details |
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20051215 Firefox/1.6a1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20051215 Firefox/1.6a1
When examining the caret offset of an accessible text area associated with a link-selected event, the offset is unreliable and usually 0.
Reproducible: Always
Steps to Reproduce:
1) Save the following html to foo.html:
<html>
<p>This is a <a href="foo1">test</a> and here is <a href="foo2">another test</a>.</p>
</html>
2) Run this tool in an xterm
3) Run Firefox and point it to foo.html
4) Tab and Shift+Tab between the two links in foo.html
Actual Results:
You will see the following output:
object:link-selected -1 0 <CORBA.any of type 'IDL:omg.org/CORBA/Null:1.0'>
text.caretOffset 7
object:link-selected -1 0 <CORBA.any of type 'IDL:omg.org/CORBA/Null:1.0'>
text.caretOffset 0
object:link-selected -1 0 <CORBA.any of type 'IDL:omg.org/CORBA/Null:1.0'>
text.caretOffset 0
object:link-selected -1 0 <CORBA.any of type 'IDL:omg.org/CORBA/Null:1.0'>
text.caretOffset 0
Expected Results:
The caret offset should reflect the caret position.
|
Reporter | |
Comment 1•20 years ago
|
||
|
|
||
Comment 2•20 years ago
|
||
2 bugs here
1)when nsAccessibleText::GetCaretOffset is called, nsISelection.focusNode is not set correctlly(always last focused node)
2)for anchor node, should compare its child text node to mTextNode, not itself
|
|
||
Updated•20 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Patch posted in Bug 320388
BTW:
Will, text.caretOffset may not be updated when link-selected event was fired.
You may got the offset where user pressed "Tab".
Assignee: nobody → ginn.chen
Fixed by Bug 320388
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•