Open
Bug 1630552
Opened 1 year ago
Updated 11 months ago
PIP - cannot trigger fullscreen right after triggering PIP from context menu
Categories
(Toolkit :: Video/Audio Controls, defect, P3)
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| firefox76 | --- | wontfix |
| firefox77 | --- | fix-optional |
People
(Reporter: cfogel, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [wfh])
Affected versions
- 76.0b5, 77.0a1 (2020-04-15)
Affected platforms
- macOS 10.15.3;
Steps to reproduce
- Launch Firefox, open any video ex: this one
- Right click for the context menu;
- Click on PIP to enable it;
- Right click on the video for the context menu again;
- Click on the Fullscreen option
Expected result
- fullscreen triggered;
Actual result
- fullscreen not triggered;
Regression range
- will check and provide one asap;
- Last good revision: 2019-10-25
- First bad revision: 2019-10-26
- Pushlog: URL
Additional notes
- on Ubuntu 18.04/Windows 10 it seems to work ok and goes full-screen mode;
- at some point the fullscreen gets triggered as well;
- error code displayed in console:
[Exception... "Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIDOMWindowUtils.addSheet]" nsresult: "0x80070057 (NS_ERROR_ILLEGAL_VALUE)" location: "JS frame :: resource://gre/modules/ExtensionCommon.jsm :: runSafeSyncWithoutClone :: line 75" data: no]
| Reporter | ||
Updated•1 year ago
|
Has Regression Range: --- → no
Has STR: --- → yes
Blocks: videopip
Priority: -- → P3
Updated•1 year ago
|
Whiteboard: [wfh]
Updated•1 year ago
|
Updated•1 year ago
|
| Reporter | ||
Comment 1•1 year ago
|
||
Not a regression, updated section in the initial report.
Visible & reproducible with the introduction of the pip button/option.
Has Regression Range: no → ---
Keywords: regression,
regressionwindow-wanted
Comment 2•1 year ago
|
||
Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is P3 (Backlog,) indicating it has been triaged, the bug's Severity is being updated to S3 (normal.)
Severity: normal → S3
Comment 3•11 months ago
|
||
Is this a duplicate of bug #1534986?
You need to log in
before you can comment on or make changes to this bug.
Description
•