[Webkit-unassigned] [Bug 119173] AccessibilityObject::stringForVisiblePositionRange() incorrectly repeats list marker text

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=119173





--- Comment #4 from chris fleizach <cfleizach at apple.com>  2013-07-27 16:10:47 PST ---
(In reply to comment #3)
> (In reply to comment #2)
> 
> > I think this bug has never come up so I don't think there's a good reason this is one way or the other. However, it seems suspect to assume position.next() will stay in sync with what the TextIterator is returning when advancing.
> 
> Fair enough. :) So.... Presumably I can calculate a new VisiblePosition for each TextIterator, but before I do that, can you think of a concrete example (in HTML) where the first text iterator is a replaced node/attachment so that we won't add the list marker to the StringBuilding?
> 
> Or to ask the question more plainly, why is the insertion of the list marker text being done in the for loop?
> 
> (Thanks again for your help!)

The iterator is going to go through many different potential text segments. If it detects a list marker it needs to handle that. If you take a range of the following snippet, the list marker will be in the middle of the string

<b>text</b>
<ul>
<li>item
</ul>
<b>text</b>

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.