- From: <bugzilla@jessica.w3.org>
- Date: Tue, 16 Oct 2012 17:09:18 +0000
- To: public-html-bugzilla@w3.org
- Message-ID: <bug-19558-2486@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19558 Priority: P2 Bug ID: 19558 CC: arun@mozilla.com, ian@hixie.ch, mike@w3.org, public-html-wg-issue-tracking@w3.org, public-html@w3.org Assignee: erika.doyle@microsoft.com Summary: Needed: An Algorithmic "Hook" For Culling URL.objectURLs with autoRevoke=true QA Contact: public-html-bugzilla@w3.org Severity: normal Classification: Unclassified OS: other Reporter: eoconnor@apple.com Hardware: Other Status: NEW Version: unspecified Component: HTML5 spec Depends on: 19554 Product: HTML WG +++ 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. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 16 October 2012 17:09:20 UTC