Does Firefox though? The Flatpak needs device access for whatever reason
Looks like it’s behind an about:config setting, media.webrtc.camera.allow-pipewire
https://github.com/linux-surface/linux-surface/issues/1215#issuecomment-1669374232
Cool, will try that!
Should?
They’re thinking about it.
This is the best summary I could come up with:
The Google Chrome/Chromium 127 web browser release should finally provide support for PipeWire camera capturing support!
Since last year there has been (experimental) PipeWire camera support within Mozilla Firefox while for Chrome (Chromium) 127 there should be similar support there as well.
The Chromium integration adds back-end support for PipeWire cameras and allows for it to work within sandboxed environments.
The PipeWire support has been a feature request going back to 2021 on the basis that using PipeWire allows for multiple applications to use the camera simultaneously, support for sandboxed environments like Flatpak via Portals, and sharing a lot of code with the desktop capture mode.
More details on this PipeWire camera support heading to Google’s web browser via this Chromium ticket.
Chrome 127 stable should be out in mid-July with this support barring any last minute issues from being discovered.
The original article contains 162 words, the summary contains 141 words. Saved 13%. I’m a bot and I’m open source!
looking forward to more things using pipewire camera, I don’t want to have to think about v4l again
deleted by creator
It was initially intended to be a video stream handler, but they had concerns with audio syncing. They figured they might as well also handle audio in one cohesive AV server instead
I cant seem to find the code for chrome that allows this. Can someone link it?
who uses Chrome on Linux
more people than you would imagine, unfortunately
the main takeaway from this is that when this becomes the default, eventually electron apps will also have this by default
