Finding/Searching in page does not differentiate between v and w (double-u) (or diacritics)
Reported by
chessax....@gmail.com,
Apr 11 2018
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36 Steps to reproduce the problem: Search (Ctrl+F, Cmd-F) for V and W (double-u) on this page, e.g. "water" and "vater". What is the expected behavior? "water" does not match "vater" "vater" does not match "water" What went wrong? "water" does match "vater" "vater" does match "water" Did this work before? No Chrome version: 65.0.3325.181 Channel: stable OS Version: OS X 10.9.5 Flash Version: Additionally a lot of diacritics seems to be treated identically even when searching for an explicit diacritic letter, e.g. searching for "á" (acute accent), "à" (grave accent), "ã" (tilde), "ā" (macron) and "ǎ" (caron) etc. all matches "a". "å" (overring) and "ä" (diaeresis/umlaut) are the only ones commonly distinguished (but might simply be because of my Swedish localization). If ease of searching is desired hence why diacritics are ignored when searching for "a" then I guess that is fine. However, when searching explicitly for letters with diacritics it should explicitly only match the letter with diacritic. An acceptable compromise would be to also match the base letter "a" when searching using diacritics, in case someone is being too lazy/unable to write using diacritics. There may similarly be other "optimizations" made which may be questionable, however the only one I can think of right now is "æ" matching "ä". As mentioned I assume all of these decisions were made to ease searching, but I find myself more often than not hindered by them and not helped, often resorting to either inspecting the webpage and searching or copy/pasting to (or opening in) a third party program with a more "unambiguous" search feature.
,
Apr 11 2018
Checked the issue on reported chrome version 65.0.3325.181 and on the latest canary 67.0.3394.0 using Mac 10.13.1 and Mac 10.12.6 With the below mentioned steps. 1. Launched chrome 2. Navigated to Issue 831455 3. Cmd-F and searched for Water and vater. We didn't observe any mismatch of words while searching those words. Attaching the screenshots of the same. Note: However searching for any diacritics has a different behaviour i.e., when searched for à á ... results in highlighting of 'a' too. @Reporter: Could you please have a look at the screen shots provided and let us know if we have missed anything in the process. Any further inputs from your end may help us.
,
Apr 11 2018
The steps you have taken are correct, see image attachment for different results. I did another quick test changing the language and the issue appears to be a localization issue, see text attachment for comparison. The "v"/"w" problem only appears under Swedish and Finnish (and maybe others?). But there still appears to be other inconsistencies among different languages. Regarding localization there's little sense in treating "v" and "w" the same in Swedish. While Swedish now technically does have both v and w in the alphabet, w is rarely used for any Swedish word, however due to proper nouns and many loanwords being introduced into the language (mostly from English) means that there's still a difference. Anyway, searching does not always mean searching for swedish text, the majority of the Internet is not written in Swedish, hence having strict rules for searching in Swedish may often be detrimental to the user's experience, and since the only way to change the behavior seems to be to change system language (at leas on a Mac) makes it more than just a mere inconvenience. Other similar examples include: ß = ss ü = y/ue ä = æ/ae Letters that are not phonetically different in Swedish include: c = k or s q = k w = v x = ks z = s However treating these as identical when searching would still be misleading in most cases and it's not even limited to Swedish in several cases. The only letter with pretty much no use in swedish is "q", however it is still used due to proper nouns and various loanwords being introduced recently. I'm sorry for being a bit lengthy and going a bit off topic, I'm just trying to build a strong case of that there's something inherently wrong about how Chrome tries to be "smart" about searching yet ending up being dumb. I also remembered there being another bug report with the same issue(s) but my first search failed, however trying again I managed to find this archived issue: Issue 166456 , it suggests it not being OS specific, but strengthens the argument for localization specificity.
,
Apr 11 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 11 2018
,
Apr 16 2018
,
Sep 20
,
Nov 21
***Mass UI Triage*** As per comment #3 |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by krajshree@chromium.org
, Apr 11 2018