The None margin option cannot be selected if failing to validate an invalid field by adjusting a value inside another field
Categories
(Toolkit :: Printing, defect, P2)
Tracking
()
People
(Reporter: asoncutean, Assigned: emmamalysz)
References
(Blocks 1 open bug)
Details
(Whiteboard: [print2020_v83] [old-ui-])
Attachments
(2 files)
501.55 KB,
image/gif
|
Details | |
47 bytes,
text/x-phabricator-request
|
pascalc
:
approval-mozilla-beta+
|
Details | Review |
Affected versions
- 83.0a1 (2020-10-08)
Affected platforms
- Windows 10
- Ubuntu 18.04
- macOS 10.15
Steps to reproduce
- Launch Fx
- Make sure print.tab-modal.enabled is set on true
- Hit Ctrl + P on any page (eg. https://upload.wikimedia.org/wikipedia/commons/4/47/PNG_transparency_demonstration_1.png)
- Expand More settings and select Custom option from Margins dropdown
- Input a valid value inside the Left field (eg. 2)
- Input an invalid value inside the Right field (eg. 8)
- Try to validate the Right field by lowering the value from Left field (eg. 1)
- Select None option from Margins dropdown
Expected result
- The None option is set, the adjustment are also visible in print preview
Actual result
- The Custom option is still display, but the None selection takes effect in print preview
Regression range
- Not a regression, introduced with the margins custom implementation
Suggested severity
- S3
Assignee | ||
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Assignee | ||
Comment 1•4 years ago
|
||
Updated•4 years ago
|
Updated•4 years ago
|
Pushed by emalysz@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/0b5292f5309d Once margins are reevaluated, make sure it's possible to switch to "none" r=mstriemer
Comment 3•4 years ago
|
||
Backed out for bc failures on browser_print_margins.js
Failure log: https://treeherder.mozilla.org/logviewer.html#?job_id=319028664&repo=autoland
Backout link: https://hg.mozilla.org/integration/autoland/rev/00ae638205fc834b73b2ee9c2290009776cbddaa
Pushed by emalysz@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/31a08d4d6b82 Once margins are reevaluated, make sure it's possible to switch to "none" r=mstriemer
Comment 5•4 years ago
|
||
bugherder |
Assignee | ||
Comment 6•4 years ago
|
||
Comment on attachment 9180780 [details]
Bug 1670008, Once margins are reevaluated, make sure it's possible to switch to "none"
Beta/Release Uplift Approval Request
- User impact if declined: There will be a bug in our custom margins, and users will face difficulties facing from custom to none margins.
- Is this code covered by automated tests?: Yes
- Has the fix been verified in Nightly?: No
- Needs manual test from QE?: Yes
- If yes, steps to reproduce: STR are listed in comment 0
- List of other uplifts needed: Bug 1669696
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): No string changes
- String changes made/needed: n/a
Assignee | ||
Updated•4 years ago
|
Comment 7•4 years ago
|
||
Comment on attachment 9180780 [details]
Bug 1670008, Once margins are reevaluated, make sure it's possible to switch to "none"
Approved for 83 beta 2, thanks
Comment 8•4 years ago
|
||
bugherder uplift |
Updated•4 years ago
|
Reporter | ||
Comment 9•4 years ago
|
||
This issue is verified fixed with Fx 83.0b2 and Fx 84.0a1 (2020-10-20) on Windows 10, Ubuntu 18.04 and macOS 10.15.
Description
•