New issue
Advanced search Search tips

Issue 859907 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 847236
Owner:
Closed: Jul 16
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Chrome find in PDF results no longer show up as highlights in the scrollbar

Reported by lovseb.s...@gmail.com, Jul 3

Issue description

UserAgent: Mozilla/5.0 (X11; CrOS x86_64 10718.34.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.40 Safari/537.36
Platform: 10718.34.0 (Official Build) beta-channel edgar

Steps to reproduce the problem:
1. Open a PDF document
2. Use Ctrl + F to search the document
3. Look to the scrollbar on the right hand side of the screen

What is the expected behavior?
The found matches show up as yellow bars in the scrollbar indicating their position within the document. Please see attachment for expected behavior.

What went wrong?
Since somewhere around version 48 or 50 (can't really remember) the scrollbar indications disappeared. 

Did this work before? Yes I know the feature was gone by version 50

Chrome version: 68.0.3440.40  Channel: beta
OS Version: 10718.34.0
Flash Version: 

I have waited to file a bug report since I saw that there were some other reports relating to the PDF plugin. Looking through the bug-list today I couldn't find any similar bug-reports open so I decided to file my own.
 
chrome_pdf_search.jpg
127 KB View Download
Components: Internals>Plugins>PDF
Owner: dsinclair@chromium.org
Status: Untriaged (was: Unconfirmed)
I have confirmed that the highlights are no longer occurring. I am unsure if this is an intentional change or regression.

dsinclair@, do you know if this was an intentional change or the proper person to route this to?
Owner: thestig@chromium.org
Status: Assigned (was: Untriaged)
This is a regression. thestig@ was looking at the find code a little while ago, maybe the best person to start with.
Mergedinto: 847236
Status: Duplicate (was: Assigned)
Thanks for trying to find an existing bug report. There indeed is one. This should be fixed in version 69.

Sign in to add a comment