Closed
Bug 64708
Opened 24 years ago
Closed 24 years ago
"Search Backwords" in Find of Composer|Edit doesn't work with Japanese or Chinese characters.
Categories
(Core :: DOM: Editor, defect)
Core
DOM: Editor
Tracking
()
VERIFIED
FIXED
mozilla0.8
People
(Reporter: amyy, Assigned: kinmoz)
Details
(Keywords: intl, Whiteboard: moz0.8, 19-Jan)
"Search Backwords" in Find("Find in This Page" dialog) of Composer|Edit doesn't
work with Japanese or Chinese characters.
01-08-2001 Mtrunk build with all platforms.
Steps to reproduce:
1. Open [Composer].
2. Type some Japanese or Chinese words more than 2 times.
3. Go to menu [Edit]|[Find].
4. Type Japanese or Chinese characters which are exist in the Comppser Editor
page.
5. Click the "Find" button, it will search correctly by forward, and then go to
the last match word of the page.
6. Check "Search backwords", and click "Find".
Result:
You will see an Alert "The text you entered was not found" appear. If you
entered English words or letter in "Find Text" box, the Search backwords will
work fine.
Reporter | ||
Comment 1•24 years ago
|
||
Change the QA contact, assigned to nhotta, add the keywords.
Comment 2•24 years ago
|
||
Is this working on 6.0 RTM?
Reporter | ||
Comment 3•24 years ago
|
||
It works find on RTM-jp.
Comment 4•24 years ago
|
||
Reassign to the editor group, looks like it's a regression.
Assignee: nhotta → beppe
This will probably get fixed by my Find+Replace changes when I land it.
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9
Comment 7•24 years ago
|
||
putting into moz0.8, this should land by 19-Jan
Whiteboard: moz0.8, 19-Jan
Target Milestone: mozilla0.9 → mozilla0.8
This should have been fixed by the landing of the Find/Replace feature. (Bug
#6254) Please reopen and provide a test case if you can reproduce this bug.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
ylong, please verify and mark verified-fixed...thanks.
Status: RESOLVED → VERIFIED
Reporter | ||
Comment 10•24 years ago
|
||
Fixed verified in 01-24 Mtrunk build.
You need to log in
before you can comment on or make changes to this bug.
Description
•