So you don't just want "fullscreen", you want "full screen and the user can't exit it".

Bartosz, FYI - similar to other LST cases we've been considering.

Thanks for taking the time to respond.

> you want "full screen and the user can't exit"

Yes, that is correct. The user should not be able to exit, and should require some progromatic event to take him to a PS.

If this is an Internet cafe, you control the network. Why not throw up a captive portal that forces the user to pay before browsing?

Great questions. My next phase in developing the app is to minimize (not close) the app to a small window and keep it always on top. This would allow us to display remaining time, and to allow for the user to log off when they are. 

You should be able to use the Public Session policies for session timer - "Maximum User Session Length" rather than creating an app.

https://support.google.com/chrome/a/answer/3017014?hl=en

> "Maximum User Session Length"

Correct me if I'm wrong, but I believe that setting is to enforce a uniform time for all users. There is no uniformity between users in my use case. Additionally, without an app I wouldn't be able to create a "time remaining" timer (again, unique on a per user bases, depending on the amount of credit they have and subject to updated in real time in the event that they top up), or offer other upsell opportunities.

Yes, the session length limit is just a fixed limit for every session. Your use case sounds like it will benefit from some custom UI implemented as a Chrome app but payment enforcement is probably still best done on the network side.

I see how something network side would make sense, but in this environment a welcoming and helpful "onboarding" screen would be necessary. While one could be provided via a web site, it would be more beneficial to completely take over the screen (showing a web site, no matter how obvious the login screen is, would be confusing here to lots of users).

Other functions for which a fullscreen app is more suitable include things like prevent a non authenticated user from, say, copying files.

Also note the other functions of this app, like the "time remaining" I noted above, which would necessitate running the app anyway.

Finally, while there are benefits to a captive portal, it requires a much more sophisticated setup on top of the already necessary parts (such as a billing server). Where I believe CrOS really shines in this case is in it's simplicity!

I no longer work on Chrome OS. Removing myself as owner.

Who can take this over?

There are a couple of concerns with your use-case:
1) ability to launch a chrome app in full-screen mode (this bug)
2) auto-launching an app in public session and making it a blocking app (not supported)

I am not sure if full-screen ability alone can solve your use-case.

Thanks, although I'm not sure I follow. Are you saying that the ability to "launch a chrome app in full-screen mode" is a bug?

As per "auto-launching an app in public session and making it a blocking app", I have noted the issue where this was disabled. I was hoping that there can be a public dialog on this, seeing as "secure by default" can be viewed from multiple points of view. It really depends on whether looking at the security from user or the device owner's point of view and weather the goal is to "protect the user from the device owner" or "protect the device owner from the user".

Personally I'm leaning towards giving control to the device owner, as I don't think that once purchased a device owner should be told what they can or cannot do with the device (provided the technology is easily supported). This is especially true when the requested functionality was already in place and is support - in general - across the platform.

I would love to hear other viewpoints though!

p.s. It's likely that fullscreen alone won't solve my objectives. It seems that Keep on top is also necessary

I should have been clear. It was not a bug. We disabled full-screen and wanted to show "Exit Session" button always to remind the user that they are using a public kiosk.

We are reviewing the design decision about full-screen mode.

> We are reviewing the design decision about full-screen mode.

That is great. If this is a conversation you guys would be willing to have out in the open, I'd be happy to participate!

It would be great if the device owner (using Google Device Management) can control if full screen is allowed in public session mode. So by default it is set to 'do not allow' and you can override to allow full screen.
This makes a lot of use cases possible and will drive the adoption of ChromeOS. To name a few:
- Citrix HTML5 receiver in full screen
- Allow Citrix Receiver for ChromeOS to use multiple screens
- Watch YouTube and other video's in full screen
- Use PowerPoint online and Prezi in presentation mode

This is a highly requested option for me and my customers as well. We are using Chromebox mainly with Citrix VDI environment and all devices are being managed with Google Device management and configured in public session along with some other settings. Citrix added the full screen mode to their Receiver for HTML5 client but unfortunately this is not supported in public session.
As mentioned above there are lots more use-cases to enable/allow fullscreen mode within public session. This will make a lot of customers, especially within Enterprise, very happy.

I would love to echo that being able to allow full screen mode in a public session would be extremely helpful.  I would also love this to be a configurable setting in device management.  

/UI triage

> We are reviewing the design decision about full-screen mode

Are you guys ready to share any thoughts on the matter? Would love to know where you guys stand on this!

ping - it would be great if we could get an update here!

Bump--would also like an update. Citrix org very interested in using Chrombooks with Public Sessions. 

No fullscreen is a deal breaker.

Also requesting this fix please.  How about the exit session button floats on top of the desktop like the session timer and idle timer do?  Need Citrix to run full screen for alt-tab functionality to work on the remote session.

Thanks for implementing this in v62 - fixed my issue with Citrix receiver - now able to use full screen in public session mode.

Thank you so much! While this doesn't provide a full secure environment (meta keys can be used to steal focus), it's a huge step forward. Thanks!

If you can also allow alwaysOnTop or trapping of meta keys, that would be perfect.

Hello!
This bug is receiving this notice because there has been no acknowledgment of its existence in quite a bit of time
- If you are currently working on this bug, please provide an update.
- If you are currently affected by this bug, please update with your current symptoms and relevant logs.

If there has been no updates provided by EOD Wednesday, 12/19/18 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary.

Thank you!

Due to lack of action this bug has been Archived. If work is still being done on this issue or you are still experiencing this issue please feel free to re-open with the appropriate information.