573714 - Wrong object returned from IA2_EVENT_TEXT_CARET_MOVED when navigating with keyboard into another paragraph, table, heading etc.

Status: RESOLVED INCOMPLETE

(Core :: Disability Access APIs, defect)

Description

[RaZiel]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3 (.NET CLR 3.5.30729)

Wrong object returned from IA2_EVENT_TEXT_CARET_MOVED when navigating with keyboard into another paragraph, table, heading etc. ROLE_SYSTEM_DOCUMENT is returned instead. 

When navigating the caret with the mouse, the correct object is returned. Actually two IA2_EVENT_TEXT_CARET_MOVED events are triggered if you move the caret from one paragraph to another, with the mouse.
On button press ROLE_SYSTEM_DOCUMENT is returned.
On button release paragraph is returned.
However, if you navigate the caret with the mouse within the same paragraph, one event is triggered, and the paragraph is returned on left mouse button press. 

I understand the problematic behavior that makes the difference between the mouse and keyboard. Since keyboard input may change the caret position while keeping keys pressed down. While only the selection can change while keeping a mouse button down.

But this most likely prove the need for a method which can return the object containing the caret as a part of the standard for IAccessible2. This would also help in the situation where using the focused object and recursively find the child object containing the caret.

Reproducible: Always

Steps to Reproduce:
1.Place the caret inside a paragraph.
2.Move the caret to another paragraph, using the keyboard.
Actual Results:  
The returned object is ROLE_SYSTEM_DOCUMENT, with no valid caret offset. Even if the caret has been moved to a new paragraph containing the caret.

Expected Results:  
Expected to get the paragraph containing the caret after the caret has been moved with the keyboard.

Comment 1

[David Bolter [:davidb] (NeedInfo me for attention)]

AUTO-CLOSED. This bug untouched for over 2000 days. Please reopen if you can confirm the bug and help it progress.