Find in page treats V and W as the same character when display language is set to Finnish
Reported by
the...@gmail.com,
Oct 3
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36 Steps to reproduce the problem: 1. Set Chrome display language as Finnish 2. Open any page containing letters V and W (for example, this page) 3. Open page search (ctrl+f or top right menu) 4. Type in the letter V or W (or similar words containing those letters in same positions, like "wow" and "vow") What is the expected behavior? The search should distinguish V and W as different characters. If V is typed, only letters V should be highlighted, same with W. If "wow" is searched, "wow" should be highlighted, but "vow" should not be. What went wrong? For some reason when display language is set to Finnish, the search treats V and W as the same characters, so searching for V or W highlights all occurrences of both letters, and for example, searching "wow" highlights both "wow" and "vow" (or any other word where V/W appears in the same spot) Did this work before? No Chrome version: 69.0.3497.100 Channel: stable OS Version: 6.3 Flash Version: This is duplicate of issue 756520 which has since been left untriaged and gotten archived. Resubmitting because I cannot reopen said issue.
,
Oct 5
Able to reproduce the issue on chrome reported version# 69.0.3497.100 using Windows-10, Mac 10.12.6 and Ubuntu 14.04 with steps mentioned in comment# 0. As this issue is seen from M-60, hence considering this issue as Non-Regression and marking it as Untriaged. Note: Tentatively adding UI>Browser>FindInPage component to it. Thanks!
,
Oct 5
++ Able to reproduce the issue on chrome reported version# 69.0.3497.100 and on latest chrome# 71.0.3570.0.
,
Oct 11
,
Oct 11
,
Oct 11
,
Oct 12
@robliao: As per comment# 2, able to reproduce the issue on chrome reported version# 69.0.3497.100 and latest chrome# 71.0.3570.0. As part of regular practice we consider issue as Non-Regression if the issue is seen from M-60 builds. But as per Needs-Bisect label added in comment# 6, tested the issue on M-45 build(45.0.2454.101) using Windows-10, able to reproduce the issue there also. Hence removing the Needs-Bisect label to it. Note: Feel free to add Needs-Bisect label back if required. Thanks!
,
Oct 18
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by swarnasree.mukkala@chromium.org
, Oct 3