app.kosmi.io - Missing "Local file" option from the "Select media" pop-up
Categories
(Web Compatibility :: Site Reports, defect, P2)
Tracking
(Webcompat Priority:P2, Webcompat Score:2, firefox138 affected, firefox139 affected)
People
(Reporter: rbucata, Assigned: twisniewski)
References
(Depends on 1 open bug, )
Details
(4 keywords, Whiteboard: [webcompat-source:web-bugs])
User Story
platform:windows,mac,linux,android impact:workflow-broken configuration:general affects:all branch:release diagnosis-team:media user-impact-score:160
Attachments
(2 files)
Environment:
Operating system: Windows 10
Firefox version: Firefox 139.0
Steps to reproduce:
- Navigate to: https://app.kosmi.io/
- Perform account login via Google
- Create a room
- From the room options, select the "Select media" option
- Observe the upper left side of the "Select media" pop-up
Expected Behavior:
3 options are present, including the "Local file" option
Actual Behavior:
2 options are present, the "Local file" option is missing
Notes:
- Reproduces regardless of the status of ETP
- Reproduces in firefox-nightly, and firefox-release
- Does not reproduce in chrome
Created from https://github.com/webcompat/web-bugs/issues/154252
Reporter | ||
Updated•21 days ago
|
Reporter | ||
Comment 1•21 days ago
|
||
Updated•20 days ago
|
Comment 2•14 days ago
•
|
||
Not sure, but as a guess: this might depend on the file system access DOM API (bug 1905871) where we have a negative standards-position on, per https://github.com/mozilla/standards-positions/issues/154
--> Reclassifying to diagnosis-team:dom on the basis of that guess to help clear the webcompat team's triage queue, since I think that's the team closest to that API and related features.
Comment 3•14 days ago
|
||
The site has code like this
b = (0, x.useRef) (document.createElement('video'));
return {
isMobile: y,
isIOS: u,
isAndroid: S,
isMobileOS: u ||
S,
isLandscape: p,
isBeingEmbedded: I,
hasScreenshareWithAudio: g,
canCaptureVideoElement: !!b.current.captureStream,
supportsRestrictionTarget: !!((d = window.RestrictionTarget) != null && d.fromElement)
}
It's caused by the canCaptureVideoElement: !!b.current.captureStream
. Firefox only supports mozCaptureStream
, overriding the script to change it to mozCaptureStream
fixes it.
Comment 5•14 days ago
|
||
Thanks, Sean!
Given comment 3, it looks like we can consider this diagnosed as a form of bug 1541471 (on shipping the captureStream
feature). Let's just mark it as-such.
Comment 6•14 days ago
•
|
||
I think there's a chance we could sitepatch this with some hacky JS that does foo.captureStream = foo.mozCaptureStream
for some foo
(I'm hand-waving a bit, but you get the idea.)
Not sure if our prefixed implementation works or not with this particular site; comment 3 suggests that maybe it does, so it'd probably worth attempting an intervention if someone has the time (given that the underlying bug 1541471 is currently webcompat:blocked-resources
).
Assignee | ||
Updated•5 days ago
|
Assignee | ||
Comment 7•5 days ago
|
||
Updated•5 days ago
|
Comment 9•4 days ago
|
||
bugherder |
Assignee | ||
Updated•4 days ago
|
Updated•3 days ago
|
Description
•