Find in page not working properly with specific search terms on Wikipedia pages
Reported by
molecule...@gmail.com,
Apr 10 2018
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36 Steps to reproduce the problem: 1. Open a random Wikipedia page, say https://en.wikipedia.org/wiki/Lesser_Antillean_macaw 2. Press Cmd+F (or Edit->Find -> Find), and input "jump" (or "ju", "jum") in the find box. 3. It shows something like "1 of 20" results (which is not correct, since there is no "jump" in the page). And it cannot locate (jump to) the text if the page actually contains the text. What is the expected behavior? It should either find nothing or should be able to locate the text we input. What went wrong? The Find box is unable to jump to the text. And the find result is not correct. This only happens on Wikipedia pages as I tested. Did this work before? N/A Chrome version: 65.0.3325.181 Channel: stable OS Version: OS X 10.13.4 Flash Version: Shockwave Flash 29.0 r0 I think "jump" is a "magic word" to Chrome and Wikipedia
,
Apr 10 2018
,
Apr 10 2018
,
Apr 10 2018
This also happens to Firefox and Safari. The number of the find result coincides with the number citation references in the end of the Wikipedia page. It seems some kind of hidden text is within some span tags in the page (not in page source, maybe loaded later). In Firefox, we can "View Selection Source" of the Find result, it shows a page view-source:data:text/html;charset=utf-8,%3Cspan%20class%3D%22cite-accessibility-label%22%3E%EF%B7%90Jump%EF%B7%AF%20up%20to%3A%20%3C%2Fspan%3E with the following content: """ <span class="cite-accessibility-label">Jump up to: </span> """ I know it's a Firefox feature and screenshot, but I just want to provide more clues since this seems to affect both of them.
,
Apr 11 2018
Able to reproduce the issue on reported chrome version 65.0.3325.181 and on the latest version 67.0.3394.0 using Windows 10, Ubuntu 14.04 and Mac 10.12.6. As the issue is seen from M60(60.0.3112.0) considering it as Non-Regression and marking it as Untriaged. Thanks!
,
Nov 22
***Mass UI Triage*** We are able to reproduce this bug on latest canary #72.0.3618.0 and its a Non-Regression issue From M60.Hence adding respective labels for further triage. Thanks! |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by molecule...@gmail.com
, Apr 10 2018495 KB
495 KB View Download