[Webkit-unassigned] [Bug 65277] Make functions to find word boundaries more flexible

[bugzilla-daemon at webkit.org]

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





--- Comment #54 from Van Lam <vanlam at google.com>  2011-08-27 03:17:10 PST ---
(In reply to comment #52)
> Also, <p>te|st</p><p>test</p> (two words separated by a paragraph break).

In this case nextWordBoundaryBeforeWord returns VisiblePosition(). Because the two "test" strings are in different blocks (I think this is the correct term) the behavior of the function will work like:

call nextBoundary: <p>te|st</p><p>test</p> -> <p>test|</p><p>test</p>
call nextBoundary: <p>test|</p><p>test</p> -> <p>test|</p><p>test</p> (same position returned)

At this point the code returns VisiblePosition() and the correct word break (at the end of the first line) is computed in another part of visual word movement code.

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