[Webkit-unassigned] [Bug 55844] Expose page dismissal event status through the WebKit API for chromium

Fri Mar 11 16:33:46 PST 2011

https://bugs.webkit.org/show_bug.cgi?id=55844

--- Comment #22 from Sreeram Ramachandran <sreeram at google.com>  2011-03-11 16:33:46 PST ---
(In reply to comment #21)
> > I think the decision on whether alert()s should be ignored during unload events should be handled on the Chromium side. Safari and other webkit clients may not want to disable alerts (which is the current behaviour in all browsers). In addition, even in Chromium, we don't always want to ignore alerts (e.g.: I think extension_host doesn't want to).
> 
> I have to disagree.  We are trying to change the behavior of the web platform here, and the definition of the web platform should reside as much as possible within the webkit repository and not be spread between multiple repositories.
> 
> We should be championing this breaking change on the working groups and experimenting with this implementation in webkit behind a compile time flag to inform the html spec.

I agree (that it should be standard behaviour). I went this route only because of what Ojan said at http://crbug.com/68780#c3

I think it'd be nice to implement this in Chromium for now, show that the web isn't horribly broken because of it (e.g.: no complaints about it); such evidence might give us better standing to argue for it to become standard behaviour.

Should I withdraw this API and the CL in progress at http://codereview.chromium.org/6627063/?

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.