Tuesday, 16 December 2014
Monday, 15 December 2014
- [Bug 27605] [NewObject] and Promise
- [Bug 27605] [NewObject] and Promise
- [Bug 27605] [NewObject] and Promise
- [Bug 27605] [NewObject] and Promise
Saturday, 13 December 2014
- [Bug 27605] New: [NewObject] and Promise
- [Bug 27557] Consider introducing a prose-friendly way to refer to enumerations
Friday, 12 December 2014
- [Bug 27557] Consider introducing a prose-friendly way to refer to enumerations
- [Bug 27557] Consider introducing a prose-friendly way to refer to enumerations
Wednesday, 10 December 2014
- [Bug 27553] Support Symbol
- [Bug 27553] Support Symbol
- [Bug 27553] Support Symbol
- [Bug 27557] Consider introducing a prose-friendly way to refer to enumerations
- [Bug 27557] Consider introducing a prose-friendly way to refer to enumerations
- [Bug 27557] New: Consider introducing a prose-friendly way to refer to enumerations
- [Bug 27553] New: Support Symbol
Tuesday, 9 December 2014
- [Bug 27317] Provide explicit guidance on enum value naming
- [Bug 27317] Provide explicit guidance on enum value naming
- [Bug 27317] Provide explicit guidance on enum value naming
- [Bug 27549] Support holes or undefined values in the sequences as return values?
- [Bug 27549] Support holes or undefined values in the sequences as return values?
- [Bug 27549] Support holes or undefined values in the sequences as return values?
- [Bug 27549] Support holes in the sequence return values?
- [Bug 27549] Support holes in the sequence return values?
- [Bug 27549] Support holes in the sequence return values?
- [Bug 27549] New: Support holes in the sequence return values?
Monday, 8 December 2014
Saturday, 6 December 2014
Friday, 5 December 2014
Thursday, 4 December 2014
Friday, 5 December 2014
- Re: Figuring out the behavior of WindowProxy in the face of non-configurable properties
- [Bug 26901] Stop using "octet"
- Re: Figuring out the behavior of WindowProxy in the face of non-configurable properties
- [Bug 26901] Stop using "octet"
- [Bug 26901] Stop using "octet"
- Re: Figuring out the behavior of WindowProxy in the face of non-configurable properties
- [Bug 26901] Stop using "octet"
- Re: Figuring out the behavior of WindowProxy in the face of non-configurable properties
- Re: Figuring out the behavior of WindowProxy in the face of non-configurable properties
- [Bug 26901] Stop using "octet"
- Re: Figuring out the behavior of WindowProxy in the face of non-configurable properties
Thursday, 4 December 2014
- RE: Figuring out the behavior of WindowProxy in the face of non-configurable properties
- [Bug 20567] Change [[Prototype]] for concept-node-adopt?
- [Bug 27521] Hook for changing prototype of an object to that of a specified global
- [Bug 20567] Change [[Prototype]] for concept-node-adopt?
- [Bug 27521] New: Hook for changing prototype of an object to that of a specified global
- Re: Figuring out the behavior of WindowProxy in the face of non-configurable properties
- [Bug 26901] Stop using "octet"
- [Bug 26901] Stop using "octet"
- RE: Figuring out the behavior of WindowProxy in the face of non-configurable properties
- [Bug 26901] Stop using "octet"
- [Bug 26901] Stop using "octet"
- Re: Figuring out the behavior of WindowProxy in the face of non-configurable properties
- Re: Figuring out the behavior of WindowProxy in the face of non-configurable properties
Tuesday, 2 December 2014
- [Bug 27284] Should InvalidAccessError be discouraged?
- [Bug 27284] Should InvalidAccessError be discouraged?
- Re: Figuring out the behavior of WindowProxy in the face of non-configurable properties
- Re: Figuring out the behavior of WindowProxy in the face of non-configurable properties
- Re: Figuring out the behavior of WindowProxy in the face of non-configurable properties
- Re: Figuring out the behavior of WindowProxy in the face of non-configurable properties
- Re: Figuring out the behavior of WindowProxy in the face of non-configurable properties
Monday, 1 December 2014
- [Bug 22156] Allow trailing commas in Web IDL lists
- Re: Figuring out the behavior of WindowProxy in the face of non-configurable properties
- Re: Figuring out the behavior of WindowProxy in the face of non-configurable properties
Sunday, 30 November 2014
Wednesday, 26 November 2014
- RE: Weak set usage in streams
- Re: Weak set usage in streams
- Re: Weak set usage in streams
- Weak set usage in streams
- [Bug 17713] Exceptions thrown from event handlers should not be propagated
- [Bug 25138] "Invoking callback functions"
- [Bug 17713] Exceptions thrown from event handlers should not be propagated
- [Bug 17713] Exceptions thrown from event handlers should not be propagated
Tuesday, 25 November 2014
- [Bug 23202] Add @@unscopeables sugar
- [Bug 27428] [ArrayClass] should serialize as an array by default
- [Bug 27428] [ArrayClass] should serialize as an array by default
- [Bug 27428] [ArrayClass] should serialize as an array by default
- [Bug 27428] [ArrayClass] should serialize as an array by default
- [Bug 27428] New: [ArrayClass] should serialize as an array by default
Monday, 24 November 2014
Thursday, 20 November 2014
- [Bug 27354] Internal slots
- [Bug 27354] Internal slots
- [Bug 27381] Basing Object.observe() for IDL objects on internal slots
- [Bug 27381] Basing Object.observe() for IDL objects on internal slots
- [Bug 27381] Basing Object.observe() for IDL objects on internal slots
- [Bug 27381] Basing Object.observe() for IDL objects on internal slots
- [Bug 27381] Basing Object.observe() for IDL objects on internal slots
- [Bug 27381] New: Basing Object.observe() for IDL objects on internal slots
- [Bug 27354] Internal slots
Tuesday, 18 November 2014
- [Bug 27317] Provide explicit guidance on enum value naming
- [Bug 27361] [Unforgeable] and "[[Enumerable]]: true"
- [Bug 27361] New: [Unforgeable] and "[[Enumerable]]: true"
- [Bug 27354] Internal slots
- [Bug 27354] Internal slots
- [Bug 27354] Internal slots
- [Bug 27354] Internal slots
- Re: Determining what prototype should be used for an object
- Re: Determining what prototype should be used for an object
- Re: Determining what prototype should be used for an object
- [Bug 27354] Internal slots
- [Bug 27354] Internal slots
- [Bug 27354] Internal slots
- Re: Determining what prototype should be used for an object
Monday, 17 November 2014
- [Bug 27356] Define [LegacyNewObject]
- [Bug 27354] Internal slots
- [Bug 27356] Define [LegacyNewObject]
- [Bug 27355] Define object creation
- [Bug 24652] Deal with associated global / Realm
- [Bug 27355] Define object creation
- [Bug 27356] New: Define [LegacyNewObject]
- [Bug 27354] Internal slots
- [Bug 27355] New: Define object creation
- [Bug 27354] New: Internal slots
- Re: Determining what prototype should be used for an object
- [Bug 24581] Fix ByteString type & [EnsureUTF16] flag story
- [Bug 20159] Introduce attributes for DOMString coercion
- Re: Determining what prototype should be used for an object
- Re: Determining what prototype should be used for an object
- Re: Determining what prototype should be used for an object
- [Bug 27346] Data properties
- Re: Determining what prototype should be used for an object
- Re: Determining what prototype should be used for an object
- Re: Determining what prototype should be used for an object
- [Bug 27346] Data properties
- Re: Determining what prototype should be used for an object
- Re: Determining what prototype should be used for an object
- RE: Determining what prototype should be used for an object
- [Bug 27346] Data properties
- Re: Determining what prototype should be used for an object
- [Bug 27346] Data properties
- Re: Determining what prototype should be used for an object
- Re: Determining what prototype should be used for an object
- Re: Determining what prototype should be used for an object
- Re: Determining what prototype should be used for an object
- Re: Determining what prototype should be used for an object
- [Bug 27346] Data properties
- [Bug 27346] New: Data properties
- Re: Determining what prototype should be used for an object
Sunday, 16 November 2014
- Re: Determining what prototype should be used for an object
- Re: Determining what prototype should be used for an object
Saturday, 15 November 2014
Friday, 14 November 2014
- Re: Determining what prototype should be used for an object
- Re: Determining what prototype should be used for an object
- Re: Determining what prototype should be used for an object
- Re: Determining what prototype should be used for an object
- Re: Determining what prototype should be used for an object
- Re: Determining what prototype should be used for an object
- Re: Determining what prototype should be used for an object
- Re: Determining what prototype should be used for an object
- Re: Determining what prototype should be used for an object
- Re: Determining what prototype should be used for an object
- Re: Determining what prototype should be used for an object
- Re: Determining what prototype should be used for an object
- Re: Determining what prototype should be used for an object
- Re: Determining what prototype should be used for an object
- Re: WebIDL validity in continuous integration
- Re: Determining what prototype should be used for an object
- WebIDL validity in continuous integration
- Re: Determining what prototype should be used for an object
- RE: Determining what prototype should be used for an object
- [Bug 27062] DOMException constructor should allow name to be supplied
- Determining what prototype should be used for an object
Thursday, 13 November 2014
- [Bug 27317] Provide explicit guidance on enum value naming
- Re: This objects for static methods
- Re: This objects for static methods
- Re: This objects for static methods
- Re: This objects for static methods
- This objects for static methods
- Re: Conventions for composed words in enum
- [Bug 27317] New: Provide explicit guidance on enum value naming
- Re: Conventions for composed words in enum
- Re: Conventions for composed words in enum
- Re: Advice on EventStreams vs. Observables Proposal
- Re: Advice on EventStreams vs. Observables Proposal
- Advice on EventStreams vs. Observables Proposal
Wednesday, 12 November 2014
Tuesday, 11 November 2014
- [Bug 24652] Deal with associated global / Realm
- [Bug 27301] New: Define context variables, such as "context object"
- Vehicle web API
Monday, 10 November 2014
Saturday, 8 November 2014
Thursday, 6 November 2014
Tuesday, 4 November 2014
- [Bug 27237] Need to make it clear that .prototype on an interface object is non-configurable, etc
- [Bug 27237] New: Need to make it clear that .prototype on an interface object is non-configurable, etc
Friday, 31 October 2014
Thursday, 30 October 2014
Monday, 27 October 2014
Saturday, 25 October 2014
- [Bug 27170] Define "name" property (.name) for interface objects
- [Bug 27170] Define "name" property (.name) for interface objects
- [Bug 27170] New: Define "name" property (.name) for interface objects
Monday, 20 October 2014
- [Bug 27110] "typedef (ArrayBufferData or ArrayBuffer) Buffer..."
- [Bug 27110] "typedef (ArrayBufferData or ArrayBuffer) Buffer..."
- [Bug 23369] Provide hooks for Typed Arrays (ArrayBuffer and friends)
- [Bug 27110] New: "typedef (ArrayBufferData or ArrayBuffer) Buffer..."
- [Bug 23369] Provide hooks for Typed Arrays (ArrayBuffer and friends)
Wednesday, 15 October 2014
- [Bug 27062] DOMException constructor should allow name to be supplied
- [Bug 27062] DOMException constructor should allow name to be supplied
- [Bug 27062] New: DOMException constructor should allow name to be supplied
Tuesday, 14 October 2014
- [Bug 27048] Allow partial enums
- [Bug 27048] New: Allow partial enums
- [Bug 17713] Exceptions thrown from event handlers should not be propagated
- Re: Ambient light API redesign
Friday, 10 October 2014
- [Bug 23369] Provide hooks for Typed Arrays (ArrayBuffer and friends)
- [Bug 27008] "Initializing objects from iterables" needs syntax
Thursday, 9 October 2014
- [Bug 27008] "Initializing objects from iterables" needs syntax
- [Bug 27008] "Initializing objects from iterables" needs syntax
- [Bug 27008] "Initializing objects from iterables" needs syntax
- [Bug 27008] "Initializing objects from iterables" needs syntax
- [Bug 27008] "Initializing objects from iterables" needs syntax
- [Bug 23033] Requesting PermissionDeniedError to be added
- [Bug 23033] Requesting PermissionDeniedError to be added
- [Bug 27008] "Initializing objects from iterables" needs syntax
- [Bug 27008] "Initializing objects from iterables" needs syntax
- [Bug 23033] Requesting PermissionDeniedError to be added
- [Bug 23033] Requesting PermissionDeniedError to be added
- [Bug 27008] "Initializing objects from iterables" needs syntax
- [Bug 27008] "Initializing objects from iterables" needs syntax
- [Bug 26517] Methods that return promises are unable to throw exceptions
- [Bug 26190] Sequence and OpenEndedDictionary should be distinguishable
- [Bug 27008] New: "Initializing objects from iterables" needs syntax
Tuesday, 7 October 2014
- [Bug 26517] Methods that return promises are unable to throw exceptions
- [Bug 26517] Methods that return promises are unable to throw exceptions
- [Bug 26517] Methods that return promises are unable to throw exceptions
- [Bug 26517] Methods that return promises are unable to throw exceptions
- [Bug 26517] Methods that return promises are unable to throw exceptions
- [Bug 26517] Methods that return promises are unable to throw exceptions
- [Bug 26517] Methods that return promises are unable to throw exceptions
- [Bug 23682] Fix the current [ArrayClass], [] and sequence<T> mess
Monday, 6 October 2014
- [Bug 23682] Fix the current [ArrayClass], [] and sequence<T> mess
- [Bug 23682] Fix the current [ArrayClass], [] and sequence<T> mess
- [Bug 23682] Fix the current [ArrayClass], [] and sequence<T> mess
- Re: map() annotation for iterables?
- [Bug 26985] Remove requirement for prose around iterable<> if object has indexed properties
- [Bug 26985] Remove requirement for prose around iterable<> if object has indexed properties
- [Bug 26985] Remove requirement for prose around iterable<> if object has indexed properties
- [Bug 26986] New: Rename getter and friends to legacygetter and legacyfriends
- [Bug 26985] New: Remove requirement for prose around iterable<> if object has indexed properties
- [Bug 26984] New: Remove legacyiterable
- [Bug 26980] New: Require that promise rejection are instances of error
- [Bug 26183] make it easier to define an iterator on an interface that iterates over a set of values
Sunday, 5 October 2014
- [Bug 17648] [Awaiting ES6] Add iterators
- [Bug 26973] make iterable declarations' iterator prototype objects inherit from %IteratorPrototype%
- [Bug 23682] Fix the current [ArrayClass], [] and sequence<T> mess
- [Bug 23682] Fix the current [ArrayClass], [] and sequence<T> mess
- Re: map() annotation for iterables?
- [Bug 23682] Fix the current [ArrayClass], [] and sequence<T> mess
- [Bug 23682] Fix the current [ArrayClass], [] and sequence<T> mess
- [Bug 23682] Fix the current [ArrayClass], [] and sequence<T> mess
- [Bug 26973] make iterable declarations' iterator prototype objects inherit from %IteratorPrototype%
- Re: map() annotation for iterables?
- Re: map() annotation for iterables?
- [Bug 26973] make iterable declarations' iterator prototype objects inherit from %IteratorPrototype%
- Re: map() annotation for iterables?
- [Bug 26973] make iterable declarations' iterator prototype objects inherit from %IteratorPrototype%
- [Bug 26183] make it easier to define an iterator on an interface that iterates over a set of values
- [Bug 26973] make iterable declarations' iterator prototype objects inherit from %IteratorPrototype%
- [Bug 26973] New: make iterable declarations' iterator prototype objects inherit from %IteratorPrototype%
- RE: map() annotation for iterables?
Saturday, 4 October 2014
- Re: map() annotation for iterables?
- Re: map() annotation for iterables?
- [Bug 26183] make it easier to define an iterator on an interface that iterates over a set of values
- [Bug 26970] factor out "location of properties that usually go on an interface prototype object" wording
- [Bug 26970] New: factor out "location of properties that usually go on an interface prototype object wording"
- [Bug 26969] New: "Prose accompanying an interface with a pair ite..."
- [Bug 26183] make it easier to define an iterator on an interface that iterates over a set of values
- [Bug 26966] " The result of converting an IDL value of any b..."
- [Bug 26966] New: " The result of converting an IDL value of any b..."
- [Bug 23369] Provide hooks for Typed Arrays (ArrayBuffer and friends)
- map() annotation for iterables?
- [Bug 26183] make it easier to define an iterator on an interface that iterates over a set of values
- [Bug 17648] [Awaiting ES6] Add iterators
- [Bug 17648] [Awaiting ES6] Add iterators
- [Bug 17648] [Awaiting ES6] Add iterators
- [Bug 23367] Move exceptions into IDL
- [Bug 23367] Move exceptions into IDL
- [Bug 23367] Move exceptions into IDL
- [Bug 23367] Move exceptions into IDL
- [Bug 23367] Move exceptions into IDL
Friday, 3 October 2014
- [Bug 26183] make it easier to define an iterator on an interface that iterates over a set of values
- [Bug 23369] Provide hooks for Typed Arrays (ArrayBuffer and friends)
- [Bug 26183] make it easier to define an iterator on an interface that iterates over a set of values
- [Bug 26183] make it easier to define an iterator on an interface that iterates over a set of values
- [Bug 26183] make it easier to define an iterator on an interface that iterates over a set of values
- [Bug 23369] Provide hooks for Typed Arrays (ArrayBuffer and friends)
- [Bug 26183] make it easier to define an iterator on an interface that iterates over a set of values
- [Bug 24581] Fix ByteString type & [EnsureUTF16] flag story
- [Bug 24581] Fix ByteString type & [EnsureUTF16] flag story
- [Bug 26961] Recommend against JavaScript SyntaxError
- [Bug 24581] Fix ByteString type & [EnsureUTF16] flag story
- [Bug 24581] Fix ByteString type & [EnsureUTF16] flag story
- [Bug 26961] Recommend against JavaScript SyntaxError
- [Bug 23367] Move exceptions into IDL
- [Bug 26961] Recommend against JavaScript SyntaxError
- [Bug 24581] Fix ByteString type & [EnsureUTF16] flag story
- [Bug 26961] New: Recommend against JavaScript SyntaxError
- [Bug 23369] Provide hooks for Typed Arrays (ArrayBuffer and friends)
- [Bug 23367] Move exceptions into IDL
- [Bug 26183] make it easier to define an iterator on an interface that iterates over a set of values
- [Bug 26183] make it easier to define an iterator on an interface that iterates over a set of values
- [Bug 26183] make it easier to define an iterator on an interface that iterates over a set of values
Thursday, 2 October 2014
- [Bug 26183] make it easier to define an iterator on an interface that iterates over a set of values
- [Bug 22646] So if we want to say on a per-object basis whether it ought to be exposed to workers (which I think is useful) lets introduce "exposed to document environments", "exposed to worker environments", and [...]
- [Bug 26183] make it easier to define an iterator on an interface that iterates over a set of values
- [Bug 26183] make it easier to define an iterator on an interface that iterates over a set of values
- [Bug 26183] make it easier to define an iterator on an interface that iterates over a set of values
- [Bug 26183] make it easier to define an iterator on an interface that iterates over a set of values
- [Bug 26183] make it easier to define an iterator on an interface that iterates over a set of values
- [Bug 26183] make it easier to define an iterator on an interface that iterates over a set of values
- [Bug 26183] make it easier to define an iterator on an interface that iterates over a set of values
- [Bug 26183] make it easier to define an iterator on an interface that iterates over a set of values
Wednesday, 1 October 2014
- [Bug 23682] Fix the current [ArrayClass], [] and sequence<T> mess
- [Bug 26947] New: Fixed length sequences of varying types
- [Bug 22866] remove Object.prototype.toString override and use ES6 @@toStringTag instead
- [Bug 26183] make it easier to define an iterator on an interface that iterates over a set of values
- [Bug 26945] New: "throw an exception."
- [Bug 26944] New: "not return a value"