[Webkit-unassigned] [Bug 65277] Provide flexible (in terms of position relative to space) logical word breaker to improve performance of --webkit-visual-word

[bugzilla-daemon at webkit.org]

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





--- Comment #30 from Van Lam <vanlam at google.com>  2011-08-15 16:38:16 PST ---
(In reply to comment #29)
> (From update of attachment 103969 [details])
> View in context: https://bugs.webkit.org/attachment.cgi?id=103969&action=review
> 
> > Source/WebCore/ChangeLog:21
> > +        (WebCore::previousWordPositionBoundaryLogicallyBeforeWord):
> > +        (WebCore::previousWordPositionBoundaryLogicallyAfterWord):
> > +        (WebCore::nextWordPositionBoundaryLogicallyBeforeWord):
> > +        (WebCore::nextWordPositionBoundaryLogicallyAfterWord):
> > +        (WebCore::leftWordPositionAcrossBoundary):
> > +        (WebCore::rightWordPositionAcrossBoundary):
> 
> I cannot really figure out from these function names what they are doing. Does "logically" have something to do with RTL languages? What is a "position across boundary"?

I'm aiming to specify where word breaks should be. So "logically after word" means those boundaries that follow words:

In LTR text: abc| def|
RTL: |FED |CBA

The usage of these functions is that one is passed into nextBoundary/previousBoundary to specify where the word break should be; it would mean the difference between:

(calling nextBoundary)
|abc def -> abc| def   and   |abc def -> abc |def

Currently when calling nextBoundary, there is only one clear function to pass in at the word-movement level and that will always return the word break logically after the word; same goes for previousBoundary except it returns the word break logically before the word.

An alternative is to specify visually (previousWordPositionBoundaryOnLeftOfWord, etc.).

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