Closed
      
        Bug 1669696
      
      
        Opened 5 years ago
          Closed 5 years ago
      
        
    
  
Custom margins are not applied if a second value is changed after the error message is triggered and the “trigger” value is than changed to a valid one
Categories
(Toolkit :: Printing, defect, P2)
Tracking
()
        VERIFIED
        FIXED
        
    
  
        
            84 Branch
        
    
  
People
(Reporter: asoncutean, Assigned: emmamalysz)
References
(Blocks 1 open bug)
Details
(Whiteboard: [print2020_v83] [old-ui-])
Attachments
(2 files)
| 382.02 KB,
          image/gif         | Details | |
| 47 bytes,
          text/x-phabricator-request         | pascalc
:
              
              approval-mozilla-beta+ | Details | Review | 
Affected versions
- 83.0a1 (2020-10-07)
Affected platforms
- Windows 10
- macOS 10.14
- Ubuntu 18.04
Steps to reproduce
- Launch Fx
- Make sure print.tab-modal.enabled is set on true
- Hit Ctrl + P on any page
- Set an invalid value for the Left (or any other option) in order to trigger the error message
- Change the value for any other option (eg. Right)
- Change the value from step 4 to a valid one
Expected result
- The options are validated (the red border disappear), the error message is no longer displayed, the print preview is updated according to the changes
Actual result
- The options are validated (the red border disappear), the error message is still displayed, the print preview is not updated according to the changes
Regression range
- Not a regression, introduced with the Custom margins functionality
Additional notes
- Once another modification is made inside any of the field, the issue is no longer present
Suggested severity
- S3
| Assignee | ||
| Updated•5 years ago
           | 
Assignee: nobody → emalysz
| Assignee | ||
| Updated•5 years ago
           | 
Severity: -- → S4
Priority: -- → P2
| Assignee | ||
| Comment 1•5 years ago
           | ||
| Updated•5 years ago
           | 
Status: NEW → ASSIGNED
| Updated•5 years ago
           | 
Has STR: --- → yes
Pushed by emalysz@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/5b2a95a6e071
update custom margins if both values are valid r=mstriemer
| Comment 3•5 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
Flags: needinfo?(emalysz)
Pushed by emalysz@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/5b922807f962
update custom margins if both values are valid r=mstriemer
| Comment 5•5 years ago
           | ||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
          status-firefox84:
          --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 84 Branch
| Assignee | ||
| Comment 6•5 years ago
           | ||
Comment on attachment 9180752 [details]
Bug 1669696: update custom margins if both values are valid
Beta/Release Uplift Approval Request
- User impact if declined: Custom margin functionality is very buggy. They will not revalidate with new inputs
- 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 listed in comment 0
- List of other uplifts needed: None
- 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
Flags: needinfo?(emalysz)
        Attachment #9180752 -
        Flags: approval-mozilla-beta?
| Assignee | ||
| Updated•5 years ago
           | 
Flags: qe-verify+
| Comment 7•5 years ago
           | ||
Comment on attachment 9180752 [details]
Bug 1669696: update custom margins if both values are valid
Approved for 83 beta 2, thanks
        Attachment #9180752 -
        Flags: approval-mozilla-beta? → approval-mozilla-beta+
| Comment 8•5 years ago
           | ||
| bugherder uplift | ||
| Updated•5 years ago
           | 
QA Whiteboard: [qa-triaged]
| Reporter | ||
| Comment 9•5 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.
Status: RESOLVED → VERIFIED
Flags: qe-verify+
          You need to log in
          before you can comment on or make changes to this bug.
        
 screencast issue.gif
 screencast issue.gif
            
Description
•