Changeset 1558
- Timestamp:
- 2008-02-19 09:14:52 (5 months ago)
- Location:
- FCKeditor/trunk
- Files:
-
- 2 modified
-
editor/dialog/fck_replace.html (modified) (2 diffs)
-
_whatsnew.html (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
-
FCKeditor/trunk/editor/dialog/fck_replace.html
r1541 r1558 55 55 // This will be the starting point of our search. 56 56 var GlobalRange = new oEditor.FCKDomRange( oEditor.FCK.EditorWindow ) ; 57 GlobalRange.SetStart( oEditor.FCK.EditorDocument.body, 1 ) ; 58 GlobalRange.SetEnd( oEditor.FCK.EditorDocument.body, 1 ) ; 59 GlobalRange.Collapse( true ) ; 57 58 function ResetGlobalRange() 59 { 60 GlobalRange.SetStart( oEditor.FCK.EditorDocument.body, 1 ) ; 61 GlobalRange.SetEnd( oEditor.FCK.EditorDocument.body, 1 ) ; 62 GlobalRange.Collapse( true ) ; 63 } 64 ResetGlobalRange() ; 60 65 61 66 var HighlightRange = null ; … … 389 394 } 390 395 391 return true ;396 return true ; 392 397 } 393 398 else 394 return false; 399 { 400 ResetGlobalRange() ; 401 return false ; 402 } 395 403 } 396 404 -
FCKeditor/trunk/_whatsnew.html
r1541 r1558 100 100 will no longer display wrong starting positions for the match when there are multiple and identical 101 101 characters preceding the character at the real starting point of the match.</li> 102 <li>[<a target="_blank" href="http://dev.fckeditor.net/ticket/1878">#1878</a>] Fixed a JavaScript error 103 which occurs in the Find/Replace dialog when the user presses "Find" or "Replace" after the "No 104 match found" message has appeared.</li> 102 105 </ul> 103 106 <p>