Tuesday, 29 December 2009
Thursday, 24 December 2009
Wednesday, 23 December 2009
- [XHR][XHR2] single source file
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- WebApps' 2009 publication summary -> KUTGW!
- Re: [WebSimpleDB] Introduce a pause/resume pattern for coordinated access to multiple stores
- [WebSimpleDB] Introduce a pause/resume pattern for coordinated access to multiple stores
Tuesday, 22 December 2009
- RE: [WebSimpleDB] Allowing schema operations anywhere
- RE: to publish new Working Draft of Indexed Database API; deadline December 21
- Re: to publish new Working Draft of Indexed Database API; deadline December 21
- Seeking comments on LCWDs of Server-events, Web Storage, Web Workers; deadline 30-June-2010
- RE: [widgets] View Modes Media Feature document from Vodafone
- Re: to publish new Working Draft of Indexed Database API; deadline December 21
- RE: to publish new Working Draft of Indexed Database API; deadline December 21
- RE: to publish new Working Draft of Indexed Database API; deadline December 21
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
Monday, 21 December 2009
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: [widgets] Request for Comments: LCWD of Widget Access Request Policy spec; deadline 13-Jan-2010
- Re: XMLHttpRequest Comments from W3C Forms WG
- Re: [widgets] white space handling
- Re: XMLHttpRequest Comments from W3C Forms WG
Sunday, 20 December 2009
- Re: XMLHttpRequest Comments from W3C Forms WG
- Re: XMLHttpRequest Comments from W3C Forms WG
- Re: XMLHttpRequest Comments from W3C Forms WG
- Re: Are we making a Category Mistake?
- Re: Are we making a Category Mistake?
- Re: Are we making a Category Mistake?
- Re: Are we making a Category Mistake?
- Re: Are we making a Category Mistake?
- Re: Are we making a Category Mistake?
- Re: Are we making a Category Mistake?
- Re: Are we making a Category Mistake?
Saturday, 19 December 2009
Friday, 18 December 2009
- RE: [public-webapps] Comments on Widget URI (General)
- Re: XMLHttpRequest Comments from W3C Forms WG
- RE: XMLHttpRequest Comments from W3C Forms WG
- RE: XMLHttpRequest Comments from W3C Forms WG
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- RE: XMLHttpRequest Comments from W3C Forms WG
- Re: [widgets] white space handling
- Are we making a Category Mistake?
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: [widgets] white space handling
- Re: Seeking status of testing Widget Digital Signature spec
- Re: [widgets] white space handling
- Re: [widgets] View Modes Media Feature document from Vodafone
- Re: Why preflight per-resource rather than per-origin?
- Re: [widgets] white space handling
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: [widgets] Anyone working on SNIFF in Java?
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: XMLHttpRequest Comments from W3C Forms WG
- Re: XMLHttpRequest Comments from W3C Forms WG
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
Thursday, 17 December 2009
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- RE: XMLHttpRequest Comments from W3C Forms WG
- Re: XMLHttpRequest Comments from W3C Forms WG
- RE: XMLHttpRequest Comments from W3C Forms WG
- Re: XMLHttpRequest Comments from W3C Forms WG
- RE: XMLHttpRequest Comments from W3C Forms WG
- Re: XMLHttpRequest Comments from W3C Forms WG
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- RE: XMLHttpRequest Comments from W3C Forms WG
- [widgets] Anyone working on SNIFF in Java?
- Why preflight per-resource rather than per-origin?
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: XMLHttpRequest Comments from W3C Forms WG
- RE: XMLHttpRequest Comments from W3C Forms WG
- RE: XMLHttpRequest Comments from W3C Forms WG
- Re: XMLHttpRequest Comments from W3C Forms WG
- Re: [DataCache] Some Corrections
- Re: XMLHttpRequest Comments from W3C Forms WG
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- RE: XMLHttpRequest Comments from W3C Forms WG
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: XMLHttpRequest Comments from W3C Forms WG
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: [widgets] test-suite: start file encoding
- RE: XMLHttpRequest Comments from W3C Forms WG
- Re: XMLHttpRequest Comments from W3C Forms WG
- [widgets] test-suite: start file encoding
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- RE: XMLHttpRequest Comments from W3C Forms WG
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- [widgets] Draft Minutes for 17 December 2009 Voice Conference
- [widgets] Authorities will never have authority?
- [widgets] white space handling
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: XMLHttpRequest Comments from W3C Forms WG
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- [DataCache] Event Handlers on DataCache
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: [DataCache] Some Corrections
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- [DataCache] Remove or Replace a Local Server Handler?
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: CfC: to publish LCWD of: Server-Events, Web {SQL Database, Sockets, Storage, Worker}; deadline 15 December
- RE: [public-webapps] Comment on Widget URI (7)
- Re: [DataCache] CacheTransaction missing committed state
- Re: CfC: to publish LCWD of: Server-Events, Web {SQL Database, Sockets, Storage, Worker}; deadline 15 December
- Re: [DataCache] Some Corrections
- Re: [DataCache] Some Corrections
- Re: [DataCache] Some Corrections
- Re: [DataCache] Some Corrections
Wednesday, 16 December 2009
- Re: [DataCache] Some Corrections
- Re: [DataCache] Some Corrections
- RE: XMLHttpRequest Comments from W3C Forms WG
- Re: CfC: to publish LCWD of: Server-Events, Web {SQL Database, Sockets, Storage, Worker}; deadline 15 December
- RE: XMLHttpRequest Comments from W3C Forms WG
- Re: CfC: to publish LCWD of: Server-Events, Web {SQL Database, Sockets, Storage, Worker}; deadline 15 December
- RE: XMLHttpRequest Comments from W3C Forms WG
- Re: XMLHttpRequest Comments from W3C Forms WG
- Re: The most basic File API use case
- RE: XMLHttpRequest Comments from W3C Forms WG
- RE: XMLHttpRequest Comments from W3C Forms WG
- RE: XMLHttpRequest Comments from W3C Forms WG
- Re: [xhr] events for async requests (was: Re: [whatwg] Thread to run Web Socket feedback from the protocol ?)
- Re: CfC: to publish LCWD of: Server-Events, Web {SQL Database, Sockets, Storage, Worker}; deadline 15 December
- Re: CfC: to publish LCWD of: Server-Events, Web {SQL Database, Sockets, Storage, Worker}; deadline 15 December
- FW: [widgets] comments re View Modes Interface spec
- Re: The most basic File API use case
- Re: [xhr] events for async requests (was: Re: [whatwg] Thread to run Web Socket feedback from the protocol ?)
- Re: CfC: to publish LCWD of: Server-Events, Web {SQL Database, Sockets, Storage, Worker}; deadline 15 December
- Re: [xhr] Blocked headers with underscore rather than hyphen (was: Re: call for reviewers: XMLHttpRequest Last Call)
- [xhr] Blocked headers with underscore rather than hyphen (was: Re: call for reviewers: XMLHttpRequest Last Call)
- Re: [XHR] Small text correction.
- Re: Comments on Last Call Working Draft of XHR
- Re: XMLHttpRequest Comments from W3C Forms WG
- [xhr] events for async requests (was: Re: [whatwg] Thread to run Web Socket feedback from the protocol ?)
- Regrets
- [widgets] Draft Agenda for 17 December 2009 voice conference
- Re: Widget specification - liquid height support
- Widget packaging conformance
- RE: Widget specification - liquid height support
- Re: CfC: to publish LCWD of: Server-Events, Web {SQL Database, Sockets, Storage, Worker}; deadline 15 December
- [widgets] duplicated feature elements ?
- [widgets] feature: inconsistent behavior ?
- [widgets] features: default value for required
- RE: CfC: to publish LCWD of: Server-Events, Web {SQL Database, Sockets, Storage, Worker}; deadline 15 December
- RE: Microsoft pre-LCWD feedback on WebSocket API
- Re: [public-webapps] Comment on Widget URI (3)
Tuesday, 15 December 2009
- Re: [AC/CORS] Proper behavior for user agents who return 'null' Access-Control-Allow-Origin
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: [public-webapps] Comment on Widget URI (5)
- Re: [public-webapps] Comment on Widget URI (2)
- Re: [widgets] test suite: br.wgt
- Re: [public-webapps] Comment on Widget URI (5)
- Re: [public-webapps] Comments on Widget URI (General)
- Re: [widgets] test suite: br.wgt
- Re: [widgets] test suite: br.wgt
- Re: [public-webapps] Comment on Widget URI (5)
- Re: [public-webapps] Comment on Widget URI (3)
- [widgets] test suite: br.wgt
- Re: [widgets] test suite, the width/height attribute
- Re: [public-webapps] Comment on Widget URI (2)
- Re: [public-webapps] Comment on Widget URI (1)
- Re: [public-webapps] Comments on Widget URI (General)
- Re: [public-webapps] Comment on Widget URI (4)
- Re: [public-webapps] Comment on Widget URI (7)
- Re: [public-webapps] Comment on Widget URI (7)
- Re: CfC: to publish LCWD of: Server-Events, Web {SQL Database, Sockets, Storage, Worker}; deadline 15 December
- Re: [AC/CORS] Proper behavior for user agents who return 'null' Access-Control-Allow-Origin
- [XHR] Small text correction.
- Re: [widgets] test suite, the width/height attribute
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: Next Steps for CORS and Uniform Messaging [Was: Re: CORS versus Uniform Messaging?]
Monday, 14 December 2009
- Re: Caching breakout session at TPAC
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: Next Steps for CORS and Uniform Messaging [Was: Re: CORS versus Uniform Messaging?]
- Re: CORS versus Uniform Messaging?
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: Wiki for WebApps' Database, Storage, AppCache and related specs
- CfC: to publish new Working Draft of Indexed Database API; deadline December 21
- Re: Next Steps for CORS and Uniform Messaging [Was: Re: CORS versus Uniform Messaging?]
- Re: CORS versus Uniform Messaging?
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: Wiki for WebApps' Database, Storage, AppCache and related specs
- Re: Next Steps for CORS and Uniform Messaging [Was: Re: CORS versus Uniform Messaging?]
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Indexed Database API (previously WebSimpleDB) ready for a new WD
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: Next Steps for CORS and Uniform Messaging [Was: Re: CORS versus Uniform Messaging?]
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- [widgets] Widget Updates PAG recommendations
- Re: [widgets] test suite, the width/height attribute
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- [widgets] View Modes Media Feature document from Vodafone
- Next Steps for CORS and Uniform Messaging [Was: Re: CORS versus Uniform Messaging?]
- Re: [AC/CORS] Proper behavior for user agents who return 'null' Access-Control-Allow-Origin
- Re: CORS versus Uniform Messaging?
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
Sunday, 13 December 2009
- Re: Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Scientific Literature on Capabilities (was Re: CORS versus Uniform Messaging?)
- Re: CORS versus Uniform Messaging?
- Re: CORS versus Uniform Messaging?
- Re: CORS versus Uniform Messaging?
- Re: CORS versus Uniform Messaging?
- Re: CORS versus Uniform Messaging?
- Re: CORS versus Uniform Messaging?
- Re: CORS versus Uniform Messaging?
- Re: CORS versus Uniform Messaging?
Saturday, 12 December 2009
- Re: CfC: to publish LCWD of: Server-Events, Web {SQL Database, Sockets, Storage, Worker}; deadline 15 December
- Re: CfC: to publish LCWD of: Server-Events, Web {SQL Database, Sockets, Storage, Worker}; deadline 15 December
- Re: CfC: to publish LCWD of: Server-Events, Web {SQL Database, Sockets, Storage, Worker}; deadline 15 December
- Re: CfC: to publish LCWD of: Server-Events, Web {SQL Database, Sockets, Storage, Worker}; deadline 15 December
Friday, 11 December 2009
- Re: [DataCache] Updated Examples
- Re: [WebSimpleDB] Flatting APIs to simplify primary cases
- Re: [WebSimpleDB] Allowing schema operations anywhere
- Re: WebSimpleDB Issues
- [widgets] Widget Interface Test Suite
- Re: Widget specification - liquid height support
- Re: [WARP] comment on subdomains
- Re: Web Storage Mutex
- Re: [AC/CORS] Proper behavior for user agents who return 'null' Access-Control-Allow-Origin
- Web Storage Mutex
Thursday, 10 December 2009
- [AC/CORS] Proper behavior for user agents who return 'null' Access-Control-Allow-Origin
- WebGL | The 3D Canvas Context for HTML
- Widget specification - liquid height support
- Re: [widgets] test-cases for icons: some possible errors
- Re: Semi-public resources in Uniform Messaging
- [DataCache] Updated Examples
- Re: The most basic File API use case
- Re: CORS versus Uniform Messaging?
- Re: Semi-public resources in Uniform Messaging
- Re: CORS versus Uniform Messaging?
- Re: Semi-public resources in Uniform Messaging
- [DataCache] CacheTransaction missing committed state
- [DataCache] Unhandled Cases in Networking Changes
- Re: CORS versus Uniform Messaging?
- Fwd: Draft PER of Associating Style Sheets with XML documents 1.0 (Second Edition) available for review
- Re: The most basic File API use case
- [DataCache] "ready" CacheEvent and Related Questions
- Re: The most basic File API use case
- Re: Semi-public resources in Uniform Messaging
- Re: Semi-public resources in Uniform Messaging
- [WARP] comment on subdomains
- Re: [widgets] Draft Minutes for 10 December 2009 Voice Conference
- [widgets] Draft Minutes for 10 December 2009 Voice Conference
- Re: [WARP4U] WARP with UPnP
- Re: File API: Directories and System
- Re: Semi-public resources in Uniform Messaging
- Re: [widgets] test-cases for icons: some possible errors
Wednesday, 9 December 2009
- Re: Semi-public resources in Uniform Messaging
- Re: [widgets] test-cases for icons: some possible errors
- Re: [widgets] test-cases for icons: some possible errors
- Re: The most basic File API use case
- Re: Semi-public resources in Uniform Messaging
- RE: [public-webapps] Comment on Widget URI (7)
- Re: The most basic File API use case
- Re: Semi-public resources in Uniform Messaging
- RE: [public-webapps] Comment on Widget URI (7)
- File API: Directories and System
- RE: [public-webapps] Comment on Widget URI (4)
- RE: [public-webapps] Comment on Widget URI (3)
- Re: Semi-public resources in Uniform Messaging
- Re: Semi-public resources in Uniform Messaging
- RE: [public-webapps] Comment on Widget URI (2)
- Re: Length of LC comment period
- Re: Length of LC comment period
- Re: Semi-public resources in Uniform Messaging
- Re: Semi-public resources in Uniform Messaging
- Re: [widgets] test-cases for icons: some possible errors
- Re: [widgets] test-cases for icons: some possible errors
- Re: [widgets] test-cases for icons: some possible errors
- [widgets] Draft Agenda for 10 December 2009 Voice Conf
- Re: [widgets] test-cases for icons: some possible errors
- Re: Length of LC comment period
- Re: Length of LC comment period
- Re: [widgets] test-cases for icons: some possible errors
- [widgets] P&C simplifying some rules (editorial)
- RE: [EventSource] Comments to the current draft
- Re: call for reviewers: XMLHttpRequest Last Call
- Re: call for reviewers: XMLHttpRequest Last Call
- Re: Length of LC comment period
- Re: Semi-public resources in Uniform Messaging
- Re: Semi-public resources in Uniform Messaging
- Re: Length of LC comment period
Tuesday, 8 December 2009
- oops: Re: Feedback on the Strict-Transport-Security specification (EricLaw)
- Re: Feedback on the Strict-Transport-Security specification (Adam)
- Feedback on the Strict-Transport-Security specification (EricLaw)
- Strict Transport Security (STS) discussion -> public-web-security@w3.org
- Re: Welcome to the W3C web security mailing list
- Re: Feedback on WebSocket API, Editor's Draft 13 November 2009.
- Re: Semi-public resources in Uniform Messaging
- Re: Semi-public resources in Uniform Messaging
- [widgets] Request for Comments: LCWD of Widget Access Request Policy spec; deadline 13-Jan-2010
- Re: [WebSimpleDB] Allowing schema operations anywhere
- Re: Semi-public resources in Uniform Messaging
- Re: The most basic File API use case
- Re: Length of LC comment period
- Re: Length of LC comment period
- Re: Length of LC comment period
- Re: Length of LC comment period
- Semi-public resources in Uniform Messaging
- Re: Length of LC comment period
- Re: Length of LC comment period
- Re: CfC: to publish LCWD of: Server-Events, Web {SQL Database, Sockets, Storage, Worker}; deadline 15 December
- Re: The most basic File API use case
- CfC: to publish LCWD of: Server-Events, Web {SQL Database, Sockets, Storage, Worker}; deadline 15 December
- RE: [EventSource] Comments to the current draft
Monday, 7 December 2009
- Re: The most basic File API use case
- Re: [DataCache] Some Corrections
- RE: [public-webapps] Comments on Widget URI (General)
- RE: [public-webapps] Comment on Widget URI (1)
- Re: Patent disclosure for UniMess? [Was: [cors] Uniform Messaging, a CSRF resistant profile of CORS]
- Re: Patent disclosure for UM? [Was: Patent disclosure for UniMess? [Was: [cors] Uniform Messaging, a CSRF resistant profile of CORS]]
- Patent disclosure for UM? [Was: Patent disclosure for UniMess? [Was: [cors] Uniform Messaging, a CSRF resistant profile of CORS]]
- XHR LC comment: header encoding
- Re: The most basic File API use case
- Re: Length of LC comment period
- Re: Length of LC comment period
- RE: [widgets] comments re View Modes Interface spec
- Re: Length of LC comment period [Was: Ready for LC on the various drafts I edit]
- Re: Length of LC comment period [Was: Ready for LC on the various drafts I edit]
- Re: Length of LC comment period [Was: Ready for LC on the various drafts I edit]
- Re: Length of LC comment period [Was: Ready for LC on the various drafts I edit]
- Re: Length of LC comment period [Was: Ready for LC on the various drafts I edit]
Sunday, 6 December 2009
- Re: Length of LC comment period [Was: Ready for LC on the various drafts I edit]
- Patent disclosure for UniMess? [Was: [cors] Uniform Messaging, a CSRF resistant profile of CORS]
- Re: Length of LC comment period [Was: Ready for LC on the various drafts I edit]
- Re: Length of LC comment period [Was: Ready for LC on the various drafts I edit]
- Spam Alert (was: Warning Notice!!!)
Friday, 4 December 2009
Saturday, 5 December 2009
- Re: Length of LC comment period [Was: Ready for LC on the various drafts I edit]
- Re: Feedback on WebSocket API, Editor's Draft 13 November 2009.
- Re: Length of LC comment period [Was: Ready for LC on the various drafts I edit]
- Re: Length of LC comment period [Was: Ready for LC on the various drafts I edit]
Friday, 4 December 2009
- Re: CORS versus Uniform Messaging? [Was: [cors] Uniform Messaging, a CSRF resistant profile of CORS]
- CORS versus Uniform Messaging? [Was: [cors] Uniform Messaging, a CSRF resistant profile of CORS]
- [DataCache] Some Corrections
- Re: Length of LC comment period [Was: Ready for LC on the various drafts I edit]
- Re: Length of LC comment period [Was: Ready for LC on the various drafts I edit]
- Re: suggestion - RJavaScript
- Re: [widgets] test-cases for icons: some possible errors
- [widgets] test suite, the width/height attribute
- Re: Feedback on WebSocket API, Editor's Draft 13 November 2009.
- [widgets] comments re View Modes Interface spec
- Re: Length of LC comment period [Was: Ready for LC on the various drafts I edit]
- Re: Length of LC comment period [Was: Ready for LC on the various drafts I edit]
- Length of LC comment period [Was: Ready for LC on the various drafts I edit]
- Re: Feedback on WebSocket API, Editor's Draft 13 November 2009.
- suggestion - RJavaScript
- Re: Feedback on WebSocket API, Editor's Draft 13 November 2009.
- Re: The most basic File API use case
- Ready for LC on the various drafts I edit
- Re: Feedback on WebSocket API, Editor's Draft 13 November 2009.
- Re: Microsoft pre-LCWD feedback on WebSocket API
Thursday, 3 December 2009
- Re: Feedback on the Strict-Transport-Security specification (part 2)
- Re: Feedback on the Strict-Transport-Security specification (part 1)
- Re: Wiki for WebApps' Database, Storage, AppCache and related specs
- RE: [WARP4U] WARP with UPnP, was: RE: [widgets] Draft Minutes for 19 November 2009 Voice Conference
- Re: Wiki for WebApps' Database, Storage, AppCache and related specs
- Re: [widgets] test-cases for icons: some possible errors
- Re: [WARP4U] WARP with UPnP, was: RE: [widgets] Draft Minutes for 19 November 2009 Voice Conference
- Re: Wiki for WebApps' Database, Storage, AppCache and related specs
- Re: XHR LC
- XHR LC
- [widgets] Draft Minutes for 3 December 2009 Voice Conference
- Re: [widgets] Interface published
- Re: [WARP4U] WARP with UPnP
- Re: [widgets] CfC: to publish LC#2 of the WARP spec; deadline 2 December
- RE: [widgets] CfC: to publish LC#2 of the WARP spec; deadline 2 December
- Re: [widgets] CfC: to publish LC#2 of the WARP spec; deadline 2 December
- Re: [WARP4U] WARP with UPnP
- Re: [WARP4U] WARP with UPnP
- Re: Fwd: Welcome to the W3C web security mailing list
Wednesday, 2 December 2009
- Wiki for WebApps' Database, Storage, AppCache and related specs
- RE: [widgets] CfC: to publish LC#2 of the WARP spec; deadline 2 December
- Re: Indexed Database API is the new title [Was: Renaming WebSimpleDB]
- Re: WebSimpleDB Issues
- Re: [widgets] CfC: to publish LC#2 of the WARP spec; deadline 2 December
- Indexed Database API is the new title [Was: Renaming WebSimpleDB]
- Re: [WARP4U] WARP with UPnP, was: RE: [widgets] Draft Minutes for 19 November 2009 Voice Conference
- RE: [WARP4U] WARP with UPnP, was: RE: [widgets] Draft Minutes for 19 November 2009 Voice Conference
- Re: [widgets] CfC: to publish LC#2 of the WARP spec; deadline 2 December
- Re: [WARP4U] WARP with UPnP, was: RE: [widgets] Draft Minutes for 19 November 2009 Voice Conference
- [widgets] Draft Agenda for 3 December 2009 Voice Conf
- Re: [widgets] CfC: to publish LC#2 of the WARP spec; deadline 2 December
- RE: [WARP4U] WARP with UPnP
- Re: [WARP4U] WARP with UPnP
- Re: [WARP4U] WARP with UPnP
- Re: [widgets] CfC: to publish LC#2 of the WARP spec; deadline 2 December
- Re: Transaction callback for localStorage mutex?
- Re: Transaction callback for localStorage mutex?
- RE: [widgets] CfC: to publish LC#2 of the WARP spec; deadline 2 December
- WebSimpleDB Issues
- Re: [webdatabase] Handling of the query arguments
- Re: Let's turn WebDatabase into a WG Note
- Re: Transaction callback for localStorage mutex?
- Re: Transaction callback for localStorage mutex?
- Transaction callback for localStorage mutex?
Tuesday, 1 December 2009
- Re: [widgets] CfC: to publish LC#2 of the WARP spec; deadline 2 December
- RE: [WARP4U] WARP with UPnP, was: RE: [widgets] Draft Minutes for 19 November 2009 Voice Conference
- RE: [widgets] CfC: to publish LC#2 of the WARP spec; deadline 2 December
- Re: [widgets] element-based localization
- Re: CfC - publish Selectors API as CR
- Fwd: Welcome to the W3C web security mailing list
- Re: [widgets] element-based localization
- Re: [widgets] element-based localization
- Re: [widgets] element-based localization
- Re: [public-webapps] Comments on Widget URI (General)
- Re: [webworkers] SharedWorker and ApplicationCache
- [Bug 8406] New: Stricter Specifications on Mouse Events Specifically primary, auxillary, and secondary default actions
- Re: Seeking pre-LCWD comments for: Server-sent Events, Web {Database, Sockets, Storage Workers}; deadline 19 November
- Re: Renaming WebDatabase and WebSimpleDB
- Re: Renaming WebDatabase and WebSimpleDB
- Re: [EventSource] Comments to the current draft
- Re: [webdatabase] wording on "Parsing and processing SQL statements" section
- Re: WebDatabase bug tracking
- Re: [web databases] SQLStatementErrorCallback
- Re: [web databases] changeVersion error reporting
- Re: [webdatabase] Minor Clarification Needed in Processing Model
- Re: [web databases] about rowids
- RE: CfC: to publish the First Public Working Draft of Web Database spec; deadline 7 September
- Re: Renaming WebDatabase and WebSimpleDB
- Re: Renaming WebDatabase and WebSimpleDB
- Re: WebDatabase review: SQLResultSetRowList
- Re: Renaming WebDatabase and WebSimpleDB
- Re: Renaming WebDatabase and WebSimpleDB
- Re: Renaming WebDatabase and WebSimpleDB
- Re: Renaming WebDatabase and WebSimpleDB
- Re: CfC - publish Selectors API as CR
Monday, 30 November 2009
- Re: Renaming WebDatabase and WebSimpleDB
- Re: Renaming WebDatabase and WebSimpleDB
- Re: Renaming WebDatabase and WebSimpleDB
- Re: Renaming WebDatabase and WebSimpleDB
- Re: [widgets] element-based localization
- [widgets] Reminder: the Widget Interface LC comment period ends December 8
- Re: [widgets] Publishing LC#2 of the WARP spec
- Re: [WARP4U] WARP with UPnP, was: RE: [widgets] Draft Minutes for 19 November 2009 Voice Conference
- Re: [WARP4U] WARP with UPnP
- Re: [WARP4U] WARP with UPnP
- [widgets] PAG Launched for Widgets 1.0: Access Requests Policy (WARP) spec
- Re: [selectors-api] querySelector with namespace
- Re: [selectors-api] querySelector with namespace
- Re: [widgets] CfC: to publish LC#2 of the WARP spec; deadline 2 December
- Re: [widgets] element-based localization
- Re: [selectors-api] querySelector with namespace
- Re: [widgets] test-suite, default xml:lang
- Re: [widgets] CfC: to publish LC#2 of the WARP spec; deadline 2 December
- Re: [selectors-api] querySelector with namespace
- Re: [widgets] Interface published
- Re: [widgets] Test suite full coverage of mandatory aspects in the P&C spec, was Re: OMTP BONDI Reference Implementation fully compliant against mandatory P&C tests
- Re: [widgets] Test suite full coverage of mandatory aspects in the P&C spec, was Re: OMTP BONDI Reference Implementation fully compliant against mandatory P&C tests
Sunday, 29 November 2009
Saturday, 28 November 2009
- Re: [widgets] Test suite full coverage of mandatory aspects in the P&C spec, was Re: OMTP BONDI Reference Implementation fully compliant against mandatory P&C tests
- [widgets] Test suite full coverage of mandatory aspects in the P&C spec, was Re: OMTP BONDI Reference Implementation fully compliant against mandatory P&C tests
- OMTP BONDI Reference Implementation fully compliant against mandatory P&C tests
- Re: The most basic File API use case
- Re: The most basic File API use case
- Re: CfC - publish Selectors API as CR
Friday, 27 November 2009
- Re: [widgets] test suite, duplicated test
- Re: [widgets] element-based localization
- Re: [widgets] element-based localization
- Re: [widgets] test-suite, default xml:lang
- Re: [widgets] editing problem
- Re: [widgets] Testing ITS support
- RE: [widgets] editing problem
- [widgets] editing problem
- [widgets] CfC: to publish LC#2 of the WARP spec; deadline 2 December
- Re: [widgets] Testing ITS support
- [widgets] test suite, duplicated test
- Re: [widgets] about test d1.wgt
- Re: [widgets] Testing ITS support
- Re: Selectors CR criteria
- RE: [widgets] Testing ITS support
- Re: [widgets] test-suite, default xml:lang
- [widgets] Testing ITS support
Thursday, 26 November 2009
- Selectors CR criteria (was re: Something else)
- Re: CfC - publish Selectors API as CR
- Re: CfC - publish Selectors API as CR
- Re: CfC - publish Selectors API as CR
- Re: CfC - publish Selectors API as CR
- Re: CfC - publish Selectors API as CR
- Re: CfC - publish Selectors API as CR
- Comments on Last Call Working Draft of XHR
- Re: CfC - publish Selectors API as CR
- Re: [widgets] about test d1.wgt
- Re: CfC - publish Selectors API as CR
- [widgets] test-suite, default xml:lang
- Re: CfC - publish Selectors API as CR
- Re: [selectors-api] querySelector with namespace
- Re: [selectors-api] querySelector with namespace
- Re: CfC - publish Selectors API as CR
- [widgets] element-based localization
- Re: [selectors-api] querySelector with namespace
- Re: Renaming WebDatabase and WebSimpleDB
- Re: [selectors-api] querySelector with namespace
- Re: [selectors-api] querySelector with namespace
- Re: Renaming WebDatabase and WebSimpleDB
- Re: [selectors-api] querySelector with namespace
- Re: [selectors-api] querySelector with namespace
- Re: Renaming WebDatabase and WebSimpleDB
- Re: [selectors-api] querySelector with namespace
- [selectors-api] querySelector with namespace
- Renaming WebDatabase and WebSimpleDB
- Re: Seeking pre-LCWD comments for: Server-sent Events, Web {Database, Sockets, Storage Workers}; deadline 19 November
- Re: Seeking pre-LCWD comments for: Server-sent Events, Web {Database, Sockets, Storage Workers}; deadline 19 November
- Re: [webstorage] deleting a database
- Re: [webstorage] deleting a database
- Re: [webstorage] deleting a database
- Re: [webstorage] deleting a database
- Re: Exceptions in WebDatabase
- Re: WebDatabase open interface methods
- Re: [webstorage] deleting a database
- Re: [webstorage] deleting a database
- Re: WebStorage and WebDatabase - creation and exceptions
- Re: [webdatabase] Transaction Locks
- Re: [webstorage] deleting a database
- Re: [webstorage] deleting a database
- Re: Detailed review of 4.12. Client-side database storage
Wednesday, 25 November 2009
- [Bug 8358] [WA] Fix for the localStorage mutex problem - release for *any* API operation except localStorage itself
- Re: Feedback on WebSocket API, Editor's Draft 13 November 2009.
- Re: Seeking pre-LCWD comments for: Server-sent Events, Web {Database, Sockets, Storage Workers}; deadline 19 November
- RE: XMLHttpRequest Comments from W3C Forms WG
- RE: XMLHttpRequest Comments from W3C Forms WG
- Re: XMLHttpRequest Comments from W3C Forms WG
- XMLHttpRequest Comments from W3C Forms WG
- [widgets] Publishing LC#2 of the WARP spec
- Feedback on WebSocket API, Editor's Draft 13 November 2009.
- Re: WebSimpleDB object caching
- Postponed: CfC: to publish LCWD of: Sever-Sent Events, Web Storage and Web Workers
- Re: [widgets] Interface published
- Re: Seeking pre-LCWD comments for: Server-sent Events, Web {Database, Sockets, Storage Workers}; deadline 19 November
Tuesday, 24 November 2009
- Re: [WebSimpleDB] Flatting APIs to simplify primary cases
- Re: [WebSimpleDB] Allowing schema operations anywhere
- Re: CfC - publish Selectors API as CR
- Re: CfC - publish Selectors API as CR
- Re: CfC - publish Selectors API as CR
- Re: [selectors-api] Test Suite Progress
- Widgeon release (was P+C implementation report: Widgeon)
Monday, 23 November 2009
- [Bug 8358] New: Fix for the localStorage mutex problem - release for *any* API operation except localStorage itself
- Re: Proposal for sending multiple files via XMLHttpRequest.send()
- Re: CfC - publish Selectors API as CR
- Re: [cors] Uniform Messaging, a CSRF resistant profile of CORS
- P+C implementation report: Widgeon
- Re: The most basic File API use case
- Re: [webdatabase] Why does W3C have to worry about SQL dialect?
Sunday, 22 November 2009
- [WebSimpleDB] Allowing schema operations anywhere
- RE: File writing ponderings (was: Re: Security evaluation of an example DAP policy)
- What is the Plan for Web Database? [Was: Re: Notes About Notes
- ISSUE-111 (mouse z): Add z attribute to mouse events? [DOM3 Events]
Saturday, 21 November 2009
- Re: [cors] Uniform Messaging, a CSRF resistant profile of CORS
- Re: [webdatabase] Why does W3C have to worry about SQL dialect?
- [webdatabase] Why does W3C have to worry about SQL dialect?
- Notes About Notes (was: Let's turn WebDatabase into a WG Note)
- Re: [cors] Uniform Messaging, a CSRF resistant profile of CORS
- Re: File writing ponderings (was: Re: Security evaluation of an example DAP policy)
- File writing ponderings (was: Re: Security evaluation of an example DAP policy)
- Re: Security evaluation of an example DAP policy
- Re: Let's turn WebDatabase into a WG Note
- [cors] Uniform Messaging, a CSRF resistant profile of CORS
- Re: The most basic File API use case
- RE: [widgets] LCWD#3 comments (3)
Friday, 20 November 2009
- [widgets] FW: [whatwg] FYI: Mozilla's Resource Packages
- The most basic File API use case
- RE: Security evaluation of an example DAP policy
- Re: [widgets] LCWD#3 comments (3)
- RE: [widgets] LCWD#3 comments (3)
- Re: [widgets] LCWD#3 comments (3)
- RE: Security evaluation of an example DAP policy
- Re: [widgets] about test d1.wgt
- Re: [widgets] default start file table vs. src attribute
- [widgets] about test d1.wgt
- Re: [widgets] default start file table vs. src attribute
- Re: [widgets] default start file table vs. src attribute
- Re: [widgets] About the test suite
- Re: [widgets] default start file table vs. src attribute
- Re: [widgets] multiple co-authors
- Re: [widgets] default start file table vs. src attribute
- Re: Security evaluation of an example DAP policy
- [WARP4U] WARP with UPnP, was: RE: [widgets] Draft Minutes for 19 November 2009 Voice Conference
- [widgets] default start file table vs. src attribute
- Re: [widgets] Test suite: problem with test cases
- Re: Security evaluation of an example DAP policy
- Re: Security evaluation of an example DAP policy
- Re: Security evaluation of an example DAP policy
- Re: Unzipping content into current directory widely considered poor practice
- Re: Unzipping content into current directory widely considered poor practice
- Re: Unzipping content into current directory widely considered poor practice
- Re: Re: Request for Reviewers: Section 7.4 of Web Security Context: User Interface Guidelines; deadline Sep 24 ( LC-2255)
- Re: [widgets] About the test suite
- RE: Security evaluation of an example DAP policy
- Re: Security evaluation of an example DAP policy
- Re: [Widgets] LCWD#3 comments (2)
- RE: Security evaluation of an example DAP policy
- RE: Let's turn WebDatabase into a WG Note
- Re: Security evaluation of an example DAP policy
- Re: Security evaluation of an example DAP policy
- Re: Security evaluation of an example DAP policy
- Re: [widgets] About the test suite
- Re: Security evaluation of an example DAP policy
- Re: [widgets] Test suite: problem with test cases
- Re: Let's turn WebDatabase into a WG Note
- RE: [widgets] LCWD#3 comments (3)
- CfC: to publish LCWD of: Sever-Sent Events, Web Storage and Web Workers; deadline 27 November
- Re: [widgets] Test suite: problem with test cases
- Re: [widgets] multiple co-authors
- [widgets] LCWD#3 comments (3)
- RE: [Widgets] LCWD#3 comments (2)
- Re: Seeking pre-LCWD comments for: Server-sent Events, Web {Database, Sockets, Storage Workers}; deadline 19 November
- Re: [widgets] About the test suite
- RE: Security evaluation of an example DAP policy
- Unzipping content into current directory widely considered poor practice
- RE: Let's turn WebDatabase into a WG Note
- Re: Security evaluation of an example DAP policy
- RE: Security evaluation of an example DAP policy
- Re: Moving Window and stuff out of HTML5
- Re: Security evaluation of an example DAP policy
- Re: Security evaluation of an example DAP policy
- Re: Security evaluation of an example DAP policy
- RE: Security evaluation of an example DAP policy
- RE: Security evaluation of an example DAP policy
Thursday, 19 November 2009
- Security evaluation of an example DAP policy
- Re: [widgets] Test suite: problem with test cases
- RE: Trying to summarise (was Re: DAP and security)
- Re: [webdatabase] Handling of the query arguments
- Re: [webdatabase] Handling of the query arguments
- [webdatabase] Handling of the query arguments
- RE: Trying to summarise (was Re: DAP and security)
- RE: Trying to summarise (was Re: DAP and security)
- Moving Window and stuff out of HTML5
- Re: [widgets] multiple co-authors
- Microsoft pre-LCWD feedback on WebSocket API
- Re: [widgets] multiple co-authors
- [WebSimpleDB] Flatting APIs to simplify primary cases
- Re: Trying to summarise (was Re: DAP and security)
- RE: Trying to summarise (was Re: DAP and security)
- [widgets] Draft Minutes for 19 November 2009 Voice Conference
- Re: Trying to summarise (was Re: DAP and security)
- Re: DAP and security (was: Rename "File API" to "FileReader API"?)
- Re: DAP and security (was: Rename "File API" to "FileReader API"?)
- RE: Viewmode related issues
- Re: [public-webapps] Comments on Widget URI (General)
- Re: [public-webapps] Comment on Widget URI (1)
- Re: [widgets] Interface published
- Re: [public-webapps] Comment on Widget URI (2)
- Re: [Widgets] LCWD#3 comments (2)
- Re: [widgets] Interface published
- Re: [widgets] Interface published
- RE: Constrained specification of Icon element
- Re: Constrained specification of Icon element
- Re: [public-webapps] Comment on Widget URI (3)
- Re: Trying to summarise (was Re: DAP and security)
- RE: [widgets] The people say "NO" to 1.0, was Re: [public-webapps] Comment on Widget URI (7)
- Re: [public-webapps] Comment on Widget URI (9)
- Re: [public-webapps] Comment on Widget URI (8)
- Re: [public-webapps] Comment on Widget URI (4)
- Re: [public-webapps] Comment on Widget URI (5)
- Re: [public-webapps] Comment on Widget URI (6)
- [widgets] The people say "NO" to 1.0, was Re: [public-webapps] Comment on Widget URI (7)
- Re: Trying to summarise (was Re: DAP and security)
- Re: [public-webapps] Comment on Widget URI (7)
- Re: [widgets] multiple co-authors
- RE: [WARP] Comments to WARP spec
- Re: [WARP] Call for comments on pre-LC#2 of WARP spec; deadline 18 November
- Trying to summarise (was Re: DAP and security)
- [widgets] multiple co-authors
- RE: DAP and security (was: Rename "File API" to "FileReader API"?)
- Re: [WARP] Call for comments on pre-LC#2 of WARP spec; deadline 18 November
- RE: DAP and security (was: Rename "File API" to "FileReader API"?)
- Re: DAP and security (was: Rename "File API" to "FileReader API"?)
- Re: [WARP] Comments to WARP spec
- Re: [FileReader API, ProgressEvents] Design patterns, FileWriter API
- RE: DAP and security (was: Rename "File API" to "FileReader API"?)
- RE: DAP and security (was: Rename "File API" to "FileReader API"?)
- RE: DAP and security (was: Rename "File API" to "FileReader API"?)
- RE: DAP and security (was: Rename "File API" to "FileReader API"?)
- RE: [WARP] Comments to WARP spec
- RE: DAP and security (was: Rename "File API" to "FileReader API"?)
- RE: [FileReader API, ProgressEvents] Design patterns, FileWriter API
- RE: DAP and security (was: Rename "File API" to "FileReader API"?)
- RE: DAP and security (was: Rename "File API" to "FileReader API"?)
- Re: [WARP] Comments to WARP spec
- Re: DAP and security (was: Rename "File API" to "FileReader API"?)
- Re: DAP and security (was: Rename "File API" to "FileReader API"?)
- Re: CfC - publish Selectors API as CR
- Re: DAP and security (was: Rename "File API" to "FileReader API"?)
- Re: DAP and security (was: Rename "File API" to "FileReader API"?)
- RE: DAP and security (was: Rename "File API" to "FileReader API"?)
- RE: DAP and security (was: Rename "File API" to "FileReader API"?)
- RE: DAP and security (was: Rename "File API" to "FileReader API"?)
- RE: [WARP] Comments to WARP spec
- Re: DAP and security (was: Rename "File API" to "FileReader API"?)
- Re: DAP and security (was: Rename "File API" to "FileReader API"?)
- Re: DAP and security (was: Rename "File API" to "FileReader API"?)
- Re: [FileReader API, ProgressEvents] Design patterns, FileWriter API
- Re: CfC - publish Selectors API as CR
Wednesday, 18 November 2009
- Re: [FileReader API, ProgressEvents] Design patterns, FileWriter API
- CfC - publish Selectors API as CR
- Re: Exit criteria Re: [selectors-api] Transitioning to CR
- [WARP] Call for comments on pre-LC#2 of WARP spec; deadline 18 November
- Re: Let's turn WebDatabase into a WG Note
- Re: Let's turn WebDatabase into a WG Note
- Re: Let's turn WebDatabase into a WG Note
- Re: DAP and security (was: Rename "File API" to "FileReader API"?)
- Re: Blob as URN was Re: [FileAPI] Latest Revision of Editor's Draft
- Re: [FileAPI] URL, URI, URN | Re: [FileAPI] Latest Revision of Editor's Draft
- Re: [FileAPI] URL, URI, URN | Re: [FileAPI] Latest Revision of Editor's Draft
- Re: [WARP] Comments to WARP spec
- RE: DAP and security (was: Rename "File API" to "FileReader API"?)
- RE: DAP and security (was: Rename "File API" to "FileReader API"?)
- [widgets] Draft Agenda for 19-Nov-2009 Voice Conf
- Re: [widgets] Test suite: problem with test cases
- RE: [WARP] Comments to WARP spec
- RE: [Widgets] LCWD#3 comments (1)
- RE: [WARP] Comments to WARP spec
- RE: DAP and security (was: Rename "File API" to "FileReader API"?)
- RE: [WARP] Comments to WARP spec
- RE: [FileReader API, ProgressEvents] Design patterns, FileWriter API
- Re: DAP and security (was: Rename “File API” to “FileReader API”?)
- RE: DAP and security (was: Rename “File API” to “FileReader API”?)
- Re: [FileAPI] URL, URI, URN | Re: [FileAPI] Latest Revision of Editor's Draft
- Re: CfC: to publish Last Call Working Draft of XHR (1); deadline 18 November
- RE: [Widgets] LCWD#3 comments (1)
- [Widgets] LCWD#3 comments (2)
- Re: DAP and security (was: Rename “File API” to “FileReader API”?)
- Re: [widgets] Test suite: problem with test cases
- Re: [Widgets] LCWD#3 comments (1)
- Re: [WARP] Comments to WARP spec
- Re: [WARP] Comments to WARP spec
- Re: Let's turn WebDatabase into a WG Note
- Re: [FileAPI] URL, URI, URN | Re: [FileAPI] Latest Revision of Editor's Draft
- Re: [FileReader API, ProgressEvents] Design patterns, FileWriter API
- Re: [widgets] About the test suite
- Re: Rename “File API” to “FileReader API”?
- Re: [FileAPI] File.mediaType
- Re: Let's turn WebDatabase into a WG Note
- Re: CfC: to publish Last Call Working Draft of XHR (1); deadline 18 November
- Re: [FileAPI] URL, URI, URN | Re: [FileAPI] Latest Revision of Editor's Draft
- Re: File upload superseded by File API?
- Re: [FileReader API, ProgressEvents] Design patterns, FileWriter API
- Re: Let's turn WebDatabase into a WG Note
- File upload superseded by File API?
Tuesday, 17 November 2009
Wednesday, 18 November 2009
- Re: [FileAPI] URL, URI, URN | Re: [FileAPI] Latest Revision of Editor's Draft
- Re: Let's turn WebDatabase into a WG Note
- Re: [FileAPI] URL, URI, URN | Re: [FileAPI] Latest Revision of Editor's Draft
- Re: Let's turn WebDatabase into a WG Note
- Re: Let's turn WebDatabase into a WG Note
- Re: CORS and HTTP error responses
- Re: Let's turn WebDatabase into a WG Note
- Re: Let's turn WebDatabase into a WG Note
- Let's turn WebDatabase into a WG Note
- Re: [FileAPI] URL, URI, URN | Re: [FileAPI] Latest Revision of Editor's Draft
- Blob as URN was Re: [FileAPI] Latest Revision of Editor's Draft
- Re: [FileReader API, ProgressEvents] Design patterns, FileWriter API
- [FileAPI] URL, URI, URN | Re: [FileAPI] Latest Revision of Editor's Draft
Tuesday, 17 November 2009
- Re: [widgets] Request for Comments: LCWD of Widget Interface; deadline 8 December 2009
- Re: [FileAPI] File.mediaType
- Re: more flexible ABNF for STS?
- Re: comments from Osmosoft on the File API
- Re: Proposal for sending multiple files via XMLHttpRequest.send()
- Re: Proposal for sending multiple files via XMLHttpRequest.send()
- [Widgets] LCWD#3 comments (1)
- Re: [widgets] Request for Comments: LCWD of Widget Interface; deadline 8 December 2009
- [widgets] Request for Comments: LCWD of Widget Interface; deadline 8 December 2009
- [widgets] Interface published
- Re: propose an API to return Range in <textarea> etc. form control nodes (similar functionality as document.caretRangeFromPoint)
- [cssom-view] caretPositionFromPoint() and views
- Re: CORS and HTTP error responses
- Re: CORS and HTTP error responses
- [FileReader API, ProgressEvents] Design patterns, FileWriter API
- CORS and HTTP error responses
Monday, 16 November 2009
- Re: [FileAPI] FileReader constants
- Re: [FileAPI] File.mediaType
- Re: [FileAPI] FileReader constants
- Re: [cors] unaddressed security concerns
- Re: CSRF vulnerability in Tyler's GuestXHR protocol?
- Fwd: [office] Public Review of OpenDocument Version 1.2
- [XHR2] Redirects (was: Re: [whatwg] unexpected use of the CORS specification)
- RE: [FileAPI] File.mediaType
- RE: [FileAPI] File.mediaType
- Re: [FileAPI] File.mediaType
- Re: [FileAPI] FileReader constants
Saturday, 14 November 2009
- [widgets] Test suite: problem with test cases
- Re: [WARP] Comments to WARP spec
- Re: [widgets] About the test suite
- Re: CSRF vulnerability in Tyler's GuestXHR protocol?
Friday, 13 November 2009
- Re: CSRF vulnerability in Tyler's GuestXHR protocol?
- [widgets] Apple, excludes 2 patent applications on Widgets 1.0: Access Requests Policy spec
- Re: [WebIDL] Default Values for Arguments
- Re: Rename “File API” to “FileReader API”?
- Re: [WebIDL] Default Values for Arguments
- [WebIDL] Default Values for Arguments
- Re: [FileAPI] File.name
- Work on Read before/separtely from Write? (was: Rename “File API” to “FileReader API”?)
- Re: [FileAPI] FileReader constants
- Re: [FileAPI] File.mediaType
- Re: CfC: to publish First Public Working Draft of File API spec; deadline Nov 10
- [widgets] About the test suite
- Re: What do we mean by "parking" Web Database? [Was: Re: TPAC report day 2]
- RE: [WARP] Comments to WARP spec
Thursday, 12 November 2009
- Re: What do we mean by "parking" Web Database? [Was: Re: TPAC report day 2]
- Re: [widgets interface] Tests generated from WebIDL
- Re: [widgets interface] Tests generated from WebIDL
- Re: [widgets interface] Tests generated from WebIDL
- Re: [widgets interface] Tests generated from WebIDL
- Re: [widgets interface] Tests generated from WebIDL
- Re: [widgets interface] Tests generated from WebIDL
- Re: [WARP] Comments to WARP spec
- RE: [WARP] Comments to WARP spec
- Re: [XHR2] timeout
- [widgets] Draft Minutes for 12 November 2009 Voice Conference
- Re: [WARP] Comments to WARP spec
- RE: [WARP] Comments to WARP spec
- Re: Use Cases and Requirements for Saving Files Securely
- Re: CfC: to publish Last Call Working Draft of XHR (1); deadline 18 November
- Re: CfC: to publish Last Call Working Draft of XHR (1); deadline 18 November
- RE: [fileapi] urn -> URL
- Summary of Media Annotations WG 5th F2F in Santa Clara
- Re: Use Cases and Requirements for Saving Files Securely
- Re: STS and lockCA
- Re: Use Cases and Requirements for Saving Files Securely
- Re: STS and lockCA
- Re: Use Cases and Requirements for Saving Files Securely
- Re: Use Cases and Requirements for Saving Files Securely
- Re: Use Cases and Requirements for Saving Files Securely
- Re: Use Cases and Requirements for Saving Files Securely
- Re: Use Cases and Requirements for Saving Files Securely
- DAP and security (was: Rename “File API” to “FileReader API”?)
- Re: STS and lockCA
- Re: CSRF vulnerability in Tyler's GuestXHR protocol?
- Re: [fileapi] urn -> URL
- Re: [fileapi] urn -> URL
- Re: Rename “File API” to “FileReader API”?
- Re: Use Cases and Requirements for Saving Files Securely
- Re: Rename “File API” to “FileReader API”?
- Re: Use Cases and Requirements for Saving Files Securely
Wednesday, 11 November 2009
- Re: Rename “File API” to “FileReader API”?
- Re: Use Cases and Requirements for Saving Files Securely
- [widgets] Conformance testing results
- Re: STS and lockCA
- Re: Rename “File API” to “FileReader API”?
- [widgets] Draft Agenda for 12 November 2009 VC
- Re: STS and lockCA
- Re: comments from Osmosoft on the File API
- comments from Osmosoft on the File API
- RE: Use Cases and Requirements for Saving Files Securely
- Re: [FileAPI] File.name
- Re: STS and lockCA
- Re: STS and lockCA
- Re: Use Cases and Requirements for Saving Files Securely
- Re: Rename “File API” to “FileReader API”?
- Re: Rename “File API” to “FileReader API”?
- Re: Use Cases and Requirements for Saving Files Securely
- Re: Use Cases and Requirements for Saving Files Securely
- Re: Use Cases and Requirements for Saving Files Securely
- Re: Use Cases and Requirements for Saving Files Securely
- Re: STS and lockCA
- Re: CfC: to publish Last Call Working Draft of XHR (1); deadline 18 November
- Re: Use Cases and Requirements for Saving Files Securely
- Re: Rename “File API” to “FileReader API”?
- Re: CfC: to publish Last Call Working Draft of XHR (1); deadline 18 November
- Re: [FileAPI] File.name
- Re: CfC: to publish First Public Working Draft of File API spec; deadline Nov 10
- Re: CfC: to publish Last Call Working Draft of XHR (1); deadline 18 November
Tuesday, 10 November 2009
- Re: [XHR2] timeout
- CfC: to publish Last Call Working Draft of XHR (1); deadline 18 November
- Re: [WARP] Comments to WARP spec
- Re: Use Cases and Requirements for Saving Files Securely
- Re: Rename “File API” to “FileReader API”?
- Re: WebSimpleDB object caching
- Re: CSRF vulnerability in Tyler's GuestXHR protocol?
- Re: CSRF vulnerability in Tyler's GuestXHR protocol?
- Re: CORS Background slides
- Re: [XHR2] timeout
- Re: [XHR2] timeout
- Re: [FileAPI] FileReader
- Re: [FileAPI] File.mediaType
- Re: [XHR2] timeout
- Re: [XHR2] timeout
- Re: [FileAPI] File.mediaType
- [FileAPI] FileReader
- Re: [FileAPI] File.mediaType
- Re: Use Cases and Requirements for Saving Files Securely
- [FileAPI] FileReader constants
Wednesday, 11 November 2009
Tuesday, 10 November 2009
Wednesday, 11 November 2009
Tuesday, 10 November 2009
Wednesday, 11 November 2009
Tuesday, 10 November 2009
- Re: Proposal for sending multiple files via XMLHttpRequest.send()
- Re: [WARP] Comments to WARP spec
- Re: XMLHttpRequest: Last Call?
Wednesday, 11 November 2009
Tuesday, 10 November 2009
Wednesday, 11 November 2009
Tuesday, 10 November 2009
- Re: View modes: more precision on fullscreen
- Re: Rename “File API” to “FileReader API”?
- Re: CfC: to publish First Public Working Draft of File API spec; deadline Nov 10
- Re: Rename “File API” to “FileReader API”?
- Re: Rename “File API” to “FileReader API”?
- Re: CfC: to publish First Public Working Draft of File API spec; deadline Nov 10
- Re: Rename “File API” to “FileReader API”?
- Re: Rename “File API” to “FileReader API”?
- Rename “File API” to “FileReader API”?
- Re: Constrained specification of Icon element
- Re: [WARP] Comments to WARP spec
- Re: fyi: Strict Transport Security specification
- Re: WebSimpleDB object caching
- Re: Use Cases and Requirements for Saving Files Securely
Monday, 9 November 2009
- Re: What do we mean by "parking" Web Database? [Was: Re: TPAC report day 2]
- Re: What do we mean by "parking" Web Database?
- RE: Caching breakout session at TPAC
- Re: Re: Request for Reviewers: Section 7.4 of Web Security Context: User Interface Guidelines; deadline Sep 24 ( LC-2255)
- Re: Use Cases and Requirements for Saving Files Securely
- RE: [WARP] Comments to WARP spec
- Re: CORS Background slides
- Re: [webworkers] SharedWorker and ApplicationCache
- Re: [webworkers] SharedWorker and ApplicationCache
- Re: [webworkers] SharedWorker and ApplicationCache
- Re: What do we mean by "parking" Web Database?
- Re: View modes: more precision on fullscreen
- Re: CfC: to publish First Public Working Draft of File API spec; deadline Nov 10
- Re: View modes: more precision on fullscreen
- Re: View modes: more precision on fullscreen
- Re: CfC: to publish First Public Working Draft of File API spec; deadline Nov 10
- Re: fyi: Strict Transport Security specification
- Re: What do we mean by "parking" Web Database? [Was: Re: TPAC report day 2]
- Re: [widgets] Interface: license attribute, was Re: [Widget: Warp] - license attribute
- Re: What do we mean by "parking" Web Database? [Was: Re: TPAC report day 2]
- Re: What do we mean by "parking" Web Database? [Was: Re: TPAC report day 2]
- Re: View modes: more precision on fullscreen
- Re: What do we mean by "parking" Web Database? [Was: Re: TPAC report day 2]
- Re: What do we mean by "parking" Web Database?
- Re: What do we mean by "parking" Web Database? [Was: Re: TPAC report day 2]
- Re: What do we mean by "parking" Web Database? [Was: Re: TPAC report day 2]
- Re: CfC: to publish First Public Working Draft of File API spec; deadline Nov 10
- Re: View modes: more precision on fullscreen
- Re: What do we mean by "parking" Web Database? [Was: Re: TPAC report day 2]
- Re: [WARP] Comments to WARP spec
- Re: What do we mean by "parking" Web Database? [Was: Re: TPAC report day 2]
- Re: What do we mean by "parking" Web Database? [Was: Re: TPAC report day 2]
- Re: fyi: Strict Transport Security specification
- Re: What do we mean by "parking" Web Database? [Was: Re: TPAC report day 2]
- Fwd: Caching breakout session at TPAC
Sunday, 8 November 2009
- Re: What do we mean by "parking" Web Database? [Was: Re: TPAC report day 2]
- What do we mean by "parking" Web Database? [Was: Re: TPAC report day 2]
- WebSimpleDB object caching
Saturday, 7 November 2009
- Re: [webworkers] SharedWorker and ApplicationCache
- Re: [webworkers] SharedWorker and ApplicationCache
- TPAC report day 2
- Re: [webworkers] SharedWorker and ApplicationCache
- Re: [webworkers] SharedWorker and ApplicationCache
- [webworkers] SharedWorker and ApplicationCache
- RE: [WARP] Comments to WARP spec
Friday, 6 November 2009
- Re: Constrained specification of Icon element
- Re: [widgets] Definition of Instance was: Comments on Section 6 of the 18-Aug-2009 LCWD of A&E spec
- Re: [WARP] Comments to WARP spec
- [widgets] Interface: license attribute, was Re: [Widget: Warp] - license attribute
- Re: FW: Viewmode related issues
- Re: [cors] unaddressed security concerns
- Re: [cors] unaddressed security concerns
- Re: CSRF vulnerability in Tyler's GuestXHR protocol?
- Re: [cors] unaddressed security concerns
- Re: [cors] unaddressed security concerns
Thursday, 5 November 2009
- Re: Use Cases and Requirements for Saving Files Securely
- Re: [FileAPI] Latest Revision of Editor's Draft
- Binary data (ByteArray/ByteVector) proposal on public-script-coord
- Re: bug in example
- Re: CSRF vulnerability in Tyler's GuestXHR protocol?
- Re: Seeking pre-LCWD comments for: Server-sent Events, Web {Database, Sockets, Storage Workers}; deadline 19 November
- Re: Seeking pre-LCWD comments for: Server-sent Events, Web {Database, Sockets, Storage Workers}; deadline 19 November
- Re: Seeking pre-LCWD comments for: Server-sent Events, Web {Database, Sockets, Storage Workers}; deadline 19 November
- Re: CfC: to publish First Public Working Draft of File API spec; deadline Nov 10
- RE: [FileAPI] Latest Revision of Editor's Draft
- Re: Seeking pre-LCWD comments for: Server-sent Events, Web {Database, Sockets, Storage Workers}; deadline 19 November
- [CORS] ISSUE-108: confused deputy problem
- CSRF vulnerability in Tyler's GuestXHR protocol?
- bug in example
- Re: Seeking pre-LCWD comments for: Server-sent Events, Web {Database, Sockets, Storage Workers}; deadline 19 November
- Re: CORS Background slides
- Re: [cors] unaddressed security concerns
- Re: CORS Background slides
- Re: CORS Background slides
- Re: CORS Background slides
- Re: CORS Background slides
- Re: Seeking pre-LCWD comments for: Server-sent Events, Web {Database, Sockets, Storage Workers}; deadline 19 November
- Re: CORS Background slides
- Re: CORS Background slides
- Re: CORS Background slides
- Re: CORS Background slides
- Re: CORS Background slides
- Re: CfC: to publish First Public Working Draft of File API spec; deadline Nov 10
- Re: CORS Background slides
Wednesday, 4 November 2009
- Selectors API 2 Status
- Seeking pre-LCWD comments for: Server-sent Events, Web {Database, Sockets, Storage Workers}; deadline 19 November
- [widgets] Call for comments on pre-LC#2 of TWI spec; deadline 11 November
- Re: More CORS Tuesday afternoon...
- [widgets]: Reminder: Request for Comments: 8-Oct-2009 LCWD of Widgets 1.0: Widget URIs; deadline 10 November
- [widgets] Draft Minutes for 3 November 2009 f2f meeting
- [widgets] Draft Minutes for 2 November 2009 f2f meeting
- CfC: to publish First Public Working Draft of File API spec; deadline Nov 10
- Re: [cors] unaddressed security concerns
- [Widget: Warp] - license attribute
- CORS Background slides
- OAuth protocol flow diagrams
Tuesday, 3 November 2009
- Multitouch @TPCA 16:30-17:00
- FW: OMTP BONDI 1.1 Candidate Release now available
- Re: TransAnn: LCWD#3 of Widgets 1.0: Packaging and Configuration published 29 October
- ISSUE-110 (code-point conversion): Should we remove the code-point conversion from the D3E spec? [DOM3 Events]
- RE: [FileAPI] Latest Revision of Editor's Draft
- Re: [FileAPI] Latest Revision of Editor's Draft
- RE: [FileAPI] Latest Revision of Editor's Draft
- [widgets] Definition of Instance was: Comments on Section 6 of the 18-Aug-2009 LCWD of A&E spec
- Re: More CORS Tuesday afternoon...
- Re: More CORS Tuesday afternoon...
- [WARP] local addresses, UPnP, comments
- Re: More CORS Tuesday afternoon...
- Re: Adding a note to DOM2 Views
- Seeking Comments on LCWD of Guidelines for Web Content Transformation Proxies; 6 November deadline
- Re: Web Data APIs
- Adding a note to DOM2 Views
- Re: More CORS Tuesday afternoon...
- Re: Web Data APIs
- Re: Use Cases and Requirements for Saving Files Securely
- Re: [FileAPI] Latest Revision of Editor's Draft
- Viewmode related issues
- Constrained specification of Icon element
- [widgets] Call for comments on pre-LC#2 of WARP spec; deadline 18 November
- Re: [WARP] IRI normalization only for HTTP*?
- [WARP] IRI normalization only for HTTP*?
- WebApps' publication "plans"
- TPAC first day...
- More CORS Tuesday afternoon...
- [widgets] View modes security considerations
- [WARP] Comments to WARP spec
Monday, 2 November 2009
- Re: Web Data APIs
- ISSUE-108: confused deputy problem [CORS]
- Re: Web Data APIs
- Use Cases and Requirements for Saving Files Securely
- RE: [FileAPI] Latest Revision of Editor's Draft
- [fileapi] urn -> URL
Sunday, 1 November 2009
- Re: View modes: more precision on fullscreen
- Re: View modes: more precision on fullscreen
- Re: FW: [widgets] viewmodes spec
- Travel Notification: Expect Delayed Responses
Saturday, 31 October 2009
Friday, 30 October 2009
Thursday, 29 October 2009
- Next-generation file API use cases
- RE: Proposed additional topic for joint DAP/WebApps Widgets F2F session
- Re: Proposed additional topic for joint DAP/WebApps Widgets F2F session
- RE: Proposed additional topic for joint DAP/WebApps Widgets F2F session
- Re: Proposed additional topic for joint DAP/WebApps Widgets F2F session
- Re: Proposed additional topic for joint DAP/WebApps Widgets F2F session
- RE: Proposed additional topic for joint DAP/WebApps Widgets F2F session
- [widgets] Draft Minutes for 29 October 2009 Voice Conference
- Re: [widgets interface] Tests generated from WebIDL
- Proposed additional topic for joint DAP/WebApps Widgets F2F session
- CORS: Monday Nov 2 13:30-15:00? [Was: Re: TPAC agenda - APIs]
- Re: TPAC agenda - APIs
- Re: TPAC agenda - APIs
- Re: [FileAPI] Latest Revision of Editor's Draft
- Re: TPAC agenda - APIs
- Re: TPAC agenda - APIs
- Re: TPAC agenda - APIs
Wednesday, 28 October 2009
- Re: [FileAPI] Latest Revision of Editor's Draft
- Re: [widgets interface] Tests generated from WebIDL
- [widgets interface] Tests generated from WebIDL
- Re: [FileAPI] Latest Revision of Editor's Draft
- [widgets] Media Type Registration for application/widget
- Re: [widgets] Draft agenda for 29 October 2009 voice conference; TIME CHANGE FOR US Participants
- Re: [FileAPI] Latest Revision of Editor's Draft
- Re: [widgets] Draft agenda for 29 October 2009 voice conference; TIME CHANGE FOR US Participants
- [widgets] Draft agenda for 29 October 2009 voice conference; TIME CHANGE FOR US Participants
- Re: [widgets] Comments on LCWD #3
- Re: TPAC agenda - APIs
- [EventSource] Comments to the current draft
- RE: TPAC agenda - APIs
- Re: FW: Feedback on the Strict-Transport-Security specification
- Re: [widgets] Comments on LCWD #3
- FW: Feedback on the Strict-Transport-Security specification
Tuesday, 27 October 2009
- Re: [FileAPI] Latest Revision of Editor's Draft
- Re: [FileAPI] Latest Revision of Editor's Draft
- Re: [FileAPI] Latest Revision of Editor's Draft
- Re: [FileAPI] Latest Revision of Editor's Draft
- Re: [FileAPI] Latest Revision of Editor's Draft
- Re: [FileAPI] Latest Revision of Editor's Draft
- Re: [FileAPI] Latest Revision of Editor's Draft
- Re: [FileAPI] Latest Revision of Editor's Draft
- Re: [FileAPI] Latest Revision of Editor's Draft
- [widgets] P&C Last Call 3
- Fwd: Rich Web Application Backplane XG Final Report Published
- RE: [Widgets] Security Considerations
- Re: [Widgets] Security Considerations
- Re: [cors] unaddressed security concerns
- RE: [Widgets] Security Considerations
- Re: propose an API to return Range in <textarea> etc. form control nodes (similar functionality as document.caretRangeFromPoint)
- RE: [WARP] UPnP & LAN
- Re: [widgets] Security Guidelines for Widgets? [Was: Re: [widgets] viewmodes spec]
- [widgets] Security Guidelines for Widgets? [Was: Re: [widgets] viewmodes spec]
- [WARP] UPnP & LAN
- Re: Value of Server-Sent Events
- TPAC agenda - APIs
- Re: [FileAPI] Latest Revision of Editor's Draft
- Re: [FileAPI] Latest Revision of Editor's Draft
- Re: Value of Server-Sent Events
- Re: Value of Server-Sent Events
Monday, 26 October 2009
- Re: Value of Server-Sent Events
- [Widgets] Security Considerations
- Re: [cors] unaddressed security concerns
- Re: [widgets] Comments on LCWD #3
- Re: Value of Server-Sent Events
- [FileAPI] Latest Revision of Editor's Draft
- FW: [widgets] viewmodes spec
Sunday, 25 October 2009
- Re: Value of Server-Sent Events
- Re: Value of Server-Sent Events
- Re: CfC: to publish new WDs of Server-sent Events, Web {Database, Sockets API, Storage, Workers}; deadline 26 October
- Re: Value of Server-Sent Events
- [widgets] Comments on LCWD #3
- Re: Value of Server-Sent Events
Saturday, 24 October 2009
- Re: Value of Server-Sent Events
- Re: [cors] unaddressed security concerns
- Re: [cors] unaddressed security concerns
- CORS Best PRactices (was: [cors] unaddressed security concerns)
- Re: Re: Request for Reviewers: Section 7.4 of Web Security Context: User Interface Guidelines; deadline Sep 24 ( LC-2255)
- Re: [cors] unaddressed security concerns
- Re: [cors] unaddressed security concerns
- Re: Web Notifications, do we need a new spec?
- Re: [cors] unaddressed security concerns
- Re: [cors] unaddressed security concerns
- Re: [cors] unaddressed security concerns
- Re: [cors] unaddressed security concerns
- Re: Value of Server-Sent Events
- Re: [cors] unaddressed security concerns
- Re: [cors] unaddressed security concerns
- Re: Value of Server-Sent Events
- Re: Request for Reviewers: Section 7.4 of Web Security Context: User Interface Guidelines; deadline Sep 24 ( LC-2255)
- Re: Value of Server-Sent Events
- Re: Value of Server-Sent Events
- Re: Value of Server-Sent Events
- Re: Value of Server-Sent Events
- Re: [cors] unaddressed security concerns
Friday, 23 October 2009
- Re: Value of Server-Sent Events
- Value of Server-Sent Events
- Re: CfC: to publish new WDs of Server-sent Events, Web {Database, Sockets API, Storage, Workers}; deadline 26 October
- Re: [cors] unaddressed security concerns
- Re: CfC: to publish new WDs of Server-sent Events, Web {Database, Sockets API, Storage, Workers}; deadline 26 October
- Re: CfC: to publish new WDs of Server-sent Events, Web {Database, Sockets API, Storage, Workers}; deadline 26 October
- RE: Multimodal Interaction WG questions for WebApps (especially WebAPI)
- Re: Re: Request for Reviewers: Section 7.4 of Web Security Context: User Interface Guidelines; deadline Sep 24 ( LC-2255)
- Re: Multimodal Interaction WG questions for WebApps (especially WebAPI)
- Re: CfC: to publish new WDs of Server-sent Events, Web {Database, Sockets API, Storage, Workers}; deadline 26 October
- Re: CfC: to publish new WDs of Server-sent Events, Web {Database, Sockets API, Storage, Workers}; deadline 26 October
- RE: Multimodal Interaction WG questions for WebApps (especially WebAPI)
- Re: CfC: to publish new WDs of Server-sent Events, Web {Database, Sockets API, Storage, Workers}; deadline 26 October
- Re: Multimodal Interaction WG questions for WebApps (especially WebAPI)
- CORS: email from Henry Thompson re "CORS still not getting to closure"
- Re: CfC: to publish new WDs of Server-sent Events, Web {Database, Sockets API, Storage, Workers}; deadline 26 October
- CfC: to publish new WDs of Server-sent Events, Web {Database, Sockets API, Storage, Workers}; deadline 26 October
- Headsup: short CfC to publish new WDs of Web Database, Web Storage, Web Sockets, Web Workers and Server-sent Events to be started
- Re: [cors] TAG request concerning CORS & Next Step(s)
- Re: [widgets] CfC to publish LCWD#3 of the Packaging and Configuration spec; deadline 26 October
- Re: [widgets] Draft Minutes for 22 October 2009 Voice Conf
- Re: [widgets] Potential bug in Rule for Identifying the Media Type of a File
- RE: [widgets] CfC to publish LCWD#3 of the Packaging and Configuration spec; deadline 26 October
Thursday, 22 October 2009
- Re: [cors] unaddressed security concerns
- [widgets] CfC to publish LCWD#3 of the Packaging and Configuration spec; deadline 26 October
- RE: [widgets] Potential bug in Rule for Identifying the Media Type of a File
- Re: [cors] TAG request concerning CORS & Next Step(s)
- RE: [widgets] Draft Minutes for 22 October 2009 Voice Conf
- RE: [widgets] Potential bug in Rule for Identifying the Media Type of a File
- RE: [widgets] Draft Minutes for 22 October 2009 Voice Conf
- Re: [widgets] Potential bug in Rule for Identifying the Media Type of a File
- RE: [widgets] Potential bug in Rule for Identifying the Media Type of a File
- Re: [widgets] Potential bug in Rule for Identifying the Media Type of a File
- RE: [widgets] Potential bug in Rule for Identifying the Media Type of a File
- [widgets] Draft Minutes for 22 October 2009 Voice Conf
- Re: Implementation of the widget signing spec
- Re: [widgets] Draft Agenda for 22 October 2009 Voice Conf
- Re: [widgets] Potential bug in Rule for Identifying the Media Type of a File
- [widgets] viewmodes spec
Wednesday, 21 October 2009
- Re: [Bug 7938] SECURITY_ERR when disallowing Database open is inconsistent with QUOTA_EXCEEDED_ERR for disallowing setItem
- Implementation of the widget signing spec
- FPWD of API for Media Resource 1.0 published
- RE: solving the CPU usage issue for non-visible pages
- Re: Web Notifications, do we need a new spec?
- Re: [widgets] Fail on encrypted archive
- Re: Web Notifications, do we need a new spec?
- Re: [Bug 7938] SECURITY_ERR when disallowing Database open is inconsistent with QUOTA_EXCEEDED_ERR for disallowing setItem
- [widgets] Draft Agenda for 22 October 2009 Voice Conf
- Web security bar-BOF during week of 2 November?
- Re: childElements, childElementCount, and children (was: [ElementTraversal]: Feature string for DOMImplementation.hasFeature(feature, version)?)
- Re: childElements, childElementCount, and children (was: [ElementTraversal]: Feature string for DOMImplementation.hasFeature(feature, version)?)
- Re: solving the CPU usage issue for non-visible pages
- Re: solving the CPU usage issue for non-visible pages
- Re: solving the CPU usage issue for non-visible pages
- Re: solving the CPU usage issue for non-visible pages
- Re: solving the CPU usage issue for non-visible pages
- IETF HyBi BoF
- [Bug 7938] SECURITY_ERR when disallowing Database open is inconsistent with QUOTA_EXCEEDED_ERR for disallowing setItem
- Re: childElements, childElementCount, and children
- Re: solving the CPU usage issue for non-visible pages
- Re: solving the CPU usage issue for non-visible pages
- Re: childElements, childElementCount, and children
- Re: solving the CPU usage issue for non-visible pages
- RE: solving the CPU usage issue for non-visible pages
- Re: childElements, childElementCount, and children (was: [ElementTraversal]: Feature string for DOMImplementation.hasFeature(feature, version)?)
- Re: childElements, childElementCount, and children (was: [ElementTraversal]: Feature string for DOMImplementation.hasFeature(feature, version)?)
- Re: solving the CPU usage issue for non-visible pages
- Re: childElements, childElementCount, and children (was: [ElementTraversal]: Feature string for DOMImplementation.hasFeature(feature, version)?)
- RE: solving the CPU usage issue for non-visible pages
- Re: solving the CPU usage issue for non-visible pages
- Re: solving the CPU usage issue for non-visible pages
- Re: solving the CPU usage issue for non-visible pages
- RE: solving the CPU usage issue for non-visible pages
- Re: childElements, childElementCount, and children
- Re: Editor's Response in the proposed process (with particular note of spec diff links)
- Re: solving the CPU usage issue for non-visible pages
- Editor's Response in the proposed process (with particular note of spec diff links)
Tuesday, 20 October 2009
- Re: solving the CPU usage issue for non-visible pages
- RE: solving the CPU usage issue for non-visible pages
- Re: childElements, childElementCount, and children
- Re: childElements, childElementCount, and children (was: [ElementTraversal]: Feature string for DOMImplementation.hasFeature(feature, version)?)
- Re: Use cases (appcache, etc) [progress]
- Re: Use cases (appcache, etc) [progress]
- Re: Use cases (appcache, etc) [progress]
- Re: Proposal for sending multiple files via XMLHttpRequest.send()
- Re: Proposal for sending multiple files via XMLHttpRequest.send()
- Re: Proposal for sending multiple files via XMLHttpRequest.send()
- Re: Proposal for sending multiple files via XMLHttpRequest.send()
- Re: [widgets] remove feature at risk stuff from P&C before next LCWD is published
- Re: [widgets] Test suite questions
- Re: Touch and gestures events
- Re: Proposal for sending multiple files via XMLHttpRequest.send()
- Re: Use cases (appcache, etc) [progress]
- [Widgets] Compatibility Matrix for Packaging and Configuration
- Re: Use cases (appcache, etc) [progress]
- Re: Proposal for sending multiple files via XMLHttpRequest.send()
- Re: Proposal for sending multiple files via XMLHttpRequest.send()
- Re: Use cases (appcache, etc) Re: Using progress events for other purposes
- re: Proposal for sending multiple files via XMLHttpRequest.send()
- Use cases (appcache, etc) Re: Using progress events for other purposes
- New Progress events draft: 1.32
Monday, 19 October 2009
- ISSUE-107 (multi-object end events): End state events in multi-object transactions [Progress Events]
- focus... Re: Touch and gestures events
- Re: Touch and gestures events
- Re: solving the CPU usage issue for non-visible pages
- Re: Web Notifications, do we need a new spec?
- Re: solving the CPU usage issue for non-visible pages
- solving the CPU usage issue for non-visible pages
- Re: Touch and gestures events
- Re: [widgets] Step 5 - allowing private use lang tags ; ISSUE-93
- [widgets] Step 5 - allowing private use lang tags
- Re: Using progress events for other purposes
- Re: Touch and gestures events
- Re: Using progress events for other purposes
- Re: Using progress events for other purposes
- Re: Using progress events for other purposes
- Re: Using progress events for other purposes
- Re: Using progress events for other purposes
- ISSUE-106 (mouse capture): Consider adding mouse capture/release API [DOM3 Events]
- Re: Using progress events for other purposes
- DOM4 Core (was: childElements, childElementCount, and children)
- Re: Using progress events for other purposes
- Re: Using progress events for other purposes
- Re: Using progress events for other purposes
Sunday, 18 October 2009
- Re: Using progress events for other purposes
- Re: Using progress events for other purposes
- Re: childElements, childElementCount, and children (was: [ElementTraversal]: Feature string for DOMImplementation.hasFeature(feature, version)?)
- Re: Using progress events for other purposes
- Re: childElements, childElementCount, and children (was: [ElementTraversal]: Feature string for DOMImplementation.hasFeature(feature, version)?)
- childElements, childElementCount, and children (was: [ElementTraversal]: Feature string for DOMImplementation.hasFeature(feature, version)?)
Saturday, 17 October 2009
- Re: [ElementTraversal]: Feature string for DOMImplementation.hasFeature(feature, version)?
- Re: [ElementTraversal]: Feature string for DOMImplementation.hasFeature(feature, version)?
- Re: [ElementTraversal]: Feature string for DOMImplementation.hasFeature(feature, version)?
- CfC: to publish First Public Working Draft of DataCache API spec; deadline Oct 24
- Re: [ElementTraversal]: Feature string for DOMImplementation.hasFeature(feature, version)?
- [Bug 7938] New: SECURITY_ERR when disallowing Database open is inconsistent with QUOTA_EXCEEDED_ERR for disallowing setItem
Friday, 16 October 2009
- Re: [ElementTraversal]: Feature string for DOMImplementation.hasFeature(feature, version)?
- Re: Touch and gestures events
- Re: Touch and gestures events
- Re: Touch and gestures events
- Re: [ElementTraversal]: Feature string for DOMImplementation.hasFeature(feature, version)?
- Re: propose an API to return Range in <textarea> etc. form control nodes (similar functionality as document.caretRangeFromPoint)
- DataCache - revised editor's draft available
- Re: Touch and gestures events
- Re: propose an API to return Range in <textarea> etc. form control nodes (similar functionality as document.caretRangeFromPoint)
- Re: propose an API to return Range in <textarea> etc. form control nodes (similar functionality as document.caretRangeFromPoint)
- RE: [selectors-api] Summary of Feature Requests for v2
- RE: [widgets] Potential bug in Rule for Identifying the Media Type of a File
Thursday, 15 October 2009
- Re: Touch and gestures events
- Re: Touch and gestures events
- Re: Touch and gestures events
- [widgets] Draft Minutes for 15 October 2009 Voice Conf
- Re: [selectors api] test suite red values
- Re: [widgets] Fail on encrypted archive
- [widgets] Fail on encrypted archive
- Re: Is there proposal of accessing metadata of media files?
Wednesday, 14 October 2009
- Re: Touch and gestures events
- Re: Touch and gestures events
- [widgets] Draft Agenda for 15 October 2009 Voice Conference
- Re: Touch and gestures events
- Re: [cors] unaddressed security concerns
- Re: Touch and gestures events
- Re: [cors] unaddressed security concerns
Tuesday, 13 October 2009
- Re: Is there proposal of accessing metadata of media files?
- Re: Open Review of the CORS Specification
- Re: Is there proposal of accessing metadata of media files?
- Re: Open Review of the CORS Specification
- RE: Is there proposal of accessing metadata of media files?
- Re: Is there proposal of accessing metadata of media files?
- RE: Is there proposal of accessing metadata of media files?
- Re: Accept header setting in XHR
- Re: Accept header setting in XHR
- Re: [cors] unaddressed security concerns
- Re: [public-webapps] <none>
- Re: [EventSource] feedback from implementors
- Re: [cors] unaddressed security concerns
- Re: Resending Re: WebStorage and WebDatabase - creation and exceptions
- Re: [cors] unaddressed security concerns
Saturday, 10 October 2009
Monday, 12 October 2009
- Re: propose an API to return Range in <textarea> etc. form control nodes (similar functionality as document.caretRangeFromPoint)
- Re: propose an API to return Range in <textarea> etc. form control nodes (similar functionality as document.caretRangeFromPoint)
- Re: [widgets] Potential bug in Rule for Identifying the Media Type of a File
- Re: propose an API to return Range in <textarea> etc. form control nodes (similar functionality as document.caretRangeFromPoint)
- Re: [XHR] Some comments on "charset" in the Content-Type header
- Re: [XHR] Some comments on "charset" in the Content-Type header
- Re: [XHR] Some comments on "charset" in the Content-Type header
- Re: [cors] unaddressed security concerns
- Re: [widgets] Dropping xml:lang on icon elements
- Re: [cors] unaddressed security concerns
- Re: [cors] unaddressed security concerns
- Re: [widgets] Dropping xml:lang on icon elements
- Re: [cors] unaddressed security concerns
- Re: [XHR] Some comments on "charset" in the Content-Type header
- Re: [XHR] Some comments on "charset" in the Content-Type header
- Re: [XHR] Request charset is limited to UTF-8 for x-www-form-urlencoded data
- Re: [XHR] Request charset is limited to UTF-8 for x-www-form-urlencoded data
- Re: [XHR] Some comments on "charset" in the Content-Type header
- Re: propose an API to return Range in <textarea> etc. form control nodes (similar functionality as document.caretRangeFromPoint)
- Re: [cors] unaddressed security concerns
Saturday, 10 October 2009
- [public-webapps] <none>
- [widgets] CfC: Change request for classes of products; deadline October 14
- [widgets] CfC: Remove the "At Risk" designation for the its:dir; deadline October 14
- [widgets] CfC: Dropping xml:lang on icon elements; deadline Oct 14
- Re: [XHR] Some comments on "charset" in the Content-Type header
Friday, 9 October 2009
- Re: [cors] unaddressed security concerns
- Re: [widgets] Dropping xml:lang on icon elements
- Re: propose an API to return Range in <textarea> etc. form control nodes (similar functionality as document.caretRangeFromPoint)
- Re: [widgets] Dropping xml:lang on icon elements
- Re: [widgets] Dropping xml:lang on icon elements
- Re: [widgets] Dropping xml:lang on icon elements
- File API comments
- [widgets] Dropping xml:lang on icon elements
- Re: [XHR] Some comments on "charset" in the Content-Type header
- Re: File API commens
- Re: File API commens
Thursday, 8 October 2009
- Request for Comments: 8-Oct-2009 LCWD of Widgets 1.0: Widget URIs; deadline 10 November
- Re: propose an API to return Range in <textarea> etc. form control nodes (similar functionality as document.caretRangeFromPoint)
- propose an API to return Range in <textarea> etc. form control nodes (similar functionality as document.caretRangeFromPoint)
- Re: File API commens
- Re: File API commens
- [widgets] Patent Advisory Group for Widgets 1.0 Updates spec published Recommendations
- Re: File API commens
- Re: File API commens
- Re: File API commens
- Re: File API commens
- Re: File API commens
- [cors] unaddressed security concerns
- RE: Is there proposal of accessing metadata of media files?
- Re: [cors] TAG request concerning CORS & Next Step(s)
- Re: [cors] security issue with XMLHttpRequest API compatibility
- Re: [cors] security issue with XMLHttpRequest API compatibility
- Re: [XHR] Last Call comment on about dependencies
- Re: [widgets] P+C spec doesn't normatively state whether attributes are required or not
- Re: [XHR] LC comments from the XForms Working Group
- Re: [XHR] Some comments on "charset" in the Content-Type header
- Re: [cors] TAG request concerning CORS & Next Step(s)
- Re: [cors] security issue with XMLHttpRequest API compatibility
- Re: Accept header setting in XHR
- [widgets] Draft minutes for 8 October 2009 Voice Conf
- File API commens
- Re: Widget DigSign: Example of a distributor signature document is buggy
- Re: [EventSource] feedback from implementors
- Re: Widget DigSign: Example of a distributor signature document is buggy
- Re: Is there proposal of accessing metadata of media files?
- Re: [WebIDL] Trying to understand IndexGetter/NameGetter
Wednesday, 7 October 2009
- Re: Is there proposal of accessing metadata of media files?
- Re: PFWG comments on Widgets 1.0: Packaging and Configuration Last Call (late, very late)
- Re: PFWG comments on Widgets 1.0: Packaging and Configuration Last Call (late, very late)
- Re: Widget DigSign: Example of a distributor signature document is buggy
- Re: File API proposal - marrying two alternatives
- Re: File API proposal - marrying two alternatives
- Re: [widgets] P+C spec doesn't normatively state whether attributes are required or not
- Re: [widgets] P+C spec doesn't normatively state whether attributes are required or not
- Re: [widgets] P+C spec doesn't normatively state whether attributes are required or not
- Re: [widgets] P+C spec doesn't normatively state whether attributes are required or not
- Fwd: Is there proposal of accessing metadata of media files?
- Re: [widgets] P+C spec doesn't normatively state whether attributes are required or not
- [widgets] Draft Agenda for 8 October 2009 voice conf
- [widgets] P+C spec doesn't normatively state whether attributes are required or not
- RE: [WARP] "uri" attribute is confusing
- Re: [WARP] "uri" attribute is confusing
- RE: HTML5: has input device: use motion detection been included?
- Date/time types in Web IDL
- Is there proposal of accessing metadata of media files?
- Re: [widgets] remove feature at risk stuff from P&C before next LCWD is published
- Re: File API proposal - marrying two alternatives
- Re: File API proposal - marrying two alternatives
- Re: File API proposal - marrying two alternatives
- Re: File API proposal - marrying two alternatives
- Re: File API proposal - marrying two alternatives
- File API proposal - marrying two alternatives
Tuesday, 6 October 2009
- Request for Feedback: LCWD of Mobile Web Application Best Practices; deadline November 6
- Widget DigSign: Example of a distributor signature document is buggy
- Re: [widgets] remove feature at risk stuff from P&C before next LCWD is published
- Re: [widgets] remove feature at risk stuff from P&C before next LCWD is published
- Re: [WARP] "uri" attribute is confusing
- Re: [widgets] remove feature at risk stuff from P&C before next LCWD is published
- Re: [widgets] remove feature at risk stuff from P&C before next LCWD is published
- Re: [widgets] P&C: Step 8 bug when custom start file is bogus
- Re: [widgets] P&C: remove MAY and OPTIONAL assertions?
Monday, 5 October 2009
- Re: [EventSource] feedback from implementors
- Re: [cors] update (oct5)
- [cors] update (oct5)
- [VMMF] Comments (1)
- [widgets] P&C: remove MAY and OPTIONAL assertions?
- [widgets] P&C: Step 8 bug when custom start file is bogus
- Re: [widgets] remove feature at risk stuff from P&C before next LCWD is published
- [widgets] remove feature at risk stuff from P&C before next LCWD is published
- Re: [WARP] "uri" attribute is confusing
- RE: View modes: more precision on fullscreen
- Re: View modes: more precision on fullscreen
- Re: [EventSource] feedback from implementors
- RE: View modes: more precision on fullscreen
- View modes: more precision on fullscreen
Saturday, 3 October 2009
- Re: PFWG comments on Widgets 1.0: Packaging and Configuration Last Call (late, very late)
- Re: STS and lockCA
Friday, 2 October 2009
- RE: STS and lockCA
- Re: Comment on File API's FileData::slice method
- Re: Comment on File API's FileData::slice method
- Re: STS and lockCA
- Re: ISSUE-95: P&C CR: Conformance checker behavior intermixed with UA behavior [Widgets]
- Re: Comment on File API's FileData::slice method
- Re: Comment on File API's FileData::slice method
- Re: Comment on File API's FileData::slice method
- Re: Comment on File API's FileData::slice method
- Re: ISSUE-95: P&C CR: Conformance checker behavior intermixed with UA behavior [Widgets]
- RE: [A&E] Last Call comments (2): discovery & localization
- Re: [A&E] Last Call comments (2): discovery & localization
- RE: [A&E] Last Call comments (2): discovery & localization
- [widgets] Test suite
- Re: Comment on File API's FileData::slice method
- Re: [WARP] "uri" attribute is confusing
- Comment on File API's FileData::slice method
- Re: [A&E] Last Call comments (2): discovery & localization
Thursday, 1 October 2009
- RE: [WARP] "uri" attribute is confusing
- Re: Web IDL and the New Scripting Coordination List
- STS and lockCA
- Web IDL and the New Scripting Coordination List
- RE: [A&E] Last Call comments (2): discovery & localization
- Issue with semantics of the access element in WARP
- [widgets] Draft Minutes for 1 October 2009 Voice Conference
- RE: Comments on View Modes Media Feature ED
- Re: [widgets] Closing widget Interface issues
- Re: [widgets] P&C: LC#3 and CR#2
- Re: [widgets] P&C: LC#3 and CR#2
- Re: [widgets] P&C: LC#3 and CR#2
- Re: [A&E] Last Call comments (1)
- Re: [widgets] P&C: LC#3 and CR#2
- Re: Please don't call your API "simple"
- Re: [widgets] P&C: LC#3 and CR#2
- Re: [A&E] Last Call comments (2): discovery & localization