Closed Bug 957306 Opened 11 years ago Closed 11 years ago

atk_text_get_text() should return an empty string when the start and end offsets are the same

Categories

(Core :: Disability Access APIs, defect)

x86_64
Linux
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: jdiggs, Unassigned)

References

(Blocks 2 open bugs)

Details

Attachments

(2 files)

Attached file test case: text.html
Steps to reproduce: 1. Launch the attached accessible-event listener in a terminal 2. (Re)load the attached test case Expected result: The text returned for character range (0, 0) would be an empty string. Actual result: The text returned for character range (0, 0) is the element's text.
can't confirm on xpcom level, I assume Nightly is tested?
(In reply to alexander :surkov from comment #2) > can't confirm on xpcom level, I assume Nightly is tested? 29.0a1 (2014-01-07)
Trev, would you mind to look? I don't really see how it may be so different from XPCOM part
Flags: needinfo?(trev.saunders)
(In reply to alexander :surkov from comment #4) > Trev, would you mind to look? I don't really see how it may be so different > from XPCOM part I tried, but only got one call to getTextCB with start 0 and end -1 and then before I could tell gdb to continue the document.py script printed some gerror timeout thing and no more calls to stuff in gecko happened.
Flags: needinfo?(trev.saunders)
the script doesn't use -1? Did you try to modify the script to reveal the issue?
Ok, so I figured out how to debug this, but when atk-bridge calls into gecko for the text.getText(0, 0) call gecko is passed (text, 0, -1) for some reason, so I claim this isn't our bug (I don't have symbols for libatk-bridge setup so I'm not sure why that happens)
Thanks, Trev! Cc'ing Alejandro.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: