Closed
Bug 1517777
Opened 7 years ago
Closed 2 years ago
Ctrl-F does not work for content under a floating div
Categories
(Toolkit :: Find Toolbar, defect, P2)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: classicScott, Unassigned)
References
Details
Attachments
(1 file)
|
2.13 KB,
text/html
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36
Steps to reproduce:
Related Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1430187 (marked as resolved_fixed)
(working POC is included as attachment)
1) Open POC code in browser
2) Ctrl-F and search for a line obstructed by the red box.
(The lines are in alphabetical order, if you the last line that is visible to you is "ba", the next would be "bb" followed by "bc", etc)
3) Note that "Phrase not found" appears
4) Scroll until the line is in view
5) Search again - "1 of 1 match" will appear
Actual results:
If searching for a line under the red box, "phrase not found" appears
Expected results:
1 of 1 match should have appeared
Updated•7 years ago
|
Component: Untriaged → Find Toolbar
Product: Firefox → Toolkit
Comment 1•7 years ago
|
||
Cheers for the easy reproduce, I am surprised by this behaviour and have been closing bugs where I have assumed that the page was culling invisible dom nodes, I didnt think we would be doing the culling
Mike assuming this is known behaviour, is there a larger bug to dupe to for this?
Flags: needinfo?(mdeboer)
Priority: -- → P3
Comment 3•7 years ago
|
||
why status is UNCONFIRMED while there are duplicates?
Comment 4•7 years ago
|
||
I don't think there are duplicates as specific as this, so I'm going to confirm this one and keep it open.
The work we need to here, I think, is to continue to allow finding text in invisible nodes for the find string as typed in the input field and the ones collected by the matches counter.
Flags: needinfo?(mdeboer)
Updated•7 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: P3 → P2
Updated•3 years ago
|
Severity: normal → S3
Comment 5•2 years ago
|
||
Don't see this bug, so am going to close. Please reopen if this is still an issue.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•