Tuesday, 31 December 2013
Sunday, 29 December 2013
- [Bug 24178] New: [Custom]: No way to differentiate attribute namespaces in attributeChanged callback
- [Bug 24176] New: Clarify that custom SVG elements must extend an existing SVGElement
Saturday, 28 December 2013
Wednesday, 25 December 2013
Thursday, 26 December 2013
Tuesday, 24 December 2013
Sunday, 22 December 2013
Friday, 20 December 2013
- Re: Refactoring SharedWorkers out of Web Workers W3C spec
- Re: Background sync & push messaging: declarative vs imperative
- Re: Background sync & push messaging: declarative vs imperative
- Re: [IME API]Some Insights from Chinese Input Methods
Thursday, 19 December 2013
- Re: Background sync & push messaging: declarative vs imperative
- Re: [testing] Common way to "manage" test bugs?
- Background sync & push messaging: declarative vs imperative
- Re: [testing] Common way to "manage" test bugs?
- Re: [testing] Common way to "manage" test bugs?
- RE: [testing] Common way to "manage" test bugs?
- Re: [testing] Common way to "manage" test bugs?
- Re: [testing] Common way to "manage" test bugs?
- [testing] Common way to "manage" test bugs?
Wednesday, 18 December 2013
- [ime-api]Add Some Background about Chinese Input Methods in a Mobile Platform
- [ime-api]Add Some Background about Chinese Input Methods in a Mobile Platform
Thursday, 19 December 2013
- Re: Passsword managers and autocomplete='off'
- Re: [IME API]Some Insights from Chinese Input Methods
- Re: New manifest spec - ready for FPWD?
Wednesday, 18 December 2013
- Re: Passsword managers and autocomplete='off'
- RE: Passsword managers and autocomplete='off'
- Re: inline declarative manifest, was Re: New manifest spec - ready for FPWD?
- Re: inline declarative manifest, was Re: New manifest spec - ready for FPWD?
- Re: CfC: publish Candidate Recommendation of File API; deadline November 28
- Re: inline declarative manifest, was Re: New manifest spec - ready for FPWD?
- [pointerlock] Call for Implementations and Tests
- Re: inline declarative manifest, was Re: New manifest spec - ready for FPWD?
- Re: inline declarative manifest, was Re: New manifest spec - ready for FPWD?
- RE: Refactoring SharedWorkers out of Web Workers W3C spec
- Re: Passsword managers and autocomplete='off'
Tuesday, 17 December 2013
- Re: IndexedDB: Syntax for specifying persistent/temporary storage
- Re: Passsword managers and autocomplete='off'
- Re: Passsword managers and autocomplete='off'
- Re: Passsword managers and autocomplete='off'
- Re: inline declarative manifest, was Re: New manifest spec - ready for FPWD?
- Re: inline declarative manifest, was Re: New manifest spec - ready for FPWD?
- Re: Request for feedback: Streams API
- Re: IndexedDB: Syntax for specifying persistent/temporary storage
- Re: New manifest spec - ready for FPWD?
- Contributions Re: Call for Exclusions: DOM Parsing and Serialization
Monday, 16 December 2013
- [IME API]Some Insights from Chinese Input Methods
- Re: Refactoring SharedWorkers out of Web Workers W3C spec
- Re: File API: closed Blob objects
- Re: Refactoring SharedWorkers out of Web Workers W3C spec
- Re: Refactoring SharedWorkers out of Web Workers W3C spec
- Re: File API: closed Blob objects
- Re: File API: closed Blob objects
- Re: File API: closed Blob objects
- Re: File API: closed Blob objects
- [Bug 24114] New: [imports]: add support for async loading
- Re: File API: closed Blob objects
- Re: Request for feedback: Streams API
Sunday, 15 December 2013
- Re: Custom form elements (was Re: [webcomponents] Inheritance in Custom Elements (Was Proposal for Cross Origin Use Case and Declarative Syntax))
- [Bug 24102] New: Specify the targets for events
- [Bug 24101] New: Missing word in "Return the readAsText() method, but continue to process the steps in this algorithm"
- Re: [webcomponents] Auto-creating shadow DOM for custom elements
Saturday, 14 December 2013
Friday, 13 December 2013
- Re: [webcomponents] Auto-creating shadow DOM for custom elements
- Re: [webcomponents] Auto-creating shadow DOM for custom elements
- Re: Passsword managers and autocomplete='off'
- Re: IndexedDB: Syntax for specifying persistent/temporary storage
- Re: File API: closed Blob objects
- Re: [webcomponents] Auto-creating shadow DOM for custom elements
- Re: [custom elements] Improving the name of document.register()
- Re: Allow javascript: URIs for registerProtocolHandler
- Re: Allow javascript: URIs for registerProtocolHandler
- Re: File API: closed Blob objects
- [push-api] Discussion with TAG on December 19
- Re: Call for Exclusions: DOM Parsing and Serialization
- Re: [webcomponents] Auto-creating shadow DOM for custom elements
- Re: [custom elements] Improving the name of document.register()
- Re: [custom elements] Improving the name of document.register()
- Re: [webcomponents] Auto-creating shadow DOM for custom elements
- Re: [webcomponents] Inheritance in Custom Elements (Was Proposal for Cross Origin Use Case and Declarative Syntax)
- Custom form elements (was Re: [webcomponents] Inheritance in Custom Elements (Was Proposal for Cross Origin Use Case and Declarative Syntax))
- Re: Passsword managers and autocomplete='off'
- Re: [custom elements] Improving the name of document.register()
- Re: [custom elements] Improving the name of document.register()
- Re: [custom elements] Improving the name of document.register()
- [Bug 22059] Composition dictionary should be changed
- Re: [custom elements] Improving the name of document.register()
- Re: [custom elements] Improving the name of document.register()
- [Bug 24087] New: [Custom]: Rename document.register to registerElement
- Re: Styling form control elements
- [Bug 24085] New: Specify Selection.modify
- [Bug 24084] New: Specify Selection.containsNode
- [Bug 24083] New: Window.getSelection() and HTMLDocument.getSelection() should return a nullable
- Re: [Beacon] Forbidding submitting Documents
- [Beacon] Forbidding submitting Documents
Thursday, 12 December 2013
- Re: IndexedDB: Syntax for specifying persistent/temporary storage
- Re: Passsword managers and autocomplete='off'
- Re: Passsword managers and autocomplete='off'
- Re: Passsword managers and autocomplete='off'
- Re: Passsword managers and autocomplete='off'
- Re: File API: closed Blob objects
- Re: Passsword managers and autocomplete='off'
- Re: File API: closed Blob objects
- Re: File API: closed Blob objects
- Re: File API: closed Blob objects
- Re: File API: closed Blob objects
- Re: File API: closed Blob objects
- Passsword managers and autocomplete='off'
- [Bug 24079] New: Test for initErrorEvent is invalid
- Re: File API: closed Blob objects
- Re: File API: closed Blob objects
- Re: Call for Exclusions: DOM Parsing and Serialization
- Re: File API: closed Blob objects
- Re: [custom elements] Improving the name of document.register()
- Re: Refactoring SharedWorkers out of Web Workers W3C spec
- Re: Call for Exclusions: DOM Parsing and Serialization
- Re: Refactoring SharedWorkers out of Web Workers W3C spec
- [Bug 24077] New: second-argument-null.html worker test is incorrect
- File API: closed Blob objects
- Re: [Bug 24074] New: new Worker('data:...') should not throw
- Re: Refactoring SharedWorkers out of Web Workers W3C spec
- Re: Refactoring SharedWorkers out of Web Workers W3C spec
- Re: Refactoring SharedWorkers out of Web Workers W3C spec
- Re: Refactoring SharedWorkers out of Web Workers W3C spec
- Re: [Bug 24074] New: new Worker('data:...') should not throw
- [Bug 24074] New: new Worker('data:...') should not throw
- [Bug 24072] New: Clarify handling of neutered objects
- Re: IndexedDB: Syntax for specifying persistent/temporary storage
- Re: [custom elements] Improving the name of document.register()
- Re: IndexedDB: Syntax for specifying persistent/temporary storage
- Re: [custom elements] Improving the name of document.register()
- Re: [custom elements] Improving the name of document.register()
- Re: [manifest] HTTP-based solution for loading manifests
Wednesday, 11 December 2013
- Re: [manifest] HTTP-based solution for loading manifests
- Re: Styling form control elements
- Re: Workers v2
- Re: Workers v2
- Re: Workers v2 (Was: Refactoring SharedWorkers out of Web Workers W3C spec)
- Workers v2 (Was: Refactoring SharedWorkers out of Web Workers W3C spec)
- Re: [custom elements] Improving the name of document.register()
- Re: [custom elements] Improving the name of document.register()
- [custom elements] Improving the name of document.register()
- RE: Refactoring SharedWorkers out of Web Workers W3C spec
- Re: [manifest] HTTP-based solution for loading manifests
- Re: [manifest] HTTP-based solution for loading manifests
- Re: Refactoring SharedWorkers out of Web Workers W3C spec
- Re: [manifest] HTTP-based solution for loading manifests
- Re: [manifest] HTTP-based solution for loading manifests
- Re: Refactoring SharedWorkers out of Web Workers W3C spec
Tuesday, 10 December 2013
Wednesday, 11 December 2013
- Re: Refactoring SharedWorkers out of Web Workers W3C spec
- Re: New manifest spec - ready for FPWD?
- Re: New manifest spec - ready for FPWD?
- Re: Styling form control elements
- [manifest] HTTP-based solution for loading manifests
- Re: Styling form control elements
- Re: Styling form control elements
- Re: Styling form control elements
- Re: Controling style of elements in Injection Points
- Re: Controling style of elements in Injection Points
- Re: Controling style of elements in Injection Points
Tuesday, 10 December 2013
- RE: Styling form control elements
- Re: Styling form control elements
- Re: Controling style of elements in Injection Points
- Re: Refactoring SharedWorkers out of Web Workers W3C spec
- Re: Refactoring SharedWorkers out of Web Workers W3C spec
- Re: Refactoring SharedWorkers out of Web Workers W3C spec
- Re: [webcomponents] Inheritance in Custom Elements (Was Proposal for Cross Origin Use Case and Declarative Syntax)
- Re: Refactoring SharedWorkers out of Web Workers W3C spec
- Re: [webcomponents] Inheritance in Custom Elements (Was Proposal for Cross Origin Use Case and Declarative Syntax)
- Refactoring SharedWorkers out of Web Workers W3C spec
- Re: [webcomponents] Inheritance in Custom Elements (Was Proposal for Cross Origin Use Case and Declarative Syntax)
- [Bug 24054] New: [Streams API] APIs that may use lots of resource should have some pressure on the app for consumption
- Re: Call for Exclusions: DOM Parsing and Serialization
- RfC: LCWD of DOM Parsing and Serialization; deadline 7 January 2014
- Re: Call for Exclusions: DOM Parsing and Serialization
- Re: Call for Exclusions: DOM Parsing and Serialization
- Re: [webcomponents] Inheritance in Custom Elements (Was Proposal for Cross Origin Use Case and Declarative Syntax)
- RE: [webcomponents] Inheritance in Custom Elements (Was Proposal for Cross Origin Use Case and Declarative Syntax)
- Re: [webcomponents] Inheritance in Custom Elements (Was Proposal for Cross Origin Use Case and Declarative Syntax)
- Re: [webcomponents] Inheritance in Custom Elements (Was Proposal for Cross Origin Use Case and Declarative Syntax)
- Re: [webcomponents] Inheritance in Custom Elements (Was Proposal for Cross Origin Use Case and Declarative Syntax)
- Re: Call for Exclusions: DOM Parsing and Serialization
- Re: [webcomponents] Inheritance in Custom Elements (Was Proposal for Cross Origin Use Case and Declarative Syntax)
- Re: Call for Exclusions: DOM Parsing and Serialization
- Re: [webcomponents] Inheritance in Custom Elements (Was Proposal for Cross Origin Use Case and Declarative Syntax)
- Re: Call for Exclusions: DOM Parsing and Serialization
- Call for Exclusions: DOM Parsing and Serialization
- Re: CfC: publish LCWD of DOM Parsing and Serialization; deadline December 3
- Re: [webcomponents] Auto-creating shadow DOM for custom elements
- Re: [webcomponents] Auto-creating shadow DOM for custom elements
- Re: [webcomponents] Auto-creating shadow DOM for custom elements
- Re: [webcomponents] Standard Use Case (Was Auto-creating shadow DOM for custom elements)
- Re: [webcomponents] Standard Use Case (Was Auto-creating shadow DOM for custom elements)
- [webcomponents] Standard Use Case (Was Auto-creating shadow DOM for custom elements)
- Re: [webcomponents] Auto-creating shadow DOM for custom elements
- Re: [webcomponents] Inheritance in Custom Elements (Was Proposal for Cross Origin Use Case and Declarative Syntax)
- Re: [webcomponents] Inheritance in Custom Elements (Was Proposal for Cross Origin Use Case and Declarative Syntax)
- Re: [webcomponents] Inheritance in Custom Elements (Was Proposal for Cross Origin Use Case and Declarative Syntax)
- Re: [webcomponents] Inheritance in Custom Elements (Was Proposal for Cross Origin Use Case and Declarative Syntax)
- Re: [webcomponents] Inheritance in Custom Elements (Was Proposal for Cross Origin Use Case and Declarative Syntax)
- Re: [webcomponents] Inheritance in Custom Elements (Was Proposal for Cross Origin Use Case and Declarative Syntax)
Monday, 9 December 2013
- [Bug 24043] New: [Custom]: Need to check writable too.
- [Bug 24042] New: [imports]: Parser should not wait on external resources inside imports
- Re: [webcomponents] Inheritance in Custom Elements (Was Proposal for Cross Origin Use Case and Declarative Syntax)
- Re: [webcomponents] Auto-creating shadow DOM for custom elements
- Re: [webcomponents] Auto-creating shadow DOM for custom elements
- Re: IndexedDB, Blobs and partial Blobs - Large Files
- Re: [webcomponents] Auto-creating shadow DOM for custom elements
- Fwd: Re: Please review the updated Streams API
- Re: inline declarative manifest, was Re: New manifest spec - ready for FPWD?
- Re: New manifest spec - ready for FPWD?
- Re: inline declarative manifest, was Re: New manifest spec - ready for FPWD?
- Re: inline declarative manifest, was Re: New manifest spec - ready for FPWD?
- Re: Comments on version web-apps specs from 2013-10-31
- Re: Request for feedback: Streams API
- Re: [webcomponents] Decoupling Custom Elements and Shadow DOM (Was Proposal for Cross Origin Use Case and Declarative Syntax)
- Re: [webcomponents] Inheritance in Custom Elements (Was Proposal for Cross Origin Use Case and Declarative Syntax)
Sunday, 8 December 2013
- Re: [webcomponents] Auto-creating shadow DOM for custom elements
- RE: [webcomponents] Inheritance in Custom Elements (Was Proposal for Cross Origin Use Case and Declarative Syntax)
- Re: [webcomponents] Inheritance in Custom Elements (Was Proposal for Cross Origin Use Case and Declarative Syntax)
- Re: [webcomponents] Auto-creating shadow DOM for custom elements
- Re: [webcomponents] Auto-creating shadow DOM for custom elements
- RE: [webcomponents] Inheritance in Custom Elements (Was Proposal for Cross Origin Use Case and Declarative Syntax)
- Re: [webcomponents] Inheritance in Custom Elements (Was Proposal for Cross Origin Use Case and Declarative Syntax)
- Re: RE : Sync IO APIs in Shared Workers
Saturday, 7 December 2013
- Re: [webcomponents] Auto-creating shadow DOM for custom elements
- Re: [webcomponents] Auto-creating shadow DOM for custom elements
- Re: [webcomponents] Auto-creating shadow DOM for custom elements
- Re: [webcomponents] Binding Custom Element without Polluting Global Scope (Was Proposal for Cross Origin Use Case and Declarative Syntax)
- Re: [webcomponents] Auto-creating shadow DOM for custom elements
- RE: [webcomponents] Auto-creating shadow DOM for custom elements
- Re: [webcomponents] Auto-creating shadow DOM for custom elements
- Re: [webcomponents] Auto-creating shadow DOM for custom elements
- RE: [webcomponents] Auto-creating shadow DOM for custom elements
- Re: [webcomponents] Auto-creating shadow DOM for custom elements
- RE: [webcomponents] Auto-creating shadow DOM for custom elements
- Re: [webcomponents] Auto-creating shadow DOM for custom elements
- Re: [webcomponents] Auto-creating shadow DOM for custom elements
- RE: [webcomponents] Auto-creating shadow DOM for custom elements
- Re: [webcomponents] Auto-creating shadow DOM for custom elements
- RE: [webcomponents] Auto-creating shadow DOM for custom elements
- Re: [webcomponents] Auto-creating shadow DOM for custom elements
- RE: Styling form control elements
- Re: [webcomponents] Auto-creating shadow DOM for custom elements
- RE: Styling form control elements
- Re: [WebComponents] List for new bug announcements [Was: Re: Why can't we just use constructor instead of createdCallback?]
- Re: Objection to publishing DOM Parsing and Serialization (was Re: CfC: publish LCWD of DOM Parsing and Serialization; deadline December 3)
- Re: Objection to publishing DOM Parsing and Serialization (was Re: CfC: publish LCWD of DOM Parsing and Serialization; deadline December 3)
- [WebComponents] List for new bug announcements [Was: Re: Why can't we just use constructor instead of createdCallback?]
- Re: [webcomponents] Binding Custom Element without Polluting Global Scope (Was Proposal for Cross Origin Use Case and Declarative Syntax)
- Re: Styling form control elements
- Re: [webcomponents] Auto-creating shadow DOM for custom elements
- Re: [webcomponents] Auto-creating shadow DOM for custom elements
- Re: [webcomponents] Auto-creating shadow DOM for custom elements
- Re: Styling form control elements
- RE: Styling form control elements
- Re: [webcomponents] Binding Custom Element without Polluting Global Scope (Was Proposal for Cross Origin Use Case and Declarative Syntax)
- Re: [webcomponents] Binding Custom Element without Polluting Global Scope (Was Proposal for Cross Origin Use Case and Declarative Syntax)
- Re: RE : Sync IO APIs in Shared Workers
- Re: RE : RE : Sync IO APIs in Shared Workers
Friday, 6 December 2013
- Re: Why can't we just use constructor instead of createdCallback?
- Re: IndexedDB: Syntax for specifying persistent/temporary storage
- Re: IndexedDB: Syntax for specifying persistent/temporary storage
- Re: Styling form control elements
- Re: IndexedDB: Syntax for specifying persistent/temporary storage
- Re: CfC: publish new WD of Input Method Editor API; deadline December 13
- Re: Objection to publishing DOM Parsing and Serialization (was Re: CfC: publish LCWD of DOM Parsing and Serialization; deadline December 3)
- Re: IndexedDB: Syntax for specifying persistent/temporary storage
- Re: Styling form control elements
- [Bug 24023] New: [Streams API] Returned promise of write() should be fulfilled with current available space size rather than how many bytes were written
- [Bug 24022] New: [Streams API] Lazily encode write()-en DOMString
- CfC: publish new WD of Input Method Editor API; deadline December 13
- Re: Updating Input Method Editor API working draft
- [Bug 24021] [Streams API] Fix process pendingWriteQueue alrogithm
- [Bug 24021] New: [Streams API] Fix process pendingWriteQueue alrogithm
- Re: Styling form control elements
- Re: Styling form control elements
- Re: Why can't we just use constructor instead of createdCallback?
- IndexedDB: Syntax for specifying persistent/temporary storage
- Re: Why can't we just use constructor instead of createdCallback?
- Re: Updating Input Method Editor API working draft
- Re: Styling form control elements
- Re: Objection to publishing DOM Parsing and Serialization (was Re: CfC: publish LCWD of DOM Parsing and Serialization; deadline December 3)
- Re: Styling form control elements
- Objection to publishing DOM Parsing and Serialization (was Re: CfC: publish LCWD of DOM Parsing and Serialization; deadline December 3)
- Re: Updating Input Method Editor API working draft
- Re: Styling form control elements
- Re: [webcomponents] Auto-creating shadow DOM for custom elements
- Re: [webcomponents] Binding Custom Element without Polluting Global Scope (Was Proposal for Cross Origin Use Case and Declarative Syntax)
- Re: Why can't we just use constructor instead of createdCallback?
- Re: Why can't we just use constructor instead of createdCallback?
- Re: Why can't we just use constructor instead of createdCallback?
- Re: Why can't we just use constructor instead of createdCallback?
- Re: [webcomponents] Inheritance in Custom Elements (Was Proposal for Cross Origin Use Case and Declarative Syntax)
- Re: [webcomponents] Inheritance in Custom Elements (Was Proposal for Cross Origin Use Case and Declarative Syntax)
- Re: [webcomponents] Inheritance in Custom Elements (Was Proposal for Cross Origin Use Case and Declarative Syntax)
- Re: [webcomponents] Inheritance in Custom Elements (Was Proposal for Cross Origin Use Case and Declarative Syntax)
- Updating Input Method Editor API working draft
- Re: Why can't we just use constructor instead of createdCallback?
- Re: [webcomponents] Inheritance in Custom Elements (Was Proposal for Cross Origin Use Case and Declarative Syntax)
- Re: Why can't we just use constructor instead of createdCallback?
- Re: Browser search API
- Re: Why can't we just use constructor instead of createdCallback?
- Re: [webcomponents] Inheritance in Custom Elements (Was Proposal for Cross Origin Use Case and Declarative Syntax)
- Re: Why can't we just use constructor instead of createdCallback?
- Re: [webcomponents] Inheritance in Custom Elements (Was Proposal for Cross Origin Use Case and Declarative Syntax)
- Re: Styling form control elements
- [webcomponents] Inheritance in Custom Elements (Was Proposal for Cross Origin Use Case and Declarative Syntax)
- Re: [webcomponents] Decoupling Custom Elements and Shadow DOM (Was Proposal for Cross Origin Use Case and Declarative Syntax)
- Re: [webcomponents] Decoupling Custom Elements and Shadow DOM (Was Proposal for Cross Origin Use Case and Declarative Syntax)
- [webcomponents] Binding Custom Element without Polluting Global Scope (Was Proposal for Cross Origin Use Case and Declarative Syntax)
- [webcomponents] Decoupling Custom Elements and Shadow DOM (Was Proposal for Cross Origin Use Case and Declarative Syntax)
- RE: Styling form control elements
- Re: Browser search API
- [webcomponents] Auto-creating shadow DOM for custom elements
- Why can't we just use constructor instead of createdCallback?
- Re: Styling form control elements
Thursday, 5 December 2013
- Re: Styling form control elements
- Re: Styling form control elements
- Re: Styling form control elements
- Re: Browser search API
- [Bug 23790] Remove size argument from read() and introduce pullAmount attribute instead
- [Bug 24008] New: [Streams API] Partially decreasing numBytesBeingReturned without calling next read()
- [Bug 23720] Make it able to issue multiple write()s on a Stream without waiting for completion
- [Bug 23772] Just return read result when there's data synchronously readable
- [Bug 23724] Merge skip() method into read() by adding "none" type to StreamReadType
- [Bug 23718] Stream interface should be decoupled into WritableStream and ReadableStream
- [Bug 23732] Consider adding best-effort scatter/gather mode
- [Bug 23743] Split the functionality to read exact N bytes into readExact() method
- Re: RfC: LCWD of Custom Elements; deadline November 21
- Re: Styling form control elements
- Re: Styling form control elements
- Re: Styling form control elements
- Re: [webcomponents] HTML Imports
- Re: Styling form control elements
- Re: Styling form control elements
- Re: Browser search API
- Re: inline declarative manifest, was Re: New manifest spec - ready for FPWD?
- Re: [process] Process Violation with Custom Elements LC? [Was: Re: RfC: LCWD of Custom Elements; deadline November 21]
- Re: Request for feedback: Streams API
- [process] Process Violation with Custom Elements LC? [Was: Re: RfC: LCWD of Custom Elements; deadline November 21]
- RE : RE : Sync IO APIs in Shared Workers
- Re: [webcomponents] HTML Imports
- Styling form control elements
- Re: Request for feedback: Streams API
- Re: RE : Sync IO APIs in Shared Workers
- Re: RfC: LCWD of Custom Elements; deadline November 21
- Re: Cross Origin Web Components: Fixing iframes
- Re: [webcomponents] HTML Imports
- Re: RE : Sync IO APIs in Shared Workers
Wednesday, 4 December 2013
- Re: [HTML Imports]: what scope to run in
- Re: [webcomponents] HTML Imports
- Re: Request for feedback: Streams API
- Re: Last Call for High Resolution Time Level 2
- RE: Request for feedback: Streams API
- Re: Request for feedback: Streams API
- Re: [webcomponents] HTML Imports
- Re: [webcomponents] HTML Imports
- Re: inline declarative manifest, was Re: New manifest spec - ready for FPWD?
- RE: Last Call for High Resolution Time Level 2
- Re: [webcomponents] HTML Imports
- Re: Request for feedback: Streams API
- Re: [webcomponents] HTML Imports
- Re: [webcomponents] HTML Imports
- Re: Request for feedback: Streams API
- Re: IndexedDB, Blobs and partial Blobs - Large Files
- Request for feedback: Streams API
- Re: [HTML Imports]: Sync, async, -ish?
- Re: Browser search API
- Re: Last Call for High Resolution Time Level 2
- Re: Browser search API
- Re: inline declarative manifest, was Re: New manifest spec - ready for FPWD?
- Re: inline declarative manifest, was Re: New manifest spec - ready for FPWD?
- Re: [webcomponents] HTML Imports
- Re: RfC: LCWD of Custom Elements; deadline November 21
- Re: in-page search, was Re: New manifest spec - ready for FPWD?
- RE : Sync IO APIs in Shared Workers
- Re: inline declarative manifest, was Re: New manifest spec - ready for FPWD?
- Re: IndexedDB, Blobs and partial Blobs - Large Files
- Re: inline declarative manifest, was Re: New manifest spec - ready for FPWD?
- Re: [webcomponents] HTML Imports
- Re: [HTML Imports]: Sync, async, -ish?
- Re: inline declarative manifest, was Re: New manifest spec - ready for FPWD?
- Re: inline declarative manifest, was Re: New manifest spec - ready for FPWD?
- Re: inline declarative manifest, was Re: New manifest spec - ready for FPWD?
- Re: RfC: LCWD of Custom Elements; deadline November 21
- Re: [webcomponents] HTML Imports
- Re: [webcomponents] HTML Imports
- Re: [webcomponents] HTML Imports
- Re: Cross Origin Web Components: Fixing iframes
- Re: RfC: LCWD of Custom Elements; deadline November 21
- [Bug 23907] How do web apps distinguish if a keydown event causes text input?
Tuesday, 3 December 2013
- Re: inline declarative manifest, was Re: New manifest spec - ready for FPWD?
- Re: in-page search, was Re: New manifest spec - ready for FPWD?
- in-page search, was Re: New manifest spec - ready for FPWD?
- Re: New manifest spec - ready for FPWD?
- Re: Sync IO APIs in Shared Workers
- inline declarative manifest, was Re: New manifest spec - ready for FPWD?
- RE: CfC: publish LCWD of DOM Parsing and Serialization; deadline December 3
- Re: New manifest spec - ready for FPWD?
- Re: IndexedDB, Blobs and partial Blobs - Large Files
- [Bug 23946] Lift the ban on query parts in “blob:” URIs
- Re: IndexedDB, Blobs and partial Blobs - Large Files
- Re: [HTML Imports]: Sync, async, -ish?
- Re: RfC: LCWD of Custom Elements; deadline November 21
- Re: [manifest] orientation member
- Re: [HTML Imports]: Sync, async, -ish?
- Re: [HTML Imports]: Sync, async, -ish?
- Re: New manifest spec - ready for FPWD?
- Re: [screen-orientation] Locking to 'current' orientation
- Re: [screen-orientation] screen orientation angle
- Re: [manifest] orientation member
- [Bug 23977] New: [Streams API] Generic object stream
- [Bug 23946] Lift the ban on query parts in “blob:” URIs
- Last Call for High Resolution Time Level 2
- [Bug 23975] New: [Streams API] Remove read as Blob support
- [Bug 23974] New: [Streams API] Don't inherit object URL feature
- [Bug 23973] New: [Streams API] Introduce in-band error signaling
- Re: [manifest] orientation member
- Re: [manifest] orientation member
- Re: [manifest] orientation member
- Re: [screen-orientation] screen orientation angle
- Re: IndexedDB, Blobs and partial Blobs - Large Files
- Re: [manifest] orientation member
- Re: File API | lastModified and Date attribute change
- Re: [screen-orientation] Locking to 'current' orientation
- Re: [screen-orientation] Locking to 'current' orientation
- Re: New manifest spec - ready for FPWD?
- Fwd: Reminder: TPAC 2013 feedback requested by 8 December
- Re: New manifest spec - ready for FPWD?
- Re: New manifest spec - ready for FPWD?
- Re: [screen-orientation] Locking to 'current' orientation
- Re: [screen-orientation] screen orientation angle
- Re: [screen-orientation] Locking to 'current' orientation
- Re: New manifest spec - ready for FPWD?
- Re: [screen-orientation] Locking to 'current' orientation
- Re: [manifest] orientation member
- [Bug 22093] Consider adding candidatewindowshow/update/hide events and getCandidateWindowClientRect()
- [Bug 22059] Composition dictionary should be changed
- [Bug 22028] Consider adding hasComposition() in InputMethodContext
- [Bug 23829] Split current draft into 2 specs
Monday, 2 December 2013
- Re: File API | lastModified and Date attribute change
- Re: File API | lastModified and Date attribute change
- Re: Fixing appcache: a proposal to get us started
- Re: CfC: publish FPWD of Manifest for web apps and bookmarks; deadline December 9
- Re: IndexedDB, Blobs and partial Blobs - Large Files
- File API | lastModified and Date attribute change
- Re: CfC: publish Candidate Recommendation of File API; deadline November 28
- RE: Browser search API
- Re: Browser search API
- CfC: publish FPWD of Manifest for web apps and bookmarks; deadline December 9
- IndexedDB, Blobs and partial Blobs - Large Files
- [admin] F2F meetings in 2014
- Re: [screen-orientation] Locking to 'current' orientation
- [admin] December 7 is last day to start a CfC to publish a spec in December
- Re: LINK only in HEAD?
- Re: [manifest] orientation member
- Re: Browser search API
- Re: [screen-orientation] When window orientation != screen orientation...
- Re: Browser search API
- CfC: publish Candidate Recommendation of Pointer Lock; deadline Dec 9
- Re: Browser search API
Sunday, 1 December 2013
- Re: Controling style of elements in Injection Points
- Re: CfC: publish Candidate Recommendation of File API; deadline November 28
- Re: RfC: LCWD of Pointer Lock; deadline November 28
Saturday, 30 November 2013
- [Bug 23946] New: Lift the ban on query parts in “blob:” URIs
- Re: Fixing appcache: a proposal to get us started
- Re: RfC: LCWD of Pointer Lock; deadline November 28
- Browser search API
Friday, 29 November 2013
Thursday, 28 November 2013
- Re: LINK only in HEAD?
- Re: Controling style of elements in Injection Points
- Re: [Bug 23853] Please clarify the interpretation of the WebIDL undefined Date in the File constructor
- Re: Controling style of elements in Injection Points
- Re: LINK only in HEAD?
- [Bug 23853] Please clarify the interpretation of the WebIDL undefined Date in the File constructor
- Re: CfC: publish LCWD of DOM Parsing and Serialization; deadline December 3
- Re: [screen-orientation] When window orientation != screen orientation...
- Re: New manifest spec - ready for FPWD?
- Re: Controling style of elements in Injection Points
- Re: LINK only in HEAD?
- Re: Controling style of elements in Injection Points
- Re: Controling style of elements in Injection Points
- Re: Fixing appcache: a proposal to get us started
- Controling style of elements in Injection Points
Wednesday, 27 November 2013
- Re: Fixing appcache: a proposal to get us started
- Re: Allow javascript: URIs for registerProtocolHandler
- Re: [HTML Imports]: Sync, async, -ish?
- Re: RfC: LCWD of Custom Elements; deadline November 21
- RE: New manifest spec - ready for FPWD?
- Re: LINK only in HEAD?
- Re: LINK only in HEAD?
- Re: LINK only in HEAD?
- Re: LINK only in HEAD?
- Re: [HTML Imports]: Sync, async, -ish?
- Re: LINK only in HEAD?
- Re: [HTML Imports]: Sync, async, -ish?
- Re: [HTML Imports]: Sync, async, -ish?
- Re: LINK only in HEAD?
- LINK only in HEAD?
- Re: [HTML Imports]: Sync, async, -ish?
- Re: [HTML Imports]: Sync, async, -ish?
- RE: CfC: publish LCWD of DOM Parsing and Serialization; deadline December 3
- RE: CfC: publish LCWD of DOM Parsing and Serialization; deadline December 3
- Re: New manifest spec - ready for FPWD?
- Re: CfC: publish LCWD of DOM Parsing and Serialization; deadline December 3
- Re: CfC: publish LCWD of DOM Parsing and Serialization; deadline December 3
- Re: CfC: publish LCWD of DOM Parsing and Serialization; deadline December 3
- RE: New manifest spec - ready for FPWD?
- Re: [screen-orientation] screen orientation angle
- [screen-orientation] When window orientation != screen orientation...
- Re: New manifest spec - ready for FPWD?
- Re: CfC: publish LCWD of DOM Parsing and Serialization; deadline December 3
- Re: Cross Origin Web Components: Fixing iframes
- Re: Cross Origin Web Components: Fixing iframes
Tuesday, 26 November 2013
- Re: Cross Origin Web Components: Fixing iframes
- Re: New manifest spec - ready for FPWD?
- Re: [HTML Imports]: Sync, async, -ish?
- Re: New manifest spec - ready for FPWD?
- Re: New manifest spec - ready for FPWD?
- New manifest spec - ready for FPWD?
- Re: [screen-orientation] screen orientation angle
Wednesday, 27 November 2013
Tuesday, 26 November 2013
- CfC: publish LCWD of DOM Parsing and Serialization; deadline December 3
- RE: publish LCWD of DOM Parsing and Serialization; deadline November 25
- Re: [screen-orientation] screen orientation angle
- Re: [screen-orientation] screen orientation angle
- Re: [screen-orientation] screen orientation angle
- RE: [screen-orientation] screen orientation angle
- Re: [screen-orientation] screen orientation angle
- Re: [screen-orientation] screen orientation angle
- Re: [screen-orientation] screen orientation angle
- Re: [screen-orientation] Locking to 'current' orientation
- [screen-orientation] screen orientation angle
- Re: [screen-orientation] Locking to 'current' orientation
- Re: [screen-orientation] Locking to 'current' orientation
- Re: [screen-orientation] Locking to 'current' orientation
- [screen-orientation] Locking to 'current' orientation
- Re: publish LCWD of DOM Parsing and Serialization; deadline November 25
- Re: [testing] Seeking Test Facilitator(s) for Indexed Database API
- RE: [testing] Seeking Test Facilitator(s) for Indexed Database API
- Cross Origin Web Components: Fixing iframes
- RE: publish LCWD of DOM Parsing and Serialization; deadline November 25
Monday, 25 November 2013
- Re: Fixing appcache: a proposal to get us started
- [Bug 13913] Attributes don't have an order
- [Bug 13913] Attributes don't have an order
- Re: Fixing appcache: a proposal to get us started
- Re: Fixing appcache: a proposal to get us started
- Re: Fixing appcache: a proposal to get us started
- Re: Fixing appcache: a proposal to get us started
- Re: Fixing appcache: a proposal to get us started
- Re: Fixing appcache: a proposal to get us started
- [Bug 23787] Clarify that which HTTP entity body is referred in ProgressEvent spec
- Re: Fixing appcache: a proposal to get us started
- Re: Fixing appcache: a proposal to get us started
Sunday, 24 November 2013
- Re: Sync IO APIs in Shared Workers
- [Bug 23900] New: WebRTC DataChannels are not called out as producers/consumers
- Re: Sync IO APIs in Shared Workers
Saturday, 23 November 2013
- Re: Sync IO APIs in Shared Workers
- Re: [HTML Imports]: what scope to run in
- Re: [HTML Imports]: what scope to run in
- Re: RTC in Web workers
- RTC in Web workers
Friday, 22 November 2013
- Re: Sync IO APIs in Shared Workers
- [testing] Seeking Test Facilitator(s) for Indexed Database API
- Re: Sync IO APIs in Shared Workers
- Re: [HTML Imports]: Sync, async, -ish?
- Re: [HTML Imports]: Sync, async, -ish?
- Re: [HTML Imports]: Sync, async, -ish?
- Re: [HTML Imports]: Sync, async, -ish?
- Re: [HTML Imports]: Sync, async, -ish?
- Re: [HTML Imports]: Sync, async, -ish?
- Re: Sync IO APIs in Shared Workers
- Re: CfC: publish Candidate Recommendation of File API; deadline November 28
- Reminder: RfC: LCWD of Pointer Lock; deadline November 28
- Re: Sync IO APIs in Shared Workers
- [Bug 23787] Clarify that which HTTP entity body is referred in ProgressEvent spec
- Sync IO APIs in Shared Workers
- Re: [HTML Imports]: Sync, async, -ish?
- Re: [HTML Imports]: Sync, async, -ish?
Thursday, 21 November 2013
- Re: [HTML Imports]: Sync, async, -ish?
- Re: [HTML Imports]: Sync, async, -ish?
- Re: [HTML Imports]: Sync, async, -ish?
- Re: [HTML Imports]: Sync, async, -ish?
- Re: [HTML Imports]: Sync, async, -ish?
- CfC: publish Candidate Recommendation of File API; deadline November 28
- Re: [FileAPI] LC Comment Tracking
- [Bug 21264] referrer source is wrong
- [Bug 23780] Check XMLHttpRequest and Notification don't break given the new script settings object stuff
- RE: Comments on version web-apps specs from 2013-10-31
- Re: [HTML Imports]: what scope to run in
- Re: [HTML Imports]: what scope to run in
- Re: [HTML Imports]: what scope to run in
Wednesday, 20 November 2013
- [Bug 23878] New: figure out termination of requests when documents become inactive
- Re: [HTML Imports]: what scope to run in
- Comments on version web-apps specs from 2013-10-31
- Re: [HTML Imports]: what scope to run in
- Re: [HTML Imports]: Sync, async, -ish?
- Re: [HTML Imports]: Sync, async, -ish?
- Re: [HTML Imports]: Sync, async, -ish?
- Re: [HTML Imports]: Sync, async, -ish?
- Re: [HTML Imports]: Sync, async, -ish?
- Re: [HTML Imports]: Sync, async, -ish?
- Re: [HTML Imports]: Sync, async, -ish?
- Re: [HTML Imports]: Sync, async, -ish?
Tuesday, 19 November 2013
- Re: [HTML Imports]: what scope to run in
- Re: [HTML Imports]: what scope to run in
- Re: [HTML Imports]: what scope to run in
- Re: [HTML Imports]: what scope to run in
- [Bug 23601] Define a variable to replace "with prejudice"
- Re: [HTML Imports]: what scope to run in
- [Bug 23853] Please clarify the interpretation of the WebIDL undefined Date in the File constructor
- Re: XMLHttpRequest.prototype.responseURL
- Re: [HTML Imports]: what scope to run in
- RE: CfC: publish Proposed Recommendation of Progress Events; deadline November 25
- RE: CfC: publish Proposed Recommendation of Progress Events; deadline November 25
- Re: [HTML Imports]: what scope to run in
- Re: [HTML Imports]: what scope to run in
- Re: [HTML Imports]: what scope to run in
- Re: CfC: publish Proposed Recommendation of Progress Events; deadline November 25
- Re: [HTML Imports]: what scope to run in
- Re: [HTML Imports]: Sync, async, -ish?
- Re: [HTML Imports]: Sync, async, -ish?
- [Bug 23450] Add Specification Note Describing "Save As" Behavior for File Objects
- Re: [HTML Imports]: what scope to run in
- [HTML Imports]: what scope to run in
- Re: [HTML Imports]: Sync, async, -ish?
Monday, 18 November 2013
- Re: [HTML Imports]: Sync, async, -ish?
- Re: [HTML Imports]: Sync, async, -ish?
- Re: [HTML Imports]: Sync, async, -ish?
- Re: [HTML Imports]: Sync, async, -ish?
- Re: [HTML Imports]: Sync, async, -ish?
- [HTML Imports]: Sync, async, -ish?
- Canceled: CfC: publish LCWD of DOM Parsing and Serialization; deadline November 25
- Re: CfC: publish LCWD of DOM Parsing and Serialization; deadline November 25
- RE: publish LCWD of DOM Parsing and Serialization; deadline November 25
- Re: XMLHttpRequest.prototype.responseURL
- Re: XMLHttpRequest.prototype.responseURL
- XMLHttpRequest.prototype.responseURL
- [Bug 21264] referrer source is wrong
- [Bug 21264] referrer source is wrong
- [Bug 23780] Check XMLHttpRequest and Notification don't break given the new script settings object stuff
- [Bug 23853] New: Please clarify the interpretation of the WebIDL undefined Date in the File constructor
- Re: CfC: publish Proposed Recommendation of Progress Events; deadline November 25
- [Bug 23450] Add Specification Note Describing "Save As" Behavior for File Objects
- CfC: publish Proposed Recommendation of Progress Events; deadline November 25
- CfC: publish LCWD of DOM Parsing and Serialization; deadline November 25
Sunday, 17 November 2013
- Re: [IndexedDB] MultiEntry compound index proposal
- [IndexedDB] MultiEntry compound index proposal
- [Bug 23431] File API should say what to do with the query string in blob: URLs
Saturday, 16 November 2013
Thursday, 14 November 2013
- [Bug 21830] KeyboardEvent.locale is too general.
- [Bug 21083] Proposal key names for Android
- [Bug 23830] New: Move attributes of Composition interface to CompositionEvent
- [Bug 23829] New: Split current draft into 2 specs
Wednesday, 13 November 2013
- Draft minutes: 12 November 2013
- Draft minutes: 11 November 2013
- Re: [webcomponents] Proposal for Cross Origin Use Case and Declarative Syntax
- Re: [webcomponents] Proposal for Cross Origin Use Case and Declarative Syntax
Tuesday, 12 November 2013
- Re: [webcomponents] Proposal for Cross Origin Use Case and Declarative Syntax
- Re: [webcomponents] Proposal for Cross Origin Use Case and Declarative Syntax
- Re: Thoughts behind the Streams API ED
- Re: Thoughts behind the Streams API ED
- [Bug 23799] New: [Streams API] Feature req: in-band control signal
- Re: [webcomponents] Proposal for Cross Origin Use Case and Declarative Syntax
- Re: Thoughts behind the Streams API ED
- Re: Thoughts behind the Streams API ED
- Re: Thoughts behind the Streams API ED
- Re: Why no TypeError in FileReaderSync.readAsArrayBuffer
- RE: [webcomponents] Proposal for Cross Origin Use Case and Declarative Syntax
- [Bug 23780] Check XMLHttpRequest and Notification don't break given the new script settings object stuff
- Re: Why no TypeError in FileReaderSync.readAsArrayBuffer
- Re: [webcomponents] Proposal for Cross Origin Use Case and Declarative Syntax
Monday, 11 November 2013
- Re: [webcomponents] Proposal for Cross Origin Use Case and Declarative Syntax
- Re: [webcomponents] Proposal for Cross Origin Use Case and Declarative Syntax
- Re: Thoughts behind the Streams API ED
- Re: Why no TypeError in FileReaderSync.readAsArrayBuffer
- Re: Why no TypeError in FileReaderSync.readAsArrayBuffer
- Re: [webcomponents] Proposal for Cross Origin Use Case and Declarative Syntax
- Re: [webcomponents] Proposal for Cross Origin Use Case and Declarative Syntax
- Re: [webcomponents] Proposal for Cross Origin Use Case and Declarative Syntax
- [Bug 23787] Clarify that which HTTP entity body is referred in ProgressEvent spec
- Re: [webcomponents] Proposal for Cross Origin Use Case and Declarative Syntax
- [Bug 23790] New: Remove size argument from read() and introduce pullAmount attribute instead
- Re: [webcomponents] Proposal for Cross Origin Use Case and Declarative Syntax
- [webcomponents] The latest editor's drafts of the Web Components specifications are now hosted on github.
- [Bug 23787] New: Clarify that which HTTP entity body is referred in ProgressEvent spec
- Re: [webcomponents] Proposal for Cross Origin Use Case and Declarative Syntax
- [Bug 16312] use of undocumented 'switch' convention for rule formulation is ambiguous
Thursday, 7 November 2013
Friday, 8 November 2013
- [webcomponents] Proposal for Cross Origin Use Case and Declarative Syntax
- Re: [FileAPI] LC Comment Tracking
- Re: Thoughts behind the Streams API ED
- Re: Thoughts behind the Streams API ED
- Re: Thoughts behind the Streams API ED
- Re: Thoughts behind the Streams API ED
- Re: [coord] Request for Inter-Group Coordination at TPAC
- Re: Thoughts behind the Streams API ED
- [Bug 23772] New: Just return read result when there's data synchronously readable
- [Bug 23731] Should readEncoding be merged into readType?
Thursday, 7 November 2013
- [Bug 23763] New: Separate MIME type from Stream or not
- [FileAPI] LC Comment Tracking
- [Bug 16312] use of undocumented 'switch' convention for rule formulation is ambiguous
- [Bug 12837] Define unloading document cleanup steps
- [Bug 16312] use of undocumented 'switch' convention for rule formulation is ambiguous
- [Bug 23363] requestFullscreen and dialog.showModal interaction
- [Bug 12837] Define unloading document cleanup steps
- Re: Thoughts behind the Streams API ED
- Re: Thoughts behind the Streams API ED
- Re: Thoughts behind the Streams API ED
- Re: Thoughts behind the Streams API ED
- Re: Thoughts behind the Streams API ED
- [Bug 22093] Consider adding candidatewindowshow/update/hide events and getCandidateWindowClientRect()
- [Bug 22059] Composition dictionary should be changed
Wednesday, 6 November 2013
- Re: Define window.orientation
- Re: Define window.orientation
- Re: Define window.orientation
- Re: Thoughts behind the Streams API ED
- Re: Polished FileSystem API proposal
- [Bug 23743] New: Divide "arraybuffer" StreamReadType into "arraybuffer/exact" and "arraybuffer"
- Re: Polished FileSystem API proposal
- Re: Polished FileSystem API proposal
- Re: Polished FileSystem API proposal
- Re: Polished FileSystem API proposal
- Re: Define window.orientation
- Re: Thoughts behind the Streams API ED
- Re: Define window.orientation
- Re: Polished FileSystem API proposal
Tuesday, 5 November 2013
Wednesday, 6 November 2013
- [Bug 23736] New: [Streams API] Add fork() method instead of having pipe(Stream[]) overload
- [Bug 23735] New: [Streams API] Failure signaling to object URL created from Stream
- [Bug 22059] Composition dictionary should be changed
- [Bug 22093] Consider adding candidatewindowshow/update/hide events and getCandidateWindowClientRect()
- Re: Define window.orientation
- Re: Define window.orientation
Tuesday, 5 November 2013
- Re: Define window.orientation
- Re: Define window.orientation
- Re: Define window.orientation
- Re: Polished FileSystem API proposal
- [Bug 23732] New: [Streams API] Consider adding best-effort scatter/gather mode
- [Bug 23731] New: [Streams API] Should readEncoding be merged into readType?
- Re: Polished FileSystem API proposal
- Re: Polished FileSystem API proposal
- [Bug 23726] New: Integration between XMLHttpRequest and Streams API
- [Bug 23725] New: Consider strongly-defined createStream to add generic stream support for APIs
- [Bug 23724] New: Merge skip() method into read() by adding "none" type to StreamReadType
- [Bug 23234] Mark document response entity body as HTML document
- Re: Thoughts behind the Streams API ED
- Re: Define window.orientation
- Re: Define window.orientation
- Define window.orientation
- "where" Re: CfC: publish WD of Streams API; deadline Nov 3
- [Bug 23720] New: Make it able to issue multiple write()s on a Stream without waiting for completion
- [Bug 23719] New: Consider adding pull style flow control method to Stream
- [Bug 23718] New: Stream interface should be decoupled into WritableStream and ReadableStream
Monday, 4 November 2013
- Re: CfC: publish WD of Streams API; deadline Nov 3
- Re: Thoughts behind the Streams API ED
- Thoughts behind the Streams API ED
- Need review for changes to some html/webapps tests
- [xhr-1] Keep the responseType "json"
- RE: [coord] Is there still a need for WebApps + SysApps meeting at TPAC?
- RE: CfC: publish WD of Streams API; deadline Nov 3
- Re: CfC: publish WD of Streams API; deadline Nov 3
- Re: CfC: publish new WD of Quota Management API; deadline November 3
Sunday, 3 November 2013
- RE: CfC: publish WD of Streams API; deadline Nov 3
- Re: Overlap between StreamReader and FileReader
- Re: CfC: publish WD of Streams API; deadline Nov 3
- Re: CfC: publish WD of Streams API; deadline Nov 3
- Re: CfC: publish WD of Streams API; deadline Nov 3
Friday, 1 November 2013
- [Manifest] use cases, was Re: [coord] Is there still a need for WebApps + SysApps meeting at TPAC?
- [Bug 15418] sort out HTTP auth
- Re: UNS: Re: [coord] Re: Request for Inter-Group Coordination at TPAC
- Re: [coord] Re: Request for Inter-Group Coordination at TPAC
- [Bug 23704] New: Define username/password better
- RE: [coord] Is there still a need for WebApps + SysApps meeting at TPAC?
- [Bug 23564] IDL for open() doesn't match implementation reality
- Re: [coord] Re: Request for Inter-Group Coordination at TPAC
- [coord] IndieUI WG Request for Inter-Group Coordination at TPAC
- Re: CfC: publish WD of Streams API; deadline Nov 3
- Re: [coord] Is there still a need for WebApps + SysApps meeting at TPAC?
- Re: CfC: publish WD of Streams API; deadline Nov 3
- [Bug 23697] New: KeyboardEventInit in UI Events doesn't include keyCode/charCode/which but in D3E, it includes them
- RE: [coord] Is there still a need for WebApps + SysApps meeting at TPAC?
- Re: CfC: publish WD of Streams API; deadline Nov 3
- RE: CfC: publish WD of Streams API; deadline Nov 3
- Re: CfC: publish WD of Streams API; deadline Nov 3
- RE: publish WD of Streams API; deadline Nov 3
- Re: Splitting Stream into InputStream and OutputStream (was Re: CfC: publish WD of Streams API; deadline Nov 3)
- Re: publish WD of Streams API; deadline Nov 3
- [Bug 23431] File API should say what to do with the query string in blob: URLs
Thursday, 31 October 2013
- [Bug 23310] bugs in WebIDL fragments
- [Bug 23416] Introduce new concept of neutered
- [Bug 23431] File API should say what to do with the query string in blob: URLs
- [widgets] Widget Interface is a W3C Recommendation
- RfC: LCWD of Pointer Lock; deadline November 28
- [Bug 23451] Error Attribute Setting and Error Event Firing Currently Have Backwards Order
- [Bug 23319] 第6.4.1.节,多了个右括号
- Re: [FileAPI]
- Re: [coord] Is there still a need for WebApps + SysApps meeting at TPAC?
- Re: [coord] Is there still a need for WebApps + SysApps meeting at TPAC?
- RE: [coord] Is there still a need for WebApps + SysApps meeting at TPAC?
- Re: [coord] Is there still a need for WebApps + SysApps meeting at TPAC?
- Re: [FileAPI]
- [coord] Is there still a need for WebApps + SysApps meeting at TPAC?
- Re: publish WD of Streams API; deadline Nov 3
- Re: Splitting Stream into InputStream and OutputStream (was Re: CfC: publish WD of Streams API; deadline Nov 3)
- RE: Defining generic Stream than considering only bytes (Re: CfC: publish WD of Streams API; deadline Nov 3)
- Defining generic Stream than considering only bytes (Re: CfC: publish WD of Streams API; deadline Nov 3)
- Splitting Stream into InputStream and OutputStream (was Re: CfC: publish WD of Streams API; deadline Nov 3)
- Re: CfC: publish WD of Streams API; deadline Nov 3
- Re: Polished FileSystem API proposal
- Re: Polished FileSystem API proposal
- Re: publish WD of Streams API; deadline Nov 3
- [Bug 23479] File Constructor and Blob Constructor should have same signature
Wednesday, 30 October 2013
- Re: Shadow DOM and Fallback contents for images
- Re: Shadow DOM and Fallback contents for images
- Re: CfC: publish WD of Streams API; deadline Nov 3
- Re: FYI: Resource Priorities and Beacon API
- RE: publish WD of Streams API; deadline Nov 3
- Re: Polished FileSystem API proposal
- FYI: Resource Priorities and Beacon API
- Re: Polished FileSystem API proposal
- [push-api]: Push API Patent Advisory Group (PAG) Recommends Continuing work on Push API Spec
- [xhr][xhr-1] status and plans
- Re: Overlap between StreamReader and FileReader
- Re: Overlap between StreamReader and FileReader
- Re: Polished FileSystem API proposal
- Re: Shadow DOM and Fallback contents for images
- Re: Polished FileSystem API proposal
Tuesday, 29 October 2013
- Re: Polished FileSystem API proposal
- CfC: publish new WD of Quota Management API; deadline November 3
- Re: CfC: publish WD of Streams API; deadline Nov 3
- Re: [webcomponents]: Allowing text children of ShadowRoot is a bad time
- Re: [webcomponents]: Allowing text children of ShadowRoot is a bad time
Monday, 28 October 2013
- Re: [webcomponents]: Allowing text children of ShadowRoot is a bad time
- Re: [webcomponents]: Allowing text children of ShadowRoot is a bad time
- Re: Polished FileSystem API proposal
- [Bug 23072] Interaction with DeviceOrientation/Motion
- [Bug 23072] Interaction with DeviceOrientation/Motion
- CfC: publish WD of Streams API; deadline Nov 3
- [Bug 23653] New: Advice on CORS and caches
Sunday, 27 October 2013
- Re: [screen-orientation] Seeking status and plans
- Re: [screen-orientation] Seeking status and plans
- Re: [screen-orientation] Seeking status and plans
Saturday, 26 October 2013
Friday, 25 October 2013
- [Bug 14664] Defining CORS headers
- [Bug 14663] Advice on CORS and caches
- [Bug 14664] Defining CORS headers
- [Bug 14663] Advice on CORS and caches
- [Bug 23632] New: Define/reference Content-Type parsing
- [admin] RfC: Updates of the Technical Reports process; deadline November 27
- [admin] RfC: Updates of the Technical Reports process; deadline November 27
- Re: [screen-orientation] Seeking status and plans
Thursday, 24 October 2013
- Re: [webcomponents]: Allowing text children of ShadowRoot is a bad time
- Re: [webcomponents]: Allowing text children of ShadowRoot is a bad time
- RfC: LCWD of Custom Elements; deadline November 21
- Re: [webcomponents] Cross origin HTML imports
- Re: [webcomponents] Cross origin HTML imports
- Re: [webcomponents] Cross origin HTML imports
Wednesday, 23 October 2013
- Re: [FileAPI]
- [FileAPI]
- [Bug 21111] response property should return incremental data for ArrayBuffer and Blob
- Re: Overlap between StreamReader and FileReader
- [Bug 23259] Expose ticks in wheel events
- Re: [webcomponents] Cross origin HTML imports
- Re: [webcomponents] Cross origin HTML imports
- CfC: publish new WD of UI Events; deadline October 30
- CfC: publish new WD of DOM Events Level 3
Tuesday, 22 October 2013
Wednesday, 23 October 2013
- [Bug 23601] New: Define a variable to replace "with prejudice"
- Request for publication: DOM L3 Events & UI Events
Tuesday, 22 October 2013
Monday, 21 October 2013
- [Bug 21083] Proposal key names for Android
- [Bug 23576] Clarify what to do when received null value subprotocol in reply to non-empty subprotocol
- CfC: publish LCWD of Pointer Lock; deadline October 28
- Re: Missing Features: Stream Control
- Re: Overlap between StreamReader and FileReader
- Re: Missing Features: Stream Control
- Re: Simple API proposal for writing file in local file system
- [Bug 23576] New: Clarify what to do when received null value subprotocol in reply to non-empty subprotocol
- [Bug 23575] New: The paragraph about patent policy is duplicated.
Sunday, 20 October 2013
Saturday, 19 October 2013
- Re: Shadow DOM and Fallback contents for images
- Re: Simple API proposal for writing file in local file system
Friday, 18 October 2013
- Re: Missing Features: Stream Control
- Re: [webcomponents] HTML Imports
- Re: [webcomponents] HTML Imports
- Re: [webcomponents] HTML Imports
- Re: Simple API proposal for writing file in local file system
- [Bug 23564] New: IDL for open() doesn't match implementation reality
- Re: Simple API proposal for writing file in local file system
- Re: Missing Features: Stream Control
- Re: Missing Features: Stream Control
- Re: Missing Features: Stream Control
- Re: Missing Features: Stream Control
- Re: Simple API proposal for writing file in local file system
- Re: Missing Features: Stream Control
- Re: Missing Features: Stream Control
- Simple API proposal for writing file in local file system
- Re: Sync API for workers
- Re: Shadow DOM and Fallback contents for images
- Re: Shadow DOM and Fallback contents for images
- Re: Shadow DOM and Fallback contents for images
- Re: Shadow DOM and Fallback contents for images
Thursday, 17 October 2013
- Re: Shadow DOM and Fallback contents for images
- RE: Shadow DOM and Fallback contents for images
- Re: Shadow DOM and Fallback contents for images
- Re: Shadow DOM and Fallback contents for images
- Reminder: RfC: LCWD of File API; deadline October 24
- Re: [clipboard] Add RTF to the "mandatory data types" list?
- [clipboard] Add RTF to the "mandatory data types" list?
- Re: Shadow DOM and Fallback contents for images
- Re: Shadow DOM and Fallback contents for images
- Re: Shadow DOM and Fallback contents for images
- Re: Shadow DOM and Fallback contents for images
- Re: [clipboard-apis] Seeking status and plans
- Re: Shadow DOM and Fallback contents for images
- Re: Shadow DOM and Fallback contents for images
- Re: Shadow DOM and Fallback contents for images
Wednesday, 16 October 2013
Tuesday, 15 October 2013
- Re: [gamepad] Seeking status and plans
- Re: Shadow DOM and Fallback contents for images
- Re: [gamepad] Seeking status and plans
- Re: [gamepad] Seeking status and plans
- Re: [gamepad] Seeking status and plans
- Re: Shadow DOM and Fallback contents for images
Monday, 14 October 2013
- Re: [gamepad] Seeking status and plans
- CfC: publish LCWD of Custom Elements; deadline October 21
- Re: Sync API for workers
- Re: Sync API for workers
- Re: Sync API for workers
- Re: Sync API for workers
- Re: Sync API for workers
- Re: Sync API for workers
- Re: Sync API for workers
- Re: Shadow DOM and Fallback contents for images
- Re: Shadow DOM and Fallback contents for images
- Re: Sync API for workers
- Re: Sync API for workers
- Re: Sync API for workers
- Re: Sync API for workers
Sunday, 13 October 2013
- Re: Sync API for workers
- Re: Sync API for workers
- Re: Sync API for workers
- Re: Sync API for workers
- Re: Sync API for workers
- Re: Sync API for workers
- [Bug 23487] New: Actually define going fullscreen
- Re: Sync API for workers
- Re: Sync API for workers
- Re: Sync API for workers
- Re: Sync API for workers
- Re: Sync API for workers
- Re: Sync API for workers
- Re: Sync API for workers
Saturday, 12 October 2013
- RE: [streams-api] Seeking status and plans
- Re: Sync API for workers
- Re: Sync API for workers
- Re: Sync API for workers
- Re: Shadow DOM and Fallback contents for images
- Re: Shadow DOM and Fallback contents for images
- Re: [widgetsapi] reference to WebIDL
- Re: Sync API for workers
- Re: Sync API for workers
Friday, 11 October 2013
- Re: Sync API for workers
- Re: Sync API for workers
- [Bug 21388] handling of analog vs. digital buttons
- Re: [widgetsapi] reference to WebIDL
- Re: [IndexedDB] blocked event should have default operation to close the connection
- Re: [streams-api] Seeking status and plans
- Re: [streams-api] Seeking status and plans
- Re: [webcomponents]: Allowing text children of ShadowRoot is a bad time
Thursday, 10 October 2013
- Re: [webcomponents]: Allowing text children of ShadowRoot is a bad time
- Re: [gamepad] Seeking status and plans
- Re: Problem in the Entry interface description (filesystem)
- Problem in the Entry interface description (filesystem)
- RE: [streams-api] Seeking status and plans
- Re: [streams-api] Seeking status and plans
- [Bug 23479] New: File Constructor and Blob Constructor should have same signature
- Re: [streams-api] Seeking status and plans
- [Bug 23422] Adding a method to deliver editing-related events to a DOM element
- Re: [webcomponents]: Allowing text children of ShadowRoot is a bad time
- Re: [webcomponents] HTML Imports
Wednesday, 9 October 2013
- Re: [webcomponents]: Allowing text children of ShadowRoot is a bad time
- Re: [webcomponents]: Allowing text children of ShadowRoot is a bad time
- Re: [IndexedDB] blocked event should have default operation to close the connection
- Re: [webcomponents] HTML Imports
- Re: [IndexedDB] blocked event should have default operation to close the connection
- [IndexedDB] blocked event should have default operation to close the connection
- Re: [ime-api] Seeking status and plans
- Re: [webcomponents]: Allowing text children of ShadowRoot is a bad time
- Re: [ime-api] Seeking status and plans
Tuesday, 8 October 2013
- Re: [clipboard] typo in WebIDL
- [webcomponents]: Allowing text children of ShadowRoot is a bad time
- Re: [clipboard] typo in WebIDL
- Re: [clipboard] typo in WebIDL
- Re: [clipboard] typo in WebIDL
- Re: [clipboard] typo in WebIDL
- Re: [clipboard] typo in WebIDL
- [IndexedDB] add "dataLossMessage" field to upgradeneeded event
Monday, 7 October 2013
- Re: [XHR] Content-Length header for data: URLs
- Re: Shadow DOM and Fallback contents for images
- Re: [XHR] Content-Length header for data: URLs
- Re: [webcomponents] HTML Imports
- Re: [FileAPI] Questions on using Blobs for img src and a href
- [Bug 23451] New: Error Attribute Setting and Error Event Firing Currently Have Backwards Order
- [Bug 23450] New: Add Specification Note Describing "Save As" Behavior for File Objects
- Re: [admin] Recommended way to mark bugs as `next level`? [Was: Re: [custom-elements] Seeking pre-LC comments for Custom Elements; deadline Oct 13
- Re: Shadow DOM and Fallback contents for images
- Re: [webcomponents] HTML Imports
Friday, 4 October 2013
Sunday, 6 October 2013
- Re: [webcomponents] HTML Imports
- Re: [webcomponents] HTML Imports
- Re: [webcomponents] HTML Imports
- Re: [webcomponents] HTML Imports
- [webcomponents] HTML Imports
Saturday, 5 October 2013
- Re: [admin] Recommended way to mark bugs as `next level`? [Was: Re: [custom-elements] Seeking pre-LC comments for Custom Elements; deadline Oct 13
- Re: [admin] Recommended way to mark bugs as `next level`? [Was: Re: [custom-elements] Seeking pre-LC comments for Custom Elements; deadline Oct 13
- Re: [admin] Recommended way to mark bugs as `next level`? [Was: Re: [custom-elements] Seeking pre-LC comments for Custom Elements; deadline Oct 13
- [admin] Recommended way to mark bugs as `next level`? [Was: Re: [custom-elements] Seeking pre-LC comments for Custom Elements; deadline Oct 13
- Re: [XHR] Event firing order. XMLHttpRequestUpload then XMLHttpRequest or reverse
- Re: [custom-elements] Seeking pre-LC comments for HTML Templates; deadline June 1
- Re: [custom-elements] Seeking pre-LC comments for Custom Elements; deadline October 13
- Re: [custom-elements] Seeking pre-LC comments for HTML Templates; deadline June 1
- [FileAPI] Question on order of calling onerror vs. setting error attribute
- Re: [custom-elements] Seeking pre-LC comments for HTML Templates; deadline October 13
Friday, 4 October 2013
- Re: [FileAPI] Questions on using Blobs for img src and a href
- [custom-elements] Seeking pre-LC comments for HTML Templates; deadline June 1
- Re: [FileAPI] Questions on using Blobs for img src and a href
- Re: [FileAPI] Questions on using Blobs for img src and a href
- [Bug 19297] May user agents apply additional restrictions on entering pointer lock?
- Re: [XHR] Event firing order. XMLHttpRequestUpload then XMLHttpRequest or reverse
- Re: Testing Pointer Lock
- Re: [FileAPI] Questions on using Blobs for img src and a href
- Re: [FileAPI] Questions on using Blobs for img src and a href
- Re: [FileAPI] Questions on using Blobs for img src and a href
- CfC: publish Selectors API Level 2 as WG Note; deadline October 11
- Re: [XHR] Event firing order. XMLHttpRequestUpload then XMLHttpRequest or reverse
- Re: Reminder of WebApps' off-list topic policy [Was: ...]
- Re: [XHR] Event firing order. XMLHttpRequestUpload then XMLHttpRequest or reverse
- Re: Testing Pointer Lock
- Re: Overlap between StreamReader and FileReader
Thursday, 3 October 2013
Friday, 4 October 2013
Thursday, 3 October 2013
- Testing Pointer Lock
- Re: [selectors-api2] Seeking status and plans
- RE: [uievents] Seeking status and plans
- RE: [D3E] Seeking status and plan
- Re: [pointerlock] Seeking status and plans
- Re: [pointerlock] Seeking status and plans
- Re: [selectors-api2] Seeking status and plans
- [Bug 23431] New: File API should say what to do with the query string in blob: URLs
- Re: [quota-api] Seeking status and plans
- Re: [admin] DOM4 is now a deliverable of the HTMLWG
- [admin] Oct 28 is deadline to start a CfC to publish before TPAC 2013
- [admin] DOM4 is now a deliverable of the HTMLWG
- Re: Overlap between StreamReader and FileReader
- Re: [XHR] Event firing order. XMLHttpRequestUpload then XMLHttpRequest or reverse
- Re: [quota-api] Seeking status and plans
Wednesday, 2 October 2013
- Reminder of WebApps' off-list topic policy [Was: ...]
- Re: [selectors-api2] Seeking status and plans
- Re: [webcomponents] Seeking status and plans
- Re: [file-{writer,system}-api] Seeking status and plans
- Re: [webcomponents] Seeking status and plans
- Re: [XHR] Content-Length header for data: URLs
- Re: [xhr] Seeking status and plans
- Re: [fullscreen] Seeking status and plans
- [clipboard-apis] Seeking status and plans
- [xhr] Seeking status and plans
- [gamepad] Seeking status and plans
- [file-{writer,system}-api] Seeking status and plans
- [workers] Seeking Interop & Test Suite status and plans
- [IndexedDB] Seeking Interop & Test Suite status and plans
- [pointerlock] Seeking status and plans
- [push-api] Seeking status and plans
- [D3E] Seeking status and plan
- [ime-api] Seeking status and plans
- [fullscreen] Seeking status and plans
- [uievents] Seeking status and plans
- [progress-events] Seeking Interop & Test Suite status and plans
- [selectors-api2] Seeking status and plans
- [screen-orientation] Seeking status and plans
- [quota-api] Seeking status and plans
- [webcomponents] Seeking status and plans
- [eventsource] Seeking Interop & Test Suite status and plans
- [websockets] Seeking Interop & Test Suite status and plans
- [webmessaging] Seeking Interop & Test Suite status and plans
- [DOM-Parsing] Seeking status and plans
- [streams-api] Seeking status and plans
- [admin] Spec status and plans ...
- Re: [webcomponents]: Shadow trees styling issue
- Re: blob URIs and the query string
- [Bug 23422] New: Adding a method to deliver editing-related events to a DOM element
- Re: blob URIs and the query string
- Re: blob URIs and the query string
- Re: blob URIs and the query string
- Re: blob URIs and the query string
- Re: blob URIs and the query string
- blob URIs and the query string
- [Bug 23416] New: Introduce new concept of neutered
- [DOM3Events] telco minutes published
Tuesday, 1 October 2013
- Re: [custom-elements] Rationale behind 5.2 (copying properties of the last value to a new prototype)
- Re: Regarding: Making the W3C Web SQL Database Specification Active
- Re: Regarding: Making the W3C Web SQL Database Specification Active
- September 2013 edition of Standards for Web Applications on Mobile: current state and roadmap
- [custom-elements] Rationale behind 5.2 (copying properties of the last value to a new prototype)