Does Chrome OS have a similar policy that we could harmonize with?

To make sure my understanding is correct, the desire here is to make it possible for an administrator to pick a time window during which browsers will relaunch without user interaction should an update be available. Some questions:

- Does this mean that the browser should not prompt the user to relaunch outside of this time window (i.e., the app menu will not change to the green arrow)?

- What if a user has a partially-filled form, or something else that blocks the restart (i.e., a beforeunload dialog would normally be shown)?

Can anyone think of any other edge cases?

Assigning to Anuj to try to answer Greg's question.

The CrOS team said that it already exists in client code as the DeviceAutoUpdateTimeRestrictions policy. Could also be combined with RebootAfterUpdate. 

Yes - I think if this policy is set then the arrow reminder should not appear.

> Does this mean that the browser should not prompt the user to relaunch outside of this time window (i.e., the app menu will not change to the green arrow)?

Anuj, thx for adding me. This fits perfectly into the current discussion regarding the RelaunchPolicy

https://docs.google.com/document/d/15x8qzV5ZxoYRNEBPApXW5Q0ULMhfccS25dAX3CHCqoA/edit

Do you have a timeline for implementation?

Marcus, we don't currently have a timeline as it is P3 priority.

DeviceAutoUpdateTimeRestrictions is about performing update checks (using the network) and installing updates (using device resources). This isn't obviously the same as when to force a relaunch. I'm not sure that these two things should be entwined.

grt: You're correct - let's not intertwine DeviceAutoUpdateTimeRestrictions and RelaunchTime.