- From: <bugzilla@jessica.w3.org>
- Date: Mon, 16 Aug 2010 23:48:41 +0000
- To: public-webapps@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10381 Summary: [IndexedDB] Structured clones should be created synchronously Product: WebAppsWG Version: unspecified Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Indexed Database API AssignedTo: nikunj.mehta@oracle.com ReportedBy: pablo.castro@microsoft.com QAContact: member-webapi-cvs@w3.org CC: mike@w3.org, public-webapps@w3.org The spec for the asynchronous "put" and "add" methods in object store as well as "update" in cursors don't explicitly state when clones are created, and can even be read as if clones should be created after the function call returned, when the queued up task is executed. This leads to problems where the clone may be modified after the call to put/add/update happens. Spec needs to be updated to indicate that the actual creation of the clone should happen synchronously while the put/add/update method is running, so the state of the object used to perform the database operation is as it was at the time the call was made, regardless of the timing of the actual execution of the method, timing of the callbacks, etc. Related discussion thread here: http://lists.w3.org/Archives/Public/public-webapps/2010JulSep/0501.html -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
Received on Monday, 16 August 2010 23:48:42 UTC