That was indeed intentional, but I can't find any discussion about that specifically.  My thought was that since the receiver page isn't considered interactive, it made sense to keep the controller focused.  I see how the fullscreen toggle situation causes confusion though.  Maybe Mark, John, and/or Derek can chime in.

Brandon - is this planned for M66? If not please bump to M67

My understanding of the original logic to make it initially inactive is that presentations aren't usually intended to be interactive.  Can you (John), Mark, or Derek chime in on whether we now want to make it initially active to avoid the possible keyboard focus confusion?

It's possible for presentation receiver windows to be interactive, but generally that's not assumed by the web developer, since it may be shown on a screen without input capability.

So it would be odd to focus a window by default that normally would not receive input.

I can't really comment for certain on this very specific issue around fullscreen without seeing the flow in person.

A few thoughts.

What's the desired flow here?
I imagine it as the following, but correct me if I'm wrong.

1. A user is on the content (presentation) they want to present.
2. They click the cast button (I'm assuming there is a cast button, but it could be a site specific button) and get a list of screens to show it on.
3. They select/click their local screen (not the one they are on).
4. Presentation begins.

It sounds like this bug is saying their is a step 5, which is go to the presentation window and press F11 to toggle fullscreen, but I'm not clear on why they would ever want to do that.  Is the problem that we show a toast on that screen which would be confusing since it's not actionable?


So my vote I guess is to leave it as is with the focus on the controls and not switched to the presentation window (if they had selected a separate device like a chromecast they wouldn't be able to select that window anyway).


If I'm making some incorrect assumptions, though, I'm interested in hearing more.

Marking WontFix based on the discussion.