Issue metadata
Sign in to add a comment
|
we should reduce the amount of time we give beforeunload/unload handlers to run |
||||||||||||||||||||||||
Issue descriptionToday we have a 1 second timeout. That is too much time given that this is on the critical path of a user closing a tab. We should reduce that to something like 500ms or less. See also related issue 701434 .
,
Mar 27 2017
I don't know of any tracking of whether it's subframes or parent pages. As per the latest discussion in issue 692224 , it won't help here because we're still running the code. We're just not allowing for showing the dialog.
,
Aug 25 2017
Issue 365039 should help with this, where we won't try to run the beforeunload handler if there isn't one registered. As I mentioned on issue 701434 , I'd be concerned about slow machines not having enough time to tell the user that they're going to lose data if we lower the timeout too much. Maybe some UMA stats could give us a sense for how often this happens?
,
Oct 18 2017
,
Sep 12
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by dcheng@chromium.org
, Mar 27 2017