Meeting minutes
ACTION: Steven to spec file read and write
https://
https://
Steven: Please check that you are OK with this: https://
[back] and [wake] events
https://
Steven: Second link should be https://
Alain: There are some restrictions
… it depends on what you are expecting
… there is an event 'before-unload', it is just about [back]
Erik: We discussed this before. My view is that there is no reliable way to do it.
… it's unclear to me that this really works...
… the back button does not necessarily leave the document
… pop-state event
… I see negative comments.
… I'm unclear if any of this works
Erik: We don't want to lose state on back, the only thing to do is to warn the user.
Steven: Steven: So single-page apps, how do they do it?
Erik: You can catch unload, and ask if the user really wants that
… but you can't do any processing.
… the documentation says that the event is not reliably fired.
Steven: So you don't think that back is possible to catch?
… couldn't an implementation push a state, and then a pop-state could be caught
Steven: Difficult. How about the wake event?
Erik: Seems more doable.
Steven: I have apps in tabs, and returning I'd like to be able check that the state is still consistent (date, data still current, etc)
Erik: There's an API that dispatches events when the browser navigates back to your document
… or returns from being frozen
… page lifecycle API maybe
<ebruchez> https://
Steven: I see focus event on the page. That looks like what I want
… I think the result is "Needs more research"
Coming meetings
Steven: Meet next week.
[ADJOURN]