Closed
Bug 1052504
Opened 10 years ago
Closed 4 years ago
atk_text_get_text_at_offset and IAccessibleText::textAtOffset sometimes return an empty line instead of the line at offset
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1525631
People
(Reporter: jdiggs, Unassigned)
References
(Blocks 2 open bugs)
Details
Attachments
(2 files)
Steps to reproduce: 1. Load the attached test case in Firefox 2. Load the attached accessible event listener in a terminal 3. Enable caret navigation in Firefox (F7) 4. Arrow left and right within the line to move the caret Expected results: The accessible event listener would print "hello world" and the associated start and end offsets each time the caret moves. Actual results: The accessible event listener prints an empty line each time the caret moves. Sample output: Caret moved in [section | ] to offset 3 Line at offset 3: ('', 0, 0) Caret moved in [section | ] to offset 4 Line at offset 4: ('', 0, 0) Caret moved in [section | ] to offset 5 Line at offset 5: ('', 0, 0)
Reporter | ||
Comment 1•10 years ago
|
||
Comment 2•10 years ago
|
||
I can reproduce this too. Note that you can still reproduce it if you remove the div (except that obviously you'll be fetching offsets from the document accessible).
Comment 3•5 years ago
|
||
Since James can reproduce it on Windows, we can probably reflect that in the bug metadata by removing the Linux platform, and add IAccessibleText::textAtOffset in the title? (it seems I can't do it myself)
Updated•5 years ago
|
Flags: needinfo?(mzehe)
Updated•5 years ago
|
Flags: needinfo?(mzehe)
OS: Linux → All
Summary: atk_text_get_text_at_offset sometimes returns an empty line instead of the line at offset → atk_text_get_text_at_offset and IAccessibleText::textAtOffset sometimes return an empty line instead of the line at offset
Comment 4•4 years ago
|
||
This will be fixed by an upcoming patch to bug 1525631. The root cause is the same.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•