Home
last modified time | relevance | path

Searched refs:getRangeAt (Results 1 – 13 of 13) sorted by relevance

/external/webkit/WebCore/inspector/front-end/
DTextPrompt.js148 var selectionRange = selection.getRangeAt(0);
162 var selectionRange = selection.getRangeAt(0);
239 var selectionRange = selection.getRangeAt(0);
DSourceFrame.js319 var expression = selection.getRangeAt(0).toString().trimWhitespace();
Dutilities.js284 var selectionRange = selection.getRangeAt(0);
DStylesSidebarPane.js1084 var selectionRange = selection.getRangeAt(0);
/external/webkit/WebCore/page/
DDOMSelection.h81 PassRefPtr<Range> getRangeAt(int, ExceptionCode&);
DDOMSelection.idl56 Range getRangeAt(in long index)
DDOMSelection.cpp333 PassRefPtr<Range> DOMSelection::getRangeAt(int index, ExceptionCode& ec) in getRangeAt() function in WebCore::DOMSelection
/external/webkit/WebCore/
DChangeLog-2006-05-1031613 (khtml::SelectionController::getRangeAt):
34318 (khtml::SelectionController::getRangeAt):
37107 Mozilla's Selection object API, added getRangeAt and outlined the
37114 * editing/selection/getRangeAt.html
37131 (khtml::SelectionController::getRangeAt):
DChangeLog-2007-10-1420648 (WebCore::DOMSelection::getRangeAt):
37879 getRangeAt() and collapse() which are part of the spec (FF throws NS_ERROR_FAILURE).
37881 Not throwing exceptions yet for too high offsets (except getRangeAt()) as it is
DChangeLog-2009-06-1640505 (WebCore::DOMSelection::getRangeAt):
41277 DOMSelection.getRangeAt() returns a different range than the selection
41282 Test: fast/dom/Selection/getRangeAt.html
41328 (WebCore::DOMSelection::getRangeAt):
DChangeLog478 (WebCore::DOMSelection::getRangeAt): Return a range that starts
DChangeLog-2008-08-1011886 (WebCore::DOMSelection::getRangeAt):
73878 (WebCore::DOMSelection::getRangeAt):
/external/webkit/WebKit/mac/
DChangeLog5763 DOMSelection.getRangeAt() returns a different range than the selection