Friday, 30 September 2011
- IndexedDB: spec nit - IDBFactory.cmp returns int?
- Re: [XHR2] responseText for text/html before the encoding has stabilized
- Re: Mutation Observers: a replacement for DOM Mutation Events
- Re: [XHR2] responseText for text/html before the encoding has stabilized
- [Bug 14347] New: Consider "createContextualFragment in detached contexts" thread
- Re: [XHR2] responseText for text/html before the encoding has stabilized
- Re: [XHR2] responseText for text/html before the encoding has stabilized
- Re: [FileAPI] FileReader.abort() and File[Saver|Writer].abort have different behaviors
- Re: [XHR2] responseText for text/html before the encoding has stabilized
- Re: [FileAPI] FileReader.abort() and File[Saver|Writer].abort have different behaviors
- Re: [XHR2] responseText for text/html before the encoding has stabilized
- Re: [XHR2] responseText for text/html before the encoding has stabilized
- Re: [XHR2] responseText for text/html before the encoding has stabilized
- Re: [XHR2] responseText for text/html before the encoding has stabilized
- Re: [XHR2] responseText for text/html before the encoding has stabilized
- Re: Biblio references and authors Re: RfC: LCWD of Web Socket API; comment deadline October 21
- Re: Biblio references and authors Re: RfC: LCWD of Web Socket API; comment deadline October 21
- Re: Biblio references and authors Re: RfC: LCWD of Web Socket API; comment deadline October 21
- Biblio references and authors Re: RfC: LCWD of Web Socket API; comment deadline October 21
- Re: RfC: LCWD of Web Socket API; comment deadline October 21
- Re: [indexeddb] New WebIDL Exception Model for IndexedDB
- Re: [File API] Issue 182 about OperationNowAllowed
- Re: [XHR2] Avoiding charset dependencies on user settings
- Re: Behavior Attachment Redux, was Re: HTML element content models vs. components
- Re: Behavior Attachment Redux, was Re: HTML element content models vs. components
- Re: Behavior Attachment Redux, was Re: HTML element content models vs. components
- Re: Behavior Attachment Redux, was Re: HTML element content models vs. components
- Re: Behavior Attachment Redux, was Re: HTML element content models vs. components
- Re: Behavior Attachment Redux, was Re: HTML element content models vs. components
- Re: Behavior Attachment Redux, was Re: HTML element content models vs. components
Thursday, 29 September 2011
- [File API] Issue 182 about OperationNowAllowed
- RE: [indexeddb] New WebIDL Exception Model for IndexedDB
- Re: Behavior Attachment Redux, was Re: HTML element content models vs. components
- Re: [FileAPI] FileReader.abort() and File[Saver|Writer].abort have different behaviors
- Re: [XHR2] Avoiding charset dependencies on user settings
- Re: HTML element content models vs. components
- Re: [FileAPI] FileReader.abort() and File[Saver|Writer].abort have different behaviors
- Re: Custom tags over wire, was Re: HTMLElement.register--giving components tag names
- Re: Adding Web Intents to the Webapps WG deliverables
- Re: [File API] opaque string
- Re: Behavior Attachment Redux, was Re: HTML element content models vs. components
- Re: [File API] opaque string
- RfC: LCWD of Web Socket API; comment deadline October 21
- Re: Mutation Observers: a replacement for DOM Mutation Events
- [XHR] Progress Events and open() / send() / abort()
- [XHR2] responseText for text/html before the encoding has stabilized
- [Bug 14331] New: Hello! Why tasks that are queued by EventSource doesnot removed from task queues with "close" method? Thanks!
- Re: Adding Web Intents to the Webapps WG deliverables
Wednesday, 28 September 2011
Thursday, 29 September 2011
- Re: [indexeddb] New WebIDL Exception Model for IndexedDB
- Re: [XHR2] Avoiding charset dependencies on user settings
- Re: RfC: Last Call Working Draft of Web IDL; deadline October 18
- Dynamic behavior attachment does not work, subtyping elements could work (Was: Re: Behavior Attachment Redux, was Re: HTML element content models vs. components)
- Re: Behavior Attachment Redux, was Re: HTML element content models vs. components
- Re: Behavior Attachment Redux, was Re: HTML element content models vs. components
- Re: [IndexedDB] New version API checked in
- Re: [XHR2] Avoiding charset dependencies on user settings
Wednesday, 28 September 2011
- Re: Behavior Attachment Redux, was Re: HTML element content models vs. components
- Re: Behavior Attachment Redux, was Re: HTML element content models vs. components
- Re: [File API] opaque string
- Re: Behavior Attachment Redux, was Re: HTML element content models vs. components
- Re: Behavior Attachment Redux, was Re: HTML element content models vs. components
- RE: [IndexedDB] New version API checked in
- Re: Behavior Attachment Redux, was Re: HTML element content models vs. components
- Re: The algorithm to determine encoding for FileReader.readAsText() doesn't account for predefined content types
- Re: Behavior Attachment Redux, was Re: HTML element content models vs. components
- Re: [XHR2] Avoiding charset dependencies on user settings
- Re: Behavior Attachment Redux, was Re: HTML element content models vs. components
- Re: Behavior Attachment Redux, was Re: HTML element content models vs. components
- Re: Behavior Attachment Redux, was Re: HTML element content models vs. components
- Re: Behavior Attachment Redux, was Re: HTML element content models vs. components
- Re: Behavior Attachment Redux, was Re: HTML element content models vs. components
- Re: Behavior Attachment Redux, was Re: HTML element content models vs. components
- Re: HTML element content models vs. components
- Re: Behavior Attachment Redux, was Re: HTML element content models vs. components
- Re: Behavior Attachment Redux, was Re: HTML element content models vs. components
- Re: HTML element content models vs. components
- [Bug 14329] New: I believe the possible DoS attack "message flooding" should be addressed i.e. a rogue domain uses "postMessage" to crash an implementation, crash another window etc. Jean-Lou Dupont html5@jldupont.com
- Re: Behavior Attachment Redux, was Re: HTML element content models vs. components
- Re: HTML element content models vs. components
- Behavior Attachment Redux, was Re: HTML element content models vs. components
- Re: Web Components use cases, was Re: Notes from a component model pow-wow
- Re: Mutation Observers: a replacement for DOM Mutation Events
- Re: HTML element content models vs. components
- Re: Mutation Observers: a replacement for DOM Mutation Events
- [Bug 14296] sorry, does this work
- [workers] Back to LC? [Was: RfC: LCWD of Web Workers; deadline September 27]
- [webstorage] Back to LC? [Was] RfC: LCWD of Web Storage; deadline September 27
- Re: [XHR2] Avoiding charset dependencies on user settings
- Re: HTML element content models vs. components
- Re: HTML element content models vs. components
- [Bug 14323] New: This API could easily be used by XForms implementations if protocols such as "localstorage://" could also be specified. Thanks! Alain Couthures agenceXML Invited Expert in Forms Work Group
- Re: HTML element content models vs. components
- HTML element content models vs. components
- Re: [XHR2] Avoiding charset dependencies on user settings
- Re: Web Components use cases, was Re: Notes from a component model pow-wow
- [Bug 14322] New: Update URL of the WebSocket protocol
- Re: [XHR2] Avoiding charset dependencies on user settings
- Re: [IndexedDB] New version API checked in
Tuesday, 27 September 2011
- Re: Publishing specs before TPAC; Oct 14 is last day to start a CfC
- [Bug 14318] New: Importance of the upgradeneeded event should be more explicit
- RE: [IndexedDB] New version API checked in
- Re: Storage Quota API
- Re: Storage Quota API
- Re: Publishing specs before TPAC; Oct 14 is last day to start a CfC
- Re: Notes from a component model pow-wow
- Re: Mutation Observers: a replacement for DOM Mutation Events
- RfC: Last Call Working Draft of Web IDL; deadline October 18
- Re: [editing] Using public-webapps for editing discussion
- [Bug 14297] ja sam manijak iz gimnazijskog parka, veÄ danima sakriven ja gledam te iz mraka
- Re: Mouse Lock
- Re: Storage Quota API
- Should the shadow host element be rendered? (Was: Re: Notes from a component model pow-wow)
- Re: Storage Quota API
- Re: Mutation Observers: a replacement for DOM Mutation Events
- Re: Storage Quota API
- [Bug 13410] XML serialisation incompletely defined.
- Re: [indexeddb] New WebIDL Exception Model for IndexedDB
- RE: [indexeddb] New WebIDL Exception Model for IndexedDB
- Re: Storage Quota API
- Re: Storage Quota API
- Re: Storage Quota API
Monday, 26 September 2011
- Re: Storage Quota API
- Re: Storage Quota API
- Re: Storage Quota API
- [Bug 14297] New: ja sam manijak iz gimnazijskog parka, veÄ danima sakriven ja gledam te iz mraka
- Storage Quota API
- Publishing specs before TPAC; Oct 14 is last day to start a CfC
- Re: Mutation Observers: a replacement for DOM Mutation Events
- Re: [widgets] Killing file:// of evil (widget URI ready for pub)
- Re: CfI: Progress Events is a W3C Candidate Recommendation
- Re: Mutation Observers: a replacement for DOM Mutation Events
- Re: [FileAPI] BlobBuilder.append("native")
- Re: [FileAPI, common] UTF-16 to UTF-8 conversion
- Re: Mutation Observers: a replacement for DOM Mutation Events
- Re: Mutation Observers: a replacement for DOM Mutation Events
- CfI: Progress Events is a W3C Candidate Recommendation
- Re: Mutation Observers: a replacement for DOM Mutation Events
- [Bug 14296] sorry, does this work
- [Bug 14296] New: sorry, does this work
- Re: Mutation Observers: a replacement for DOM Mutation Events
- Re: XBL2 is dead.
- Re: [widgets] Killing file:// of evil (widget URI ready for pub)
- Re: [widgets] Killing file:// of evil (widget URI ready for pub)
- Re: [XHR2] Avoiding charset dependencies on user settings
- Re: [widgets] Killing file:// of evil (widget URI ready for pub)
- Re: [widgets] Killing file:// of evil (widget URI ready for pub)
- Re: [widgets] Killing file:// of evil (widget URI ready for pub)
- [Bug 14288] New: document.documentElement.insertAdjacentHTML specs WebKit behavior instead of IE behavior
- Re: [XHR2] Avoiding charset dependencies on user settings
- Re: [XHR2] Avoiding charset dependencies on user settings
- Re: [indexeddb] New WebIDL Exception Model for IndexedDB
- Re: Mutation Observers: a replacement for DOM Mutation Events
- Re: [indexeddb] New WebIDL Exception Model for IndexedDB
- Re: XBL2 is dead.
- Re: [cors] Ability to read Access-Control-Expose-Headers
Sunday, 25 September 2011
- Re: Adding Web Intents to the Webapps WG deliverables
- Re: [XHR2] Blobs, names and FormData
- Re: Adding Web Intents to the Webapps WG deliverables
Saturday, 24 September 2011
Friday, 23 September 2011
Sunday, 25 September 2011
Saturday, 24 September 2011
Friday, 23 September 2011
- Re: Mutation Observers: a replacement for DOM Mutation Events
- Re: Mutation Observers: a replacement for DOM Mutation Events
- Re: Mutation Observers: a replacement for DOM Mutation Events
- Re: Adding Web Intents to the Webapps WG deliverables
- Re: Adding Web Intents to the Webapps WG deliverables
- Re: Adding Web Intents to the Webapps WG deliverables
- Mutation Observers: a replacement for DOM Mutation Events
- Re: Adding Web Intents to the Webapps WG deliverables
- Re: [editing] Using public-webapps for editing discussion
- Re: Adding Web Intents to the Webapps WG deliverables
- Re: Adding Web Intents to the Webapps WG deliverables
- Re: [editing] Using public-webapps for editing discussion
- Re: Adding Web Intents to the Webapps WG deliverables
- Re: [XHR2] Avoiding charset dependencies on user settings
- [Bug 14273] regerhsh ezer ge
- [Bug 14273] New: regerhsh ezer ge
- [Bug 14272] regerhsh ezer ge
- [Bug 14272] New: regerhsh ezer ge
- [Bug 14269] fg jdrt drt
- [Bug 14270] fg jdrt drt
- [Bug 14271] regerhsh ezer ge
- [Bug 14271] New: regerhsh ezer ge
- [Bug 14270] New: fg jdrt drt
- [Bug 14269] New: fg jdrt drt
- Re: [widgets] Killing file:// of evil (widget URI ready for pub)
- Re: [widgets] Killing file:// of evil (widget URI ready for pub)
- Re: [widgets] Killing file:// of evil (widget URI ready for pub)
- Re: [widgets] Killing file:// of evil (widget URI ready for pub)
- Re: [FileAPI] BlobBuilder.append("native")
- Re: [FileAPI] BlobBuilder.append("native")
- Re: [XHR2] Avoiding charset dependencies on user settings
- Re: [widgets] Killing file:// of evil (widget URI ready for pub)
- Re: [FileAPI] BlobBuilder.append("native")
- Re: [FileAPI, common] UTF-16 to UTF-8 conversion
- Re: [XHR2] Avoiding charset dependencies on user settings
- Re: Adding Web Intents to the Webapps WG deliverables
- Re: Adding Web Intents to the Webapps WG deliverables
Thursday, 22 September 2011
- [FileAPI] BlobBuilder.append("native")
- Re: Adding Web Intents to the Webapps WG deliverables
- [FileAPI, common] UTF-16 to UTF-8 conversion
- [widgets] Killing file:// of evil (widget URI ready for pub)
- [indexeddb] New WebIDL Exception Model for IndexedDB
- Re: Adding Web Intents to the Webapps WG deliverables
- Re: [editing] Using public-webapps for editing discussion
- Re: Adding Web Intents to the Webapps WG deliverables
- [Bug 14254] New: insertText has to handle things like \r, \0, etc. sanely
- [Bug 14253] New: Add new fontSize variant that accepts pt/px/etc. instead of legacy values
- [Bug 14251] Stop allowing non-numeric values for fontSize
- [Bug 14119] Strip collapsed whitespace on insertText
- [Bug 14252] New: Put DOM Range to rest
- [Bug 14251] New: Stop allowing non-numeric values for fontSize
- Re: [XHR2] Avoiding charset dependencies on user settings
- [Bug 14250] New: Conformance tests need to test that the selection is correct
- [Bug 14249] New: Define some type of selection normalization
- [Bug 14248] New: Merge selection spec into editing spec
- Re: [editing] Using public-webapps for editing discussion
- Important: TPAC Registration
- Re: [editing] Using public-webapps for editing discussion
- [Bug 14247] New: Add manual conformance tests
- Draft Proposal for Streams API
- XBL2 is dead.
- Re: [editing] Using public-webapps for editing discussion
- Web Components use cases, was Re: Notes from a component model pow-wow
- Re: [editing] Using public-webapps for editing discussion
- Deconstructing Intents was, Re: Adding Web Intents to the Webapps WG deliverables
- Re: [FileAPI] FileReader.abort() and File[Saver|Writer].abort have different behaviors
- [XHR2] Avoiding charset dependencies on user settings
- Re: Adding Web Intents to the Webapps WG deliverables
- Re: [editing] Using public-webapps for editing discussion
- Re: [FileAPI] FileReader.abort() and File[Saver|Writer].abort have different behaviors
- Re: [FileAPI] FileReader.abort() and File[Saver|Writer].abort have different behaviors
- Re: [indexeddb] Updates to the Event Constructor to match DOM 4
- Re: [IndexedDB] New version API checked in
- Re: [IndexedDB] New version API checked in
- Re: [FileAPI] FileReader.abort() and File[Saver|Writer].abort have different behaviors
- Re: [indexeddb] Updates to the Event Constructor to match DOM 4
- RE: [indexeddb] Updates to the Event Constructor to match DOM 4
- Re: [FileAPI] FileReader.abort() and File[Saver|Writer].abort have different behaviors
- Re: [FileAPI] FileReader.abort() and File[Saver|Writer].abort have different behaviors
- Re: [FileAPI] FileReader.abort() and File[Saver|Writer].abort have different behaviors
- Re: [FileAPI] FileReader.abort() and File[Saver|Writer].abort have different behaviors
Wednesday, 21 September 2011
- Re: [FileAPI] FileReader.abort() and File[Saver|Writer].abort have different behaviors
- Re: [FileAPI] FileReader.abort() and File[Saver|Writer].abort have different behaviors
- Re: [FileAPI] FileReader.abort() and File[Saver|Writer].abort have different behaviors
- Re: [FileAPI] FileReader.abort() and File[Saver|Writer].abort have different behaviors
- Re: [FileAPI] FileReader.abort() and File[Saver|Writer].abort have different behaviors
- Re: [FileAPI] FileReader.abort() and File[Saver|Writer].abort have different behaviors
- Re: [FileAPI] FileReader.abort() and File[Saver|Writer].abort have different behaviors
- Re: [indexeddb] Updates to the Event Constructor to match DOM 4
- Re: [FileAPI] FileReader.abort() and File[Saver|Writer].abort have different behaviors
- Re: [FileAPI] FileReader.abort() and File[Saver|Writer].abort have different behaviors
- Re: IndexedDB: API for enumerating databases within an origin
- Re: [indexeddb] Updates to the Event Constructor to match DOM 4
- [Bug 14231] Force values of runs of consecutive nodes, not individual nodes
- [Bug 13811] Handle collapsed whitespace better
- [indexeddb] Updates to the Event Constructor to match DOM 4
- [Bug 13957] Remove special handling for WebKit class on blockquote
- Re: [FileAPI] FileReader.abort() and File[Saver|Writer].abort have different behaviors
- [Bug 13996] Don't wrap invisible nodes when doing inline styling
- [Bug 14231] New: Force values of runs of consecutive nodes, not individual nodes
- IndexedDB: API for enumerating databases within an origin
- [Bug 14062] Preserve state/value overrides when running commands like indent or insertorderedlist
- [Bug 14066] Work around inconsistency in browser handling of align=* on random elements
- Re: Adding Web Intents to the Webapps WG deliverables
- Re: Notes from a component model pow-wow
- Re: Notes from a component model pow-wow
- Re: Notes from a component model pow-wow
- Re: Notes from a component model pow-wow
- Re: Notes from a component model pow-wow
- Re: Notes from a component model pow-wow
- Re: Adding Web Intents to the Webapps WG deliverables
- Re: [FileAPI] FileReader.abort() and File[Saver|Writer].abort have different behaviors
- Re: [FileAPI] FileReader.abort() and File[Saver|Writer].abort have different behaviors
- Re: [FileAPI] FileReader.abort() and File[Saver|Writer].abort have different behaviors
- Re: [FileAPI] FileReader.abort() and File[Saver|Writer].abort have different behaviors
Tuesday, 20 September 2011
- Notes from a component model pow-wow
- Re: [FileAPI] FileReader.abort() and File[Saver|Writer].abort have different behaviors
- Re: [FileAPI] FileReader.abort() and File[Saver|Writer].abort have different behaviors
- Re: [FileAPI] FileReader.abort() and File[Saver|Writer].abort have different behaviors
- Re: Adding Web Intents to the Webapps WG deliverables
- Re: [FileAPI] FileReader.abort() and File[Saver|Writer].abort have different behaviors
- Re: Adding Web Intents to the Webapps WG deliverables
- Re: Adding Web Intents to the Webapps WG deliverables
- RE: publish a LCWD of Web Socket API; deadline September 27
- Re: Adding Web Intents to the Webapps WG deliverables
- Re: Adding Web Intents to the Webapps WG deliverables
- RE: New tests submitted by Microsoft for WebApps specs
- Re: Adding Web Intents to the Webapps WG deliverables
- Re: Adding Web Intents to the Webapps WG deliverables
- Re: Adding Web Intents to the Webapps WG deliverables
- Re: Adding Web Intents to the Webapps WG deliverables
- Re: Adding Web Intents to the Webapps WG deliverables
- Re: Adding Web Intents to the Webapps WG deliverables
- Re: Adding Web Intents to the Webapps WG deliverables
- Re: [widgets] Proposal to publish Widget Requirements and Widget Landscape docs as Working Group Notes; deadline Sep 23
- Re: Adding Web Intents to the Webapps WG deliverables
- Re: Adding Web Intents to the Webapps WG deliverables
- Re: Adding Web Intents to the Webapps WG deliverables
- Re: Adding Web Intents to the Webapps WG deliverables
- Re: Adding Web Intents to the Webapps WG deliverables
- Re: Adding Web Intents to the Webapps WG deliverables
- Fwd: RfC: LCWD of Web Workers; deadline September 27
- Reminder: RfC: LCWD of Web Storage; deadline September 27
- CfC: publish a LCWD of Web Socket API; deadline September 27
- Re: RfC: Is Web Sockets API ready for LC publication? [Was: Re: [websockets] Getting WebSockets API to Last Call]
- Re: Adding Web Intents to the Webapps WG deliverables
- [Bug 14220] In reply to comment #0) > Every browser that I know of can have two web pages open at once. Those 2 web > pages both have a DOM, they don't share a DOM. Some browsers implement this > as 2 different processes, some as 2 threads. This is where you're m
- Re: [widgets] Proposal to publish Widget Requirements and Widget Landscape docs as Working Group Notes; deadline Sep 23
- Discovery API proposals: call for comments
- Re: New tests submitted by Microsoft for WebApps specs
- Re: Adding Web Intents to the Webapps WG deliverables
Monday, 19 September 2011
Tuesday, 20 September 2011
- Re: Adding Web Intents to the Webapps WG deliverables
- Re: Adding Web Intents to the Webapps WG deliverables
- Re: New tests submitted by Microsoft for WebApps specs
- Adding Web Intents to the Webapps WG deliverables
Monday, 19 September 2011
- [Bug 13777] The WebSocket protocol draft (hybi-10) restricts the value of subprotocols as follows: The elements that comprise this value MUST be non- empty strings with characters in the range U+0021 to U+007E not including separator characters as defined
- Re: [widgets] Proposal to publish Widget Requirements and Widget Landscape docs as Working Group Notes; deadline Sep 23
- [Bug 13938] Explicitly allow UAs to let the user execute commands without author intervention
- [Bug 14063] Get runtest.html working in IE, and preferably Opera
- [Bug 14069] Split up conformance tests into manageable chunks
- Re: [editing] Using public-webapps for editing discussion
- Re: [editing] Using public-webapps for editing discussion
- Re: [editing] Using public-webapps for editing discussion
- Re: [editing] Using public-webapps for editing discussion
- Re: [widgets] Proposal to publish Widget Requirements and Widget Landscape docs as Working Group Notes; deadline Sep 23
- [Bug 14220] New: In reply to comment #0) > Every browser that I know of can have two web pages open at once. Those 2 web > pages both have a DOM, they don't share a DOM. Some browsers implement this > as 2 different processes, some as 2 threads. This is where you're m
- Re: [widgets] Proposal to publish Widget Requirements and Widget Landscape docs as Working Group Notes; deadline Sep 23
- [Bug 14218] New: Check CharData when serializing Text
- Re: Widgets & ApplicationCache (was: Standards for Web applications on mobile devices: August 2011 updates)
- [Bug 14214] New: missing definition of Transferable
- Re: Widgets & ApplicationCache (was: Standards for Web applications on mobile devices: August 2011 updates)
- [Bug 14120] Current spec for EventSource close method doesn't defined behaviour when close called after 'onopen' or 'onmessage'. For example, Google Chrome, closes connection if 'close' called while 'open' event dispatching and Opera doen't close it.
Sunday, 18 September 2011
- [Bug 14201] New: IDBFactory.deleteDatabase text mentions IDBVersionChangeRequest
- [Bug 14200] New: Provide a hook to serialize a Document
- [Bug 14199] New: IDBVersionChangeEvent still uses DOMString for version
- [Bug 13104] Enable keepalive on WebSocket API
Saturday, 17 September 2011
- Re: Widgets & ApplicationCache (was: Standards for Web applications on mobile devices: August 2011 updates)
- Re: IndexedDB: negative zero as keys/values
Friday, 16 September 2011
- IndexedDB: negative zero as keys/values
- Re: [editing] Using public-webapps for editing discussion
- [Bug 14068] Think about what to return for backColor/hiliteColor value if it winds up being fully transparent
- Re: [DOM4] Remove Node.isSameNode
- Re: [editing] Using public-webapps for editing discussion
- Whoa! [Was: Re: [editing] Using public-webapps for editing discussion]
- Re: [editing] Using public-webapps for editing discussion
- Re: [editing] Using public-webapps for editing discussion
- Re: [editing] Using public-webapps for editing discussion
- Re: Widgets & ApplicationCache
- Re: Widgets & ApplicationCache (was: Standards for Web applications on mobile devices: August 2011 updates)
- Re: [DOM4] Remove Node.isSameNode
- Re: Widgets & ApplicationCache (was: Standards for Web applications on mobile devices: August 2011 updates)
- Re: Widgets & ApplicationCache (was: Standards for Web applications on mobile devices: August 2011 updates)
- Re: [widgets] Proposal to publish Widget Requirements and Widget Landscape docs as Working Group Notes; deadline Sep 23
- [widgets] Proposal to publish Widget Requirements and Widget Landscape docs as Working Group Notes; deadline Sep 23
- Widgets & ApplicationCache (was: Standards for Web applications on mobile devices: August 2011 updates)
- [Bug 14180] Call onclose() passing as argument the WS close frame status and status code and reason
- [widgets] Status of Packing, DigSig and view-modes Proposed Recommendations
- [Bug 14180] New: Call onclose() passing as argument the WS close frame status and status code and reason
- Re: [editing] Using public-webapps for editing discussion
Thursday, 15 September 2011
- [Bug 14067] Value for createLink and unlink can be null instead of a string
- [Bug 14067] Value for createLink and unlink can be null instead of a string
- [Bug 14067] Value for createLink and unlink can be null instead of a string
- Re: [editing] Using public-webapps for editing discussion
- Proposal to add Mouse Lock to the Web Events Working Group
- Re: RfC: Is Web Sockets API ready for LC publication? [Was: Re: [websockets] Getting WebSockets API to Last Call]
- DOM4 published ; please use www-dom for related discussions
- Re: CfC: new WD of Clipboard API and Events; deadline April 5
- Re: [DOM4] Remove Node.isSameNode
- Re: [DOM4] Remove Node.isSameNode
- Re: [DOM4] Remove Node.isSameNode
- Re: [editing] Using public-webapps for editing discussion
- Re: [editing] Using public-webapps for editing discussion
Wednesday, 14 September 2011
- Re: [editing] Using public-webapps for editing discussion
- [Bug 14048] Suggestion of change in process for "dispatch the event" in Server-Sent Events
- [Bug 13984] Need a way to object detect which binary formats are supported before connecting
- [Bug 13104] Enable keepalive on WebSocket API
- [Bug 14148] New: shouldn't WorkerLocation also have resolveURL?
- RfC: Is Web Sockets API ready for LC publication? [Was: Re: [websockets] Getting WebSockets API to Last Call]
- Re: RfC: LCWD of Touch Events version 1; deadline October 11
- Re: Joystick support
- RE: New tests submitted by Microsoft for WebApps specs
- New tests submitted by Microsoft for WebApps specs
- cross origin workers [was Re: [workers] Moving the Web Workers spec back to Last Call WD]
Tuesday, 13 September 2011
- Re: [editing] Using public-webapps for editing discussion
- Re: [editing] Using public-webapps for editing discussion
- [editing] Using public-webapps for editing discussion
- [Bug 14144] New: Adding link to resolve the URL
- Re: RfC: LCWD of Touch Events version 1; deadline October 11
- Re: RfC: LCWD of Touch Events version 1; deadline October 11
- RfC: LCWD of Touch Events version 1; deadline October 11
- [Bug 14093] Just to throw out an idea, to allow use of the XML parser, and alert() for debugging, one could implement web workers as simply another open page in the browser, with full access to the DOM, etc, with the ability to communicate to the 'parent' by posting
- [Bug 14116] Regarding a previous post, a browser could launch itself (CreateProcess() on Windows) again and pass say a port number, a URL, and a boolean flag to the spawned child process. The browser could then be modified to examine it's command line- if there are 3
- [Bug 14138] Lastly, to make clear. I am not proposing web workers share the DOM with the main thread. I am proposing the each web worker has it's own INDEPENDENT DOM. (No sharing of memory or DOMs between workers/main thread).
- [Bug 14137] Just want to add - don't get hung up on the process/thread stuff. It is just a metaphor. I don't really care how it is implemented. One could do it all in one process. The present design fits the process model nicely. There is no sharing of memory.
- [Bug 14138] New: Lastly, to make clear. I am not proposing web workers share the DOM with the main thread. I am proposing the each web worker has it's own INDEPENDENT DOM. (No sharing of memory or DOMs between workers/main thread).
- [Bug 14137] New: Just want to add - don't get hung up on the process/thread stuff. It is just a metaphor. I don't really care how it is implemented. One could do it all in one process. The present design fits the process model nicely. There is no sharing of memory.
- [Bug 14120] New: Current spec for EventSource close method doesn't defined behaviour when close called after 'onopen' or 'onmessage'. For example, Google Chrome, closes connection if 'close' called while 'open' method dispatching and Opera doen't close it.
- Re: What changes to Web Messaging spec are proposed? [Was: Re: Using ArrayBuffer as payload for binary data to/from Web Workers]
Monday, 12 September 2011
- [indexeddb] Implicit Transaction Request associated with failed transactions
- RE: [IndexedDB] New version API checked in
- Re: Mouse Lock
- RE: [indexeddb] Compound Key support for Primary Keys and Indexes
- RE: [IndexedDB] New version API checked in
- WebApps TPAC2011 meeting Oct 31 and November 1; request for agenda topics
- [Bug 14119] New: Strip collapsed whitespace on insertText
- Re: DOM4 not compatible with ACID3 tests
- [Bug 13104] 1) ping(msg); //allow client to send server ping as per websocket spec 2) onpong(); //allow client to receive response of ping
- [Bug 14116] New: Regarding a previous post, a browser could launch itself (CreateProcess() on Windows) again and pass say a port number, a URL, and a boolean flag to the spawned child process. The browser could then be modified to examine it's command line- if there are 3
Sunday, 11 September 2011
- [Bug 14108] It works as expected. Thanks for making this.
- [Bug 14108] New: It works as expected. Thanks for making this.
Saturday, 10 September 2011
- [Bug 14057] In section "The WebSocket interface" when describing the operation of the WebSocket constructor, the following statement is made: "Return a new WebSocket object, and continue these steps in the background (without blocking scripts). ... Establish a WebSoc
- [Bug 14083] status box is too big. wrong id?
- [Bug 14093] Just to throw out an idea, to allow use of the XML parser, and alert() for debugging, one could implement web workers as simply another open page in the browser, with full access to the DOM, etc, with the ability to communicate to the 'parent' by posting
- [Bug 13990] Need a spec for CloseEvent constructor
- [Bug 13989] Need a spec for ErrorEvent constructor
- Re: [DOM4] Remove Node.isSameNode
- Re: [DOM4] Remove Node.isSameNode
- Re: [DOM4] Remove Node.isSameNode
- Re: [WebSocket API] .binaryType
- Re: [DOM4] Remove Node.isSameNode
- Re: [DOM4] Remove Node.isSameNode
Friday, 9 September 2011
- Re: [DOM4] Remove Node.isSameNode
- [websockets] Getting WebSockets API to Last Call
- Re: [DOM4] Remove Node.isSameNode
- Fwd: W3C Workshop on the Future of Offline Web Applications (Call for Participation)
- Fwd: W3C Workshop on the Future of Offline Web Applications (Call for Participation)
- [DOM4] Remove Node.isSameNode
- Re: DOM4 not compatible with ACID3 tests
- RE: publish LC#2 of Web IDL; deadline September 16
- [Clipboard] Processing model feedback (and other)
- CfC: publish LC#2 of Web IDL; deadline September 16
- Re: [DOMCore] Web messaging references
- Re: DOM4 not compatible with ACID3 tests
- Re: RfC: how to organize the DOM specs [Was: CfC: publish new WD of DOM Core]
- Re: [WebIDL] remove modules
- Re: RfC: how to organize the DOM specs [Was: CfC: publish new WD of DOM Core]
- Re: [DOM3Events] CR
- Re: DOM4 not compatible with ACID3 tests
- Re: DOM Mutation Events Replacement: When to deliver mutations
- Re: DOM4 not compatible with ACID3 tests
Thursday, 8 September 2011
- [Bug 14094] New: add example where you listen for and use an event other than 'message'. see <http://www.w3.org/mid/CAA2gsfoQkK1WJu8u_Dm743p4cOPng1OfHM29T7c_1RrpuE95vA@mail.gmail.com>
- [Bug 14093] New: Just to throw out an idea, to allow use of the XML parser, and alert() for debugging, one could implement web workers as simply another open page in the browser, with full access to the DOM, etc, with the ability to communicate to the 'parent' by posting
- Re: DOM4 not compatible with ACID3 tests
- Re: [EventSource] Is the field name "event" supported in current browsers?
- Re: [EventSource] Question on event type
- Re: [EventSource] Is the field name "event" supported in current browsers?
- Re: [EventSource] Question on event type
- [EventSource] Is the field name "event" supported in current browsers?
- Re: [EventSource] Question on event type
- Re: [EventSource] Question on event type
- Re: [EventSource] Question on event type
- RE: rename DOM Core to DOM4; deadline Sept 9
- Re: [EventSource] Question on event type
- [EventSource] Question on event type
- [Bug 14086] New: When performing AJAX type queries, they are already asynchronous and already occur in another thread. However, I have found that parsing the XML reply and converting that to a representation usable by the javascript application can result in freezes to t
- [Bug 14084] New: Hi! Returning a null from getItem() if the key does not exist is downright semantically wrong. null is a full-fledged value which can be serialized (JSONed), and is NOT the value we get if we do: var x = myObject.someUnknownProperty; In that case we get t
- [Bug 14083] New: status box is too big. wrong id?
- Re: DOM4 not compatible with ACID3 tests
- DOM4 not compatible with ACID3 tests
Wednesday, 7 September 2011
- Re: DOM Mutation Events Replacement: When to deliver mutations
- [Bug 14069] New: Split up conformance tests into manageable chunks
- [Bug 14065] Test queryCommand*() in conformance tests
- [Bug 13686] Remove the special case from onmessage (to call start())
- [Bug 14068] New: Think about what to return for backColor/hiliteColor value if it winds up being fully transparent
- [Bug 14067] New: Value for createLink and unlink can be null instead of a string
- [Bug 14066] New: Work around inconsistency in browser handling of align=* on random elements
- [Bug 13956] Port tests to a form usable by browsers
- [Bug 14065] New: Test queryCommand*() in conformance tests
- [Bug 14063] New: Get runtest.html working in IE, and preferably Opera
- [Bug 14062] New: Preserve state/value overrides when running commands like indent or insertorderedlist
- [Bug 14061] New: Make sure gentest.html works in the face of browser serialization bugs
- Re: [DOM] Scope
- RfC: rename DOM Core to DOM4; deadline Sept 9
- Re: before/after editaction
- Re: RfC: how to organize the DOM specs [Was: CfC: publish new WD of DOM Core]
- [Bug 14059] New: Reconsider backspace behavior at the start of a list item
- Re: before/after editaction
- Re: Fwd: Re: CfC: new WD of Clipboard API and Events; deadline April 5
- Re: CfC: new WD of Clipboard API and Events; deadline April 5
- Re: Fwd: Re: CfC: new WD of Clipboard API and Events; deadline April 5
- Re: Re: CfC: new WD of Clipboard API and Events; deadline April 5
- [Bug 14057] New: In section "The WebSocket interface" when describing the operation of the WebSocket constructor, the following statement is made: "Return a new WebSocket object, and continue these steps in the background (without blocking scripts). ... Establish a WebSoc
- Re: before/after editaction
- Re: HTMLElement.register--giving components tag names
- Re: Fwd: Re: CfC: new WD of Clipboard API and Events; deadline April 5
Tuesday, 6 September 2011
- Re: Fwd: Re: CfC: new WD of Clipboard API and Events; deadline April 5
- Re: [Clipboard API] Copy to clipboard
- [Bug 13373] Privacy: Limit SharedWorker connections to same top-level domain
- Re: HTMLElement.register--giving components tag names
- Re: [Clipboard API] Copy to clipboard
- Public repositories, was: Re: Reference to the HTML specification
- Re: Reference to the HTML specification
- Re: Reference to the HTML specification
- RE: [DOM3Events] CR
- Re: Reference to the HTML specification
- [DOMCore] Web messaging references
- Re: [DOM] Name
- Re: [DOM] Name
- Re: [DOM] Name
- Re: Reference to the HTML specification
- Re: Reference to the HTML specification
- Re: RfC: how to organize the DOM specs [Was: CfC: publish new WD of DOM Core]
- Re: Reference to the HTML specification
- Re: [widgets] CFC to republish Widget URI spec
- RfC: LCWD of Web Workers; deadline September 27
- RfC: LCWD of Web Storage; deadline September 27
- Re: RfC: how to organize the DOM specs [Was: CfC: publish new WD of DOM Core]
- Re: Fwd: Re: CfC: new WD of Clipboard API and Events; deadline April 5
- [Bug 11966] Catrope's feedback
- Re: Reference to the HTML specification
- Re: RfC: how to organize the DOM specs [Was: CfC: publish new WD of DOM Core]
- Re: riks of the new clipboard operations API
- Re: riks of the new clipboard operations API (was: Re: CfC: new WD of Clipboard API and Events; deadline April 5)
- [Bug 14037] Should XMLDocument be standardized?
Monday, 5 September 2011
- Re: Reference to the HTML specification
- Re: CfC: new WD of Clipboard API and Events; deadline April 5
- Re: [DOM] Name
- Re: [DOM] Name
- Re: [DOM] Name
- Re: Reference to the HTML specification
- Re: [DOM] Name
- Re: [DOM] Name
- Re: RfC: how to organize the DOM specs [Was: CfC: publish new WD of DOM Core]
- Re: Reference to the HTML specification
- Re: [DOM] Name
- Re: Reference to the HTML specification
- [Bug 13870] el.insertAdjacentHTML("beforebegin"/"afterend" broken when el.parentNode is a DocumentFragment
- Re: [DOM] Name
- Re: [DOM] Name
- Re: CfC: new WD of Clipboard API and Events; deadline April 5
- Re: [DOM] Name
- Re: [DOM3Events] CR
- Re: Fwd: Re: CfC: new WD of Clipboard API and Events; deadline April 5
- [DOM] Extensibility
- Re: [DOMCore] Extension specifications
- Re: Reference to the HTML specification
Sunday, 4 September 2011
Monday, 5 September 2011
- Re: Reference to the HTML specification
- Re: Copy prevention... up-and-running
- Copy prevention... up-and-running
- Re: [Clipboard API] Copy to clipboard
- Re: [Clipboard API] setData description
- Re: Fwd: Re: CfC: new WD of Clipboard API and Events; deadline April 5
- Re: [Clipboard API] Copy to clipboard
- Re: [Clipboard API] setData description
- Re: [Clipboard API] setData description
- [Bug 12434] Spec doesn't match IE when calling insertAdjacentHTML with position afterend or beforebegin on head or body
- Re: Fwd: Re: CfC: new WD of Clipboard API and Events; deadline April 5
- Re: Fwd: Re: CfC: new WD of Clipboard API and Events; deadline April 5
- Re: Fwd: Re: CfC: new WD of Clipboard API and Events; deadline April 5
- Re: RfC: LCWD of Progress Events; deadline September 1
- Re: Reference to the HTML specification
- Re: Reference to the HTML specification
- Re: Custom tags over wire, was Re: HTMLElement.register--giving components tag names
- Re: Custom tags over wire, was Re: HTMLElement.register--giving components tag names
- Re: Reference to the HTML specification
- [Clipboard API] Copy to clipboard
- Re: Custom tags over wire, was Re: HTMLElement.register--giving components tag names
Sunday, 4 September 2011
- [Clipboard API] setData description
- Re: CfC: new WD of Clipboard API and Events; deadline April 5
- clipboard events draft updated
- Re: Fwd: Re: CfC: new WD of Clipboard API and Events; deadline April 5
- Re: [DOM] Name
- [DOMCore] Extension specifications
- [Bug 12434] Spec doesn't match IE when calling insertAdjacentHTML with position afterend or beforebegin on head or body
- Mouse vs. Touch Events (was: [DOM3Events] CR)
- [Bug 12584] outerHTML should probably merge with adjacent text nodes if applicable. IE seems to do this to some extent, and WebKit just changed to do it: <https://bugs.webkit.org/show_bug.cgi?id=52686> This test shows behavior for outerText and outerHTML: <http://so
- Re: [DOM3Events] CR
- Re: [DOM3Events] CR
- Re: [DOM3Events] CR
- Re: [DOM3Events] CR
- [DOM3Events] CR
- CfC: publish Candidate Recommendation of Progress Events; deadline Sept 11
- [DOM] Name
- [DOM] Scope
- Re: RfC: how to organize the DOM specs [Was: CfC: publish new WD of DOM Core]
- Re: Reference to the HTML specification
- [IndexedDB] New version API checked in
- Re: Reference to the HTML specification
- Re: RfC: LCWD of Progress Events; deadline September 1
- Re: HTMLElement.register--giving components tag names
- Re: HTMLElement.register--giving components tag names
- Re: HTMLElement.register--giving components tag names
- Re: Custom tags over wire, was Re: HTMLElement.register--giving components tag names
Saturday, 3 September 2011
- Re: HTMLElement.register--giving components tag names
- Re: Custom tags over wire, was Re: HTMLElement.register--giving components tag names
- Re: Standards for Web applications on mobile devices: August 2011 updates
- Re: Reference to the HTML specification
- Re: [WebSocket API] .binaryType
- Re: Custom tags over wire, was Re: HTMLElement.register--giving components tag names
- Re: HTMLElement.register--giving components tag names
- Re: Reference to the HTML specification
- Re: Custom tags over wire, was Re: HTMLElement.register--giving components tag names
- Re: Custom tags over wire, was Re: HTMLElement.register--giving components tag names
- Re: Custom tags over wire, was Re: HTMLElement.register--giving components tag names
Friday, 2 September 2011
- Re: Custom tags over wire, was Re: HTMLElement.register--giving components tag names
- [Bug 14009] New: Consider treating linebreaks in <pre> specially for formatBlock etc.
- Re: Custom tags over wire, was Re: HTMLElement.register--giving components tag names
- Re: Custom tags over wire, was Re: HTMLElement.register--giving components tag names
- Re: Custom tags over wire, was Re: HTMLElement.register--giving components tag names
- Re: Custom tags over wire, was Re: HTMLElement.register--giving components tag names
- Standards for Web applications on mobile devices: August 2011 updates
- Re: RfC: LCWD of Progress Events; deadline September 1
- Re: [indexeddb] Compound Key support for Primary Keys and Indexes
- Re: Custom tags over wire, was Re: HTMLElement.register--giving components tag names
Thursday, 1 September 2011
- [WebSocket API] .binaryType
- Re: Last Call: Performance Timeline, User Timing, and Resource Timing
- Last Call: Performance Timeline, User Timing, and Resource Timing
- Re: HTTP, websockets, and redirects
- Re: HTTP, websockets, and redirects
- [Bug 13996] New: Don't wrap invisible nodes when doing inline styling
- Re: HTTP, websockets, and redirects
- [Bug 13990] New: Need a spec for CloseEvent constructor
- [Bug 13989] New: Need a spec for ErrorEvent constructor
- [Bug 13792] Remove all notes about sharing the connection. It can't work since what's received may depend on the request. It's also not reasonable to buffer every event in case they have to be dispatched again.
Wednesday, 31 August 2011
- [Bug 13984] New: Need a way to object detect binary support before connecting
- Re: HTMLElement.register--giving components tag names
- Re: HTMLElement.register--giving components tag names
- Re: xdash name prefixes (was Re: Component Model Update)
- Re: HTMLElement.register--giving components tag names
- Re: [XHR2] Blobs, names and FormData
- Re: HTMLElement.register--giving components tag names
- Re: HTMLElement.register--giving components tag names
- Re: xdash name prefixes (was Re: Component Model Update)
- Re: Mouse Lock
- RE: HTTP, websockets, and redirects
- Re: [XHR2] Blobs, names and FormData
- Re: RfC: how to organize the DOM specs [Was: CfC: publish new WD of DOM Core]
- Re: xdash name prefixes (was Re: Component Model Update)
- Re: Custom tags over wire, was Re: HTMLElement.register--giving components tag names
- Re: [XHR2] Blobs, names and FormData
- Custom tags over wire, was Re: HTMLElement.register--giving components tag names
- CfC: obsolescence text for DOM 2 View Recommendation; deadline September 7
- Re: [XHR2] Blobs, names and FormData
- Re: RfC: how to organize the DOM specs [Was: CfC: publish new WD of DOM Core]
- Re: RfC: how to organize the DOM specs [Was: CfC: publish new WD of DOM Core]
- Re: [XHR2] Blobs, names and FormData
- Re: RfC: how to organize the DOM specs [Was: CfC: publish new WD of DOM Core]
- Re: Rescinding the DOM 2 View Recommendation?
- Re: [File API] Blob.slice()
- Re: [File API] FileList
- Re: [File API] dependencies
- [File API] Dereferencing Model for Blob URIs
- Re: [File API] opaque string
- Re: [XHR2] Blobs, names and FormData
- Re: HTMLElement.register--giving components tag names
- Re: [XHR2] Blobs, names and FormData
- Re: [XHR2] Blobs, names and FormData
- HTMLElement.register--giving components tag names
- Re: [File API] opaque string
- Re: [File API] dependencies
- Re: [File API] asynchronous methods
- Re: [File API] Determining Encoding
- Re: [File API] constants -> strings
- Re: [File API] exceptions
- Re: [File API] Blob.slice()
- Re: [File API] FileList
- [Bug 8241] Named properties on window
- Re: [XHR2] Blobs, names and FormData
- Re: before/after editaction
- Re: [XHR2] Blobs, names and FormData
- Re: [XHR2] Blobs, names and FormData
- Re: before/after editaction
Tuesday, 30 August 2011
- Re: before/after editaction
- Re: [selectors-api] Return an Array instead of a static NodeList
- Re: before/after editaction
- before/after editaction
- Re: [XHR2] Blobs, names and FormData
- Re: Some way to change an element's name would be useful
- Re: [selectors-api] Return an Array instead of a static NodeList
- Re: Some way to change an element's name would be useful
- RE: [indexeddb] Compound Key support for Primary Keys and Indexes
- [Bug 13976] New: Backspacing in between two lists should merge them
- [Bug 13975] New: Get rid of multi-Range Selections
- [Bug 13974] New: Allow Selections to be cloned, saved, etc.
- [Bug 13830] "Delete the contents" has to be rewritten to delete the selection
- [Bug 13973] New: Refactor delete stuff
- Re: [XHR2] Blobs, names and FormData
- Re: [selectors-api] Return an Array instead of a static NodeList
- [Bug 13972] New: var bgPage = chrome.extension.getBackgroundPage(); function saveTabData(tab, data) { if (tab.incognito) { bgPage[tab.url] = data; // Persist data ONLY in memory } else { localStorage[tab.url] = data; // OK to store data }
- Re: Some way to change an element's name would be useful
- Re: [indexeddb] Issues stated on the current spec
- Re: [indexeddb] Compound Key support for Primary Keys and Indexes
- Re: [selectors-api] Return an Array instead of a static NodeList
- Re: [XHR2] Blobs, names and FormData
- Re: [selectors-api] Return an Array instead of a static NodeList
- Re: Some way to change an element's name would be useful
- Re: [selectors-api] Return an Array instead of a static NodeList
- [Bug 13949] Fantastic geocities.com reference in the section on Cross-directory attacks!
- Re: [selectors-api] Return an Array instead of a static NodeList
- [Bug 13967] New: Webkit implementation does not use the second argument 'targetOrigin',
Monday, 29 August 2011
- Re: Reference to the HTML specification
- Re: Some way to change an element's name would be useful
- Re: Some way to change an element's name would be useful
- Re: Some way to change an element's name would be useful
- Re: Some way to change an element's name would be useful
- Re: Some way to change an element's name would be useful
- Re: Some way to change an element's name would be useful
- Re: Some way to change an element's name would be useful
- Some way to change an element's name would be useful
- [Bug 13957] New: Remove special handling for WebKit class on blockquote
- [Bug 13956] New: Port tests to a form usable by browsers
- [Bug 13955] New: Add more notes!
- [Bug 13954] New: Define DOM mutation operations that automatically check for editability
- [Bug 13953] New: Investigate the user-modify CSS property
- [Bug 13952] New: Specify selection change events
- [Bug 13951] New: Should be able to treat an image with caption as a unit
- [Bug 13950] New: Specify that links etc. aren't focusable/don't work in editable areas
- Re: Request for participation in W3C widgets standard
- Re: how to organize the DOM specs [Was: CfC: publish new WD of DOM Core]
- [Bug 13949] New: Fantastic geocities.com reference in the section on Cross-directory attacks!
- Re: [selectors-api] Return an Array instead of a static NodeList
- Re: HTTP, websockets, and redirects
- Re: [whatwg] window.cipher HTML crypto API draft spec
- Reminder: RfC: LCWD of Progress Events; deadline September 1
- Re: CfC: publish LCWD of Server-sent Events spec; deadline August 17
- Re: CfC: publish LCWD of Web Workers; deadline August 17
- Re: CfC: publish LCWD of Web Storage; deadline August 17
- Re: Mouse Lock
Sunday, 28 August 2011
Thursday, 25 August 2011
Sunday, 28 August 2011
- Re: Mouse Lock
- [Bug 13938] New: Explicitly allow UAs to let the user execute commands without author intervention
- [Bug 13937] New: Specify editing of form controls
- [Bug 13936] New: Require that non-editable and embeddable content be movable
- [Bug 13930] New: Refer to rniwa's undo/redo spec
Saturday, 27 August 2011
- Re: [indexeddb] Issues stated on the current spec
- [indexeddb] Compound Key support for Primary Keys and Indexes
Friday, 26 August 2011
- Re: Mouse Lock
- [indexeddb] Issues stated on the current spec
- Re: [selectors-api] Return an Array instead of a static NodeList
- Re: xdash name prefixes (was Re: Component Model Update)
- Re: [Component Model]: Shadow DOM Subtree per element: One or Many?
- Re: Component Model Update
- Re: Components/constructable DOM elements: mandatory tag registration?
- Components/constructable DOM elements: mandatory tag registration?
- Re: xdash name prefixes (was Re: Component Model Update)
- Re: Component Model Update
- Re: [Component Model]: Shadow DOM Subtree per element: One or Many?
- Re: how to organize the DOM specs [Was: CfC: publish new WD of DOM Core]
- Re: Joystick support
- Re: [WebIDL] remove modules
- Re: xdash name prefixes (was Re: Component Model Update)
- Re: Mouse Lock
- [Bug 13913] New: Attributes don't have an order
- [Bug 13911] New: Active range's definition relies on the "context object" but there might not be one
- [Bug 13910] New: There can never be no active range
- [Bug 13909] New: Selections have three possible directions, not two
- [Bug 13908] New: WordStar semantics aren't supported
- Re: how to organize the DOM specs [Was: CfC: publish new WD of DOM Core]
Thursday, 25 August 2011
- Re: [selectors-api] Return an Array instead of a static NodeList
- RE: [indexeddb] Updates to the IDBCursor.advance method text and exception list.
- Re: [selectors-api] Return an Array instead of a static NodeList
- Re: HTTP, websockets, and redirects
- Re: Joystick support
- [Component Model] Declarative syntax for shadow DOM subtrees, was Re: Component Model Update
- Re: Component Model Update
- Re: Component Model Update
- RE: Joystick support
- RE: Joystick support
- Re: Component Model Update
- Re: how to organize the DOM specs [Was: CfC: publish new WD of DOM Core]
- Re: Joystick support
- Re: Joystick support
- Re: Joystick support
- Re: Component Model Update
- Re: Component Model Update
Wednesday, 24 August 2011
Thursday, 25 August 2011
- Re: [selectors-api] Return an Array instead of a static NodeList
- Re: Component Model Update
- Re: [XHR2] Blobs, names and FormData
- Re: [Component Model]: Shadow DOM Subtree per element: One or Many?
- Re: [Component Model]: Shadow DOM Subtree per element: One or Many?
- Re: [selectors-api] Return an Array instead of a static NodeList
- Re: [XHR2] Blobs, names and FormData
- Re: [selectors-api] Return an Array instead of a static NodeList
- Re: [Component Model]: Shadow DOM Subtree per element: One or Many?
- Re: Component Model Update
- Re: Component Model Update
- Re: Component Model Update
- Re: [Component Model]: Shadow DOM Subtree per element: One or Many?
- Re: [Component Model]: Shadow DOM Subtree per element: One or Many?
- Re: [Component Model]: Shadow DOM Subtree per element: One or Many?
- Re: Component Model Update
- Re: xdash name prefixes (was Re: Component Model Update)
- xdash name prefixes (was Re: Component Model Update)
Wednesday, 24 August 2011
- [Bug 13118] [editing] Consider firing the 'input' event for contenteditable="" areas as well
- Re: Component Model Update
- Re: [Component Model]: Shadow DOM Subtree per element: One or Many?
- Re: [Component Model]: Shadow DOM Subtree per element: One or Many?
- Re: Component Model Update
- Re: [XHR2] Blobs, names and FormData
- [Bug 13893] New: Only HTML elements should be editable
- Re: [Component Model]: Shadow DOM Subtree per element: One or Many?
- [Bug 13892] New: Background color should be settable for table cells
- [Bug 13891] New: Allow author scripts that fire before or after every command
- Re: [Component Model]: Shadow DOM Subtree per element: One or Many?
- Re: [selectors-api] Return an Array instead of a static NodeList
- [Component Model]: Shadow DOM Subtree per element: One or Many?
- Re: [selectors-api] Return an Array instead of a static NodeList
- Re: Component Model Update
- Re: Component Model Update
- [widgets] CFC to republish Widget URI spec
- Re: Component Model Update
- Re: [XHR2] Blobs, names and FormData
Sunday, 21 August 2011
Wednesday, 24 August 2011
Tuesday, 23 August 2011
- RE: FW: [indexeddb] transaction commit failure
- Component Model Update
- Re: [XHR2] Blobs, names and FormData
- Re: [XHR2] Blobs, names and FormData
- Re: [XHR2] Blobs, names and FormData
- [Bug 13834] Garbage collection policy for XMLHttpRequestUpload
- Re: [XHR2] Blobs, names and FormData
- Re: [XHR2] Blobs, names and FormData
- [Bug 13786] Drop the charset parameter or made it non-conforming. Other MIME types introduced by this specification do not allow the charset parameter.
- Re: [XHR2] Blobs, names and FormData
- Re: [XHR2] Blobs, names and FormData
- [Bug 13373] Privacy: Limit SharedWorker connections to same top-level domain
- Re: [indexeddb] Updates to the IDBCursor.advance method text and exception list.
- Re: FW: [indexeddb] transaction commit failure
- Re: [XHR2] Blobs, names and FormData
- [indexeddb] Updates to the IDBCursor.advance method text and exception list.
- Re: Mouse Lock
- [Bug 13786] Drop the charset parameter or made it non-conforming. Other MIME types introduced by this specification do not allow the charset parameter.
Monday, 22 August 2011
- RE: [indexeddb] Handling negative parameters for the advance method
- RE: FW: [indexeddb] transaction commit failure
- Re: DOM Mutation Events Replacement: Findings from implementing "net-effect" projections
- Re: [XHR2] Blobs, names and FormData
- [Bug 13844] Does web work add complex to web?
- Re: how to organize the DOM specs [Was: CfC: publish new WD of DOM Core]
- Re: how to organize the DOM specs [Was: CfC: publish new WD of DOM Core]
- [Bug 13856] New: I am not sure whether it is due to the nature of this documentation but it would be very helpful to include an example of HTTP response and how it should react to HTTP 3xx and 4xx.
Saturday, 20 August 2011
- RE: how to organize the DOM specs [Was: CfC: publish new WD of DOM Core]
- [Bug 13844] New: Does web work add complex to web?
- Re: [IndexedDB] Transaction Auto-Commit
Friday, 19 August 2011
- [Bug 9738] Improve IDL documentation
- [Bug 13373] Privacy: Limit SharedWorker connections to same top-level domain
- [Bug 13842] One issue that I have noticed is that there is no way to create an EventSource and attach event listeners to it before it connects to the server. This means that there is no way to ensure that no messages are missed between the creation of the EventSourc
- RE: http://www.w3.org/TR/IndexedDB/#key-construct ordering confusion
- [Bug 13843] New: Define Range mutation for normalize()
- [Bug 13842] New: One issue that I have noticed is that there is no way to create an EventSource and attach event listeners to it before it connects to the server. This means that there is no way to ensure that no messages are missed between the creation of the EventSourc
- [Bug 13841] New: Investigate what should happen when hitting Enter inside nested single-line containers
- [Bug 13840] New: selectAll needs to behave differently inside an editing host
- [Bug 13839] New: Merge adjacent inline markup when deleting
- [Bug 13834] New: Garbage collection policy for XMLHttpRequestUpload
Thursday, 18 August 2011
- Re: [XHR] support for streaming data
- Re: [XHR] support for streaming data
- [Bug 13831] New: Deleting a block should leave style tags nested inside
- [Bug 13830] New: "Delete the contents" has to be rewritten to delete the selection
- Re: [XHR] support for streaming data
- [Bug 13829] New: Ensure that hiliteColor is the innermost style applied
- [Bug 13817] Storage is definately persistent. Annoyingly so. As the client, I can't get rid of it. Maybe I'm missing something? Thanks.
- [Bug 12838] Define garbage collection policy
- [Bug 13817] New: Storage is definately persistent. Annoyingly so. As the client, I can't get rid of it. Maybe I'm missing something? Thanks.
- Re: [XHR] support for streaming data
Wednesday, 17 August 2011
- Re: FW: [indexeddb] transaction commit failure
- [Bug 13611] Example in 3.1.3 says key path can contain array indices
- [Bug 13812] New: The EventSource garbage collection does not mention open/error events. It also does not seem to match the language entirely of WebSocket garbage collection.
- Re: [XHR] support for streaming data
- Re: [XHR2] PATCH Method support
- FW: [indexeddb] transaction commit failure
- [Bug 13811] New: Add tests for collapsed whitespace
- [Bug 13631] Change visible/invisible to take display: none and collapsed whitespace into account
- Re: [XHR2] PATCH Method support
- Re: http://www.w3.org/TR/IndexedDB/#key-construct ordering confusion
- http://www.w3.org/TR/IndexedDB/#key-construct ordering confusion
- [Bug 13681] Make FormData.append return the FormData object
- Re: Mutation events replacement
- [Bug 13808] New: Let users make whitespace visible
- [Bug 13807] New: Allow user-typed URLs to automatically become links
- [Bug 13806] New: Allow users to edit tables somehow
- Re: DOM Mutation Events Replacement: Findings from implementing "net-effect" projections
- Re: publish new WD of DOM Core; deadline August 10
- [Bug 13681] Make FormData.append return the FormData object
- [Bug 13678] Misleading encoding in FormData objects created on HTML Forms
- Re: DOM Mutation Events Replacement: Findings from implementing "net-effect" projections
- Re: [XHR2] PATCH Method support
- Re: [XHR2] PATCH Method support
- Re: [XHR2] PATCH Method support
- [XHR2] PATCH Method support
- DOM Mutation Events Replacement: Findings from implementing "net-effect" projections
Tuesday, 16 August 2011
- [Bug 13799] New: Should Transferables be transfered even when postMessage fails?
- Re: DOM Mutation Events Replacement: When to deliver mutations
- RE: Possible errata for http://www.w3.org/TR/IndexedDB/
- Re: ISSUE-137 (IME-keypress): Should keypress events fire when using an IME? [DOM3 Events]
- RE: publish new WD of DOM Core; deadline August 10
- RE: how to organize the DOM specs [Was: CfC: publish new WD of DOM Core]
- [Bug 9739] Editorial review from timeless on March 24/25, 2010
- Re: Reference to the HTML specification
- RE: [IndexedDB] Transaction Auto-Commit
- [Bug 13795] New: Support user resizing of editable content
- [Bug 13794] New: I think length-prefixed messages would be a lot more useful than line-delimited messages. Sentinel terminators, especially newlines, are more error prone to generate and parse than a few bytes of length prefix followed by a message, repeat. In addition, t
- Re: DOM Mutation Events Replacement: When to deliver mutations
- Re: [indexeddb] transaction commit failure
- Re: [IndexedDB] Transaction Auto-Commit
- [Bug 13792] New: Remove all notes about sharing the connection. It can't work since what's received may depend on the request. It's also not reasonable to buffer every event in case they have to be dispatched again.
- Re: RfC: LCWD of Progress Events; deadline September 1
- Re: RfC: LCWD of Progress Events; deadline September 1
- Re: Re: Indicating certificate order in XML Dig Sig ( LC-2504)
- Re: [indexeddb] transaction commit failure
- Re: [IndexedDB] Transaction Auto-Commit
Monday, 15 August 2011
- [indexeddb] transaction commit failure
- RE: [indexeddb] Handling negative parameters for the advance method
- Re: [indexeddb] Handling negative parameters for the advance method
- [Bug 13632] Update removeFormat to use a blacklist, not a whitelist
- Re: Re: Indicating certificate order in XML Dig Sig ( LC-2504)
- Re: [File API] opaque string
- RE: [indexeddb] Handling negative parameters for the advance method
- Re: [File API] opaque string
- Re: [File API] dependencies
- Re: [File API] opaque string
- [Bug 13786] New: Drop the charset parameter or made it non-conforming. Other MIME types introduced by this specification do not allow the charset parameter.
- Re: DOM Mutation Events Replacement: When to deliver mutations
- Re: publish new WD of DOM Core; deadline August 10
- [Bug 13777] New: The WebSocket protocol draft (hybi-10) restricts the value of subprotocols as follows: The elements that comprise this value MUST be non- empty strings with characters in the range U+0021 to U+007E not including separator characters as defined
- [Bug 13686] Remove the special case from onmessage (to call start())
Sunday, 14 August 2011
- Re: [indexeddb] Handing negative parameters for the advance method
- [Bug 13686] Either remove the special case from onmessage (to call start()) or add it also to addEventListener listeners
- [Bug 13686] Either remove the special case from onmessage (to call start()) or add it also to addEventListener listeners
- Re: [File API] constants -> strings
- [File API] opaque string
- [File API] dependencies
- [File API] asynchronous methods
- [File API] Determining Encoding
- [File API] constants -> strings
- [File API] exceptions
- [File API] Blob.slice()
- [File API] FileList
- Re: RfC: LCWD of Progress Events; deadline September 1
Saturday, 13 August 2011
- [Bug 13772] New: Example code should contain a comma instead of semicolon: worker.port.postMessage({ foo: 'structured', bar: ['data', 'also', 'possible']});
- Re: Proposal to allow Transferables to be used in initMessageEvent
- Re: DOM Mutation Events Replacement: When to deliver mutations
- Re: [XHR] support for streaming data
- Re: Rescinding the DOM 2 View Recommendation?
- Re: Proposal to allow Transferables to be used in initMessageEvent
- Re: Mouse Lock
- [Bug 13763] The WebSocket API should provide a polling mechanism too. Only event based capture messages is not good because if a method in a JS-Class send a message the reply arrive in the event handler. The event handler has no access (if no global var exists) to th
- Re: [XHR2] responseType and response properties
- Re: [indexeddb] Handling negative parameters for the advance method
- RE: [indexeddb] Handling negative parameters for the advance method
- Re: [indexeddb] What happens after we reach the AutoInc maximum value?
- Re: [XHR2] responseType and response properties
- Re: [WebIDL] remove modules
- Re: [WebIDL] remove modules
- [indexeddb] What happens after we reach the AutoInc maximum value?
Friday, 12 August 2011
- Re: Mouse Lock
- Re: [WebIDL] remove modules
- Re: [WebIDL] remove modules
- Re: [WebIDL] remove modules
- Re: Mouse Lock
- Re: [indexeddb] Handing negative parameters for the advance method
- Re: Mouse Lock
- [indexeddb] Handing negative parameters for the advance method
- Re: [WebIDL] remove modules
- Re: Mouse Lock
- Re: Mouse Lock
- Re: Mouse Lock
- Re: Mouse Lock
- Re: [WebIDL] remove modules
- Re: [XHR] support for streaming data
- Re: [XHR] support for streaming data
- Re: [WebIDL] remove modules
- Re: Rescinding the DOM 2 View Recommendation?
- Re: Mouse Lock
- RE: Rescinding the DOM 2 View Recommendation?
- Re: [WebIDL] remove modules
- Re: [WebIDL] remove modules
- Re: Rescinding the DOM 2 View Recommendation?
- Reminder: RfC: Last Call Working Draft of Web IDL; deadline August 23
- [Bug 13763] New: The WebSocket API should provide a polling mechanism too. Only event based capture messages is not good because if a method in a JS-Class send a message the reply arrive in the event handler. The event handler has no access (if no global var exists) to th
- Re: Mouse Lock
- Re: [WebIDL] remove modules
- Re: Mouse Lock
- Re: Mouse Lock
Thursday, 11 August 2011
- Re: [File API] Latest Editor's Draft | Call for Review
- Re: [File API] Latest Editor's Draft | Call for Review
- Re: Proposal to allow Transferables to be used in initMessageEvent
Tuesday, 9 August 2011
Thursday, 11 August 2011
Tuesday, 9 August 2011
Thursday, 11 August 2011
- Re: [whatwg] File API Streaming Blobs
- Re: [whatwg] File API Streaming Blobs
- [Bug 13634] Document autoimplementation.html and link to it more prominently
- [File API] Latest Editor's Draft | Call for Review
- Re: HTTP, websockets, and redirects
- Re: DOM Mutation Events Replacement: When to deliver mutations
- [Bug 13761] New: Now that event data can be discarded (if there is no newline before eof), the last id field value received should be stored in a buffer and set as the EventSource's lastEventId only when the event is actually dispatched. That way the id associated with th
- Re: DOM Mutation Events Replacement: When to deliver mutations
- Re: DOM Mutation Events Replacement: When to deliver mutations
- Re: RfC: how to organize the DOM specs [Was: CfC: publish new WD of DOM Core]
- Re: CfC: publish LCWD of Server-sent Events spec; deadline August 17
- Re: RfC: how to organize the DOM specs [Was: CfC: publish new WD of DOM Core]
- RfC: how to organize the DOM specs [Was: CfC: publish new WD of DOM Core]
- Re: DOM Mutation Events Replacement: When to deliver mutations
- Re: [XHR] support for streaming data
- Re: HTTP, websockets, and redirects
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mouse Lock
- Re: Mutation events replacement
- Re: DOM Mutation Events Replacement: When to deliver mutations
- DOM Mutation Events Replacement: When to deliver mutations
- DOM Mutation Events Replacement: The Story So Far / Existing Points of Consensus
- Re: [XHR] support for streaming data
- Re: [XHR] support for streaming data
Wednesday, 10 August 2011
- Re: Rescinding the DOM 2 View Recommendation?
- Re: [XHR] support for streaming data
- Re: [whatwg] File API Streaming Blobs
- Re: Mutation events replacement
- Re: Mutation events replacement
- Rescinding the DOM 2 View Recommendation?
- Re: Reference to the HTML specification
- Re: Reference to the HTML specification
- Re: Reference to the HTML specification
- Re: Reference to the HTML specification
- CfC: publish LCWD of Server-sent Events spec; deadline August 17
- Re: Reference to the HTML specification
- Re: Restricted Contexts (private browsing / sandbox)
- Re: Permission Systems across APIs
- Re: CfC: publish LCWD of Web Workers; deadline August 17
- Re: CfC: publish LCWD of Web Storage; deadline August 17
- Re: HTTP, websockets, and redirects
- CfC: publish LCWD of Web Workers; deadline August 17
- CfC: publish LCWD of Web Storage; deadline August 17
- Re: RfC: LCWD of Progress Events; deadline September 1
- [Bug 13742] Please don't use section numbers as these tend to change rapidly and make your feedback harder to understand.
- [Bug 13743] Please don't use section numbers as these tend to change rapidly and make your feedback harder to understand.
- [Bug 13743] New: Please don't use section numbers as these tend to change rapidly and make your feedback harder to understand.
- [Bug 13742] New: Please don't use section numbers as these tend to change rapidly and make your feedback harder to understand.
Tuesday, 9 August 2011
- [Bug 13717] New: Clarify that a MessagePort clone, when created, hasn't been transfered, even if it was created as a result of another being transfered. ("If any object is listed in transfer more than once, or any of the Transferable objects listed in transfer have alread
- RfC: LCWD of Progress Events; deadline September 1
- [Bug 13686] Either remove the special case from onmessage (to call start()) or add it also to addEventListener listeners
- Re: ISSUE-137 (IME-keypress): Should keypress events fire when using an IME? [DOM3 Events]
- Re: [XHR] support for streaming data
- Re: [XHR] support for streaming data
- Re: [XHR] support for streaming data
- Re: [whatwg] File API Streaming Blobs
- Re: [XHR] support for streaming data
- Re: [XHR] support for streaming data
- Re: [XHR] support for streaming data
- [XHR] support for streaming data
Monday, 8 August 2011
- Re: [whatwg] File API Streaming Blobs
- [Bug 13690] method setItem(key, value) Why don't you fix a third optional parameter to set the "duration" of the key/value pair. If it is not set the key/value pair will not expire otherwise it will expire as it is set in the 'duration' parameter.
- Re: [whatwg] File API Streaming Blobs
- Re: [whatwg] File API Streaming Blobs
- [Bug 13588] [web messaging] Erroneous origin check in algorithm
- [Bug 13322] Add UDP! Quake uses UDP, I can't continue development of WebQuake because it uses UDP.
- [Bug 13525] Define what .origin should be for message events
- [Bug 13686] Either remove the special case from onmessage (to call start()) or add it also to addEventListener listeners
- [Bug 13295] The "make disappear a WebSocket object" case should not fail the WebSocket connection
- [Bug 13525] Define what .origin should be for message events
- [Bug 13580] web workers postMessage
- [Bug 13526] "One distinction we have decided to draw is to prevent downgrading mixed content with websockets (i.e. you cannot connect to a ws:// url from a https:// based context)." -- http://www.ietf.org/mail-archive/web/hybi/current/msg08017.html - specify this if
- [Bug 13426] "Attempt to fetch each resource identified by the resulting absolute URLs, from the entry script's origin" â this makes it sound as if you should only fetch URLs frm that origin, which looking more closely isn't the meaning. This should be made more obv
- Re: [whatwg] File API Streaming Blobs
- [Bug 13373] Privacy: Limit SharedWorker connections to same top-level domain
- Re: [whatwg] File API Streaming Blobs
- [Bug 13255] When I use importScripts in my worker to load a separate "library" file, it works, but I get the error: ReferenceError: Can't find variable: importScripts (Safari) Uncaught ReferenceError: importScripts is not defined So it's throwing an error, but that
- [Bug 13232] I think the section on DedicatedWorkerScope should include information about the kinds of data that postMessage can send to a worker, and the kinds of data that a worker can send back. http://dev.w3.org/html5/workers/#dedicated-workers-and-the-dedicatedwo
- Re: Element.create(): a proposal for more convenient element creation
- Re: Element.create(): a proposal for more convenient element creation
- Re: Element.create(): a proposal for more convenient element creation
- Re: Reference to the HTML specification
- Re: Element.create(): a proposal for more convenient element creation
- Re: Element.create(): a proposal for more convenient element creation
- Re: Element.create(): a proposal for more convenient element creation
- Re: Element.create(): a proposal for more convenient element creation
- Re: Element.create(): a proposal for more convenient element creation
Sunday, 7 August 2011
- Re: Reference to the HTML specification
- [Bug 13700] New: W3C SotD of this document still mentions whatwg.org version of the WebSocket protocol which is out of date.
- [Bug 13322] Add UDP! Quake uses UDP, I can't continue development of WebQuake because it uses UDP.
Saturday, 6 August 2011
- Re: Element.create(): a proposal for more convenient element creation
- Re: Element.create(): a proposal for more convenient element creation
- Re: Element.create(): a proposal for more convenient element creation
- Re: Element.create(): a proposal for more convenient element creation
- [Bug 13691] method setItem(key, value) Why don't you fix a third optional parameter to set the "duration" of the key/value pair. If it is not set the key/value pair will not expire otherwise it will expire as it is set in the 'duration' parameter.
- [Bug 13686] Either remove the special case from onmessage (to call start()) or add it also to addEventListener listeners
- [Bug 13691] New: method setItem(key, value) Why don't you fix a third optional parameter to set the "duration" of the key/value pair. If it is not set the key/value pair will not expire otherwise it will expire as it is set in the 'duration' parameter.
- [Bug 13690] New: method setItem(key, value) Why don't you fix a third optional parameter to set the "duration" of the key/value pair. If it is not set the key/value pair will not expire otherwise it will expire as it is set in the 'duration' parameter.
- [Bug 13686] Either remove the special case from onmessage (to call start()) or add it also to addEventListener listeners
- [Bug 10930] CanvasPixelArray out of range behavior needs clarification
- [Bug 13295] The "make disappear a WebSocket object" case should not fail the WebSocket connection
Friday, 5 August 2011
- [Bug 12574] AbstractWorker and WorkerGlobalScope should inherit EventTarget
- [Bug 13322] Add UDP! Quake uses UDP, I can't continue development of WebQuake because it uses UDP.
- [Bug 13294] The send() method should fail the WebSocket connection when data cannot be sent
- [Bug 13295] The "make disappear a WebSocket object" case should not fail the WebSocket connection
- [Bug 13633] Add high-level overviews to more of the abstract algorithms, like for "set the selection's value"
- Re: Reference to the HTML specification
- WebGL/Khronos liaison (Was: Reference to the HTML specification)
- Re: Reference to the HTML specification
- Re: Reference to the HTML specification
- Re: Reference to the HTML specification
- Re: Reference to the HTML specification
- Re: Reference to the HTML specification
- Re: Reference to the HTML specification
- [Bug 13686] New: Either remove the special case from onmessage (to call start()) or add it also to addEventListener listeners
- [Bug 13180] [Editorial] Causes that lead to failing the WebSocket connection, which results in an error event, should be more clearly specified
- [Bug 13264] please more pics to visually understand. too much reading.
- [Bug 13675] MessageEvent::ports should be a nullable platform array object for interop
- Re: Reference to the HTML specification
- Re: Reference to the HTML specification
- Re: Reference to the HTML specification
- [Bug 13063] MessagePort normatively referenced by not defined
- [Bug 13064] WindowBase64 normatively referenced by not defined
- [Bug 13065] WindowTimers normatively referenced by not defined
- Re: Reference to the HTML specification
- Re: Reference to the HTML specification
- Re: Reference to the HTML specification
- Re: Reference to the HTML specification
- Re: Reference to the HTML specification
- Re: Reference to the HTML specification
- Re: Reference to the HTML specification
- Re: publish new WD of DOM Core; deadline August 10
- Possible errata for http://www.w3.org/TR/IndexedDB/
- Re: Element.create(): a proposal for more convenient element creation
- Re: Element.create(): a proposal for more convenient element creation
- [Bug 13681] New: Make FormData.append return the FormData object
- [Bug 13678] New: Misleading encoding in FormData objects created on HTML Forms
Thursday, 4 August 2011
- Re: publish new WD of DOM Core; deadline August 10
- [Bug 13229] The following text from the "Security considerations" part of "11 IANA considerations" is wrong: "An event stream from an origin distinct from the origin of the content consuming the event stream can result in information leakage. To avoid this, user agen
- [Bug 13065] WindowTimers normatively referenced by not defined
- Re: CfC: publish new WD of XMLHttpRequest Level 2; deadline August 10
- Re: CfC: publish new WD of DOM Core; deadline August 10
- [Bug 13064] WindowBase64 normatively referenced by not defined
- [Bug 13172] The definition for [MessageEvent] is missing.
- [Bug 13071] "Once the end of the file is reached, the user agent must dispatch the event one final time, as defined below" means an implementation may parse a partial (corrupt) event as a final event if the connection is interrupted. Spec should always require an exp
- Re: Element.create(): a proposal for more convenient element creation
- [Bug 13064] WindowBase64 normatively referenced by not defined
- [Bug 13063] MessagePort normatively referenced by not defined
- [Bug 13156] The charset parameter is now an optional parameter (even though it can only be set to UTF-8). That should probably be stated here.
- [Bug 13155] The security considerations section needs to be updated to take CORS into account.
- [Bug 13020] No user agent will implement the storage mutex so this passage does not reflect reality
- [Bug 13083] postMessage should have an optional parameter for a synchronous request. Cross-domain AJAX calls are enough of a problem that it merits a supported way of fixing it, and this could be it.
- [Bug 13065] WindowTimers normatively referenced by not defined
- [Bug 13064] WindowBase64 normatively referenced by not defined
- [Bug 13063] MessagePort normatively referenced by not defined
- Re: Mutation events replacement
- Re: publish new WD of DOM Core; deadline August 10
- Re: Mutation events replacement
- RE: publish new WD of DOM Core; deadline August 10
- Re: publish new WD of DOM Core; deadline August 10
- [Bug 13675] New: MessageEvent::ports should be a nullable platform array object for interop
- RE: publish new WD of DOM Core; deadline August 10
- Re: [IndexedDB] Transaction Auto-Commit
- Re: Mutation events replacement
- Reference to the HTML specification
- Re: Mutation events replacement
- Re: [cors] Two minor processing issues
- FYI: new IETF mail list re IANA Registration
- Re: [cors] Two minor processing issues
- Re: [cors] Two minor processing issues
- Re: [IndexedDB] Transaction Auto-Commit
- [Bug 12111] spec for Storage object getItem(key) method does not match implementation behavior
Wednesday, 3 August 2011
- Re: [cors] Two minor processing issues
- Re: Adding a note to DOM2 Views
- Re: Adding a note to DOM2 Views
- Re: Adding a note to DOM2 Views
- [eventsource] Resolving URLs
- Re: Adding a note to DOM2 Views
- [Bug 13634] New: Document autoimplementation.html and link to it more prominently
- [Bug 13633] New: Add high-level overviews to more of the abstract algorithms, like for "set the selection's value"
- [Bug 13632] New: Update removeFormat to use a blacklist, not a whitelist
- [Bug 13631] New: Change visible/invisible to take display: none and collapsed whitespace into account
- Re: [widgets] Re: Call for Prior Art Related to US Patent 7,743,336 and US Patent Application 20070101146
- Restricted Contexts (private browsing / sandbox)
- Permission Systems across APIs
- [cors] Two minor processing issues
- Re: [IndexedDB] Transaction Auto-Commit
- Re: CfC: publish new WD of XMLHttpRequest Level 2; deadline August 10
- Re: CfC: publish new WD of DOM Core; deadline August 10
- Re: Element.create(): a proposal for more convenient element creation
- Re: Element.create(): a proposal for more convenient element creation
- Re: Element.create(): a proposal for more convenient element creation
- Re: Element.create(): a proposal for more convenient element creation
- Re: Element.create(): a proposal for more convenient element creation
- Re: Element.create(): a proposal for more convenient element creation
- [Bug 13611] New: Example in 3.1.3 says key path can contain array indices
- Re: [cors] Legacy Servers: POST Body Format
- CfC: publish new WD of XMLHttpRequest Level 2; deadline August 10
- CfC: publish new WD of DOM Core; deadline August 10
- RE: UAs shipping unprefixed websocket API implementations?
- Re: UAs shipping unprefixed websocket API implementations?
- [Bug 13580] web workers postMessage
- [Bug 13588] [web messaging] Erroneous origin check in algorithm
- [Bug 13584] [web messaging] Channel Messaging Origins
- Re: CORS/UMP to become joint WebApps and WebAppSec joint deliverable
- Re: CORS/UMP to become joint WebApps and WebAppSec joint deliverable
- Re: [cors] Legacy Servers: POST Body Format
- Re: CORS/UMP to become joint WebApps and WebAppSec joint deliverable
- Re: Element.create(): a proposal for more convenient element creation
- Re: CORS/UMP to become joint WebApps and WebAppSec joint deliverable
Tuesday, 2 August 2011
- [Bug 13526] New: "One distinction we have decided to draw is to prevent downgrading mixed content with websockets (i.e. you cannot connect to a ws:// url from a https:// based context)." -- http://www.ietf.org/mail-archive/web/hybi/current/msg08017.html - specify this if
- [Bug 13525] New: Define what .origin should be for message events
- Re: Element.create(): a proposal for more convenient element creation
- Re: Element.create(): a proposal for more convenient element creation
- Re: Element.create(): a proposal for more convenient element creation
- Re: Element.create(): a proposal for more convenient element creation
- Re: Element.create(): a proposal for more convenient element creation
- Re: Element.create(): a proposal for more convenient element creation
- Re: Element.create(): a proposal for more convenient element creation
- Re: Element.create(): a proposal for more convenient element creation
- Re: Element.create(): a proposal for more convenient element creation
- Re: Element.create(): a proposal for more convenient element creation
- Re: [XHR]
- Re: [XHR]
- Re: [XHR]
- [XHR]
- [XHR]
- Re: Element.create(): a proposal for more convenient element creation
- RE: publish Last Call WD of Progress Events; deadline August 2
- Re: Element.create(): a proposal for more convenient element creation
- Re: Element.create(): a proposal for more convenient element creation
- Re: [cors] Legacy Servers: POST Body Format
- Re: UAs shipping unprefixed websocket API implementations?
- Re: UAs shipping unprefixed websocket API implementations?
- Re: UAs shipping unprefixed websocket API implementations?
- UAs shipping unprefixed websocket API implementations?
- Re: [cors] Request for a reverse CORS mechanism
- Re: [IndexedDB] Transaction Auto-Commit
- Re: CORS/UMP to become joint WebApps and WebAppSec joint deliverable
- Re: CORS/UMP to become joint WebApps and WebAppSec joint deliverable
- Re: [web messaging] Erroneous origin check in algorithm
- Re: [web messaging] Erroneous origin check in algorithm
- Re: CORS/UMP to become joint WebApps and WebAppSec joint deliverable
- Re: CORS/UMP to become joint WebApps and WebAppSec joint deliverable
Monday, 1 August 2011
Tuesday, 2 August 2011
- Re: Element.create(): a proposal for more convenient element creation
- Re: Element.create(): a proposal for more convenient element creation
- Re: Element.create(): a proposal for more convenient element creation
- Re: Element.create(): a proposal for more convenient element creation
- Re: Element.create(): a proposal for more convenient element creation
- Re: Element.create(): a proposal for more convenient element creation
- Re: Element.create(): a proposal for more convenient element creation
- Re: Element.create(): a proposal for more convenient element creation
- Re: Element.create(): a proposal for more convenient element creation
- Re: Element.create(): a proposal for more convenient element creation
- Re: Element.create(): a proposal for more convenient element creation
- Re: Element.create(): a proposal for more convenient element creation
- Re: Element.create(): a proposal for more convenient element creation
- Re: Element.create(): a proposal for more convenient element creation
- Re: Element.create(): a proposal for more convenient element creation
- Re: Element.create(): a proposal for more convenient element creation
- Re: Element.create(): a proposal for more convenient element creation
- Element.create(): a proposal for more convenient element creation
Monday, 1 August 2011
- Re: App Cache and History API
- Re: From-Origin FPWD
- Re: From-Origin FPWD
- Re: CORS/UMP to become joint WebApps and WebAppSec joint deliverable
- RE: From-Origin FPWD
- Re: From-Origin FPWD
- Re: From-Origin FPWD
Thursday, 28 July 2011
Friday, 29 July 2011
- Re: Test suites and RFC2119
- Re: [websockets] Making optional extensions mandatory in the API (was RE: Getting WebSockets API to Last Call)
- Re: [CORS] Does "Origin" have to be included in the "Access-Control-Request-Headers" field?
- Re: [websockets] Making optional extensions mandatory in the API (was RE: Getting WebSockets API to Last Call)
Thursday, 28 July 2011
- [Bug 13427] "Attempt to fetch each resource identified by the resulting absolute URLs, from the entry script's origin" â this makes it sound as if you should only fetch URLs frm that origin, which looking more closely isn't the meaning. This should be made more obv
- [Bug 13427] New: "Attempt to fetch each resource identified by the resulting absolute URLs, from the entry script's origin" â this makes it sound as if you should only fetch URLs frm that origin, which looking more closely isn't the meaning. This should be made more obv
- [Bug 13426] New: "Attempt to fetch each resource identified by the resulting absolute URLs, from the entry script's origin" â this makes it sound as if you should only fetch URLs frm that origin, which looking more closely isn't the meaning. This should be made more obv
- Re: [IndexedDB] setVersion is cra... is not good
- [Bug 13162] The notes really do need to be cleaned up to be made explicit. Like WTH does this actually say? "The fail the WebSocket connection algorithm invokes the close the WebSocket connection algorithm, which then establishes that the WebSocket connection is clo
- RE: From-Origin FPWD
- Re: HTTP, websockets, and redirects
Wednesday, 27 July 2011
- RE: From-Origin FPWD
- Re: [websockets] Making optional extensions mandatory in the API (was RE: Getting WebSockets API to Last Call)
- Re: [websockets] Making optional extensions mandatory in the API (was RE: Getting WebSockets API to Last Call)
- Re: [websockets] Making optional extensions mandatory in the API (was RE: Getting WebSockets API to Last Call)
- Re: [websockets] Making optional extensions mandatory in the API (was RE: Getting WebSockets API to Last Call)
- Re: [websockets] Making optional extensions mandatory in the API (was RE: Getting WebSockets API to Last Call)
- Re: [websockets] Making optional extensions mandatory in the API (was RE: Getting WebSockets API to Last Call)
- Re: [CORS] Does "Origin" have to be included in the "Access-Control-Request-Headers" field?
- Re: [CORS] Does "Origin" have to be included in the "Access-Control-Request-Headers" field?
- Re: [websockets] Making optional extensions mandatory in the API (was RE: Getting WebSockets API to Last Call)
- Re: [websockets] Making optional extensions mandatory in the API (was RE: Getting WebSockets API to Last Call)
- Re: [websockets] Making optional extensions mandatory in the API (was RE: Getting WebSockets API to Last Call)
- Re: [websockets] Making optional extensions mandatory in the API (was RE: Getting WebSockets API to Last Call)
- [Reminder]: Last Call Working Drafts transition announcement of the API for Media Resources 1.0
- Re: [websockets] Making optional extensions mandatory in the API (was RE: Getting WebSockets API to Last Call)
- Re: [CORS] Does "Origin" have to be included in the "Access-Control-Request-Headers" field?
- [CORS] Does "Origin" have to be included in the "Access-Control-Request-Headers" field?
- Re: [websockets] Making optional extensions mandatory in the API (was RE: Getting WebSockets API to Last Call)
- Re: [websockets] Making optional extensions mandatory in the API (was RE: Getting WebSockets API to Last Call)
- Re: [websockets] Making optional extensions mandatory in the API (was RE: Getting WebSockets API to Last Call)
Tuesday, 26 July 2011
- RE: [IndexedDB] Client API state after calling deleteIndex and deleteObjectStore
- Re: [Bug 13373] New: Privacy: Limit SharedWorker connections to same top-level domain
- Re: [Bug 13373] New: Privacy: Limit SharedWorker connections to same top-level domain
- Re: [Bug 13373] New: Privacy: Limit SharedWorker connections to same top-level domain
- [Bug 13373] New: Privacy: Limit SharedWorker connections to same top-level domain
- Re: More use-cases for mutation events replacement
- Re: CfC: publish Last Call WD of Progress Events; deadline August 2
Saturday, 23 July 2011
Tuesday, 26 July 2011
- CfC: publish Last Call WD of Progress Events; deadline August 2
- Re: [websockets] Making optional extensions mandatory in the API (was RE: Getting WebSockets API to Last Call)
- Re: More use-cases for mutation events replacement
Monday, 25 July 2011
- Re: [websockets] Making optional extensions mandatory in the API (was RE: Getting WebSockets API to Last Call)
- RE: [websockets] Making optional extensions mandatory in the API (was RE: Getting WebSockets API to Last Call)
- Re: [websockets] Making optional extensions mandatory in the API (was RE: Getting WebSockets API to Last Call)
- Re: [From-Origin] on "theft"
- Re: [IndexedDB] Transaction Auto-Commit
- [IndexedDB] Transaction Auto-Commit
- Re: Mutation events replacement
- Re: CfC: publish Proposed Recommendation of view-mode Media Feature; deadline July 27
- CfC: IETF Media Type Specifications and Registration Procedures
Sunday, 24 July 2011
- Re: HTTP, websockets, and redirects
- More use-cases for mutation events replacement
- Re: Mutation events replacement
- HTTP, websockets, and redirects
Friday, 22 July 2011
- Re: [websockets] Making optional extensions mandatory in the API (was RE: Getting WebSockets API to Last Call)
- Re: [websockets] Making optional extensions mandatory in the API (was RE: Getting WebSockets API to Last Call)
Saturday, 23 July 2011
- [From-Origin] on "privacy leakage"
- [From-Origin] on "clickjacking"
- [From-Origin] on "theft"
- Re: Mutation events replacement
Friday, 22 July 2011
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Adding a note to DOM2 Views
- Re: From-Origin FPWD
- Re: From-Origin FPWD
- Re: [IndexedDB] Client API state after calling deleteIndex and deleteObjectStore
- Re: [DOMCore] Traversal
- Re: Adding a note to DOM2 Views
- Re: Adding a note to DOM2 Views
- Re: Adding a note to DOM2 Views
- Re: [DOMCore] Traversal
- Re: [DOMCore] Traversal
- Re: Mutation events replacement
- RE: [IndexedDB] Client API state after calling deleteIndex and deleteObjectStore
- Re: Mutation events replacement
- [DOMCore] Traversal
- Re: From-Origin FPWD
- Re: Mutation events replacement
- Re: From-Origin FPWD
- Re: From-Origin FPWD
- RfC: Last Call of Page Visibility API; deadline August 18
- Re: Mutation events replacement
- Re: From-Origin FPWD
- From-Origin FPWD
- Re: [websockets] Making optional extensions mandatory in the API
- Re: [websockets] Making optional extensions mandatory in the API (was RE: Getting WebSockets API to Last Call)
- Re: Mutation events replacement
- Re: Mutation events replacement
Thursday, 21 July 2011
- Re: Mutation events replacement
- RE: [websockets] Making optional extensions mandatory in the API (was RE: Getting WebSockets API to Last Call)
- Re: [websockets] Making optional extensions mandatory in the API (was RE: Getting WebSockets API to Last Call)
- Re: Mutation events replacement
- Re: [websockets] Making optional extensions mandatory in the API (was RE: Getting WebSockets API to Last Call)
- Re: Mutation events replacement
- [Bug 13321] This is amazing! Awesome for multiplayer games!
- RE: [websockets] Making optional extensions mandatory in the API (was RE: Getting WebSockets API to Last Call)
- [Bug 13322] New: Add UDP! Quake uses UDP, I can't continue development of WebQuake because it uses UDP.
- RE: [websockets] Making optional extensions mandatory in the API (was RE: Getting WebSockets API to Last Call)
- [Bug 13321] New: This is amazing! Awesome for multiplayer games!
- Re: [websockets] Making optional extensions mandatory in the API (was RE: Getting WebSockets API to Last Call)
- RE: [websockets] Making optional extensions mandatory in the API (was RE: Getting WebSockets API to Last Call)
- Re: [websockets] Making optional extensions mandatory in the API (was RE: Getting WebSockets API to Last Call)
- Re: [websockets] Making optional extensions mandatory in the API (was RE: Getting WebSockets API to Last Call)
- Re: [websockets] Making optional extensions mandatory in the API (was RE: Getting WebSockets API to Last Call)
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: [websockets] Getting WebSockets API to Last Call
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: SpellCheck API?
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
Wednesday, 20 July 2011
- Re: Mutation events replacement
- Re: [IndexedDB] setVersion is cra... is not good
- Re: Mutation events replacement
- Re: Mutation events replacement
- RE: [IndexedDB] setVersion is cra... is not good
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Global variables and id lookup for elements
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Global variables and id lookup for elements
- CfC: publish Proposed Recommendation of view-mode Media Feature; deadline July 27
- Re: Seeking view-mode Media Feature implementation data
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Global variables and id lookup for elements
- Re: Global variables and id lookup for elements
- Re: Mutation events replacement
- Re: Global variables and id lookup for elements
Tuesday, 19 July 2011
- Re: Mutation events replacement
- Re: Global variables and id lookup for elements
- Re: Global variables and id lookup for elements
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: [websockets] Reminder: review Web Socket Protocol v10; deadline July 25
- Seeking view-mode Media Feature implementation data
- [websockets] Reminder: review Web Socket Protocol v10; deadline July 25
- [Bug 13295] New: The "make disappear a WebSocket object" case should not fail the WebSocket connection
- [Bug 13294] New: The send() method should fail the WebSocket connection when data cannot be sent
Monday, 18 July 2011
- Re: [XHR2] Blobs, names and FormData
- Re: [XHR2] Blobs, names and FormData
- Re: [XHR2] Blobs, names and FormData
- Re: [XHR2] Blobs, names and FormData
- RE: [XHR2] Blobs, names and FormData
- Re: [XHR2] Blobs, names and FormData
- Re: [XHR2] Blobs, names and FormData
- RE: [XHR2] Blobs, names and FormData
- Re: [IndexedDB] setVersion is cra... is not good
- RE: [IndexedDB] setVersion is cra... is not good
- [Bug 13287] Hello! Into HTML5, i need browser to browser connection (p2p), directly! without server! Thanks.
- [Bug 13287] New: Hello! Into HTML5, i need browser to browser connection (p2p), directly! without server! Thanks.
- Re: Test suites and RFC2119
Sunday, 17 July 2011
- Re: [IndexedDB] setVersion is cra... is not good
- [Bug 13280] Why isn't MessageEvent linked to a definition? It's not at all clear what this object is. And the postMsg API has a MessageEvent, but that object doesn't have the "target" property, which is used in the sample code below. A lot more information about Mess
- [Bug 13280] New: Why isn't MessageEvent linked to a definition? It's not at all clear what this object is. And the postMsg API has a MessageEvent, but that object doesn't have the "target" property, which is used in the sample code below. A lot more information about Mess
Saturday, 16 July 2011
Friday, 15 July 2011
- Re: [widgets] Implementing the Storage Event for widget preferences
- Re: CORS/UMP to become joint WebApps and WebAppSec joint deliverable
- Re: CORS/UMP to become joint WebApps and WebAppSec joint deliverable
- Re: Indicating certificate order in XML Dig Sig
- CORS/UMP to become joint WebApps and WebAppSec joint deliverable
- RE: RE: [IndexedDB] Client API state after calling deleteIndex and deleteObjectStore
Thursday, 14 July 2011
- Unified Approaches
- [Bug 13264] New: please more pics to visually understand. too much reading.
- Re: FW: [IndexedDB] Client API state after calling deleteIndex and deleteObjectStore
- FW: [IndexedDB] Client API state after calling deleteIndex and deleteObjectStore
- RE: [indexeddb] IDBRequest.transaction property set to null
- [Bug 13255] New: When I use importScripts in my worker to load a separate "library" file, it works, but I get the error: ReferenceError: Can't find variable: importScripts (Safari) Uncaught ReferenceError: importScripts is not defined So it's throwing an error, but that
- [Bug 13254] what the hell is this
- [Bug 13254] New: what the hell is this
- Re: [WebIDL] remove modules
- [proposal] Local-Networked Service [Discovery and] Messaging API
- [WebIDL] remove modules
- Re: [websockets] Getting WebSockets API to Last Call
- Re: [websockets] Getting WebSockets API to Last Call
Wednesday, 13 July 2011
- Re: [IndexedDB] Client API state after calling deleteIndex and deleteObjectStore
- RE: [indexeddb] Should deleteDatabase return IDBVersionChangeRequest?
- RE: [IndexedDB] Client API state after calling deleteIndex and deleteObjectStore
- [Bug 11270] Interaction between in-line keys and key generators
- Re: [indexeddb] Behavior when calling IDBCursor.continue multiple times
- RE: [indexeddb] Behavior when calling IDBCursor.continue multiple times
- Re: [IndexedDB] Client API state after calling deleteIndex and deleteObjectStore
- [indexeddb] Client API state after calling deleteIndex and deleteObjectStore
- Client API state after calling deleteIndex and deleteObjectStore
- [Bug 13232] New: I think the section on DedicatedWorkerScope should include information about the kinds of data that postMessage can send to a worker, and the kinds of data that a worker can send back. http://dev.w3.org/html5/workers/#dedicated-workers-and-the-dedicatedwo
- Re: [widgets] Implementing the Storage Event for widget preferences
- Re: [widgets] Implementing the Storage Event for widget preferences
- [widgets] Implementing the Storage Event for widget preferences
- [WebIDL] platofmr array objects
- The algorithm to determine encoding for FileReader.readAsText() doesn't account for predefined content types
- Re: [indexeddb] Client API state after calling trasnaction.abort
- Re: [indexeddb] Client API state after calling trasnaction.abort
- [indexeddb] Client API state after calling trasnaction.abort
- RE: [indexeddb] Behavior when calling IDBCursor.continue multiple times
- Re: [indexeddb] Behavior when calling IDBCursor.continue multiple times
- [Bug 13229] New: The following text from the "Security considerations" part of "11 IANA considerations" is wrong: "An event stream from an origin distinct from the origin of the content consuming the event stream can result in information leakage. To avoid this, user agen
Tuesday, 12 July 2011
- RE: [indexeddb] Behavior when calling IDBCursor.continue multiple times
- [widgets] Interface Implementation report
- Re: Frame embedding: One problem, three possible specs?
- Re: [indexeddb] Effects of calling Cursor.Update() on an existing Index
- Re: [websockets] Getting WebSockets API to Last Call
- [indexeddb] Effects of calling Cursor.Update() on an existing Index
- RfC: Last Call Working Draft of the API for Media Resources 1.0; deadline August 7
- Last Call Working Drafts transition announcement of the API for Media Resources 1.0
- Re: Test suites and RFC2119
- RfC: Last Call Working Draft of Web IDL; deadline August 23
- Re: Overview of behavior attachment as a general problem on the Web
- Re: [indexeddb] Behavior when calling IDBCursor.continue multiple times
Monday, 11 July 2011
- [IndexedDB] setVersion is cra... is not good
- RE: [indexeddb] Count property on IDBCursor
- Re: [websockets] Getting WebSockets API to Last Call
- [Bug 12654] createIndex's options should include whether a field is optional/required
- Re: [XHR2] Blobs, names and FormData
- Fwd: Discontinuing UK and FR dial-in numbers for Zakim
- RE: [XHR2] Blobs, names and FormData
- Re: [XHR2] Blobs, names and FormData
- Re: [XHR2] Blobs, names and FormData
- RE: [indexeddb] Using WebIDL Dictionary in IDBObjectStore.createIndex for optionalParameters
- Re: [websockets] Getting WebSockets API to Last Call
- Re: [websockets] Getting WebSockets API to Last Call
- Re: [XHR2] Blobs, names and FormData
- Re: [websockets] Getting WebSockets API to Last Call
- Re: [websockets] Getting WebSockets API to Last Call
- Re: [websockets] Getting WebSockets API to Last Call
- Re: [websockets] Getting WebSockets API to Last Call
- Re: [websockets] Getting WebSockets API to Last Call
- Re: [websockets] Getting WebSockets API to Last Call
- RE: [XHR2] Blobs, names and FormData
- Re: [XHR2] Blobs, names and FormData
- Re: [XHR2] Blobs, names and FormData
- Re: [XHR2] Blobs, names and FormData
- RE: [XHR2] Blobs, names and FormData
- Re: [XHR2] Blobs, names and FormData
- Re: Test suites and RFC2119
- Re: [XHR2] Blobs, names and FormData
- Re: Test suites and RFC2119
- Re: [websockets] IETF HyBi current status and next steps
- Re: XHR using user and password parameters
- XHR using user and password parameters
- Re: [websockets] IETF HyBi current status and next steps
- Re: [XHR2] Blobs, names and FormData
- [widgets] Re: Call for Prior Art Related to US Patent 7,743,336 and US Patent Application 20070101146
- Re: CORS Findings
Sunday, 10 July 2011
Friday, 8 July 2011
Sunday, 10 July 2011
- Re: Test suites and RFC2119
- Re: Test suites and RFC2119
- Re: Test suites and RFC2119
- Re: Test suites and RFC2119
- Re: CfC: publish Last Call Working Draft of Web IDL; deadline July 7
- Re: CfC: publish Last Call Working Draft of Web IDL; deadline July 7
Saturday, 9 July 2011
- Re: Mutation events replacement
- Re: Where to discuss TR process issues? [Was: Re: [eventsource] Is Server-Sent Events ready for LC? ; deadline July 1
- Re: CfC: publish Last Call Working Draft of Web IDL; deadline July 7
- Re: Overview of behavior attachment as a general problem on the Web
- Re: Overview of behavior attachment as a general problem on the Web
Friday, 8 July 2011
- RE: [indexeddb] IDBRequest.transaction property set to null
- Re: [websockets] Getting WebSockets API to Last Call
- Re: [WebIDL] Exceptions
- Re: [indexeddb] IDBRequest.transaction property set to null
- Re: [websockets] Making optional extensions mandatory in the API (was RE: Getting WebSockets API to Last Call)
- [websockets] Making optional extensions mandatory in the API (was RE: Getting WebSockets API to Last Call)
- Re: [WebIDL] Exceptions
- Re: [WebIDL] Exceptions
- Call for Prior Art Related to US Patent 7,743,336 and US Patent Application 20070101146
- Re: [websockets] Getting WebSockets API to Last Call
- Overview of behavior attachment as a general problem on the Web
- Re: [websockets] Getting WebSockets API to Last Call
- [Bug 13178] binaryType should be immutable after connection is established
- [Bug 13104] 1) ping(msg); //allow client to send server ping as per websocket spec 2) onpong(); //allow client to receive response of ping
- Re: [WebIDL] Exceptions
- RE: [indexeddb] IDBRequest.transaction property set to null
- Re: Mutation events replacement
- RE: [indexeddb] IDBTransaction.oncomplete event type equals commit
- RE: [indexeddb] openCursor optional parameters issue
- Re: [WebIDL] Exceptions
- Re: Mutation events replacement
- Re: Mutation events replacement
- RE: [FileAPI] FileReader.readAsXXX when pased null
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: [eventsource] Is Server-Sent Events ready for LC? ; deadline July 1
- Re: [websockets] Getting WebSockets API to Last Call
- Re: Mutation events replacement
- Re: [WebIDL] Exceptions
- Re: [indexeddb] Calling update on a cursor index with a unique value constraint
- Re: [websockets] Getting WebSockets API to Last Call
- Re: [FileAPI] FileReader.readAsXXX when pased null
- Re: Mutation events replacement
- Re: [indexeddb] Calling update on a cursor index with a unique value constraint
- Re: Mutation events replacement
- RE: [indexeddb] Calling update on a cursor index with a unique value constraint
- Re: [indexeddb] openCursor optional parameters issue
- RE: [indexeddb] openCursor optional parameters issue
- Re: Mutation events replacement
Thursday, 7 July 2011
- Re: Mutation events replacement
- RE: Frame embedding: One problem, three possible specs?
- Re: Mutation events replacement
- RE: [websockets] Getting WebSockets API to Last Call
- Re: Mutation events replacement
- Re: [websockets] Getting WebSockets API to Last Call
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- RE: [indexeddb] Behavior when calling IDBCursor.continue multiple times
- Re: Mutation events replacement
- Re: Frame embedding: One problem, three possible specs?
- Re: Mutation events replacement
- Re: Mutation events replacement
- [websockets] Getting WebSockets API to Last Call
- Re: Mutation events replacement
- [Bug 13180] New: [Editorial] Causes that lead to failing the WebSocket connection, which results in an error event, should be more clearly specified
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Frame embedding: One problem, three possible specs?
- Re: Mutation events replacement
- Re: [indexeddb] Calling update on a cursor index with a unique value constraint
- Re: [indexeddb] Calling update on a cursor index with a unique value constraint
- Re: [WebIDL] Exceptions
- [Bug 13178] New: binaryType should be immutable after connection is established
- Re: [WebIDL] Exceptions
- RE: publish Last Call Working Draft of Web IDL; deadline July 7
- Re: [FileAPI] Updates to FileAPI Editor's Draft
- Re: Mutation events replacement
- Re: [WebIDL] Exceptions
- Re: [WebIDL] Exceptions
- Re: [WebIDL] Exceptions
- Re: [WebIDL] Exceptions
- [Bug 13172] New: The definition for [MessageEvent] is missing.
- Re: [FileAPI] FileReader.readAsXXX when pased null
- Re: [FileAPI] Updates to FileAPI Editor's Draft
- Re: [indexeddb] Calling update on a cursor index with a unique value constraint
- Re: [FileAPI] FileReader.readAsXXX when pased null
- Re: [indexeddb] IDBRequest.transaction property set to null
- Re: [WebIDL] Exceptions
- Re: [WebIDL] Exceptions
- [FileAPI] FileReader.readAsXXX when pased null
- Re: [WebIDL] Exceptions
- Re: [WebIDL] Exceptions
- RE: [XHR2] Blobs, names and FormData
- Re: Mutation events replacement
- Re: [WebIDL] Exceptions
Wednesday, 6 July 2011
- [Bug 11406] [IndexedDB] IDBDatabase.transaction needs to specify exception for invalid mode parameter
- Re: Where to discuss TR process issues? [Was: Re: [eventsource] Is Server-Sent Events ready for LC? ; deadline July 1
- Re: Where to discuss TR process issues? [Was: Re: [eventsource] Is Server-Sent Events ready for LC? ; deadline July 1
- Re: [eventsource] Is Server-Sent Events ready for LC? ; deadline July 1
- Re: [WebIDL] Exceptions
- Re: Mutation events replacement
- Where to discuss TR process issues? [Was: Re: [eventsource] Is Server-Sent Events ready for LC? ; deadline July 1
- Re: [eventsource] Is Server-Sent Events ready for LC? ; deadline July 1
- [Bug 12179] We should spec the order in which version change events fire
- Re: [WebIDL] Exceptions
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: [eventsource] Is Server-Sent Events ready for LC? ; deadline July 1
- [Bug 13162] New: The notes really do need to be cleaned up to be made explicit. Like WTH does this actually say? "The fail the WebSocket connection algorithm invokes the close the WebSocket connection algorithm, which then establishes that the WebSocket connection is clo
- RE: [indexeddb] IDBRequest.transaction property set to null
- [indexeddb] Calling update on a cursor index with a unique value constraint
- Re: [webstorage] Plan to move the spec to Last Call Working Draft
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Publishing From-Origin Proposal as FPWD
- Re: Mutation events replacement
- [Bug 13158] i dont understand this
- [Bug 13158] New: i dont understand this
- Re: [eventsource] Is Server-Sent Events ready for LC? ; deadline July 1
- [WebIDL] Exceptions
- Re: Publishing From-Origin Proposal as FPWD
- Re: Mutation events replacement
- Re: Mutation events replacement
- [Bug 13156] New: The charset parameter is now an optional parameter (even though it can only be set to UTF-8). That should probably be stated here.
- [Bug 13155] New: The security considerations section needs to be updated to take CORS into account.
- Re: [eventsource] Is Server-Sent Events ready for LC? ; deadline July 1
- Re: Mutation events replacement
- Re: Mutation events replacement
- RE: Publishing From-Origin Proposal as FPWD
- RE: [indexeddb] Using IDBDatabaseSync.close or IDBFactorySync.deleteDatabase inside transaction's callback method
- Re: Mutation events replacement
- Re: [indexeddb] Using IDBDatabaseSync.close or IDBFactorySync.deleteDatabase inside transaction's callback method
- Re: Mutation events replacement
- Re: Mutation events replacement
Tuesday, 5 July 2011
- [indexeddb] Using IDBDatabaseSync.close or IDBFactorySync.deleteDatabase inside transaction's callback method
- Re: Publishing From-Origin Proposal as FPWD
- Re: Mutation events replacement
- Re: Test suites and RFC2119
- Re: Mutation events replacement
- Re: Publishing From-Origin Proposal as FPWD
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Publishing From-Origin Proposal as FPWD
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- AUTO: Alain Vagner is out of the office. (returning 18/07/2011)
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: [eventsource] Is Server-Sent Events ready for LC? ; deadline July 1
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- [Bug 9653] How to handle nullable violations is not specified.
- [Bug 12234] [IndexedDB] Integrate with the HTML5 event loop
- Re: Mutation events replacement
- Re: Mutation events replacement
- CfC: publish FPWD of Cross-Origin Resource Embedding Exclusion; deadline July 12
- Re: Publishing From-Origin Proposal as FPWD
- [Bug 13146] hola como estan
- RE: Publishing From-Origin Proposal as FPWD
- [Bug 13146] New: hola como estan
- Re: Publishing From-Origin Proposal as FPWD
- Re: Publishing From-Origin Proposal as FPWD
- Re: [eventsource] Is Server-Sent Events ready for LC? ; deadline July 1
Monday, 4 July 2011
Tuesday, 5 July 2011
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
Monday, 4 July 2011
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Test suites and RFC2119
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Test suites and RFC2119
- Re: Test suites and RFC2119
- Re: Test suites and RFC2119
- Re: Test suites and RFC2119
- Test suites and RFC2119
- Re: Mutation events replacement
- Re: [widgets] What is the status and plan for Widget URI spec?
Sunday, 3 July 2011
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
Saturday, 2 July 2011
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: [XHR] setRequestHeader and redirects
- Re: [XHR2] Blobs, names and FormData
- Re: Mutation events replacement
- Re: Mutation events replacement
Friday, 1 July 2011
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- RE: Publishing From-Origin Proposal as FPWD
- [Bug 8241] Named properties on window
- Re: Publishing From-Origin Proposal as FPWD
- Re: [widgets] What is the status and plan for Widget URI spec?
- Re: Indicating certificate order in XML Dig Sig
- TPAC2011 Meeting Registration Open; 31Oct - 4 Nov @ Santa Clara, CA
- Re: [widgets] What is the status and plan for Widget URI spec?
- Re: CORS Security Question
- Re: CORS Security Question
- CORS Security Question
- Re: Mutation events replacement
- Re: Publishing From-Origin Proposal as FPWD
- Re: Component Models and Encapsulation (was Re: Component Model: Landing Experimental Shadow DOM API in WebKit)
- Re: [FileAPI] Updates to FileAPI Editor's Draft
- Re: Mutation events replacement