Closed
      
        Bug 1671588
      
      
        Opened 5 years ago
          Closed 4 years ago
      
        
    
  
PiP window is not visible if enabled right after changing resolution 
    Categories
(Toolkit :: Video/Audio Controls, defect, P3)
        Toolkit
          
        
        
      
        
    
        Video/Audio Controls
          
        
        
      
        
    Tracking
()
        VERIFIED
        FIXED
        
    
  
        
            84 Branch
        
    
  
People
(Reporter: sbadau, Assigned: baumga91)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
Affected versions
Firefox Nightly 83.0a1
Affected platforms
Windows 10
Steps to reproduce
- Navigate to Youtube.
- Start playing any video at a 720p resolution.
- Change the resolution of the video to 1080p and right after toggle the PiP button.
Expected result
The PiP window should be properly opened.
Actual Result
The PiP window is seen in the TaskBar but can't be accessed. Please see the screencast for more details.
If this issue is a regression, is not a recent one since I've reproduced it on Firefox 78.3.1 esr, Firefox 81.0.2, and Firefox 82. I'll investigate more as soon as possible.
Severity-Suggestion:
S3 severity.
| Reporter | ||
| Comment 1•5 years ago
           | ||
Not a regression, reproduced this issue ever since Nightly 69.0a1.
| Updated•5 years ago
           | 
| Assignee | ||
| Comment 2•4 years ago
           | ||
| Updated•4 years ago
           | 
Assignee: nobody → baumga91
Status: NEW → ASSIGNED
Pushed by mconley@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/533c8598febd
The Picture-in-Picture toggle is updated after changing video source. r=mconley
|   | ||
| Comment 4•4 years ago
           | ||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
          status-firefox84:
          --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 84 Branch
| Updated•4 years ago
           | 
| Updated•4 years ago
           | 
Flags: qe-verify+
| Comment 5•4 years ago
           | ||
This issue is Verified as fixed in our latest Beta build 84.0b3
          You need to log in
          before you can comment on or make changes to this bug.
        
Description
•