Ctrl+F highlighting covers website header

NEW
Unassigned

Status

()

Toolkit
Find Toolbar
a year ago
a year ago

People

(Reporter: Ruben, Unassigned)

Tracking

(Blocks: 1 bug)

53 Branch
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox50 unaffected, firefox51 unaffected, firefox52 unaffected, firefox53 affected)

Details

Attachments

(1 attachment)

(Reporter)

Description

a year ago
Created attachment 8810825 [details]
FF53Nightly_FindInPage_Highlighting_Covers_Header.png

User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:53.0) Gecko/20100101 Firefox/53.0
Build ID: 20161114043454

Steps to reproduce:

1. Go to website with header that doesn't move while scrolling (CNN.com).
2. Press Ctrl+F to find text in page. Search for 'Travel' and go to the second occurrence of this word (first one is in header itself).
3. Scroll down.


Actual results:

The yellowish text highlighting moves up and covers the website header (see attachment). The same thing happens with the white text highlighting for matches not in focus. These also cover the header while scrolling.


Expected results:

The yellowish text highlighting disappears under the website header.

Comment 1

a year ago
Another issue is highlighting is broken for the keyword found in the header when you scroll, you can see artifacts remaining.
Component: Untriaged → Search
Blocks: 1291278
Component: Search → Find Toolbar
Product: Firefox → Toolkit
I see similar problem with the Mozilla Mana wiki. Unfortunately, this site is only accessible to people with mozilla.com LDAP.

STR:
1. Load https://mana.mozilla.org/wiki/display/PM
2. CTRL+F for "Program"
3. See the white word highlights
4. Slowly scroll the page

RESULT:
The white word highlights jump around and then stop scrolling even though the page text continues to scroll.
Status: UNCONFIRMED → NEW
Ever confirmed: true
status-firefox50: --- → unaffected
status-firefox51: --- → unaffected
status-firefox52: --- → unaffected
status-firefox53: --- → affected
Depends on: 1302470
You need to log in before you can comment on or make changes to this bug.