Friday, 29 June 2012
Thursday, 28 June 2012
- [Bug 17620] Add steps to convert a sequence of Unicode characters to a DOMString
- [Bug 17620] Add steps to convert a sequence of Unicode characters to a DOMString
- iterators
- Serializer comments
- Re: Handling of objects with both named and indexed properties is probably incorrect
- [Bug 17620] Add steps to convert a sequence of Unicode characters to a DOMString
- Re: An iterable DOM
Wednesday, 27 June 2012
- [Bug 17620] New: Add steps to convert a sequence of Unicode characters to a DOMString
- [Bug 16725] Treat omitted dictionary the same as empty dictionary
Tuesday, 26 June 2012
- [Bug 16725] Treat omitted dictionary the same as empty dictionary
- [Bug 17593] Figure out if something needs to be said about [[Construct]]
- Re: Proposal: Security checks after same-origin revocation with document.domain
- Re: Proposal: Security checks after same-origin revocation with document.domain
- Re: Proposal: Security checks after same-origin revocation with document.domain
Monday, 25 June 2012
- [Bug 17593] Figure out if something needs to be said about [[Construct]]
- Re: Proposal: Security checks after same-origin revocation with document.domain
- Re: Proposal: Security checks after same-origin revocation with document.domain
- Re: Proposal: Security checks after same-origin revocation with document.domain
- Re: Proposal: Security checks after same-origin revocation with document.domain
- [Bug 17593] Figure out if something needs to be said about [[Construct]]
- [Bug 17593] New: Figure out if something needs to be said about [[Construct]]
- Re: [idl] ByteString
- [Bug 16725] Treat omitted dictionary the same as empty dictionary
- Re: Unclear behavior of dictionary member default values
- Re: Why do WebIDL dictionary members not have [TreatNullAs], [TreatUndefinedAs] apply to them?
- [Bug 16725] Treat omitted dictionary the same as empty dictionary
- Re: [idl] ByteString
- Re: [WebIDL] toJSON
Sunday, 24 June 2012
Saturday, 23 June 2012
- Re: [WebIDL] Comments on [Clamp]
- Re: Should Exceptions be Errors in the ECMAScript bindings?
- Re: [idl] ByteString
- Re: Should Exceptions be Errors in the ECMAScript bindings?
- Re: Should Exceptions be Errors in the ECMAScript bindings?
- Re: Should Exceptions be Errors in the ECMAScript bindings?
Friday, 22 June 2012
- Re: Proposal: Security checks after same-origin revocation with document.domain
- Re: [idl] ByteString
- Re: Should Exceptions be Errors in the ECMAScript bindings?
- Re: Should Exceptions be Errors in the ECMAScript bindings?
- Re: Should Exceptions be Errors in the ECMAScript bindings?
- Re: Should Exceptions be Errors in the ECMAScript bindings?
- Re: Should Exceptions be Errors in the ECMAScript bindings?
- Re: Should Exceptions be Errors in the ECMAScript bindings?
- Re: Detecting the "type" of a DOM object
- Re: Should Exceptions be Errors in the ECMAScript bindings?
- Re: Should Exceptions be Errors in the ECMAScript bindings?
- Re: Detecting the "type" of a DOM object
- Re: Detecting the "type" of a DOM object
- Re: [idl] ByteString
- Re: Should Exceptions be Errors in the ECMAScript bindings?
- Re: Should Exceptions be Errors in the ECMAScript bindings?
- [Bug 17435] WebIDL: Bug in definition of whitespace terminal?
- [Bug 17452] WebIDL: at some places in the grammar you probably intend mandatory whitespace
- Re: Should restrictions on attribute types look at flattened member types of unions?
- Re: Why are dictionary-typed attributes not allowed?
- Re: [idl] static attributes
- Re: Distinguishability checking for nullable unions is not correct
- Re: Detecting the "type" of a DOM object
- Re: Detecting the "type" of a DOM object
- Re: Detecting the "type" of a DOM object
Thursday, 21 June 2012
- Re: Detecting the "type" of a DOM object
- Re: announcing normative ECMAScript specification in HTML
- Re: Detecting the "type" of a DOM object
- Re: Detecting the "type" of a DOM object
- Re: Detecting the "type" of a DOM object
- Re: Detecting the "type" of a DOM object
- Re: Detecting the "type" of a DOM object
- Re: Detecting the "type" of a DOM object
- Re: Detecting the "type" of a DOM object
- Re: Detecting the "type" of a DOM object
- Re: Detecting the "type" of a DOM object
- Re: Detecting the "type" of a DOM object
- Re: Detecting the "type" of a DOM object
- Re: Detecting the "type" of a DOM object
- Re: Detecting the "type" of a DOM object
- Re: Detecting the "type" of a DOM object
- Re: Detecting the "type" of a DOM object
- Re: Detecting the "type" of a DOM object
- Re: Detecting the "type" of a DOM object
- Re: Detecting the "type" of a DOM object
- Re: Detecting the "type" of a DOM object
- [Bug 16767] Allow user objects for Array[] types
- Re: Detecting the "type" of a DOM object
- Re: Detecting the "type" of a DOM object
- Re: Can callback interfaces have consequential interfaces?
- Re: Can callback interfaces have consequential interfaces?
- Re: Detecting the "type" of a DOM object
- Re: Detecting the "type" of a DOM object
- Re: Should restrictions on attribute types look at flattened member types of unions?
- Re: Detecting the "type" of a DOM object
- FYI: API design discussions in WebRTC
- Re: Detecting the "type" of a DOM object
- Re: Detecting the "type" of a DOM object
- [Bug 17531] Exceptions: rename type to name
- Re: Should restrictions on attribute types look at flattened member types of unions?
- Re: An iterable DOM
- Re: An iterable DOM
- [Bug 17561] typo in normative references
- [Bug 17561] typo in normative references
Wednesday, 20 June 2012
- [Bug 17561] New: typo in normative references
- [Bug 17560] readonly binding unspecified for ECMAScript
- [Bug 17560] readonly binding unspecified for ECMAScript
- [Bug 17560] New: readonly binding unspecified for ECMAScript
- Re: An iterable DOM
- Re: Question about implements statements
- Re: [TreatNonCallableAsNull] extended attribute
- RE: Question about implements statements
- Re: An iterable DOM
- [Bug 16767] Allow user objects for Array[] types
- Re: Question about implements statements
- Re: Should non-callback interfaces be allowed to inherit from callback interfaces?
- [Bug 16832] Don't get the length property off platform objects with indexed properties
- [Bug 16832] Don't get the length property off platform objects with indexed properties
- [Bug 16832] Don't get the length property off platform objects with indexed properties
- [Bug 16832] Don't get the length property off platform objects with indexed properties
- [Bug 16767] Allow user objects for Array[] types
- [Bug 16767] Allow user objects for Array[] types
- [Bug 16767] Allow user objects for Array[] types
- Re: [TreatNonCallableAsNull] extended attribute
- branching the Web IDL spec out for v2
Tuesday, 19 June 2012
- An iterable DOM
- Re: Question about implements statements
- RE: Question about implements statements
- Should restrictions on attribute types look at flattened member types of unions?
- Re: Question about implements statements
Monday, 18 June 2012
- Re: Question about implements statements
- RE: Question about implements statements
- [Bug 17531] Exceptions: rename type to name
- Distinguishability checking for nullable unions is not correct
- [Bug 17531] New: Exceptions: rename type to name
Friday, 15 June 2012
- Re: Question about implements statements
- RE: Question about implements statements
- Question about implements statements
- Handling of objects with both named and indexed properties is probably incorrect
Thursday, 14 June 2012
- Can callback interfaces have consequential interfaces?
- Should non-callback interfaces be allowed to inherit from callback interfaces?
Tuesday, 12 June 2012
Monday, 11 June 2012
Sunday, 10 June 2012
Saturday, 9 June 2012
- Re: Unclear behavior of dictionary member default values
- [Bug 17452] New: WebIDL: at some places in the grammar you probably intend mandatory whitespace
- Re: Unclear behavior of dictionary member default values
Friday, 8 June 2012
- Re: Unclear behavior of dictionary member default values
- Re: Unclear behavior of dictionary member default values
- Re: Unclear behavior of dictionary member default values
- Re: Unclear behavior of dictionary member default values
- Re: Unclear behavior of dictionary member default values
- Re: Unclear behavior of dictionary member default values
- Re: Unclear behavior of dictionary member default values
- Re: Unclear behavior of dictionary member default values
- Re: Unclear behavior of dictionary member default values
- Re: Unclear behavior of dictionary member default values
- Unclear behavior of dictionary member default values
Thursday, 7 June 2012
- Re: Detecting the "type" of a DOM object
- RE: [WebIDL] toJSON
- [idl] ByteString
- Re: Why are dictionary-typed attributes not allowed?
- Re: Why do WebIDL dictionary members not have [TreatNullAs], [TreatUndefinedAs] apply to them?
- Re: Why are dictionary-typed attributes not allowed?
- Re: Why are dictionary-typed attributes not allowed?
- Re: Why do WebIDL dictionary members not have [TreatNullAs], [TreatUndefinedAs] apply to them?
- Re: Why are dictionary-typed attributes not allowed?
- Re: Why do WebIDL dictionary members not have [TreatNullAs], [TreatUndefinedAs] apply to them?
- Re: Why are dictionary-typed attributes not allowed?
- Re: Detecting the "type" of a DOM object
- [Bug 17435] WebIDL: Bug in definition of whitespace terminal?
- [Bug 17435] New: WebIDL: Bug in definition of whitespace terminal?
- Re: Why do WebIDL dictionary members not have [TreatNullAs], [TreatUndefinedAs] apply to them?
- Re: Detecting the "type" of a DOM object
- Re: Question about diamond-shaped patterns formed by "implements"
- Re: Why do WebIDL dictionary members not have [TreatNullAs], [TreatUndefinedAs] apply to them?
- Re: Why are dictionary-typed attributes not allowed?
- Re: Why are dictionary-typed attributes not allowed?
- Why are dictionary-typed attributes not allowed?
- Why do WebIDL dictionary members not have [TreatNullAs], [TreatUndefinedAs] apply to them?
Wednesday, 6 June 2012
- Re: variable declarations shadowing named properties on window
- Question about diamond-shaped patterns formed by "implements"
- Re: Detecting the "type" of a DOM object
- Re: Detecting the "type" of a DOM object
- Re: [WebIDL] toJSON
- Detecting the "type" of a DOM object
- Re: [WebIDL] toJSON
- Re: [WebIDL] toJSON
Saturday, 2 June 2012
Friday, 1 June 2012
Thursday, 31 May 2012
- Re: announcing normative ECMAScript specification in HTML
- Re: [WebIDL] toJSON
- Re: [WebIDL] toJSON
- Re: [WebIDL] toJSON
- Re: [WebIDL] toJSON
Wednesday, 30 May 2012
- Re: [WebIDL] toJSON
- RE: [WebIDL] toJSON
- Re: [WebIDL] toJSON
- Re: [WebIDL] toJSON
- RE: [WebIDL] toJSON
- [WebIDL] toJSON
Friday, 25 May 2012
Thursday, 24 May 2012
- Re: announcing normative ECMAScript specification in HTML
- Re: announcing normative ECMAScript specification in HTML
- Re: announcing normative ECMAScript specification in HTML
- Re: announcing normative ECMAScript specification in HTML
- announcing normative ECMAScript specification in HTML
Wednesday, 9 May 2012
Monday, 14 May 2012
Saturday, 12 May 2012
Friday, 11 May 2012
Wednesday, 9 May 2012
Monday, 7 May 2012
Friday, 4 May 2012
Friday, 27 April 2012
- Re: Should Exceptions be Errors in the ECMAScript bindings?
- Re: Should Exceptions be Errors in the ECMAScript bindings?
- Re: [Public WebGL] Should WebGLContextAttributes be a callback interface?
Thursday, 26 April 2012
- [Bug 16725] Treat omitted dictionary the same as empty dictionary
- [Bug 16725] Treat omitted dictionary the same as empty dictionary
Wednesday, 25 April 2012
Tuesday, 24 April 2012
- [Bug 16833] consider always exposing a "length" property for objects with indexed properties
- [Bug 16832] Don't get the length property off platform objects with indexed properties
- [Bug 16832] New: Don't get the length property off platform objects with indexed properties
Thursday, 19 April 2012
- [Bug 16767] Allow user objects for Array[] types
- [IDL] rationale for undefined -> null in nullable types
Wednesday, 18 April 2012
- Re: Should Exceptions be Errors in the ECMAScript bindings?
- Re: Should Exceptions be Errors in the ECMAScript bindings?
- RE: Should Exceptions be Errors in the ECMAScript bindings?
- [Bug 16767] Allow user objects for Array[] types
- Re: WebIDL test suite time
- Should Exceptions be Errors in the ECMAScript bindings?
- Re: WebIDL test suite time
- [Bug 16767] Allow user objects for Array[] types
- Re: WebIDL test suite time
- Re: WebIDL test suite time
- WebIDL test suite time
- [Bug 16767] Allow user objects for Array[] types
- [Bug 16767] New: Allow user objects for Array[] types
Tuesday, 17 April 2012
Monday, 16 April 2012
Friday, 13 April 2012
Monday, 16 April 2012
Saturday, 14 April 2012
- Re: Named constant as default value
- Named constant as default value
- [Bug 16720] Strange ordering in 4.2.25. Union types
- Re: Nullable union types containing other nullable types
- Re: Nullable union types containing other nullable types
- [Bug 16725] Treat omitted dictionary the same as empty dictionary
- [Bug 16720] Strange ordering in 4.2.25. Union types
- Re: Proposal: Security checks after same-origin revocation with document.domain
Friday, 13 April 2012
- Re: Proposal: Security checks after same-origin revocation with document.domain
- Re: Proposal: Security checks after same-origin revocation with document.domain
- Re: Proposal: Security checks after same-origin revocation with document.domain
- [Bug 16725] New: Treat omitted dictionary the same as empty dictionary
- [Bug 16720] New: Strange ordering in 4.2.25. Union types
Thursday, 12 April 2012
Wednesday, 11 April 2012
- Nullable union types containing other nullable types
- Re: regrets for this week
- regrets for this week
Tuesday, 10 April 2012
- Re: Invoking methods with optional arguments with no default values specified
- Re: Overload resolution algorithm applies default values before it knows how many it will need
- Re: Invoking methods with optional arguments with no default values specified
- Re: [Public WebGL] Re: WebGL IDL for uniform1fv is not valid WebIDL
Monday, 9 April 2012
- Re: [Public WebGL] Re: WebGL IDL for uniform1fv is not valid WebIDL
- Re: WebGL IDL for uniform1fv is not valid WebIDL
- Invoking methods with optional arguments with no default values specified
- Overload resolution algorithm applies default values before it knows how many it will need
- Re: [XHR] Constructor behavior seems to be underdefined
- Re: [Public WebGL] Should WebGLContextAttributes be a callback interface?
- Re: [Public WebGL] Should WebGLContextAttributes be a callback interface?
- Re: [Public WebGL] Should WebGLContextAttributes be a callback interface?
- Re: [Public WebGL] Should WebGLContextAttributes be a callback interface?
- Re: [Public WebGL] Should WebGLContextAttributes be a callback interface?
- Re: [Public WebGL] Should WebGLContextAttributes be a callback interface?
- Re: [Public WebGL] Should WebGLContextAttributes be a callback interface?
- Re: [webidl] Unions involving a primitive and a string don't make any sense
- Re: WebGL IDL for uniform1fv is not valid WebIDL
- Re: WebGL IDL for uniform1fv is not valid WebIDL
- Re: [Public WebGL] Re: WebGL IDL for uniform1fv is not valid WebIDL
- Re: Unrestricted float
Sunday, 8 April 2012
- [Bug 16618] Use "-" instead of "−"
- [Bug 16609] Do we need exception inheritance?
- [Bug 16647] CR exit criteria should explicitly list features "at risk"
- Re: Unrestricted float
Saturday, 7 April 2012
Friday, 6 April 2012
- Re: Unrestricted float
- Re: Unrestricted float
- Re: Unrestricted float
- Re: Unrestricted float
- Re: Unrestricted float
- Re: Unrestricted float
- Re: Unrestricted float
- [Bug 16609] Do we need exception inheritance?
- [Bug 16607] Errors in type conversion to nullable types
- [Bug 16647] New: CR exit criteria should explicitly list features "at risk"
- [Bug 16604] RFE: add unsigned byte as synonym for octet
- [Bug 16604] RFE: add unsigned byte as synonym for octet
- [Bug 16607] Errors in type conversion to nullable types
- [Bug 16609] Do we need exception inheritance?
- Re: Arrays in WebIDL aren't making sense to me so far
- Re: [Public WebGL] Re: Should WebGL's getSupportedExtensions return an array or a sequence?
Thursday, 5 April 2012
Wednesday, 4 April 2012
- Re: [Public WebGL] Re: Should WebGL's getSupportedExtensions return an array or a sequence?
- [Bug 16604] RFE: add unsigned byte as synonym for octet
- [Bug 16604] RFE: add unsigned byte as synonym for octet
- Re: [XHR] Constructor behavior seems to be underdefined
Tuesday, 3 April 2012
- [Bug 16604] RFE: add unsigned byte as synonym for octet
- [Bug 16604] RFE: add unsigned byte as synonym for octet
- Re: [Public WebGL] Re: WebGL IDL for uniform1fv is not valid WebIDL
- [Bug 16604] RFE: add unsigned byte as synonym for octet
- [Bug 16618] Use "-" instead of "−"
- [Bug 16618] Use "-" instead of "−"
- [Bug 16618] Use "-" instead of "−"
- [Bug 16618] New: Use "-" instead of "−"
- Re: Unrestricted float
- Re: Unrestricted float
- Re: Unrestricted float
- Unrestricted float
- Re: Arrays in WebIDL aren't making sense to me so far
- Re: [Public WebGL] Re: WebGL IDL for uniform1fv is not valid WebIDL
- [Bug 16609] Do we need exception inheritance?
- [Bug 16609] New: Do we need exception inheritance?
- [Bug 16607] New: Errors in type conversion to nullable types
- [Bug 16604] RFE: add unsigned byte as synonym for octet
- Re: [Public WebGL] Should WebGLContextAttributes be a callback interface?
- Re: [Public WebGL] Re: WebGL IDL for uniform1fv is not valid WebIDL
- Re: Arrays in WebIDL aren't making sense to me so far
- Re: Arrays in WebIDL aren't making sense to me so far
- Re: [XHR] Constructor behavior seems to be underdefined
- Re: WebGL IDL for uniform1fv is not valid WebIDL
- Re: Can typed arrays be platform array objects for numeric types?
Monday, 2 April 2012
- Re: Can typed arrays be platform array objects for numeric types?
- Re: Should WebGL's getSupportedExtensions return an array or a sequence?
- Re: Arrays in WebIDL aren't making sense to me so far
- Re: WebGL IDL for uniform1fv is not valid WebIDL
- Re: [XHR] Constructor behavior seems to be underdefined
- Re: [XHR] Constructor behavior seems to be underdefined
- Re: [XHR] Constructor behavior seems to be underdefined
- Re: [XHR] Constructor behavior seems to be underdefined
- Re: [XHR] Constructor behavior seems to be underdefined
- Re: [XHR] Constructor behavior seems to be underdefined
- [Bug 16604] New: RFE: add unsigned byte as synonym for octet
- Can typed arrays be platform array objects for numeric types?
- Should WebGL's getSupportedExtensions return an array or a sequence?
- Arrays in WebIDL aren't making sense to me so far
- WebGL IDL for uniform1fv is not valid WebIDL
- Re: [XHR] Constructor behavior seems to be underdefined
- Re: [XHR] Constructor behavior seems to be underdefined
- Re: [webidl] Unions involving a primitive and a string don't make any sense
- Re: [XHR] Constructor behavior seems to be underdefined
- Re: [XHR] Constructor behavior seems to be underdefined
- Re: [XHR] Constructor behavior seems to be underdefined
- Re: [XHR] Constructor behavior seems to be underdefined
- Re: [Public WebGL] Should WebGLContextAttributes be a callback interface?
- Re: [Public WebGL] Should WebGLContextAttributes be a callback interface?
Sunday, 1 April 2012
- Re: [Public WebGL] Should WebGLContextAttributes be a callback interface?
- Re: [Public WebGL] Should WebGLContextAttributes be a callback interface?
- Re: Should binding section be rewritten more algorithmically?
- Re: Should binding section be rewritten more algorithmically?
- RE: [XHR] Constructor behavior seems to be underdefined