W3C home > Mailing lists > Public > whatwg@whatwg.org > May 2012

[whatwg] Declarative unload data

From: Bronislav Klučka <Bronislav.Klucka@bauglir.com>
Date: Mon, 07 May 2012 18:10:26 +0200
Message-ID: <4FA7F3F2.20301@bauglir.com>

On 7.5.2012 18:00, Boris Zbarsky wrote:
> On 5/7/12 11:54 AM, Bronislav Klu?ka wrote:
>> "I see pages doing it is that they're up to no good" well that is your
>> opinion, sure, we have all seen bad use of that, but removing
>> functionality that has no replacement, can be used for useful thinks
>> (well for bad as well) can hardly be reasonable
> Sure it can, if the abuse case is the overwhelming case.  Browsers 
> have done it before, and users were very glad they did.
> -Boris

I'm not sure about whole functionality removed without replacement... 
You wrote to Tab "the legitimate use-case for popup windows is also 
reasonable, yet browsers have popup blockers." sure, but this 
functionality was not removed, etc... I can imagine no DOM/browsing 
context manipulation (even new browsing context) by default, only on opt 
in (but when the optin? before the beforeunload :) ?) But disabling it 
altogethe, because someone may alert "Do you really want to exit this 

Received on Monday, 7 May 2012 09:10:26 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:41 UTC