Closed Bug 251891 Opened 20 years ago Closed 20 years ago

Since Find toolbar was implemented, Find as you type ( FAYT ) doesn't work with int'l charachters

Categories

(Toolkit :: Find Toolbar, defect, P2)

defect

Tracking

()

RESOLVED DUPLICATE of bug 259454

People

(Reporter: legenda, Assigned: bugzilla)

References

Details

(Keywords: intl, qawanted, regression, Whiteboard: ETA is 10/15)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040716 Firefox/0.9.1+ Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040716 Firefox/0.9.1+ I cannot use int'l characters (for example the scandic ä, ö and å) while searching with Find as you type or the Find toolbar. When I press any of the keys, nothing happens, the find engine doesn't accept the input. I've been able to reproduce this since the new Find toolbar was introduced. Reproducible: Always Steps to Reproduce: 1. Go to any webpage. 2. Start typing a keyword (if using FAYT) or open up the find toolbar. 3. Try to enter non-ASCII characters (like ä, ö and å) Actual Results: The non-ASCII characters are not accepted as input. Expected Results: All typed characters should be accepted to the keyword. Fishbert on the Mozillazine Forums was able to enter a keyword in Japanese using IME. Gorgias could reproduce this bug. (http://forums.mozillazine.org/viewtopic.php?t=96481&start=90)
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040716 Firefox/0.9.1+ Worksforme. if I type "+a the ä is highlighted
Confirming bug with: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040716 Firefox/0.9.1+ I use swedish keyboard and וצה doesnt work, when I use FAYT. There is bug 202251, but this worked before the new find toolbar was implemented. So I dont think this is a dupe of that one.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Find as you type / Find toolbar doesn't work with int'l characters → Since Find toolbar was implemented, FAYT doesn't work with int'l charachters
Keywords: regression
I tried typing ¨+a and "+a as Peter instructed, but I still can't get it to work - clean profile or not. And even if it did, IMO it _must_ work with the real characters and not substitutes.
See also bug 250751, "Find Toolbar: When IME is turned ON, starting to type no longer activates find-as-you-type". This might be a dup.
Flags: blocking-aviary1.0?
*** Bug 250751 has been marked as a duplicate of this bug. ***
It reproduces also by Mac OS X.
OS: Windows XP → All
Hardware: PC → All
Flags: blocking-aviary1.0RC1?
*** Bug 251996 has been marked as a duplicate of this bug. ***
WFM on this page (tested ä, ö and å). Default input language: English (United States) - Belgian french (from Win XP's "Regional and Language Options" dialog). Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040717 Firefox/0.9.1+/zip
I tried changing my locale to English (United States), and Finnish as the keyboard input layout. No change. And still - it _must_ work with _all_ input locales.
Flags: blocking-aviary1.0RC1?
Flags: blocking-aviary1.0RC1+
Flags: blocking-aviary1.0?
Flags: blocking-aviary1.0+
Priority: -- → P2
*** Bug 252744 has been marked as a duplicate of this bug. ***
Keywords: intl
Legenda, can you type scandic letters after opening toolbar with Ctrl+F, not "/"? I've found very similar behaviour (bug 252744) and I wonder if it is really a dupe.
(In reply to comment #13) > Legenda, can you type scandic letters after opening toolbar with Ctrl+F, not > "/"? I've found very similar behaviour (bug 252744) and I wonder if it is really > a dupe. by using Accel+F finding intl chars works (but not by using "/" "'").
Ivan, after opening search with Ctrl+F I can enter scandic characters. However, I don't know if the engine actually searches for strings including those characters. For example, in this page you can find scandic characters (ä, ö, å) but trying to search them returns the 'not found' sound effect, and no string is hilighted.
(In reply to comment #15) > Ivan, after opening search with Ctrl+F I can enter scandic characters. However, > I don't know if the engine actually searches for strings including those characters. > > For example, in this page you can find scandic characters (ä, ö, å) but trying > to search them returns the 'not found' sound effect, and no string is hilighted. At least for Hebrew - Accel+F works fine.
Fayt finds å if if I press ctrl+f first, but pressing æ ø or å (Danish/scandic keyboard lay-out) does not trigger fayt. Nor do the letters work, if fayt is triggered by pressing another letter.
*** Bug 253372 has been marked as a duplicate of this bug. ***
Summary: Since Find toolbar was implemented, FAYT doesn't work with int'l charachters → Since Find toolbar was implemented, Find as you type ( FAYT ) doesn't work with int'l charachters
I just checked in an attempted fix for this. Could someone update their branch build and try it out?
marking keywork fixed-aviary1.0 to get on the testing radar.
Keywords: fixed-aviary1.0
I'm not sure if it was this checkin, but it seems likely. FYAT seems to have regressed pretty severely, if I press non-character keys such as Page Down, Home, etc., FYAT tries to find the character code associated with that key on the page. I think it's fairly obvious that most of the time I am not trying to find the character associated with "page down" when I hit that key :).
Keywords: qawanted
(In reply to comment #19) > I just checked in an attempted fix for this. Could someone update their branch > build and try it out? FAYT in Japanese was not made like before. And also by English FAYT, why a help is displayed and it is interfered with FAYT.:-( Mac OS X 10.3.4 Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; ja-JP; rv:1.7) Gecko/20040731 Firefox/0.9.1+
this bug 253793 may be one of the regressions
FWIW, searching with å, ä and ö works again after this fix, but comment#21 is right about the regression for other keys.
Filed bug 253876 for comment 21 (arrow keys, etc trigger find bar)
*** Bug 252744 has been marked as a duplicate of this bug. ***
Flags: blocking-aviary1.0PR+
Testing with: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040802 Firefox/0.9.1+ Both bugs are fixed (this bug and bug 253876)
bug reproduced while typing chinese characters Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.7.2) Gecko/20040825 Firefox/0.9.1+
Not sure if it's related, but using "/" and "'" mode doesn't able to input Traditional Chinese with 2 famous IME by default, you've to input them by clicking the input box first(putting the caret inside the box?). Whereas it works well with Ctrl + F. I doubt it's related to the lack of caret in "/" and "'" mode, see bug 253988. Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7.3) Gecko/20040910 Firefox/0.10
Good to see it's blocking aviary 1.0 since this bug is really annoying + makes browsing for non-english users kinda not convenient
(In reply to comment #30) > Good to see it's blocking aviary 1.0 since this bug is really annoying + makes > browsing for non-english users kinda not convenient It was fixed a long time ago, is it broken for some language?
(In reply to comment #31) > It was fixed a long time ago, is it broken for some language? for traditional chinese, ctrl+f works fine, but FAYT doesn't work at all.
OK, removing fixed-aviary1.0 keyword.
Keywords: fixed-aviary1.0
*** Bug 262585 has been marked as a duplicate of this bug. ***
I use Japanese IME (skkinput) on Linux. Although I can search text with Accel+F, I can't activate a link with searched anchor text by typing Enter. By FAYT started with "/" or "'" (in English) or in earlier version of Firefox (without find toolbar), searching an anchor text and typing Enter activate the link.
*** Bug 260433 has been marked as a duplicate of this bug. ***
Whiteboard: ETA is 10/17
Whiteboard: ETA is 10/17 → ETA is 10/15
*** This bug has been marked as a duplicate of 259454 ***
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Flags: blocking-aviary1.0+
In Firefox 1.0 (in Linux) I can now search for any special character (e.g. å, ä, ö, à, é, ĉ, ŭ) if I start the search with CTRL-F. But if I start with "/", I can't type any of those special characters that I get with "dead key + something" (in my case eg. à, é, ĉ, ŭ - typed with diacritic dead key + a/e/c/u on my keyboard). So it seems that this bug is still alive. :(
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.