Meeting minutes
Best practices for beforeunload
https://
[We read]
Steven: I think visibilitychange happens before unload actually
Erik: I've never used visibilitychanged, not sure if we need it.
… if you continually backup, you don't really need it
Steven: So you think that beforeunload is the only one we need
Erik: It is a solution
Erik: It is reasonable to expose 'visibilitychange' to XForms
… though the handler for that has to be very quick
Alain: it is not possible to customise the dialogue, so it is not perfect.
Erik: The problem with beforeunload, most users won't see the dialogue
… as long as you keep the data safe continually
Erik: To do it properly, you need to register the handler.
… but that handler disturbs the cache, which is a problem.
Steven: So that sounds like we need a way to say "Data is dirty/clean" dynamically
Erik: Or dynamic listener activation
… such as a relevant on <action>
Steven: That might work.
… <action relevant="instance('admin')/state='dirty'" ev:event="beforeunload">
Steven: I propose we keep reading and thinking about solutions for this.
Next Meeting
Steven: 8 May
[ADJOURN]
<Steven> s/\\Steven/Steven
<Steven> s/\\Steven/Steven