atk_text_get_text_at_offset sometimes returns an empty line instead of the line at offset

NEW
Unassigned

Status

()

Core
Disability Access APIs
4 years ago
4 years ago

People

(Reporter: Joanmarie Diggs, Unassigned)

Tracking

(Blocks: 2 bugs)

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Reporter)

Description

4 years ago
Created attachment 8471627 [details]
test case: nolineatoffset.html

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

4 years ago
Created attachment 8471628 [details]
accessible event listener: caret-moved.py

Comment 2

4 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).

Updated

4 years ago
Blocks: 368895
You need to log in before you can comment on or make changes to this bug.