chrome.runtime.onRestartRequired event for Kiosk app

[Xiyuan Xia]

Kiosk app runs in full screen on a Chrome OS device. It needs to know when the device should be restarted. So that it could communicate with the user to finish the current session and exit at the right time. There are a few possible reasons for a restart to happen: app is updated, os/browser is updated and a periodic reboot set in device policy.

The proposal is to add a chrome.runtime.onRestartRequired event for this purpose. Current plan is to fire the event only for ChromeOS kiosk apps when a restart is scheduled. Upon receiving the event, a kiosk app should close all it's windows at its earliest convenient time to exit and let the reboot to happen. If the app does nothing, the restart will be enforced after a grace period has passed. Tracking issue is http://crbug.com/242983

Comments?

Xiyuan

[Xiyuan Xia]

Correct. The event can not be canceled.

On Tue, Jun 18, 2013 at 12:18 PM, Joe Marini <joem...@google.com> wrote:

Seems fine to me. I assume the event is not cancelable?

--
You received this message because you are subscribed to the Google Groups "extensions-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to extensions-de...@chromium.org.
For more options, visit https://groups.google.com/a/chromium.org/groups/opt_out.
 
 

--
Joe Marini

Developer Advocate / Chrome

joem...@google.com | +Joe Marini | @joemarini

[Marijn Kruisselbrink]

We already have onUpdateAvailable and onBrowserUpdateAvailable events,
so do you really need a new event for this? Although the usecase seems
to be different enough that a separate event makes sense (especially
since there is apparently a third situation possible for kiosk apps).

[Xiyuan Xia]

jyasskin had a similar concern on http://crbug.com/242983. Think we should deprecate onBrowserUpdateAvailable and use onRestartRequired instead to cover all reboot cases for kiosk app. And when we make onRestartRequired available for all apps, we could merge onUpdateAvailable into onRestrartRequired too. Eventually, think we want only one such event.