New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 724001 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Sep 13
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Search results highlighting should consider text background

Reported by mr.ber...@gmail.com, May 18 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36

Steps to reproduce the problem:
1. Open bug.html
2. F3, Type Chr1me
3. Locate hit (yes, there is one!)

What is the expected behavior?
You see it.

What went wrong?
You don't.

Did this work before? N/A 

Chrome version: 58.0.3029.110  Channel: stable
OS Version: 10.0
Flash Version: 

The attached file covers a couple of examples, of which the steps above only describe only one. Here's the rest:

In Chrome:
- Chr1me (single hit) is not highlighted (Bug); for Chr2me (two hits), you only see the other hit, not the current one (Bug)
- B1th (single hit) is highlighted (good); for B2th (two hits), you see the current hit, but not the other one (Bug)

How does IE 11 do?
- M1crosoft (single hit) is highlighted because background is turned white (better than Chrome); for M2crosoft (two hits), you see both hits (better than Chrome)
- B1th (single hit) is highlighted (good, same as Chrome); for B2th (two hits), you see the current hit, but not the other one (Bug, same as Chrome)
 
bug.html
505 bytes View Download

Comment 1 by mr.ber...@gmail.com, May 18 2017

Real-life example: Try to find the "joint session program chair" on http://2016.nss-mic.org/committee.php
Labels: Needs-Triage-M58
Cc: sureshkumari@chromium.org
Labels: M-60 OS-Linux OS-Mac
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on Windows-7,Windows-10,Mac-10.12.4 and Linux Ubuntu-14.04 using chrome stable version 58.0.3029.110 and canary 60.0.3104.0 with the steps mentioned in comment#0.
This is non-regression issue, observed from M30 #30.0.1550.0 and marking it as Untriaged to get more inputs from dev team.

Thanks.
Components: -UI UI>Browser>FindInPage
Status: Archived (was: Untriaged)
Archiving old bugs that haven't been actively assigned in over 180 days.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!

Sign in to add a comment