New issue
Advanced search Search tips

Issue 663276 link

Starred by 2 users
Status: Available
Owner: ----
Cc:
yukishiino@chromium.org
panicker@chromium.org
igrigo...@chromium.org
esprehn@chromium.org
dcheng@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug

Blocked on:
issue 583429

Participants' hotlists:
Lifecycle


Sign in to add a comment

Consider firing visibilitychange@unload event after detaching the frame

Project Member Reported by kinuko@chromium.org, Nov 8 2016 
We implemented visibilitychange event for document unloading to fire at the same timing as the unload event ( issue 554834 ), but there's been a discussion on changing the timing to fire it after detaching the frame (rather than on the middle of detaching procedure where all objects are in an unclear state / where script can still traverse frame tree).  Doing so would hopefully give a clearer state for the event handler while we first need to make script execution in detached frames clearer / verify what should work or not.  This bug is for tracking the status and discussion.

Comment 1 by kinuko@chromium.org, Nov 8 2016 

Shiino-san, I remember you've been working on making script execution in detached frames saner by incrementally improving binding layer / CallWith=ScriptState behavior when ScriptState is invalid.  Do we have a bug for tracking the detached frame work in general? If so I'd like to link this bug to that to track the progress.

(Meanwhile we're thinking about shipping visibilitychange @unload as is in the current implementation without being blocked on this)

Comment 2 by yukishiino@chromium.org, Nov 8 2016 

Issue 583429 is the one, I think.
Note: At the time that the bug was filed, people was thinking all script executions should be disallowed, so the title is "Disallow script running in a detached frame".

Comment 3 by kinuko@chromium.org, Nov 8 2016 

#2 - thanks! Should we probably change the issue subject to reflect the latest direction?

Comment 4 by yukishiino@chromium.org, Nov 9 2016 

re: #3, Done.

Comment 5 by kinuko@chromium.org, Nov 9 2016

Blockedon: 583429
Thanks Shiino-san!

Comment 6 by tdres...@chromium.org, Aug 14 2017

Owner: panicker@chromium.org
Status: Assigned (was: Available)
Assigning to panicker@ for now.
This would be a spec change, right?

Comment 7 by tdres...@chromium.org, Jan 4 2018 

Ping!

Comment 8 by tdres...@chromium.org, Mar 1 2018

Components: -Blink>PerformanceAPIs Blink>PageLifecycle

Comment 9 by panicker@chromium.org, Mar 2 2018

Cc: panicker@chromium.org
Owner: ----
Status: Available (was: Assigned)

Comment 10 by ojan@chromium.org, May 8 2018

Cc: -ojan@chromium.org
►

Sign in to add a comment