After http://trac.webkit.org/changeset/165385, TextIterator::range no longer checked the nullity of m_positionNode. As a result, [WebTextIterator currentRange] which simply calls TextIterator::range crashes. Since applications that embed WebKit don't necessarily check atEnd before calling [WebTextIterator currentRange] we need to keep the null check there.
Created attachment 226776 [details] Fixes the crash
Created attachment 226777 [details] Reverted the erroneous jsc change.
Comment on attachment 226777 [details] Reverted the erroneous jsc change. Clearing flags on attachment: 226777 Committed r165664: <http://trac.webkit.org/changeset/165664>
All reviewed patches have been landed. Closing bug.
Comment on attachment 226777 [details] Reverted the erroneous jsc change. View in context: https://bugs.webkit.org/attachment.cgi?id=226777&action=review > Source/WebKit/mac/ChangeLog:12 > + Preserve the old public API behavior by checking atEnd in [WebTextIterator currentRange]. Was the old public API behavior returning nil? I think that it might have returned a range, rather than nil, before. So this might not be a sufficient fix. What about the other methods of WebTextIterator?
Comment on attachment 226777 [details] Reverted the erroneous jsc change. View in context: https://bugs.webkit.org/attachment.cgi?id=226777&action=review >> Source/WebKit/mac/ChangeLog:12 >> + Preserve the old public API behavior by checking atEnd in [WebTextIterator currentRange]. > > Was the old public API behavior returning nil? I think that it might have returned a range, rather than nil, before. So this might not be a sufficient fix. > > What about the other methods of WebTextIterator? The old TextIterator::range returned 0 when m_positionNode was null: http://trac.webkit.org/browser/trunk/Source/WebCore/editing/TextIterator.cpp?rev=165384#L1101 I don't think other methods have the same issue.