Local media casting (see issue 721802) opens up a new tab with the local content.
As there is no other content in the tab except for the media and that media is immediately captured and sent to a remote sink (chromecast etc) the content should be fullscreen for the optimal experience.
It seems to me one of the benefits of casting vs. local playback is to retain control of your local browser window and multitask while the media plays elsewhere. Playing the media fullscreen doesn't really allow that (or requires an extra step to get back to the browser window). Does this proposal align with the feature PRD?
I created this specifically for https://chromium-review.googlesource.com/c/chromium/src/+/731669 instead of tagging it to the launch bug as Anna's original change had it.
And to be clear this is fullscreen after the capture is started, so it's fullscreen-in-tab, not actual fullscreen.
My description may be off from the PRD says, but I believe this was all planned work and in fact the only thing left blocking the launch.
Comment 1 by mfo...@chromium.org
, Oct 20 2017