Tuesday, 30 June 2009
- Re: Web IDL syntax
- Re: File API Feedback
- Re: File API Feedback
- [WebIDL] Bugs in DOMString conversion to Unichode characters (was Re: "send data using the Web Socket" and UCS-2)
- Re: File API Feedback
- Re: [WebStorage] Property enumeration and checking presence
- Re: File API Feedback
- Re: Web IDL syntax
- Re: Web IDL syntax
- Re: http://dev.w3.org/2006/waf/widgets/#reserved-file-and-folder-names
- Re: File API Feedback
- Re: [WebStorage] Property enumeration and checking presence
- Re: [WebIDL] Callback, PropertyOnly, NoInterfaceObject
- Re: [WebStorage] Property enumeration and checking presence
- Re: [WebStorage] Property enumeration and checking presence
- RE: [WebIDL] Callback, PropertyOnly, NoInterfaceObject
- Re: [cors] Additional Comments on 17 March 2009 cors draft
- [cors] Comments on 17 March 2009
- Re: [WebIDL] Callback, PropertyOnly, NoInterfaceObject
- Re: http://dev.w3.org/2006/waf/widgets/#reserved-file-and-folder-names
- Re: A+E todo
- Re: File API Feedback
- Re: File API Feedback
- RE: [WebIDL] Callback, PropertyOnly, NoInterfaceObject
- Re: [widgets] Verify Zip archive
- Re: [widgets] Rule for finding a file within a widget package
- Re: File API Feedback
- Re: [widgets] Rule for Identifying the media type of a file
- [WebIDL] grammar in ABNF
- [webstorage] deleting a database
- Re: File API Feedback
- Re: Widgets PAG seeks feedback on Widget Updates spec
- Re: File API Feedback
- Re: File API Feedback
- Re: [widgets] P&C LC comments on I18N/L10N
- Re: An import statement for Web IDL
- Re: Web IDL syntax
- Re: File API Feedback
- Re: An import statement for Web IDL
- Re: An import statement for Web IDL
- Re: An import statement for Web IDL
- Re: Fw: An import statement for Web IDL
- Re: An import statement for Web IDL
- Fw: An import statement for Web IDL
Monday, 29 June 2009
- Re: Widgets PAG seeks feedback on Widget Updates spec
- Widgets PAG seeks feedback on Widget Updates spec
- Re: File API Feedback
- [WebStorage] Property enumeration and checking presence
- A+E todo
- Re: [widgets] editorial style
- RE: [widgets] P&C LC#2 comment regarding icons
- Re: [widgets] Rule for extracting file data from a file entry
- Re: [widgets] P&C LC, general comments
- Re: [widgets] Editorial: 9x Processing
- RE: Feature names: Typo in example
- [widgets] P&C comments, 8
Friday, 26 June 2009
Monday, 29 June 2009
- Re: [widgets] P&C LC#2 comment regarding icons
- Re: [widgets] P&C LC comments on I18N/L10N
- Re: Feature names: Typo in example
- Re: An import statement for Web IDL
- An import statement for Web IDL
- Re: Specs using Web IDL
Sunday, 28 June 2009
- Re: Do we need to rename the Origin header?
- Re: Specs using Web IDL
- Re: Specs using Web IDL
- Re: Specs using Web IDL
- Re: Specs using Web IDL
- Re: Specs using Web IDL
- Re: Specs using Web IDL
Saturday, 27 June 2009
- Re: File API Feedback
- Re: Specs using Web IDL
- Re: Points of order on this WG
- Re: Points of order on this WG
- Re: Points of order on this WG
- Re: Specs using Web IDL
- Re: File API Feedback
- Re: XHR and sandboxed iframes
- Specs using Web IDL
- Re: [WebIDL] "module" in ECMAScript
- Re: XHR and sandboxed iframes (was: Re: XHR without user credentials)
- Re: Handling too few arguments in method calls
- Re: Points of order on this WG
- Re: Points of order on this WG
- Re: Berkeley DB license (was Re: Points of order on this WG)
Friday, 26 June 2009
- Re: Berkeley DB license (was Re: Points of order on this WG)
- Re: XHR and sandboxed iframes (was: Re: XHR without user credentials)
- Re: Berkeley DB license (was Re: Points of order on this WG)
- Re: Berkeley DB license (was Re: Points of order on this WG)
- Re: Berkeley DB license (was Re: Points of order on this WG)
- Re: XHR and sandboxed iframes (was: Re: XHR without user credentials)
- Re: Berkeley DB license (was Re: Points of order on this WG)
- Re: Points of order on this WG
- Berkeley DB license (was Re: Points of order on this WG)
- Re: XHR and sandboxed iframes (was: Re: XHR without user credentials)
- Re: Points of order on this WG
- Re: Points of order on this WG
- Re: Points of order on this WG
- Re: Points of order on this WG
- Re: Berkeley DB (was: Points of order on this WG)
- Re: Points of order on this WG
- Re: Points of order on this WG
- Re: Points of order on this WG
- Re: Points of order on this WG
- Re: Points of order on this WG
- Re: [widgets] dig sig RelaxNG schema
- Re: [widgets] dig sig RelaxNG schema
- RE: Points of order on this WG
- Re: Points of order on this WG
- Re: Points of order on this WG
- Re: Points of order on this WG
- Re: Points of order on this WG
- Re: Points of order on this WG
- RE: [WebIDL] Callback, PropertyOnly, NoInterfaceObject
- Re: Points of order on this WG
- RE: Points of order on this WG
- Re: Berkeley DB (was: Points of order on this WG)
- Berkeley DB (was: Points of order on this WG)
- Re: Points of order on this WG
- Re: Points of order on this WG
- Re: Points of order on this WG
- Re: Handling too few arguments in method calls
- Re: Points of order on this WG
- Re: Handling too few arguments in method calls
- Re: Handling too few arguments in method calls
- Re: Handling too few arguments in method calls
- Re: [WebIDL] Callback, PropertyOnly, NoInterfaceObject
- Re: Points of order on this WG
Thursday, 25 June 2009
- Re: Points of order on this WG
- Re: Points of order on this WG
- Re: Do we need to rename the Origin header?
- Re: Points of order on this WG
- Re: Points of order on this WG
- Re: [widgets] dig sig RelaxNG schema
- Re: Points of order on this WG
- Re: Points of order on this WG
- Re: Handling too few arguments in method calls
- Re: Points of order on this WG
- Re: Handling too few arguments in method calls
- Re: [widgets] Draft Minutes from 25 June 2009 Voice Conference
- Re: Points of order on this WG
- Re: Do we need to rename the Origin header?
- Belated Regretts for telcon.
- Re: File API Feedback
- [widgets] Draft Minutes from 25 June 2009 Voice Conference
- Re: File API Feedback
- AppCache to Widget Converter
- [widgets] dig sig RelaxNG schema
- [WebIDL] Callback, PropertyOnly, NoInterfaceObject
- Re: Do we need to rename the Origin header?
- Re: Handling too few arguments in method calls
- Re: Handling too few arguments in method calls
- Re: Do we need to rename the Origin header?
- Re: Points of order on this WG
- Re: Points of order on this WG
- Re: Points of order on this WG
- Re: [cors] TAG request concerning CORS & Next Step(s)
- Re: Points of order on this WG
- Re: [cors] TAG request concerning CORS & Next Step(s)
- RE: [cors] TAG request concerning CORS & Next Step(s)
- Re: Do we need to rename the Origin header?
- Re: Do we need to rename the Origin header?
- Re: [cors] TAG request concerning CORS & Next Step(s)
- Re: [cors] TAG request concerning CORS & Next Step(s)
- Re: [cors] TAG request concerning CORS & Next Step(s)
- Re: [cors] TAG request concerning CORS & Next Step(s)
- Re: Points of order on this WG
- RE: [cors] TAG request concerning CORS & Next Step(s)
- Re: [cors] TAG request concerning CORS & Next Step(s)
- Re: 'scroll' and 'resize' events
- Re: 'scroll' and 'resize' events
- Re: Do we need to rename the Origin header?
- Re: [cors] TAG request concerning CORS & Next Step(s)
- Re: [cors] TAG request concerning CORS & Next Step(s)
- Re: Do we need to rename the Origin header?
- Re: [cors] TAG request concerning CORS & Next Step(s)
- Points of order on this WG
- Re: dev.w3.org CVS access [was: Why I don't attend the weekly teleconference]
Wednesday, 24 June 2009
- Re: [cors] TAG request concerning CORS & Next Step(s)
- Re: [cors] TAG request concerning CORS & Next Step(s)
- Re: [cors] TAG request concerning CORS & Next Step(s)
- Re: [cors] TAG request concerning CORS & Next Step(s)
- RE: [cors] TAG request concerning CORS & Next Step(s)
- Re: [cors] TAG request concerning CORS & Next Step(s)
- Re: [cors] TAG request concerning CORS & Next Step(s)
- Re: [cors] TAG request concerning CORS & Next Step(s)
- Re: [cors] TAG request concerning CORS & Next Step(s)
- Re: [cors] TAG request concerning CORS & Next Step(s)
- Re: [cors] TAG request concerning CORS & Next Step(s)
- Re: [cors] TAG request concerning CORS & Next Step(s)
- Re: [cors] TAG request concerning CORS & Next Step(s)
- Re: [cors] TAG request concerning CORS & Next Step(s)
- Re: [widgets] [preference element] question on the value attribute
- Re: [widgets] [preference element] question on the value attribute
- Re: [widgets] [preference element] question on the value attribute
- Re: [cors] TAG request concerning CORS & Next Step(s)
- Re: [widgets] Draft Agenda for 25 June 2009 Voice Conference
- Re: Exit criteria Re: [selectors-api] Transitioning to CR
- Leaving WebApps (was RE: [widgets] Draft Agenda for 25 June 2009 Voice Conference)
- Exit criteria Re: [selectors-api] Transitioning to CR
- Re: [selectors-api] Transitioning to CR
- [widgets] Draft Agenda for 25 June 2009 Voice Conference
- Re: [widgets] [preference element] question on the value attribute
- [cors] TAG request concerning CORS & Next Step(s)
- dev.w3.org CVS access [was: Why I don't attend the weekly teleconference]
- Re: Why I don't attend the weekly teleconference (Was: Input on the agenda)
Tuesday, 23 June 2009
- Re: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- Re: [widgets] [preference element] question on the value attribute
- Re: [XHR] XMLHttpRequest name
- Re: Request for comments: Delivery Context Ontology Last Call; Deadline 7 Aug 2009
- Re: [widgets] [preference element] question on the value attribute
- Request for comments: Delivery Context Ontology Last Call; Deadline 7 Aug 2009
- Re: [XHR] XMLHttpRequest name
- [widgets] [preference element] question on the value attribute
- Re: [XHR] XMLHttpRequest name
- Re: [XHR] XMLHttpRequest name
- Re: [XHR] XMLHttpRequest name
- Alpha Widget checker
- Re: [XHR] XMLHttpRequest name
- [XHR] XMLHttpRequest name
- Re: [widgets] Please include a statement of purpose and user interaction expectations for <feature>
- Re: [widgets] Please include a statement of purpose and user interaction expectations for <feature>
- Re: [widgets] Please include a statement of purpose and user interaction expectations for <feature>
- Re: Web IDL syntax
- Re: Handling too few arguments in method calls
- Re: Web IDL syntax
- Re: Handling too few arguments in method calls
- Re: [cors] Review
- Re: Handling too few arguments in method calls
- Re: [cors] Review
Monday, 22 June 2009
- Re: [PrototypeRoot]
- Re: [cors] Review
- Re: [cors] Review
- Re: [cors] Review
- Re: [cors] Review
- Re: [cors] Review
- Re: [cors] Review
- Re: [cors] Review
- Re: [cors] Review
- Re: [cors] Review
- RE: [webstorage] Ambiguous Requirement for Key Ordering
- Re: [widgets] Please include a statement of purpose and user interaction expectations for <feature>
Wednesday, 17 June 2009
Friday, 19 June 2009
Thursday, 18 June 2009
Monday, 22 June 2009
- Re: Request for Comments: FPWD of Widgets 1.0: URI Scheme spec
- Re: Handling too few arguments in method calls
- Re: Handling too few arguments in method calls
- Re: Progress Events normative text
- Re: Input events, checkboxes and radio buttons
- Re: [PrototypeRoot]
- Handling too few arguments in method calls
Sunday, 21 June 2009
- Widgets 1.0: Packaging and Configuration LCWD review
- Re: [selectors-api] Return value of lookupNamespaceURI
- Re: Input events, checkboxes and radio buttons
Saturday, 20 June 2009
- Re: Do we need to rename the Origin header?
- Re: Progress Events normative text
- Re: Do we need to rename the Origin header?
- Re: [selectors-api] Transitioning to CR
- Re: [NameCreator] definition buggy
- Re: Input events, checkboxes and radio buttons
- Re: Input events, checkboxes and radio buttons
- Re: [selectors-api] Transitioning to CR
- Re: [PrototypeRoot]
- Re: [PrototypeRoot]
- Re: [PrototypeRoot]
- Re: [PrototypeRoot]
- Re: [PrototypeRoot]
- Re: [PrototypeRoot]
- Re: [webidl] DOMString
Friday, 19 June 2009
- Re: File API Feedback
- Re: File API Feedback
- Re: File API Feedback
- Re: File API Feedback
- Input events, checkboxes and radio buttons
- Reminder: Public call for prior art on Widget updates
- Re: [selectors-api] Transitioning to CR
- Re: [selectors-api] Transitioning to CR
- Re: [selectors-api] Transitioning to CR
- Re: [selectors-api] Transitioning to CR
- Re: [selectors-api] Transitioning to CR
- Re: [selectors-api] Transitioning to CR
- Re: Web IDL syntax
- Re: File API Feedback
- Re: File API Feedback
- Re: File API, Editor's Draft II
- RE: Web IDL syntax
- Re: [selectors-api] Transitioning to CR
- Re: File API Feedback
- Re: Web IDL syntax
- Re: File API Feedback
- Re: Request for Comments: FPWD of Widgets 1.0: URI Scheme spec
- Re: [bindings] Regarding the algorithm of 4.2.2. Interface prototype object
- Re: [Bindings] [[Delete]], hidden operations, missing arguments
- Re: Web IDL syntax
- Re: Web IDL syntax
- Web IDL syntax
- Re: File API Feedback
- RE: File API Feedback
- Re: File API Feedback
- Re: [WebIDL] On overloaded operations in an effective overload set
- Re: [WebIDL] overloading and fallback
- Re: File API Feedback
- Re: File API Feedback
Thursday, 18 June 2009
- Re: "W3C and APIs" writeup from TAG members
- "W3C and APIs" writeup from TAG members
- July 2008 f2f meeting minutes now publicly accessible
- Re: File API Feedback
- Re: File API Feedback
- Re: File API Feedback
- Re: widgets spec
- Re: File API, Editor's Draft II
- Re: File API - W3C Working Draft 7 June 2009
- File API Feedback
- Re: Progress Events normative text
- widgets spec
- widgets feedback
- widgets feedback
- Request for Comments: FPWD of Widgets 1.0: Access Requests Policy spec
- Request for Comments: FPWD of Widgets 1.0: URI Scheme spec
- [widgets] Draft Minutes from 18 June 2009 Voice Conference
- widgets feedback
- widgets feedback
- Fwd: Chat with Marcos Caceres
- RE: [widgets] RE: P&C Last Call comments 1..7+
- Re: [widgets] RE: P&C Last Call comments 1..7+
- [widgets] RE: P&C Last Call comments 1..7+
- Re: XHR and sandboxed iframes (was: Re: XHR without user credentials)
- Re: [cors] Review
- Re: XHR and sandboxed iframes (was: Re: XHR without user credentials)
- Re: XHR and sandboxed iframes (was: Re: XHR without user credentials)
- Re: XHR and sandboxed iframes (was: Re: XHR without user credentials)
- Re: [cors] Review
- Re: XHR and sandboxed iframes (was: Re: XHR without user credentials)
- Re: [cors] Review
- Re: XHR and sandboxed iframes (was: Re: XHR without user credentials)
- Re: [cors] Review
Wednesday, 17 June 2009
- Re: XHR and sandboxed iframes (was: Re: XHR without user credentials)
- Re: [cors] Review
- Re: XHR and sandboxed iframes (was: Re: XHR without user credentials)
- Re: XHR and sandboxed iframes (was: Re: XHR without user credentials)
- Re: [cors] Review
- Re: XHR and sandboxed iframes (was: Re: XHR without user credentials)
- Re: [cors] Review
- Re: [cors] Review
- Re: [cors] Review
- Re: XHR and sandboxed iframes (was: Re: XHR without user credentials)
- Re: [cors] Review
- Re: XHR and sandboxed iframes
- Re: XHR and sandboxed iframes (was: Re: XHR without user credentials)
- Re: [cors] Review
- Re: XHR and sandboxed iframes (was: Re: XHR without user credentials)
- Re: [cors] Review
- Touch and gestures events
- Re: [cors] Review
- Re: XHR and sandboxed iframes (was: Re: XHR without user credentials)
- Re: Dated URI for "Widgets 1.0: URI Scheme" seems to be broken
- Re: 'scroll' and 'resize' events
- Re: [widgets] Public keys in widgets URI scheme?
- Interaction events (Was: 'scroll' and 'resize' events)
- Re: 'scroll' and 'resize' events
- Re: Dated URI for "Widgets 1.0: URI Scheme" seems to be broken
- Re: [cors] Review
- Re: Dated URI for "Widgets 1.0: URI Scheme" seems to be broken
- Dated URI for "Widgets 1.0: URI Scheme" seems to be broken
- Re: [cors] Review
- Re: [cors] Review
- Events Re: 'scroll' and 'resize' events
- RE: [widgets] P&C Last Call comments, 7
- Re: [widgets] P&C Last Call comments, 7
- Re: [widgets] Draft Minutes from 10 June 2009 f2f meeting
- Re: Comments on Widgets spec
- Re: [P&C] Definitions: installation, instantiation
- RE: [P&C] Definitions: installation, instantiation
- Re: [P&C] Definitions: installation, instantiation
- RE: [widgets] P&C Last Call comments, zip-rel-path ABNF
- [P&C] Definitions: installation, instantiation
- Re: [widgets] P&C Last Call comments, zip-rel-path ABNF
- Re: [cors] Review
- Regrets for Thrusday's Widgets call /eom
- Re: 'scroll' and 'resize' events
- Re: [cors] origin and redirects
- Re: XHR and sandboxed iframes (was: Re: XHR without user credentials)
- Re: XHR and sandboxed iframes (was: Re: XHR without user credentials)
- Re: [widgets] Public keys in widgets URI scheme?
- Re: Progress Events normative text
- [widgets] P&C Last Call Period
- Re: [widgets] P&C LC, general comments
- [selectors-api] Transitioning to CR
- XHR and sandboxed iframes (was: Re: XHR without user credentials)
- [widgets] Draft Agenda for 18 June 2009 Voice Conference
- Re: [WebIDL] overloading and fallback
- Re: [webidl] DOMString
- Re: [WebIDL] On overloaded operations in an effective overload set
- Re: [WebIDL] On overloaded operations in an effective overload set
- Re: 'scroll' and 'resize' events
- Re: [WebIDL] On overloaded operations in an effective overload set
- [widgets] conformance requirements review
- Re: [cors] Review
Tuesday, 16 June 2009
Wednesday, 17 June 2009
- Re: [cors] Web application
- 'scroll' and 'resize' events
- Re: [cors] Web application
- Re: [webidl] DOMString
- Re: [WebIDL] On overloaded operations in an effective overload set
- Re: [WebIDL] overloading and fallback
- Re: "send data using the Web Socket" and UCS-2
- Re: [cors] Review
- Agenda:DOM3 Events Telcon
- Re: [cors] Review
- Re: XBL2 Status?
Tuesday, 16 June 2009
- Re: XHR without user credentials
- Re: XBL2 Status?
- Re: [cors] Web application
- RE: [cors] Web application
- Re: [widgets] Public keys in widgets URI scheme?
- Re: [cors] origin and redirects
- ISSUE-91: Origin and redirects [CORS]
- [cors] origin and redirects
- Re: [cors] Review
- ISSUE-90: Exposing more (~infinite) response headers [CORS]
- Re: [widgets] P&C LC, general comments
- [widgets] Specifying the view modes
- Re: [widgets] P&C Last Call comments, viewmodes, referencing other specs, guarantee of consistency
- Re: [widgets] Please include a statement of purpose and user interaction expectations for <feature>
- RE: [widgets] P&C Last Call comments, interoperability
- Re: [widgets] P&C Last Call comments, interoperability
- RE: [widgets] P&C Last Call comments, interoperability
- Re: [widgets] P&C Last Call comments, 3
- New WD of Use Cases and Requirements for Ontology and API for Media Object 1.0
- Re: [widgets] P&C Last Call comments, interoperability
- Re: [widgets] Public keys in widgets URI scheme?
- Re: [widgets] Public keys in widgets URI scheme?
- RE: [widgets] P&C Last Call comments, versioning
- Re: [widgets] P&C Last Call comments, versioning
- Re: [cors] Web application
- Re: [cors] Review
Monday, 15 June 2009
- RE: [cors] Web application
- Re: [cors] Web application
- RE: [cors] Web application
- Re: Restricting API access
- [cors] Web application
- Re: [WebIDL] double
- [widgets] Last Call Comments
- Re: Progress Events normative text
- Re: [cors] Review
- Re: [widgets] Widgets URI scheme... it's baaaack!
- Re: Comments on Widgets spec
- Re: Review of widget access request
- Re: New draft of Widgets: Access Requests Policy
- Window atttributes for timing info
- Re: [cors] Review
- Re: [WebIDL] double
- Re: [WebIDL] double
Sunday, 14 June 2009
- Re: [WebIDL] double
- Re: [WebIDL] double
- [widgets] Comments on Widgets 1.0: Packaging and configuration, 9.1 Processing rules
- Re: [webidl] definition of const string literal
- Re: [WebIDL] double
- File API - W3C Working Draft 7 June 2009
- Re: [cors] Review
- ISSUE-89: Reduce the length of the header names? [CORS]
- Re: XHR without user credentials
- Re: [cors] Review
Saturday, 13 June 2009
- Re: XHR without user credentials
- Re: XHR without user credentials
- Re: XHR without user credentials
- Re: XHR without user credentials
- Re: XHR without user credentials
- Re: XHR without user credentials
- Re: [XHR] Authorization header
- Re: [cors] Review
- Re: [cors] Review
- Re: XHR without user credentials
- Re: Progress Events normative text
- Re: XHR without user credentials
- Re: XHR without user credentials
- Re: XHR without user credentials
- Re: XHR without user credentials
Friday, 12 June 2009
- Re: XHR without user credentials
- Re: "send data using the Web Socket" and UCS-2
- Public call for prior art on Widget updates
- Comments on Widgets spec
- Re: [widgets] Draft Minutes from 10 June 2009 f2f meeting
- Reminder: June 19 deadline for comments re LCWD of Widgets 1.0: Packaging and Configuration spec
- [widgets] Draft Minutes from 11 June 2009 f2f meeting
- [widgets] Draft Minutes from 10 June 2009 f2f meeting
- [widgets] Draft Minutes from 9 June 2009 f2f meeting
Thursday, 11 June 2009
- Re: [webworkers] Tasks
- Re: [webworkers] Tasks
- Re: EventSource editorial issues
- Re: Origin enables XSS to escalate to XSRF (was: security issue with XMLHttpRequest API compatibility)
- Re: Origin enables XSS to escalate to XSRF
- Re: Origin enables XSS to escalate to XSRF (was: security issue with XMLHttpRequest API compatibility)
- File API, Editor's Draft II
Wednesday, 10 June 2009
- Re: WebSocket question
- [widgets] Step 7 - Process the Configuration Document
- RE: [WebIDL] double
- [WebIDL] double
- [WebIDL] double
- [widgets] Elements are grouped by language:
- [widgets] One element is allowed per language:
- [widgets] Verify Zip archive
- [widgets] Rule for Determining if a potential Zip archive is a Zip archive
- Re: [widgets] Rule for finding a file within a widget package
- [widgets] Rule for Identifying the media type of a file
- Re: [widgets] Rule for finding a file within a widget package
- [widgets] Rule for Identifying the Media Type of an Image
- [widgets] Rule for Parsing a Non-negative Integer
- [widgets] Rule for Getting Text Content with Normalized White Space
- [widgets] Rule for Getting Text Content
- [widgets] editorial style
- [widgets] Rule for getting a single attribute value
- [widgets] Rule for finding a file within a widget package
- [widgets] Rule for dealing with an invalid Zip archive
- [widgets] Rule for extracting file data from a file entry
- [widgets] Editorial: 9x Processing
- RE: [WebIDL] "module" in ECMAScript
- Re: XHR without user credentials
- Re: Redirect and Origin
- Re: Redirect and Origin
- Re: WebStorage feedback
Tuesday, 9 June 2009
- Re: Redirect and Origin
- Re: Redirect and Origin
- Re: Redirect and Origin
- Re: Redirect and Origin
- Re: Redirect and Origin
- Re: Redirect and Origin
- Re: Redirect and Origin
- Redirect and Origin
- Re: XHR without user credentials
- Re: XHR without user credentials
- Re: XHR without user credentials
- Re: XHR without user credentials
- Re: XHR without user credentials
- Re: XHR without user credentials
- Re: WebSocket question
- Re: XHR without user credentials
- Re: CSRF: alternative solutions
- Re: CSRF: alternative solutions
- Re: XHR without user credentials
- Re: XHR without user credentials
- Re: [widgets] What does it mean to have an unavailable API
- Re: XHR without user credentials
- Re: XHR without user credentials
- Re: XHR without user credentials
- Re: CSRF: alternative solutions
- Questions on A&E spec
- RE: [WebIDL] "module" in ECMAScript
- to www-dom Re: [DOM3Events] Use cases for Mutation Events
- Re: [widgets] What does it mean to have an unavailable API
- Re: [widgets] What does it mean to have an unavailable API
- [webstorage] Ambiguous Requirement for Key Ordering
- Re: [widgets] What does it mean to have an unavailable API
- Re: CSRF: alternative solutions
- Re: WebSocket question
- Re: [widgets] What does it mean to have an unavailable API
- Re: [widgets] What does it mean to have an unavailable API
- [WebIDL] overloading and fallback
- Review of widget access request
- RE: [widgets] P&C Last Call comments, 7
- RE: [widgets] What does it mean to have an unavailable API
- RE: [widgets] What does it mean to have an unavailable API
- RE: [widgets] What does it mean to have an unavailable API
- Re: XHR without user credentials
- Re: CSRF: alternative solutions
- Re: [widgets] What does it mean to have an unavailable API
Friday, 5 June 2009
Tuesday, 9 June 2009
- Re: XHR without user credentials
- Re: Origin enables XSS to escalate to XSRF (was: security issue with XMLHttpRequest API compatibility)
- Re: Origin enables XSS to escalate to XSRF (was: security issue with XMLHttpRequest API compatibility)
- Re: [cors] Review
- Re: XHR without user credentials
- Re: XHR without user credentials
- Response to ACTION-348
- Re: XHR without user credentials
- Re: XHR without user credentials
Monday, 8 June 2009
- Re: [widgets] What does it mean to have an unavailable API
- Re: CSRF: alternative solutions
- Re: XHR without user credentials
- Re: XHR without user credentials
- Re: [widgets] Implementing Google Wave with W3C Widgets
- Re: XHR without user credentials
- Re: [widgets] What does it mean to have an unavailable API
- Re: XHR without user credentials
- Re: XHR without user credentials
- Re: Storage and widgets
- Re: [widgets] P&C Last Call comments, 7
- Re: [widgets] What does it mean to have an unavailable API
- Re: [widgets] What does it mean to have an unavailable API
- Re: [widgets] What does it mean to have an unavailable API
- Re: [widgets] What does it mean to have an unavailable API
- Re: [widgets] What does it mean to have an unavailable API
- Re: [widgets] What does it mean to have an unavailable API
- Re: [widgets] Implementing Google Wave with W3C Widgets
- Re: [widgets] Access Requests Use Case: Restricted access to remote web services using white/black lists
- Re: [widgets] Getting A&E spec to Last Call
- Re: I18N issue: case-sensitivity of locale subdirectories
- Re: Storage and widgets
- Re: [cors] Review
- XHR without user credentials (Was: Origin enables XSS to escalate to XSRF (was: security issue with XMLHttpRequest API compatibility))
- Re: CSRF: alternative solutions
- RE: CSRF: alternative solutions
- CSRF: alternative solutions
- Re: Reminder: Comments for LCWD of Widgets 1.0: Digital Signatures due June 1
- Re: Reminder: Comments for LCWD of Widgets 1.0: Digital Signatures due June 1
- Re: Reminder: Comments for LCWD of Widgets 1.0: Digital Signatures due June 1
- RE: Reminder: Comments for LCWD of Widgets 1.0: Digital Signatures due June 1
- Re: Reminder: Comments for LCWD of Widgets 1.0: Digital Signatures due June 1
- Re: Widgets 1.0: Digital Signatures
- Re: [widgets] Moving Widgets 1.0: Digital Signature spec to Candidate Recommendation
- Re: Origin enables XSS to escalate to XSRF (was: security issue with XMLHttpRequest API compatibility)
- Re: Origin enables XSS to escalate to XSRF (was: security issue with XMLHttpRequest API compatibility)
Sunday, 7 June 2009
- Re: Origin enables XSS to escalate to XSRF (was: security issue with XMLHttpRequest API compatibility)
- Re: Origin enables XSS to escalate to XSRF (was: security issue with XMLHttpRequest API compatibility)
- Re: Origin enables XSS to escalate to XSRF (was: security issue with XMLHttpRequest API compatibility)
- Re: Origin enables XSS to escalate to XSRF (was: security issue with XMLHttpRequest API compatibility)
- Re: Origin enables XSS to escalate to XSRF (was: security issue with XMLHttpRequest API compatibility)
- Re: Origin enables XSS to escalate to XSRF (was: security issue with XMLHttpRequest API compatibility)
- Re: Origin enables XSS to escalate to XSRF (was: security issue with XMLHttpRequest API compatibility)
- Re: Origin enables XSS to escalate to XSRF (was: security issue with XMLHttpRequest API compatibility)
- Re: Origin enables XSS to escalate to XSRF (was: security issue with XMLHttpRequest API compatibility)
- Re: Origin enables XSS to escalate to XSRF (was: security issue with XMLHttpRequest API compatibility)
- Re: Origin enables XSS to escalate to XSRF (was: security issue with XMLHttpRequest API compatibility)
- to www-dom Re: [DOM3Events] Use cases for Mutation Events
Saturday, 6 June 2009
- Re: New draft of Widgets: Access Requests Policy
- Re: Origin enables XSS to escalate to XSRF (was: security issue with XMLHttpRequest API compatibility)
- Next DOM3 Events Telcon (Time and Day?)
Friday, 5 June 2009
- RE: [DOM3Events] Use cases for Mutation Events
- Fwd: [widgets] P&C LC#2 comment regarding icons
- New draft of Widgets: Access Requests Policy
- Re: [webidl] XMLHttpRequest interface object
- RE: [widgets] What does it mean to have an unavailable API
- Re: Mutation events replacement
- Re: [webidl] XMLHttpRequest interface object
Thursday, 4 June 2009
- Re: Mutation events replacement
- Re: review of A&E
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Widgets 1.0: Digital Signatures
- Re: Mutation events replacement
- Automated API specification generation
- Re: Mutation events replacement
- RE: [widgets] What does it mean to have an unavailable API
- RE: [widgets] P&C Last Call comments, zip-rel-path ABNF
- Re: Widgets 1.0: Digital Signatures
- [widgets] Draft Minutes from 4 June 2009 Voice Conference
- Re: [widgets] What does it mean to have an unavailable API
- Re: Widgets 1.0: Digital Signatures
- Re: Mutation events replacement
- Re: Mutation events replacement
- Widgets 1.0: Digital Signatures
- Re: [widgets] P&C LC, general comments
- Re: [DOM3Events] Use cases for Mutation Events
- Re: [DOM3Events] Use cases for Mutation Events
- Re: Reminder: Comments for LCWD of Widgets 1.0: Digital Signatures due June 1
- RE: [widgets] Moving Widgets 1.0: Digital Signature spec to Candidate Recommendation
- RE: Reminder: Comments for LCWD of Widgets 1.0: Digital Signatures due June 1
- Re: [DOM3Events] Use cases for Mutation Events
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: [DOM3Events] Use cases for Mutation Events
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: [DOM3Events] Use cases for Mutation Events
- Re: [DOM3Events] Use cases for Mutation Events
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- [DOM3Events] Use cases for Mutation Events
- Re: FW: Patent licensing and avoiding late Exclusions of Essential Claims in the WebApps WG
- Mutation events replacement
- RE: [widgets] What does it mean to have an unavailable API
- Re: [widgets] What does it mean to have an unavailable API
- RE: [widgets] What does it mean to have an unavailable API
- RE: [widgets] P&C Last Call comments, viewmodes, referencing other specs, guarantee of consistency
- Re: "send data using the Web Socket" and UCS-2
- Re: "send data using the Web Socket" and UCS-2
- Re: [widgets] What does it mean to have an unavailable API
Wednesday, 3 June 2009
- Origin enables XSS to escalate to XSRF (was: security issue with XMLHttpRequest API compatibility)
- Re: [widgets] P&C Last Call comments, viewmodes, referencing other specs, guarantee of consistency
- Re: [widgets] P&C Last Call comments, viewmodes, referencing other specs, guarantee of consistency
- Re: [widgets] P&C Last Call comments, viewmodes, referencing other specs, guarantee of consistency
- RE: [widgets] P&C Last Call comments, viewmodes, referencing other specs, guarantee of consistency
- Attempt at consensus on the <access> model
- Re: [widgets] P&C Last Call comments, viewmodes, referencing other specs, guarantee of consistency
- Re: [widgets] P&C LC, general comments
- [widgets] P&C Last Call comments, viewmodes, referencing other specs, guarantee of consistency
- [widgets] Draft Agenda for 4 June 2009 Voice Conference
- [widgets] P&C LC, general comments
- RE: [widgets] What does it mean to have an unavailable API
- RE: [widgets] What does it mean to have an unavailable API
- RE: [widgets] What does it mean to have an unavailable API
- [widgets] P&C LC comments on I18N/L10N
- Re: HTML 5 Database Storage Does Not Enable Chaining Transactions
- Re: Do we need to rename the Origin header?
Tuesday, 2 June 2009
- "send data using the Web Socket" and UCS-2
- Re: [widgets] What does it mean to have an unavailable API
- Re: [widgets] P&C Last Call comments, 7
- Re: [widgets] What does it mean to have an unavailable API
- RE: [widgets] P&C Last Call comments, 3
- [widgets] P&C Last Call comments, 7
- Re: [widgets] P&C Last Call comments, 3
- Re: XBL2 Status?
- Re: [widgets] What does it mean to have an unavailable API
- Re: [widgets] P&C Last Call comments, 6
- RE: [widgets] What does it mean to have an unavailable API
- RE: [widgets] What does it mean to have an unavailable API
- Re: [widgets] P&C Last Call comments, 4
- Re: [widgets] What does it mean to have an unavailable API
- RE: [widgets] P&C Last Call comments, 4
- [widgets] P&C Last Call comments, 6
- Re: [widgets] P&C Last Call comments, 4
- Re: [widgets] Please include a statement of purpose and user interaction expectations for <feature>
- Re: [widgets] What does it mean to have an unavailable API
- Re: [widgets] Please include a statement of purpose and user interaction expectations for <feature>
- [widgets] Moving Widgets 1.0: Digital Signature spec to Candidate Recommendation
- [widgets] Please include a statement of purpose and user interaction expectations for <feature>
- Re: [cors] Review
- [widgets] What does it mean to have an unavailable API
- Re: [widgets] Purpose and utility of <feature> unclear
- Re: [widgets] P&C Last Call comments, interoperability
- Re: [widgets] Purpose and utility of <feature> unclear
- Re: [widgets] P&C Last Call comments, 1
- Re: [widgets] P&C Last Call comments, versioning
- RE: [widgets] P&C Last Call comments, 4
- Re: [widgets] P&C Last Call comments, interoperability
- Re: [widgets] P&C Last Call comments, versioning
- RE: [widgets] Purpose and utility of <feature> unclear
- RE: [widgets] P&C Last Call comments, interoperability
- RE: [widgets] P&C Last Call comments, 3
- Re: [widgets] P&C Last Call comments, versioning
- RE: [widgets] P&C Last Call comments, versioning
- Re: [widgets] P&C Last Call comments, 4
- RE: [widgets] P&C Last Call comments, versioning
- RE: [widgets] P&C Last Call comments, versioning
- RE: [widgets] P&C Last Call comments, 1
- Re: [ElementTraversal]: Feature string for DOMImplementation.hasFeature(feature, version)?
Monday, 1 June 2009
- Re: [widgets] P&C Last Call comments, zip-rel-path ABNF
- Re: [widgets] Purpose and utility of <feature> unclear
- Re: [widgets] Purpose and utility of <feature> unclear
- Re: [widgets] P&C Last Call comments, interoperability
- Re: [widgets] Purpose and utility of <feature> unclear
- RE: London F2F invitation
- Re: [widgets] P&C Last Call comments, 3
- [widgets] Purpose and utility of <feature> unclear
- London F2F invitation
- Re: [widgets] P&C Last Call comments, versioning
- Re: [widgets] P&C Last Call comments, versioning
- Re: [widgets] P&C Last Call comments, 2
- Re: [widgets] P&C Last Call comments, 1
- Re: [widgets] P&C Last Call comments, 5
- Re: [widgets] P&C Last Call comments, versioning
- Re: [WebIDL] "module" in ECMAScript
Sunday, 31 May 2009
- [widgets] P&C Last Call comments, 5
- [widgets] P&C Last Call comments, zip-rel-path ABNF
- [widgets] P&C Last Call comments, versioning
- [widgets] P&C Last Call comments, interoperability
- [widgets] P&C Last Call comments, 4
- [widgets] P&C Last Call comments, 3
- [widgets] P&C Last Call comments, 2
- [widgets] P&C Last Call comments, 1
- [widgets] P&C Last Call comments, 0
- [widgets] Implementing Google Wave with W3C Widgets
Saturday, 30 May 2009
- Re: Progress Events normative text
- Re: FW: Patent licensing and avoiding late Exclusions of Essential Claims in the WebApps WG
Friday, 29 May 2009
- Re: [DOM L3] Telecon today?
- Re: Feature names: Typo in example
- RE: Feature names: Typo in example
- Re: Feature names: Typo in example
- Feature names: Typo in example
- [widgets] A&E test widget
- [WebIDL] "module" in ECMAScript
- [cors] Review
- RE: [widgets] Widgets URI scheme... it's baaaack!
Thursday, 28 May 2009
- BONDI Approved Release 1.0
- Request For Comments: Last Call WD of Widgets 1.0: Packaging and Configuration; deadline 19 June 2009
- [widgets] Draft Minutes from 28 May 2009 Voice Conference
- Re: [widgets] Regrets for 28 May 2009 Voice Conference
Wednesday, 27 May 2009
- Re: [widgets] Draft Agenda for 28 May 2009 Voice Conference
- Re: [widgets] Public keys in widgets URI scheme?
- Re: [widgets] Public keys in widgets URI scheme?
- Re: [widgets] Public keys in widgets URI scheme?
- Re: [widgets] Public keys in widgets URI scheme?
- Re: [widgets] Public keys in widgets URI scheme?
- Re: [widgets] Public keys in widgets URI scheme?
- Re: [widgets] Public keys in widgets URI scheme?
- Re: [widgets] Public keys in widgets URI scheme?
- [DOM L3] Telecon today?
- Re: [widgets] Public keys in widgets URI scheme?
- Re: [widgets] Public keys in widgets URI scheme?
- [widgets] Packaging call for review
- [widgets] Public keys in widgets URI scheme?
- Re: [widgets] Draft Agenda for 28 May 2009 Voice Conference
- [widgets] Draft Agenda for 28 May 2009 Voice Conference
- Introduction: Peter-Paul Koch
- Re: [widgets] Widgets URI scheme... it's baaaack!
- Re: [widgets] Widgets URI scheme... it's baaaack!
- [DOML3Events] keydown repeatedness
- Re: [widgets] Widgets URI scheme... it's baaaack!
- Re: [widgets] Widgets URI scheme... it's baaaack!
- Re: [widgets] Widgets URI scheme... it's baaaack!
- Re: [widgets] Widgets URI scheme... it's baaaack!
Tuesday, 26 May 2009
Wednesday, 27 May 2009
Tuesday, 26 May 2009
- Introduction: Rob Ennals from Intel
- Re: [widgets] Widgets URI scheme... it's baaaack!
- [webworkers] Tasks
Monday, 25 May 2009
- Re: [widget] Security model
- Re: [widget] Security model
- Re: [widget] Security model
- Re: [widget] Security model
- Re: [widget] Security model
- Re: [widgets] Widgets URI scheme... it's baaaack!
Sunday, 24 May 2009
Saturday, 23 May 2009
- Re: [widgets] Widgets URI scheme... it's baaaack!
- Re: [widgets] Widgets URI scheme... it's baaaack!
- Re: [widgets] Widgets URI scheme... it's baaaack!
- Re: [widgets] Widgets URI scheme... it's baaaack!
- Re: [widgets] Widgets URI scheme... it's baaaack!
Friday, 22 May 2009
- Re: [widgets] Widgets URI scheme... it's baaaack!
- Re: [widgets] Widgets URI scheme... it's baaaack!
- Re: [widgets] Widgets URI scheme... it's baaaack!
- Re: [widgets] Widgets URI scheme... it's baaaack!
- Re: [widgets] Widgets URI scheme... it's baaaack!
- Re: [widgets] Widgets URI scheme... it's baaaack!
- Re: [widgets] Widgets URI scheme... it's baaaack!
- Re: [widgets] Widgets URI scheme... it's baaaack!
- RE: [widgets] Widgets URI scheme... it's baaaack!
- Re: [widgets] Widgets URI scheme... it's baaaack!
- RE: [widgets] Widgets URI scheme... it's baaaack!
- Re: [widgets] Widgets URI scheme... it's baaaack!
- Re: [widgets] Widgets URI scheme... it's baaaack!
- [widgets] Access Requests Use Case: Restricted access to remote web services using white/black lists
- Re: [widgets] Call for Input: Use Cases and Requirements for Widgets Access Request spec
- Re: [widgets] i18n proposals document
- Re: [widgets] Call for Input: Use Cases and Requirements for Widgets Access Request spec
- Re: [widgets] Call for Input: Use Cases and Requirements for Widgets Access Request spec
- Re: [widgets] Call for Input: Use Cases and Requirements for Widgets Access Request spec
- Re: [widgets] Call for Input: Use Cases and Requirements for Widgets Access Request spec
- Re: [widgets] Widgets URI scheme... it's baaaack!
- [widgets] Widgets URI scheme... it's baaaack!
Thursday, 21 May 2009
- Reminder: Comments for LCWD of Widgets 1.0: Digital Signatures due June 1
- [widgets] Call for Input: Use Cases and Requirements for Widgets Access Request spec
- [widgets] Draft Minutes from 21 May 2009 Voice Conference
- Re: More complete draft for Widgets: Access Requests
- Re: More complete draft for Widgets: Access Requests
- Re: More complete draft for Widgets: Access Requests
Wednesday, 20 May 2009
- More complete draft for Widgets: Access Requests
- Re: [widgets] Draft Minutes from 14 May 2009 Voice Conference
- Re: FPWD for WAR?
- [widgets] P&C and window modes
- Re: FPWD for WAR?
- Re: FPWD for WAR?
- Re: FPWD for WAR?
- FPWD for WAR?
Tuesday, 19 May 2009
- [widgets] Declaring *W*A*R*
- [widgets] Draft Agenda for 21 May 2009 Voice Conference
- [widgets] Draft Minutes from 19 May 2009 Widgets Security VC
- Re: [widget] Security model
- Re: [widget] Security model
- Re: [widgets] Draft Minutes from 14 May 2009 Voice Conference
- Re: [widget] Security model
- Re: [widgets] Draft Minutes from 14 May 2009 Voice Conference
- Re: [widget] Security model
- Re: [widget] Security model
- Re: [widget] Security model
- [widget] Security model
- Re: [widgets] Base folder and resolution of relative paths
- Re: [widgets] Base folder and resolution of relative paths
- Re: [widgets] Draft Minutes from 14 May 2009 Voice Conference
- Re: Proposal for addition to WebStorage
Monday, 18 May 2009
- Re: WebStorage feedback
- Re: WebStorage feedback
- Re: [widgets] Draft Minutes from 14 May 2009 Voice Conference
- [widgets] Draft Agenda for 19 May 2009 Widgets Security VC
- [widgets] Draft Minutes from 18 May 2009 Widgets Security VC
- Re: [widgets] Security Model call on May 18 @ 13:00 Paris time
Sunday, 17 May 2009
Friday, 15 May 2009
Thursday, 14 May 2009
- Re: [widgets] Getting A&E spec to Last Call
- [widgets] Draft Minutes from 14 May 2009 Voice Conference
- Re: [cors] Redirects
Wednesday, 13 May 2009
- RE: [widgets] Agenda for 14 May 2009 Voice Conference
- Re: [widgets] Agenda for 14 May 2009 Voice Conference
- Re: [widgets] Agenda for 14 May 2009 Voice Conference
- [widgets] Agenda for 14 May 2009 Voice Conference
- Re: [widgets] Base folder and resolution of relative paths
Tuesday, 12 May 2009
Monday, 11 May 2009
- Re: [widgets] window modes in P&C, was Re: Small question aboutlatestversionof "P&C specs" (11th Mar 2009)
- RE: [widgets] window modes in P&C, was Re: Small question aboutlatestversionof "P&C specs" (11th Mar 2009)
- Re: [widgets] window modes in P&C, was Re: Small question aboutlatestversion of "P&C specs" (11th Mar 2009)
- RE: [widgets] window modes in P&C, was Re: Small question aboutlatestversion of "P&C specs" (11th Mar 2009)
- Re: [widgets] window modes in P&C, was Re: Small question about latestversion of "P&C specs" (11th Mar 2009)
- RE: [widgets] window modes in P&C, was Re: Small question about latestversion of "P&C specs" (11th Mar 2009)
- Re: [widgets] Base folder and resolution of relative paths
Saturday, 9 May 2009
Friday, 8 May 2009
- Require that XPathNSResolver be implemented on Node
- [widgets] window modes in P&C, was Re: Small question about latest version of "P&C specs" (11th Mar 2009)
- Re: ACTION-337: Review of access element
- Re: [widgets] dig sig and requirements ready for pub!
- Re: [widgets] dig sig and requirements ready for pub!
Thursday, 7 May 2009
- FW: Patent licensing and avoiding late Exclusions of Essential Claims in the WebApps WG
- Re: [widgets] dig sig and requirements ready for pub!
- [widgets] Draft minutes from 7 May 2009 Voice Conference
- [widgets-digsig] minor editorial update
- Re: [widgets] Base folder and resolution of relative paths
- Re: [widgets] Call for Additional Editor(s) for P&C spec
- Re: [widgets] Call for Additional Editor(s) for P&C spec
- Re: ACTION-337: Review of access element
- [widgets] Call for Additional Editor(s) for P&C spec
- [widgets] i18n feedback
- Re: I18N issue: case-sensitivity of locale subdirectories
Wednesday, 6 May 2009
Tuesday, 5 May 2009
- Re: [widgets] dig sig and requirements ready for pub!
- Re: [widgets] dig sig and requirements ready for pub!
- Re: [widgets] dig sig and requirements ready for pub!
- Re: [widgets] dig sig and requirements ready for pub!
- Re: [widgets] dig sig and requirements ready for pub!
- Re: [widgets] dig sig and requirements ready for pub!
- Re: [widgets] dig sig and requirements ready for pub!
- Re: I18N issue: case-sensitivity of locale subdirectories
- Working Vacation
- RE: [widgets] Comments to <access> element text
Monday, 4 May 2009
- Re: Next steps for XHR L1 spec?
- RE: Next steps for XHR L1 spec?
- Re: setTimeout() in HTML5
- Re: setTimeout() in HTML5
- Re: setTimeout() in HTML5
- Re: [widgets] dig sig and requirements ready for pub!
- Re: [widgets] dig sig and requirements ready for pub!
- Re: [widgets] dig sig and requirements ready for pub!
- Re: Next steps for XHR L1 spec?
- Re: XHR and the storage mutex
- Re: [widgets] dig sig and requirements ready for pub!
- Re: [widgets] dig sig and requirements ready for pub!
- Re: [widgets] dig sig and requirements ready for pub!
- Re: [widgets] dig sig and requirements ready for pub!
- Re: setTimeout() in HTML5
- Re: review of A&E
- setTimeout() in HTML5
Saturday, 2 May 2009
- Re: New CfC Re: [Selectors API] Call for Consensus - approve John Resig's tests
- ACTION-337: Review of access element
- Re: [widgets] Comments to <access> element text
Friday, 1 May 2009
- RE: [widgets] Comments to <access> element text
- Re: Widget instances and widget invocations
- Re: Widget instances and widget invocations
- Re: Widget instances and widget invocations
- Re: [widgets] Comments to <access> element text
- Re: I18N proposals document review...
- Re: Proposal to update signature text in Packaging and Config, remove from Widget Signature
- Re: New Widgets A&E Editors Draft
- Re: review of A&E
- LCWD of Widgets 1.0: Digital Signatures published 30-Apr-2009
- Re: [widgets] Comments to <access> element text
- Re: [widgets] dig sig and requirements ready for pub!
- Re: Widget instances and widget invocations
- Re: I18N issue: case-sensitivity of locale subdirectories
- RE: [widgets] Comments to <access> element text
Thursday, 30 April 2009
- [widget-digsig] XML Signature Properties published
- Re: Widget instances and widget invocations
- Re: [webidl] XMLHttpRequest interface object
- Re: [webidl] XMLHttpRequest interface object
- Re: [webidl] XMLHttpRequest interface object
- I18N proposals document review...
- Re: [widgets] Comments to <access> element text
- [widgets] Draft Minutes from 30 April 2009 Voice Conference
- Widget instances and widget invocations
- [widgets] Comments to <access> element text
- Re: [webidl] XMLHttpRequest interface object
- [webidl] XMLHttpRequest interface object
- RE: [widgets] Draft Agenda for 30 April 2009 Voice Conference
- Re: [widgets] Draft Agenda for 30 April 2009 Voice Conference
- RE: [widgets] Draft Agenda for 30 April 2009 Voice Conference
- Re: [widgets] Draft Agenda for 30 April 2009 Voice Conference
- Regretts Telecon Thursday 30 April
- Re: Preferences for the I18N model
- Re: Storage 'length' and enumeration
- Re: Storage 'length' and enumeration
- Re: Storage 'length' and enumeration
- Re: Storage 'length' and enumeration
- Re: Storage 'length' and enumeration
- Re: Storage 'length' and enumeration
- Re: Storage 'length' and enumeration
- Re: Storage 'length' and enumeration
- Re: Storage 'length' and enumeration
- Re: Storage 'length' and enumeration
- Re: Storage 'length' and enumeration
Wednesday, 29 April 2009
- Re: Storage 'length' and enumeration
- Re: Storage 'length' and enumeration
- Re: Storage 'length' and enumeration
- Re: Storage 'length' and enumeration
- Re: Storage 'length' and enumeration
- Re: WebStorage feedback
- Re: Storage 'length' and enumeration
- Re: Storage 'length' and enumeration
- Re: WebStorage feedback
- Re: Storage 'length' and enumeration
- Re: Storage 'length' and enumeration
- Re: I18N issue: case-sensitivity of locale subdirectories
- [widgets] dig sig and requirements ready for pub!
- Re: Widget URI ED
- Widget URI ED
- Preferences for the I18N model
- Re: Storage 'length' and enumeration
- [widgets] Requirements doc overhaul
- Re: [webidl] Callback confusion
- [widgets] Draft Agenda for 30 April 2009 Voice Conference
- I18N issue: case-sensitivity of locale subdirectories
- [widget-digsig] Update to widget signature
- Re: [widgets] Dig Sig review in prep for LC
- Re: [widgets] Dig Sig review in prep for LC
- Re: [widgets] Dig Sig review in prep for LC
- Re: [widgets] Dig Sig review in prep for LC
- Re: [widgets] Dig Sig review in prep for LC
- Re: [widgets] Dig Sig review in prep for LC
- [webidl] Callback confusion
- Re: [widgets] Dig Sig review in prep for LC
- Re: [webidl] definition of const string literal
- Re: [widgets] i18n proposals document
- Re: [DOML3Events] ACTION-267 Proposal for event iterator
- Re: [webidl] definition of const string literal
- Re: [DOML3Events] ACTION-267 Proposal for event iterator
- WebStorage feedback
- [widgets] Dig Sig review in prep for LC
- Re: Storage 'length' and enumeration
- Re: Storage 'length' and enumeration
- [NameCreator] definition buggy
- Re: Storage 'length' and enumeration
- Re: Storage 'length' and enumeration
Tuesday, 28 April 2009
- Re: Storage 'length' and enumeration
- Re: [DOML3Events] ACTION-267 Proposal for event iterator
- Re: Storage 'length' and enumeration
- Re: [DOML3Events] ACTION-267 Proposal for event iterator
- Re: Storage 'length' and enumeration
- RE: [DOML3Events] ACTION-267 Proposal for event iterator
- Re: [webstorage] disk space
- Re: [webstorage] inactive documents
- Re: [DOML3Events] ACTION-267 Proposal for event iterator
- Updates to Widget Signature
- RE: [DOML3Events] ACTION-267 Proposal for event iterator
- Storage 'length' and enumeration
- Re: [widgets] Identifying all security related issues with "core" Widgets specs
- [webstorage] disk space
- Re: Proposal for addition to WebStorage
- Re: [webidl] definition of const string literal
- Re: [webidl] definition of const string literal
Monday, 27 April 2009
- Re: Proposal to update signature text in Packaging and Config, remove from Widget Signature
- Re: [widgets] Publishing LCWD of Widgets Digital Signatures and new WD of Requirements
- Re: [webstorage] inactive documents
- Re: [webstorage] inactive documents
- [widgets] Publishing LCWD of Widgets Digital Signatures and new WD of Requirements
- Re: [webstorage] inactive documents
- Proposal to update signature text in Packaging and Config, remove from Widget Signature
- Re: Proposal for addition to WebStorage
- Re: [webstorage] inactive documents
- Re: [webidl] definition of const string literal
- Re: [webidl] definition of const string literal
- [webidl] definition of const string literal
- [widgets] Identifying all security related issues with "core" Widgets specs
- Re: Storage and widgets
- [webstorage] inactive documents
- Re: [widgets] Base folder and resolution of relative paths
- Re: Proposal for addition to WebStorage
Sunday, 26 April 2009
Saturday, 25 April 2009
- Re: Storage and widgets
- Re: Storage and widgets
- RE: [DOML3Events] ACTION-267 Proposal for event iterator
Friday, 24 April 2009
- Re: Proposal for addition to WebStorage
- Re: Web Storage & SQL
- Re: Proposal for addition to WebStorage
- Proposal for addition to WebStorage
- Re: addEventListener naming
- [webstorage] storage event should be dispatched async
- Fwd: [whatwg] Exposing EventTarget to JavaScript
- addEventListener naming
- Re: Storage and widgets
- RE: New Widgets A&E Editors Draft
- RE: [Proposal] Empowering the Widget to ask fro "mode change" in A&E
- [webstorage] events
- [webstorage] fork bombing
- Re: [widget-digsig] Updated Widget Signature editors draft
- Re: [Proposal] Empowering the Widget to ask fro "mode change" in A&E
- Re: Storage and widgets
- Re: [Proposal] Empowering the Widget to ask fro "mode change" in A&E
- Re: [Proposal] Empowering the Widget to ask fro "mode change" in A&E
- Re: Storage and widgets
- Re: [Proposal] Empowering the Widget to ask fro "mode change" in A&E
- Re: Storage and widgets
- Re: Web Storage Scope and Charter
- RE: [widget-digsig] Updated Widget Signature editors draft
- Re: review of A&E
- Re: review of A&E
- Re: Storage and widgets
- Re: Storage and widgets
- Re: [widget-digsig] Updated Widget Signature editors draft
- Re: Storage and widgets
- Re: Web Storage Scope and Charter
- Re: Web Storage Scope and Charter
- Re: Web Storage Scope and Charter
- Re: Web Storage Scope and Charter
- Re: Web Storage Scope and Charter
- Re: Web Storage Scope and Charter
- Re: Web Storage Scope and Charter
- Re: Web Storage Scope and Charter (was: CfC: FPWD of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers; deadline April 10)
- Re: Web Storage Scope and Charter (was: CfC: FPWD of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers; deadline April 10)
- Re: Web Storage Scope and Charter
- [widget-digsig] Updated Widget Signature editors draft
- Fwd: Proposal for new WG to specify "Concrete APIs"
Thursday, 23 April 2009
- Re: Web Storage Scope and Charter
- Re: Web Storage Scope and Charter (was: CfC: FPWD of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers; deadline April 10)
- Storage and widgets
- Re: Web Storage Scope and Charter
- Re: Web Storage Scope and Charter
- Re: Web Storage Scope and Charter (was: CfC: FPWD of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers; deadline April 10)
- Web Storage Scope and Charter (was: CfC: FPWD of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers; deadline April 10)
- Re: [cors] Redirects
- [widgets] Proposal to Close: ISSUE-81: ECDSAwithSHA256 as required algorithm in place of DSAwithSHA256?
- RE: [widget-digsig] Pls review: Additional considerations on elliptic curve algorithms to consider
- [widgets] Draft Minutes from 23 April 2003 Voice Conference
- Re: [cors] Redirects
- [widgets] <access> element
- Re: review of A&E
- Re: [widget-digsig] Pls review: Additional considerations on elliptic curve algorithms to consider
- RE: [widget-digsig] Pls review: Additional considerations on elliptic curve algorithms to consider
- Re: [widgets] New WD of Widgets 1.0: Digital Signatures spec published on March 31
- Re: review of A&E
- Re: [cors] Redirects
- Re: review of A&E
- Re: [cors] Redirects
- Re: [cors] Redirects
- Re: [widget-digsig] Pls review: Additional considerations on elliptic curve algorithms to consider
- Re: Proposal for ISSUE-83
- RE: [widget-digsig] Pls review: Additional considerations on elliptic curve algorithms to consider
- RE: [widgets] New WD of Widgets 1.0: Digital Signatures spec published on March 31
- RE: Proposal for ISSUE-83
- Re: Proposal for ISSUE-83
- Re: [cors] Redirects
Wednesday, 22 April 2009
- Re: [widgets] New WD of Widgets 1.0: Digital Signatures spec published on March 31
- [widget-digsig] updated Widget Signature editors draft
- Re: Proposal for ISSUE-83
- RE: [widgets] New WD of Widgets 1.0: Digital Signatures spec published on March 31
- Re: [widgets] New WD of Widgets 1.0: Digital Signatures spec published on March 31
- Re: [widgets] i18n proposals document
- Re: Small question about latest version of "P&C specs" (11th Mar 2009)
- Re: [widgets] Agenda for 23 April 2009 Voice Conference
- Re: [widgets] Agenda for 23 April 2009 Voice Conference
- Re: [widgets] Agenda for 23 April 2009 Voice Conference
- Re: Progress Events normative text
- RE: [widget] [widget-digsig] Comment on WD of Widgets 1.0: Digital Signatures - use of Created property
- Re: CfC: FPWD of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers; deadline April 10
- Re: [widgets] Agenda for 23 April 2009 Voice Conference
- Re: Next steps for CORS?
- Re: [cors] Redirects
- [widgets] Agenda for 23 April 2009 Voice Conference
- Re: [widget] [widget-digsig] Comment on WD of Widgets 1.0: Digital Signatures - use of Created property
- Re: [widgets] New WD of Widgets 1.0: Digital Signatures spec published on March 31
- agenda request: security considerations for access
- Re: [webidl] DOMString
- Re: [webidl] DOMString
- Re: [webidl] DOMString
- Re: CfC: FPWD of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers; deadline April 10
- Re: [webidl] DOMString
- Re: [webidl] DOMString
- Re: [webidl] DOMString
- Re: [webidl] DOMString
Tuesday, 21 April 2009
- Re: CfC: FPWD of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers; deadline April 10
- Re: CfC: FPWD of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers; deadline April 10
- Re: [widget] [widget-digsig] Comment on WD of Widgets 1.0: Digital Signatures - use of Created property
- Re: [widgets] New WD of Widgets 1.0: Digital Signatures spec published on March 31
- Re: Widgets 1.0 Packaging and Configuration: I18N comments...
- Re: Proposal for ISSUE-83
- Proposal for ISSUE-83
- Re: [webidl] DOMString
- RE: [widgets] Screenshots and case sensitive file names
- Re: [webidl] DOMString
- [webidl] DOMString
Monday, 20 April 2009
- Re: New Widgets A&E Editors Draft
- Re: [widgets] remove update related methods form A&E
- Re: [widgets] Screenshots and case sensitive file names
- Re: [Widgets] Widget Gallery RSS like sharing format
- Re: [widgets] restrictions on XML base
- Re: [Widgets] Widget Gallery RSS like sharing format
- Re: [widgets] Base folder and resolution of relative paths
- Re: Simple approach for <access>
Sunday, 19 April 2009
- Re: [widgets] dropping screenshot
- Re: Simple approach for <access>
- Re: Simple approach for <access>
- Re: Using xhr with file://
Saturday, 18 April 2009
Friday, 17 April 2009
- Re: Web Storage & SQL
- RE: [widgets] i18n proposals document
- two-player game application
- Re: [widgets] Jar signing vs. XML signatures
- Re: [widgets] Jar signing vs. XML signatures
- Re: [widgets] i18n proposals document
- Re: [widgets] i18n proposals document
- Re: [widgets] Jar signing vs. XML signatures
- Re: [widgets] Jar signing vs. XML signatures
- Re: [widgets] Jar signing vs. XML signatures
- RE: [widgets] i18n proposals document
Thursday, 16 April 2009
- Re: [widgets] i18n proposals document
- Re: [widgets] i18n proposals document
- Widgets unconference at WWW 2009
- [widgets] i18n proposals document
- Re: Simple approach for <access>
- Re: Simple approach for <access>
- [widgets] Draft Minutes from 16 April 2009 Widgets Voice Conference
- Re: New Widgets A&E Editors Draft
- New Widgets A&E Editors Draft
- Using xhr with file://
- review of A&E
- RE: [Widgets A&E] Removing show() and hide()
- [widgets] dropping screenshot
- [Widgets A&E] Removing show() and hide()
- Re: Widgets 1.0 Packaging and Configuration: I18N comments...
- Re: [widgets] Jar signing vs. XML signatures
- Re: June F2F
Wednesday, 15 April 2009
- June F2F
- Re: [widgets] Jar signing vs. XML signatures
- Re: [widgets] Jar signing vs. XML signatures
- Re: [widgets] Jar signing vs. XML signatures
- Re: [widgets] Jar signing vs. XML signatures
- Re: [widgets] Jar signing vs. XML signatures
- [widget] [widget-digsig] Comment on WD of Widgets 1.0: Digital Signatures - use of Created property
- Re: New CfC Re: [Selectors API] Call for Consensus - approve John Resig's tests
- Re: [Selectors] Selectors to Proposed Rec - call for consensus
- New CfC Re: [Selectors API] Call for Consensus - approve John Resig's tests
Tuesday, 14 April 2009
- Re: ISSUE-83 (digsig should not be read at runtime): Instantiated widget should not be able to read digital signature [Widgets]
- [widgets] Agenda for 16 April 2009 Voice Conference
- Re: Web Storage & SQL
- Re: [widgets] Jar signing vs. XML signatures
- Re: [widgets] Jar signing vs. XML signatures
- Re: [widgets] Jar signing vs. XML signatures
- Re: [widgets] Jar signing vs. XML signatures
- Re: [widgets] Jar signing vs. XML signatures
- Re: [cors] security issue with XMLHttpRequest API compatibility
- FYI: chartering discussion re security policy for APIs
- Re: [widgets] Jar signing vs. XML signatures
- Re: [cors] security issue with XMLHttpRequest API compatibility
- Re: [widgets] Jar signing vs. XML signatures
- Re: Simple approach for <access>
- Re: [widgets] Jar signing vs. XML signatures
- Re: [widgets] Jar signing vs. XML signatures
- Re: [widgets] Jar signing vs. XML signatures
- [widgets] Jar signing vs. XML signatures
Monday, 13 April 2009
- Re: Next steps for CORS?
- Re: ISSUE-83 (digsig should not be read at runtime): Instantiated widget should not be able to read digital signature [Widgets]
- Re: ISSUE-83 (digsig should not be read at runtime): Instantiated widget should not be able to read digital signature [Widgets]
Friday, 10 April 2009
Saturday, 11 April 2009
- Re: HTML5 Origin (aka IETF Origin draft)
- Re: HTML5 Origin (aka IETF Origin draft)
- Re: HTML5 Origin (aka IETF Origin draft)
- Re: HTML5 Origin (aka IETF Origin draft)
- Re: HTML5 Origin (aka IETF Origin draft)
- Re: Web Storage & SQL
- Re: Web Storage & SQL
- Re: Web Storage & SQL
Friday, 10 April 2009
- Re: Web Storage & SQL
- Re: Web Storage & SQL
- Re: Web Storage & SQL
- Re: CfC: FPWD of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers; deadline April 10
- Re: Web Storage & SQL
- Re: Web Storage & SQL
- Re: CfC: FPWD of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers; deadline April 10
- Re: CfC: FPWD of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers; deadline April 10
- Re: HTML5 Origin (aka IETF Origin draft)
- Re: CfC: FPWD of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers; deadline April 10
- Re: CfC: FPWD of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers; deadline April 10
- Re: Web Storage & SQL
- Re: Web Storage & SQL
Thursday, 9 April 2009
- Re: Web Storage & SQL
- Re: Web Storage & SQL
- Re: Web Storage & SQL
- Re: Web Storage & SQL
- Re: Web Storage & SQL
- Re: Web Storage & SQL
- Re: Web Storage & SQL
- Re: Do we need to rename the Origin header?
- Re: Web Storage & SQL
- Re: Web Storage & SQL
- Re: ISSUE-83 (digsig should not be read at runtime): Instantiated widget should not be able to read digital signature [Widgets]
- HTML5 Origin (aka IETF Origin draft)
- Re: Web Storage & SQL
- [Fwd: Re: Web Storage & SQL]
- Re: Web Storage & SQL
- Re: Web Storage & SQL
- Re: Do we need to rename the Origin header?
- Re: Web Storage & SQL
- Re: Web Storage & SQL
- Re: ISSUE-83 (digsig should not be read at runtime): Instantiated widget should not be able to read digital signature [Widgets]
- Re: ISSUE-83 (digsig should not be read at runtime): Instantiated widget should not be able to read digital signature [Widgets]
- Re: Web Storage & SQL
- RE: ISSUE-83 (digsig should not be read at runtime): Instantiated widget should not be able to read digital signature [Widgets]
- [widgets] blog post on recent Dig Sig spec
Saturday, 4 April 2009
Thursday, 9 April 2009
- Re: HTML 5 Database Storage Does Not Enable Chaining Transactions
- Re: Web Storage & SQL
- Re: Do we need to rename the Origin header?
- Re: Do we need to rename the Origin header?
- Re: Do we need to rename the Origin header?
- Re: Do we need to rename the Origin header?
- Re: Do we need to rename the Origin header?
Wednesday, 8 April 2009
- Re: Web Storage & SQL
- Web Storage & SQL
- Re: Do we need to rename the Origin header?
- Re: Do we need to rename the Origin header?
- Reminder: DOM3 Events Telcon Canceled
- Re: [cors] security issue with XMLHttpRequest API compatibility
- Re: Do we need to rename the Origin header?
- Re: Do we need to rename the Origin header?
- Re: Reminder: January 31 comment deadline for LCWD of Widgets 1.0: Packaging & Configuration spec
- Re: [widgets] Zip endian issue?
- Re: Discussions with HTTP WG about Origin header [was: Do we need to rename the Origin header?]
- Re: Discussions with HTTP WG about Origin header [was: Do we need to rename the Origin header?]
- Re: [widgets] dropping Asynchronous HTTP Requests and Storage
- [widget-digsig] Pls review: Additional considerations on elliptic curve algorithms to consider
- Re: [cors] security issue with XMLHttpRequest API compatibility
- Re: Widgets 1.0 Packaging and Configuration: I18N comments...
- Discussions with HTTP WG about Origin header [was: Do we need to rename the Origin header?]
- Re: [cors] security issue with XMLHttpRequest API compatibility
- Re: [cors] security issue with XMLHttpRequest API compatibility
- Content Security Policy - Updated Spec
- Re: [cors] security issue with XMLHttpRequest API compatibility
Tuesday, 7 April 2009
- Re: [cors] security issue with XMLHttpRequest API compatibility
- Re: [cors] security issue with XMLHttpRequest API compatibility
- Re: Do we need to rename the Origin header?
- Re: ISSUE-83 (digsig should not be read at runtime): Instantiated widget should not be able to read digital signature [Widgets]
- [widgets] Synching Widgets DigSig with XML Signatures 1.1 and Signatures Properties
- Re: [cors] security issue with XMLHttpRequest API compatibility
- Re: Do we need to rename the Origin header?
- Re: Do we need to rename the Origin header?
- Re: [cors] security issue with XMLHttpRequest API compatibility
- Re: [widgets] dropping Asynchronous HTTP Requests and Storage
- [webstorage] readTransaction clarification
- Re: [widgets] dropping Asynchronous HTTP Requests and Storage
- Re: [widgets] dropping Asynchronous HTTP Requests and Storage
- Re: [widgets] dropping Asynchronous HTTP Requests and Storage
- RE: [widgets] New WD of Widgets 1.0: Digital Signatures spec published on March 31
- Re: [widgets] New WD of Widgets 1.0: Digital Signatures spec published on March 31
- RE: [widgets] New WD of Widgets 1.0: Digital Signatures spec published on March 31
- Re: [widgets] dropping Asynchronous HTTP Requests and Storage
- Re: [cors] security issue with XMLHttpRequest API compatibility
- Re: [cors] security issue with XMLHttpRequest API compatibility
- Re: [cors] security issue with XMLHttpRequest API compatibility
Monday, 6 April 2009
- Re: [cors] security issue with XMLHttpRequest API compatibility
- Re: [cors] security issue with XMLHttpRequest API compatibility
- Re: [cors] security issue with XMLHttpRequest API compatibility
- Re: [cors] security issue with XMLHttpRequest API compatibility
- Re: [cors] security issue with XMLHttpRequest API compatibility
- Re: [cors] security issue with XMLHttpRequest API compatibility
- Re: Do we need to rename the Origin header?
- Re: Do we need to rename the Origin header?
- Re: [cors] security issue with XMLHttpRequest API compatibility
- Re: Do we need to rename the Origin header?
- Re: Do we need to rename the Origin header?
- Re: Do we need to rename the Origin header?
- Re: Do we need to rename the Origin header?
- [cors] security issue with XMLHttpRequest API compatibility
- Re: [widgets] remove update related methods form A&E
- Re: [widgets] dropping Asynchronous HTTP Requests and Storage
- Re: [widgets] dropping Asynchronous HTTP Requests and Storage
- Re: Do we need to rename the Origin header?
- Re: [widgets] remove update related methods form A&E
- [widgets] remove update related methods form A&E
- Re: [widgets] dropping Asynchronous HTTP Requests and Storage
- Re: Do we need to rename the Origin header?
- Re: [widgets] dropping Asynchronous HTTP Requests and Storage
- Re: [widgets] dropping Asynchronous HTTP Requests and Storage
- Re: [widgets] dropping Asynchronous HTTP Requests and Storage
- [widgets] dropping Asynchronous HTTP Requests and Storage
- Re: Do we need to rename the Origin header?
- Re: CORS for file-based web apps
Sunday, 5 April 2009
- CORS for file-based web apps
- Re: CfC: FPWD of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers; deadline April 10
- Re: Do we need to rename the Origin header?
- Re: Do we need to rename the Origin header?
Saturday, 4 April 2009
Friday, 3 April 2009
- Re: Request for Review: Cross-Origin Resource Sharing
- Request for Review: Cross-Origin Resource Sharing
- Re: Do we need to rename the Origin header?
- Re: Do we need to rename the Origin header?
- RE: Widgets 1.0 Packaging and Configuration: I18N comments...
- Re: Widgets 1.0 Packaging and Configuration: I18N comments...
- RE: Widgets 1.0 Packaging and Configuration: I18N comments...
- Re: Widgets 1.0 Packaging and Configuration: I18N comments...
- Re: [widgets] Zip endian issue?
- [widgets] Zip endian issue?
- [widgets] <update> element
- Re: Widget Packaging and configuration LC review
- Re: Do we need to rename the Origin header?
Thursday, 2 April 2009
- Re: CfC: FPWD of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers; deadline April 10
- RE: ISSUE-83 (digsig should not be read at runtime): Instantiated widget should not be able to read digital signature [Widgets]
- Re: ISSUE-83 (digsig should not be read at runtime): Instantiated widget should not be able to read digital signature [Widgets]
- RE: ISSUE-83 (digsig should not be read at runtime): Instantiated widget should not be able to read digital signature [Widgets]
- Re: CfC: FPWD of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers; deadline April 10
- Re: CfC: FPWD of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers; deadline April 10
- CfC: FPWD of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers; deadline April 10
- Re: Request for FPWD publication of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers
- [widgets] New WD of Widgets 1.0: Digital Signatures spec published on March 31
- Re: Request for FPWD publication of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers
- [widgets] Draft Minutes from 2 April 2009 Voice Conference
Wednesday, 1 April 2009
- Request for FPWD publication of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers
- [DOM3Events] Regards for teleconference of 4/1/2009
- [widgets] Agenda for 2 April 2009 Voice Conference; NOTE TIME CHANGE FOR NON-US!
- [widgets] Widget spec plan presented to BONDI Steering Group
- Re: [XHR] Authorization header
- Re: [XHR] Authorization header
- Re: [XHR] Authorization header
- Re: [XHR] Authorization header
- [XHR] Authorization header