[Fission] PiP offered but doesn't work
Categories
(Toolkit :: Video/Audio Controls, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox78 | --- | unaffected |
firefox79 | --- | unaffected |
firefox82 | --- | fixed |
People
(Reporter: overholt, Assigned: mconley)
References
Details
Attachments
(1 file)
(deleted),
text/x-phabricator-request
|
Details |
STR
- go to https://www.theverge.com/ and click on a video play button right from their home page (not an article)
- see the PiP affordance and click it
Expected: PiP video
Actual: nothing
I'm on the 2020-06-22 Nightly on Windows 10
Reporter | ||
Comment 1•4 years ago
|
||
Actually, I can make it happen on https://www.theverge.com/2020/6/24/21299924/ios-14-iphone-wwdc-2020-apple-home-screen-widgets-app-library-clips-pages-complexity, too.
Comment 2•4 years ago
|
||
Can't reproduce on beta or nightly on macOS.
Can you check a clean profile? Is this happening only with fission enabled, maybe? What OS are you seeing this on? Any errors in the browser console when PiP fails to open?
Reporter | ||
Comment 3•4 years ago
|
||
Sorry, I verified it works in a non-Fission window. Nothing in the console, FWIW.
Assignee | ||
Comment 5•4 years ago
|
||
The severity is N/A here as Fission is still off by default (even though more people are turning it on). As we get closer to enabling Fission by default on Nightly, we should adjust the Severity field.
Can confirm the issue in OP with most recent nightly build and fission.autostart = true.
To add to the discussion, I've opened a similar issue on webcompat here https://github.com/webcompat/web-bugs/issues/54274 but it was closed and the bugherder never replied about re-testing with fission enabled.
(In reply to Mike Conley (:mconley) (:⚙️) from comment #5)
The severity is N/A here as Fission is still off by default (even though more people are turning it on). As we get closer to enabling Fission by default on Nightly, we should adjust the Severity field.
This should be a S3 severity instead of N/A since the work around for the bug is leaving the feature disabled. As more people are exposed to the feature, then up-rating the severity would be, as you said, the next right thing.
Updated•4 years ago
|
Comment 8•4 years ago
|
||
Mike, this is a blocker for Fission Nightly. Is it blocked on anything from DOM?
Assignee | ||
Comment 9•4 years ago
|
||
No, I think we have everything we need from DOM. I'll see if we can get this fixed next week.
Assignee | ||
Comment 10•4 years ago
|
||
Updated•4 years ago
|
Comment 11•4 years ago
|
||
Comment 12•4 years ago
|
||
bugherder |
Description
•