This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
After the recent setVersion changes it should be using long long.
Actually, it should use 'any' for newVersion, since in a deleteDatabase call it is null.
Will make long long.
Fixed in the 1 November Editor's Draft: interface IDBVersionChangeEvent : Event { readonly attribute unsigned long long oldVersion; readonly attribute unsigned long long newVersion; void initIDBVersionChangeEvent (DOMString typeArg, boolean canBubbleArg, boolean cancelableArg, long long oldVersion, long long newVersion); }; I think newVersion should be long long rather than any. The only time it is null is when it is deleted. Thanks, Eliot
(In reply to comment #3) > Fixed in the 1 November Editor's Draft: > > interface IDBVersionChangeEvent : Event { > readonly attribute unsigned long long oldVersion; > readonly attribute unsigned long long newVersion; > void initIDBVersionChangeEvent (DOMString typeArg, boolean canBubbleArg, > boolean cancelableArg, long long oldVersion, long long newVersion); > }; > > I think newVersion should be long long rather than any. The only time it is > null is when it is deleted. It should be nullable ("unsigned long long?") then, right? /me admits to not knowing much about this whole WebIDL thing.
(In reply to comment #4) > (In reply to comment #3) > > Fixed in the 1 November Editor's Draft: > > > > interface IDBVersionChangeEvent : Event { > > readonly attribute unsigned long long oldVersion; > > readonly attribute unsigned long long newVersion; > > void initIDBVersionChangeEvent (DOMString typeArg, boolean canBubbleArg, > > boolean cancelableArg, long long oldVersion, long long newVersion); > > }; > > > > I think newVersion should be long long rather than any. The only time it is > > null is when it is deleted. > > It should be nullable ("unsigned long long?") then, right? Yes.
made all appropriate elements nullable, in the following: IDBVersionChangeEvent.oldversion IDBVersionChangeEvent.newversion IDBVersionChangeEvent.initIDBVersionChangeEvent() IDBFactory.open() IDBDatabase.version IDBFactorySync.open() IDBDatabaseSync.version IDBVersionChangeCallback.transactionStarted() Changes are published in the Editor's Draft of Dec 27. Thanks, Eliot
Actually, only the newVersion property on the IDBVersionChangeEvent can be null. All other version properties/arguments are always non-null. Changed things to reflect this. I also removed the initIDBVersionChangeEvent function in favor of a constructor since that's how DOM-Events are initialized these days.