Searched refs:previousBoundary (Results 1 – 7 of 7) sorted by relevance
44 static VisiblePosition previousBoundary(const VisiblePosition &c, unsigned (*searchFunction)(const … in previousBoundary() function201 return previousBoundary(p, startWordBoundary); in startOfWord()234 VisiblePosition prev = previousBoundary(c, previousWordPositionBoundary); in previousWordPosition()627 return previousBoundary(c, startSentenceBoundary); in startOfSentence()652 VisiblePosition prev = previousBoundary(c, previousSentencePositionBoundary); in previousSentencePosition()
427 (WebCore::previousBoundary):5817 (WebCore::previousBoundary):9252 (WebCore::previousBoundary):12578 (WebCore::previousBoundary):25422 previousBoundary.25429 (khtml::previousBoundary):28284 (khtml::previousBoundary):
16733 (khtml::previousBoundary):18050 (khtml::previousBoundary):20290 VisibleUnits previousBoundary() needed to INIT_DOWN when creating result VisiblePosition20297 (khtml::previousBoundary):24626 (khtml::previousBoundary):26835 (khtml::previousBoundary):
40806 (WebCore::previousBoundary):44470 above bug, where previousBoundary moves past the start of a 44502 (WebCore::previousBoundary):
19143 (WebCore::previousBoundary): Cleaned up by using a convenience function.34021 …(WebCore::previousBoundary): When searching for boundaries in renderers that use the textSecurity …
3040 (khtml::previousBoundary):
42200 (WebCore::previousBoundary): Changed to use Range::create.