Print renders all the <option> items in a <select> element instead of the selected one only
Categories
(Core :: Printing: Output, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr140 | --- | unaffected |
| firefox149 | + | verified |
| firefox150 | --- | verified |
| firefox151 | --- | verified |
People
(Reporter: denyshon, Assigned: emilio)
References
(Regression)
Details
(Keywords: regression)
Attachments
(4 files)
|
507 bytes,
text/html
|
Details | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-beta+
|
Details | Review |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-release+
|
Details | Review |
In Firefox version 149, a regression has been introduced with the printing of HTML <select> elements. When printing, all <option> items inside a dropdown are displayed and included in the print output in addition to the selected one.
This behavior differs from Firefox 148, where only the selected option is rendered during print preview.
Steps to reproduce:
- Create an HTML page with a <select> dropdown containing multiple <option> elements (a simple testcase attached).
- Select one of the options.
- Open print preview (Ctrl + P).
Actual results:
All options inside the <select> element are displayed and printed under the selected one.
Expected results:
Only the selected option is visible and printed.
Notes:
Reproduces in the release (v149) and the latest Nightly (v151). Does not reproduce in the previous release, v148.0.2.
Originally reported on SUMO: https://support.mozilla.org/questions/1572581
| Reporter | ||
Comment 1•2 months ago
|
||
[Tracking Requested - why for this release]:
Comment 2•2 months 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 months ago
|
||
Since nightly and release are affected, beta will likely be affected too.
For more information, please visit BugBot documentation.
Comment 4•2 months ago
|
||
I am affected by this as well and was able to bisect the regression:
Last good revision: f1c75460dbfd79bbb1bb34da66b8470993e41fd9
First bad revision: b967fdc6fff3b5ee0aa58fefd18df0f66f793b28
Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=f1c75460dbfd79bbb1bb34da66b8470993e41fd9&tochange=b967fdc6fff3b5ee0aa58fefd18df0f66f793b28
It appears this was regressed by Bug 2011709.
Comment 5•2 months ago
|
||
Set release status flags based on info from the regressing bug 2011709
:emilio, since you are the author of the regressor, bug 2011709, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
| Assignee | ||
Updated•2 months ago
|
| Assignee | ||
Comment 7•2 months ago
|
||
Clone built-in stylesheets that aren't node associated: this fixes
select.css not applying which is what fixes the bug as reported.
Clone pseudo-element type (this fixes the dropmarker not showing up in
appearance: auto mode.
Updated•2 months ago
|
| Assignee | ||
Updated•2 months ago
|
Comment 12•2 months ago
|
||
| Comment hidden (advocacy) |
Comment 15•2 months ago
|
||
Updated•1 month ago
|
Comment 18•1 month ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/4a9fdd30c2b6
https://hg.mozilla.org/mozilla-central/rev/e221b496d6d0
| Assignee | ||
Comment 21•1 month ago
|
||
Clone built-in stylesheets that aren't node associated: this fixes
select.css not applying which is what fixes the bug as reported.
Clone pseudo-element type (this fixes the dropmarker not showing up in
appearance: auto mode.
Original Revision: https://phabricator.services.mozilla.com/D289935
Updated•1 month ago
|
Comment 22•1 month ago
|
||
firefox-beta Uplift Approval Request
- User impact if declined/Reason for urgency: Multiple reports, simple fix.
- Code covered by automated testing?: yes
- Fix verified in Nightly?: yes
- Needs manual QE testing?: yes
- Steps to reproduce for manual QE testing: comment 0
- Risk associated with taking this patch: low
- Explanation of risk level: Trivial tweaks to the shadow root cloning. Note that uplift also needs this test-expectations only patch: : https://github.com/mozilla-firefox/firefox/commit/e4c240892131
- String changes made/needed?: none
- Is Android affected?: yes
| Assignee | ||
Comment 23•1 month ago
|
||
Clone built-in stylesheets that aren't node associated: this fixes
select.css not applying which is what fixes the bug as reported.
Clone pseudo-element type (this fixes the dropmarker not showing up in
appearance: auto mode.
Original Revision: https://phabricator.services.mozilla.com/D289935
Updated•1 month ago
|
Comment 24•1 month ago
|
||
firefox-release Uplift Approval Request
- User impact if declined/Reason for urgency: Multiple reports, simple fix.
- Code covered by automated testing?: yes
- Fix verified in Nightly?: yes
- Needs manual QE testing?: yes
- Steps to reproduce for manual QE testing: comment 0
- Risk associated with taking this patch: low
- Explanation of risk level: Trivial tweaks to the shadow root cloning. Note that uplift also needs this test-expectations only patch: : https://github.com/mozilla-firefox/firefox/commit/e4c240892131
- String changes made/needed?: none
- Is Android affected?: yes
Updated•1 month ago
|
Comment 27•1 month ago
|
||
| uplift | ||
Updated•1 month ago
|
Updated•1 month ago
|
Updated•1 month ago
|
Reproducible on a 2026-03-25 Firefox Nightly build on Windows 10.
Verified as fixed on Firefox Nightly 151.0a1 and Firefox 150.0b3 on Windows 10, Ubuntu 22, macOS 15.
Updated•1 month ago
|
Updated•1 month ago
|
Comment 34•1 month ago
|
||
| uplift | ||
Comment 35•1 month ago
|
||
| uplift | ||
Verified as fixed on Firefox 149.0.2 (treeherder build) on Windows 10, Ubuntu 22, macOS 13.
Description
•