W3C home > Mailing lists > Public > whatwg@whatwg.org > December 2008

[whatwg] salvaging work while navigating away from a web app -- onunload="confirm('save before quitting?')

From: Calogero Alex Baldacchino <alex.baldacchino@email.it>
Date: Fri, 12 Dec 2008 20:38:09 +0100
Message-ID: <4942BDA1.8010608@email.it>
Bil Corry ha scritto:
> Ojan Vafai wrote on 12/12/2008 12:49 PM: 
>> If we're going for matching what browsers do, there's a number of cases
>> (different in each browser) where the confirm doesn't popup. In Chrome, for
>> example, if the beforeunload handler takes too long, we kill it and navigate
>> away. Similarly, in Firefox, if the beforeunload handler hits the limit for
>> script execution and the user stops the script, the beforeunload handler
>> never fires.
>> Not sure what the right language for that is. But developers try to do
>> things like using beforeunload/unload to release locks, make server
>> requests, etc. and it's just not a very reliable thing to do in any browser.
>> It's really just useful for the quick prompt for the user as to things like
>> unsaved changes.
> Here's a fun one, I made this as a demo to show how a website could trap a user forever:
> 	http://www.corry.biz/neverleave.lasso
> I haven't tried it in any browsers lately, but a quick test with IE7 shows it still is effective (for it at least).
> - Bil

I've tested it 'en passant' with FF3: I want my base back!!!!!!! LOL
 Caselle da 1GB, trasmetti allegati fino a 3GB e in piu' IMAP, POP3 e SMTP autenticato? GRATIS solo con Email.it http://www.email.it/f
 Attiva Carta Eureka! Credito fino a 3.000?, rate da 20? e zero costi di attivazione. Conviene!
 Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=8429&d=12-12
Received on Friday, 12 December 2008 11:38:09 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:46 UTC