Find in Response doesn't handle Unicode characters correctly
Reported by
teo8...@gmail.com,
Jul 6
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36 Steps to reproduce the problem: Steps to reproduce the problem: 1. Open the Developer Tools, open the Network tab 2. Visit http://output.jsbin.com/cijeqom/1 3. In the network tab, select the first request and give focus to the "Response" tab. 4. Hit Ctrl+F and look for "ultimo" What is the expected behavior? Should find the word "último" which appears in the response, just like when you do Ctrl+F in the rendered page and it does find it What went wrong? Doesn't find any match, because apparently it doesn't consider "ú" and "u" as the same character. Did this work before? N/A Chrome version: 67.0.3396.99 Channel: stable OS Version: Flash Version:
,
Jul 9
Able to reproduce the issue on Mac 10.13.3, Win-10 and Ubuntu 17.10 using chrome reported version #67.0.3396.99 and latest canary #67.0.3368.0. This is a non-regression issue as it is observed from M60 old builds. Hence, marking it as untriaged to get more inputs from dev team. Thanks...!!
,
Jul 9
This would be cool. Not sure if we can do it performantly, however.
,
Jul 9
> This would be cool. Not sure if we can do it performantly, however. You already do it on the rendered content. If that does not pose performance challenges, why should it when searching the response source?? > Status: WontFix You are joking, right? Even if your concerns about performance made sense, you just mark it WontFix because you are "not sure"? |
|||
►
Sign in to add a comment |
|||
Comment 1 by susan.boorgula@chromium.org
, Jul 9