This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 19558 - Needed: An Algorithmic "Hook" For Culling URL.objectURLs with autoRevoke=true
Summary: Needed: An Algorithmic "Hook" For Culling URL.objectURLs with autoRevoke=true
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P2 normal
Target Milestone: ---
Assignee: Silvia Pfeiffer
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on: 19554
Blocks:
  Show dependency treegraph
 
Reported: 2012-10-16 17:09 UTC by Edward O'Connor
Modified: 2012-10-29 02:49 UTC (History)
6 users (show)

See Also:


Attachments

Description Edward O'Connor 2012-10-16 17:09:18 UTC
+++ This bug was initially created as a clone of Bug #19554 +++

Currently, URL.createObjectURL is specified to work with autoRevoke set to true, which allows Blob URLs to be valid past a provided stable state.

But stable state is not a sufficient concept, nor is the misdirected Bug 17988 which seeks to have microtask defined as a concept.

What is needed here is: something that's always invoked when exiting the outermost script (including from parser-invoked script) .  If this is provided in HTML5, we can use it to describe autoRevoke semantics.  This is useful for the createObjectURL default pattern, which avoids persisting string-based references to in-memory objects, minimizing leaks.
Comment 1 Silvia Pfeiffer 2012-10-29 02:49:01 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If
you are satisfied with this response, please change the state of
this bug to CLOSED. If you have additional information and would
like the Editor to reconsider, please reopen this bug. If you would
like to escalate the issue to the full HTML Working Group, please
add the TrackerRequest keyword to this bug, and suggest title and
text for the Tracker Issue; or you may create a Tracker Issue
yourself, if you are able to do so. For more details, see this
document:   http://dev.w3.org/html5/decision-policy/decision-policy-v2.html

Status: Accepted

Change Description:
https://github.com/w3c/html/commit/0d991000625f2fd958ba784efc85bf2812df8b13
and
https://github.com/w3c/html/commit/2a5aed7a4d461a566765c46612fc84899fcbb123

Rationale: accepted WHATWG patches for cloned bug; if this is insufficient, do re-open