New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 81759 link

Starred by 10 users

Issue metadata

Status: Fixed
User never visited
Closed: Sep 2011
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Feature

issue 81757

  • Only users with Commit permission may comment.

Sign in to add a comment

Allow background pages to call window.close()

Project Member Reported by, May 6 2011

Issue description

Extensions that need to do a bit of setup work (e.g. register a view to load later, see  bug 81758 , or display a welcome message when first installed) are stuck with a background page indefinitely, even though they no longer need it. We should allow extensions to use window.close() in their background page.

 Bug 70466  may be related.
Blocking: 81757
Labels: -mstone-x
Will this include adding context menu items? They have a Javascript environment, so it may be a bit of an issue...

Comment 4 by, May 31 2011

Status: Assigned
Project Member

Comment 6 by, Sep 7 2011

@purplesh... You're right, if you call window.close() in the backgorund page the Javascript environment will be torn down (outstanding listeners, timers, context menus, etc will all be destroyed), so you should only do it if you're really done.
Status: Fixed
Project Member

Comment 9 by, Oct 13 2012

Blocking: -chromium:81757 chromium:81757
Labels: Restrict-AddIssueComment-Commit
This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.
Project Member

Comment 10 by, Mar 10 2013

Labels: -Area-Internals -Feature-Extensions Cr-Internals Cr-Platform-Extensions

Sign in to add a comment