RESOLVED FIXED 138567
Some functions on DictionaryLookup.h should just be generic functions on Range or VisiblePosition
https://bugs.webkit.org/show_bug.cgi?id=138567
Summary Some functions on DictionaryLookup.h should just be generic functions on Rang...
Beth Dakin
Reported 2014-11-10 11:12:28 PST
Some functions on DictionaryLookup.h should just be generic functions on Range or VisiblePosition, specifically isPositionInRange() and shouldUseSelection()
Attachments
Patch (6.64 KB, patch)
2015-08-17 14:47 PDT, Tim Horton
no flags
Beth Dakin
Comment 1 2014-11-10 11:14:17 PST
And rangeExpandedAroundPositionByCharacters()! Which is code originally stolen from Editor, according to Tim.
Tim Horton
Comment 2 2015-08-17 14:47:30 PDT
Tim Horton
Comment 3 2015-08-17 19:03:16 PDT
Said Abou-Hallawa
Comment 4 2015-08-18 09:03:47 PDT
Comment on attachment 259191 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=259191&action=review > Source/WebCore/dom/Range.cpp:1963 > +bool Range::contains(const VisiblePosition& position) const Can't we be more generic here and have the prototype of this function: bool Range::contains(const VisiblePosition &start, const VisiblePosition &end)? > Source/WebCore/editing/mac/DictionaryLookup.mm:61 > + return selectedRange->contains(position); To check whether a VisiblePosition is in a range of VisibleSelection, is not it sufficient to call Range::isPointInRange()? What is the difference if VisiblePosition is at the boundary of the range of VisibleSelection when: 1. calling Range::isPointInRange() 2. calling the deleted function isPositionInRange() 3. calling Range::contains()
Note You need to log in before you can comment on or make changes to this bug.