357625 - getTextAtOffset doesn't seem to work well with text with <br> in it

Status: RESOLVED FIXED

(Core :: Disability Access APIs, defect)

Description

[Willie Walker]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20061016 Minefield/3.0a1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20061016 Minefield/3.0a1

I did a search and saw a similar problem in bug 349909 https://bugzilla.mozilla.org/show_bug.cgi?id=349909.  It was marked as fixed, but I either don't have the fix in my version from Oct 16 (the ftp site is down for me to be able to get the latest nightly) or a different bug still exists.  


Reproducible: Always

Steps to Reproduce:
1. Open the attached URL as the only content in firefox (i.e., don't open any other tabs)
2. Run the attached standalone app
3. Turn on caret navigation and arrow up/down in the content (the caret is just a way to trigger the analysis code in the standalone app).



Actual Results:  
Text (len=304): 1This sentence is in Comic Sans MSl font.
2This sentence is in Courier New Font.
3This sentence is in Garamondl font.
4This sentence is in Impact font.
5This sentence is in Lucida Console font.
6This sentence is in Sydnie font.
7This sentence is in Tahoma font.
8This sentence is in Times New Roman font.
CHAR AT OFFSET 0: '1'
LINE AT OFFSET 0: (0:41) 1This sentence is in Comic Sans MSl font.
CHAR AT OFFSET 41: '
'
CHAR AT OFFSET 42: '2'
LINE AT OFFSET 42: (0:41) 1This sentence is in Comic Sans MSl font.
END OFFSET < OFFSET!!!!


Expected Results:  
The getTextAtOffset for a line at character 42 should not be for the text range (0:41).  In this case, it should start at 42.

Comment 1

[Willie Walker]

Attachment: Standalone app showing the problem

Comment 2

[Willie Walker]

Attachment: Sample content to run with standalone test app

Comment 3

[Aaron Leventhal]

The last component change looks like an error.

Comment 4

[Aaron Leventhal]

Using TEXT_BOUNDARY_LINE_START
We should be getting 0,42 for the first line, and 42, whatever for the second line. Right?

Comment 5

[Willie Walker]

Correct!  In the output, you'll see that character 42 is '2', which is the beginning of the next line. Thanks!

Comment 6

[Aaron Leventhal]

Attachment: 1) To get end of line use eSelectLine with large desiredX, 2) Modify logic for increasing start of line index, 3) Improve <br> check at end of line so extra dom nodes don't break the check

Comment 7

[Aaron Leventhal]

Attachment: 1) To get end of line use eSelectLine with large desiredX, 2) Modify logic for increasing start of line index, 3) Improve <br> check at end of line so extra dom nodes don't break the check

Comment 8

[Firefox Bug Husbandry Bot]

https://bugzilla.mozilla.org/show_bug.cgi?id=1527381