On Fri, 04 Jun 2010 19:28:42 +0200, James Feister open...@gmail.com
wrote:
As it states in section '3.1 Origin and Base URL' objects created with
an association other than the window object are out of scope for the
document. To add a way to control this usage and not hinder the
functionality
Hi Nikunj,
On Jun 7, 2010, at 23:00 , Nikunj Mehta wrote:
We have started using Mercurial for IndexedDB. I would like to propose moving
the IndexedDB spec's location to that repository in order to enable multiple
editors to work on it. Does anyone see a problem with that?
Also, we will
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9882
Summary: Behavior when attempting to write data to an
objectStore opened as read only unspecified
Product: WebAppsWG
Version: unspecified
Platform: PC
OS/Version: All
The natural place to put this attribute seems to be on the navigator object.
This property should be made available on both the main page and within a web
worker.
For example, one way this property could be defined would be with the following
WebIDL:
[Supplemental, NoInterfaceObject]
interface
On 6/8/2010 10:22 AM, bugzi...@jessica.w3.org wrote:
When you open an objectStore with a read only mode, any subsequent write
operation should probably result in an error. I don't see anywhere in the spec
that specifically says this or mentions what error code should be used.
Currently in the
On Tue, Jun 8, 2010 at 6:56 PM, Shawn Wilsher sdwi...@mozilla.com wrote:
On 6/8/2010 10:22 AM, bugzi...@jessica.w3.org wrote:
When you open an objectStore with a read only mode, any subsequent write
operation should probably result in an error. I don't see anywhere in the
spec
that
Hello,
An updated version of the WebTiming draft is up on
http://dev.w3.org/2006/webapi/WebTiming/
Some of the changes per feedbacks:
* the timing attributes are now under the window.performance name space
* most of the sensitive timing information have been removed from
