Jonas Ådahl
Jonas Ådahl
> see the quick mockup below for an example. We still need to have some kind of separation, one where the portal provides trusted info about the source, and then...
> Can I check that this MR is "acked in principle" and just blocked on the upstream protocol to land? There has been no explicit ack from a maintainer yet,...
Next steps: release wayland-protocols with the new protocol, and bump the version needed by flatpak if enabled.
> Next steps: release wayland-protocols with the new protocol, and bump the version needed by flatpak if enabled. Can now depend on 1.32 for this.
Sorry for the delay, I had missed this report, and got poked on IRC about it. So there seems to be two issues: A usability issue, where restoring what was...
I mean that the way the screen cast portal works now can cause usability problems, as in the case you describe (restore a complex setup) means the user have to...
If the portal dialogs freeze, that is likely a portal bug, if not a compositor bug, but I suspect the problem is with the portal setting multiple dialogs the "transient"...
Hot keys is out of scope for the screen cast API itself, but could possibly be done using another portal or something similar, so lets leave that part out for...
FWIW, cameras, etc, can be remembered, and are stored as part of the permission store, thus a camera app will not necessarily be nagged about permission the second time, but...
> Right, something like the obs source name for example. Or for browsers they may want to provide the domain requesting access, etc. That's a good point.