Repository navigation
Consider window capture #55
Description
§ 5.3 Subroutine: Supported display surface type says the only supported "surfaceType is browser" with this note:
Let's discuss.
It seems to me the spec could easily be extended to cover window capture of same-browser windows, and that this would be just as useful.
This would reveal that the "window" displaySurface is in fact a browser window, but this seems relatively harmless.
Once #51 is fixed, it should be simple to add an algorithm to extract the top-level browsing context associated with the viewport captured by either the window or browser display surface.
Activity
eladalon1983 commentedon Jan 23, 2025
Glad to hear you support this extension. (It likely goes without saying that I do too.)
Repeating my earlier question - is there some guarantee that a browser window would have a singular active tab? Might it not have 0 or 2 such tabs?
alvestrand commentedon Jan 23, 2025
Multiple tabs viewed at once is not a native Chrome feature, but is available with extensions:
https://www.groovypost.com/howto/view-multiple-google-chrome-tabs-split-screen/
It seems that this extension is doing split-screen by manipulating windows on the desktop, so it's possible that the OS and the browser would still see this as multiple windows.
Given the number of pages that came up on a simple search for this functionality, it is not inconcievable that such a thing could happen in the future.
eladalon1983 commentedon Jan 23, 2025
Yes.
My thinking is also - if a 1:1 mapping is not explicitly specified, then we can't assume it.
But maybe we can have the spec handle the case where there is a 1:1 mapping, and leave it up to the UA to fail gracefully when there is no 1:1 mapping.
jan-ivar commentedon Jan 23, 2025
I agree 1:1 is most common by a large margin. But I also don't see any inherent problem with multiple tabs viewed at once. Such extensions or browsers seem free to forward e.g. wheel-based event where it makes sense. The demo already shows users can scroll iframes in a captured page for instance.
The only issue might be the two tabs start out with different zoom levels, but that seems minor.
eladalon1983 commentedon Jan 23, 2025
That doesn't appear minor to me.
The PR should be careful not to assume otherwise. Happy to review.