<details> elements remain interactive in print preview
Categories
(Core :: Print Preview, defect, P3)
Tracking
()
People
(Reporter: kimberly.grey, Assigned: grover7677)
Details
(Keywords: good-first-bug)
Attachments
(3 files)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:109.0) Gecko/20100101 Firefox/111.0
Steps to reproduce:
- Open the attached file in Firefox.
- Open the print preview dialog.
3a. In the preview of the page, click on the <summary> text "I am open by default".
3b. In the preview of the page, click on the <summary> text "I am closed by default".
Actual results:
In both cases: All content of the clicked <details> element, including the <summary>, becomes invisible. The content below it does not change position.
3a: Upon printing, the <details> element is closed, with only the <summary> text visible. Content below it has moved upwards to fill the space left by the closed <details> element.
3b: Upon printing, the <details> element is open, with the <summary> text and all child content visible. Content below it has moved downwards to accommodate it.
Expected results:
It is unexpected that <details> elements remain interactive in the print preview window.
If this is an undocumented 'feature', then it is unexpected that the print preview does not reflect the document that is finally printed.
| Reporter | ||
Comment 1•2 years ago
|
||
As a clarification:
Only the first clicked <details> turns invisible, however all clicks appear to be registered and reflected in the printed document.
Comment 2•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Printing: Output' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 3•2 years ago
|
||
Uhh, yeah, this is rather unexpected indeed. I wonder if it's a regression. We have this code to nerf the cursor, and it seems this is what causes buttons etc to not be interactive. We probably need something similar for <details>, maybe even just move that -moz-user-input: none to where the cursor declaration is.
Probably we also want to drop a pointer-events: none there for good measure.
| Assignee | ||
Comment 4•2 years ago
|
||
Updated•2 years ago
|
Updated•2 years ago
|
Comment 6•2 years ago
|
||
Comment 8•2 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/5efd007fd272
https://hg.mozilla.org/mozilla-central/rev/5f266371028f
Updated•2 years ago
|
Reproducible on a 2023-06-17 Nightly build on Windows 10.
Verified as fixed on Firefox 116.0b4(build ID: 20230711183052) and Nightly 117.0a1(build ID: 20230713091748) on Windows 10, macOS 12, Ubuntu 22.
Description
•