409621 - BR element forces trailing embedded object characters to become out of sync with their children, using IAccessibleText::HyperlinkIndex

Status: RESOLVED INVALID

(Core :: Disability Access APIs, defect)

Description

[Michael Curran]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9b3pre) Gecko/2007122205 Minefield/3.0b3pre

If a parent element contains elements such that there is a BR element situated before element N, doing IAccessibleHypertext::Hyperlink(IAccessibleHypertext::HyperlinkIndex(x)) where x is the offset in the parent element where element N+[1|2|...]'s embedded object character should be, the call returns a link to the element before the one it is supposed to return.
 In other words, When recursivly visiting objects with IAccessibleHypertext, and there is a preceeding BR element at the same level as the embeded objects, either an object is visited twice, or the very last one is skipped.

 

Reproducible: Always

Steps to Reproduce:
1. Load attachment test_ff3_embedded-objects-after-br-element.html in to Firefox3 latest trunk
2. Locate the IA2 object representing the DIV element.
3. queryInterface to IAccessibleHypertext
4. call IAccessibleHypertext::Text(0,-1),  containing a linebreak at offset 0, and then embeeded object chars after that.
5. call IAccessibleHypertext.Hyperlink(IAccessibleHypertext.HyperlinkIndex(1)) and then IAccessibleHypertext.Hyperlink(IAccessibleHypertext.HyperlinkIndex(2))

Actual Results:  
The two objects returned are identical

Expected Results:  
The two objects should be different

www.google.com also shows this bug: recursivly using IAccessibleHypertext will visit the google search button twice, rather than the google search button and then the I'm feeling lucky button. Also the graphic is visited twice.

Comment 1

[Michael Curran]

Attachment: an html file which when loaded in Firefox3, causes embedded objects in the div element to be out of sync due to the BR element at the start.

Comment 2

[Michael Curran]

I am sorry, this bug can be removed, the bug was in deed in the NVDA screen reader, the text was getting mutated as it came out of IAccessibleText::Text, therefore making the embedded object chars out of sync with what Gecko thought were link offsets.