[Bug 17661] New: I would like to try this input box. Thanks
[Bug 17657] New: Empty arrays shouldn't be valid KeyPaths
[Bug 17656] New: Rewrite Blob constructor algorithm
WebIDL overload resolution, arrays and Nullable
- Re: WebIDL overload resolution, arrays and Nullable
- Re: WebIDL overload resolution, arrays and Nullable
[Bug 17653] New: <!doctype html> <html lang="ja"> <head> <meta charset="utf-8"> <title>撮影依頼 - ちくせいロケーションサービス「ちくロケ!」</title> <meta name="description" content="下記に必要事項をご記入のうえ、送信してください。お探しのイメージを出来るだけ詳細..." /> <meta name="keywords" content="撮影依頼,ロケ地,撮影,田園地帯, 学校撮影,=?U
[Bug 17652] New: Blob constructor: the blobParts array should probably not have nullable elements
[Bug 17650] New: Make createIndex throw InvalidAccessError instead of NotSupportedError
[Bug 17649] New: Address WebIDL comments from Kyle Huey
[Bug 17645] New: Define more precisely what the "origin" of the IDBEnvironment is
[Bug 17644] New: OK I spent hours all over the web and your docs getting to grips with websocket, my question now is this.... in the the handshake....how does one actually implement the header for the websocket? there is not explanation of this anywhere... how is the head
[Bug 17643] New: What should transaction.error be set to if a error handler throws an exception
RfC: LCWD of Selectors API Level 1; deadline July 19
[Bug 17609] New: [IndexedDB] Events fired after transaction abort should not set active flag
CfC: publish new WD of File API; deadline July 3
- Re: CfC: publish new WD of File API; deadline July 3
- RE: publish new WD of File API; deadline July 3
[IndexedDB] Null argument for optionalParameters?
Re: [FileAPI] File.slice spec bug
[Bug 16292] conflation of DOMString and deflated DOMString
Re: [XHR] Redirects
Fwd: TPAC 2012 Registration
Web Intent work scope
Selectors API Implementation Report
[websockets] Seeking comments on moving back to CR; deadline June 28
- Re: [websockets] Seeking comments on moving back to CR; deadline June 28
- [websockets] Seeking comments on moving back to CR; deadline July 9
[Shadow DOM] Shadown DOM and Regions CSSOM
Tags and origins (was: Re: Web Notifications)
Web Notifications
[IndexedDB] Extracting keys and null/undefined
[IndexedDB] Origins and document.domain
Fwd: IndieUI Call For Proposals
[Bug 17538] New: [IndexedDB] Remove error clauses for invalid index keys
[selectors-api] Consider backporting find() behavior to querySelector()
- Re: [selectors-api] Consider backporting find() behavior to querySelector()
- RE: [selectors-api] Consider backporting find() behavior to querySelector()
- Re: [selectors-api] Consider backporting find() behavior to querySelector()
- Re: [selectors-api] Consider backporting find() behavior to querySelector()
- Re: [selectors-api] Consider backporting find() behavior to querySelector()
- Re: [selectors-api] Consider backporting find() behavior to querySelector()
- Re: [selectors-api] Consider backporting find() behavior to querySelector()
- Bikesheds Re: [selectors-api] Consider backporting find() behavior to querySelector()
- Re: Bikesheds Re: [selectors-api] Consider backporting find() behavior to querySelector()
- Re: Bikesheds Re: [selectors-api] Consider backporting find() behavior to querySelector()
- Re: Bikesheds Re: [selectors-api] Consider backporting find() behavior to querySelector()
- Re: Bikesheds Re: [selectors-api] Consider backporting find() behavior to querySelector()
- Re: [selectors-api] Consider backporting find() behavior to querySelector()
CfC: publish a LCWD of Selectors API Level 1; deadline June 25
- Re: CfC: publish a LCWD of Selectors API Level 1; deadline June 25
- Re: CfC: publish a LCWD of Selectors API Level 1; deadline June 25
CfC: publish WD of Selectors API Level 2; deadline June 25
- RE: publish WD of Selectors API Level 2; deadline June 25
- Re: CfC: publish WD of Selectors API Level 2; deadline June 25
[selectors-api] NAMESPACE_ERR or SYNTAX_ERR when both applied
- Re: [selectors-api] NAMESPACE_ERR or SYNTAX_ERR when both applied
- Re: [selectors-api] NAMESPACE_ERR or SYNTAX_ERR when both applied
- Re: [selectors-api] NAMESPACE_ERR or SYNTAX_ERR when both applied
- Re: [selectors-api] NAMESPACE_ERR or SYNTAX_ERR when both applied
Browser Payments API proposal
Re: Should MutationObservers be able to observe work done by the HTML parser?
- Re: Should MutationObservers be able to observe work done by the HTML parser?
- Re: Should MutationObservers be able to observe work done by the HTML parser?
- Re: Should MutationObservers be able to observe work done by the HTML parser?
- Re: Should MutationObservers be able to observe work done by the HTML parser?
- Re: Should MutationObservers be able to observe work done by the HTML parser?
- Re: Should MutationObservers be able to observe work done by the HTML parser?
- Re: Should MutationObservers be able to observe work done by the HTML parser?
- Re: Should MutationObservers be able to observe work done by the HTML parser?
- Re: Should MutationObservers be able to observe work done by the HTML parser?
- Re: Should MutationObservers be able to observe work done by the HTML parser?
- Re: Should MutationObservers be able to observe work done by the HTML parser?
- Re: Should MutationObservers be able to observe work done by the HTML parser?
- Re: Should MutationObservers be able to observe work done by the HTML parser?
- Re: Should MutationObservers be able to observe work done by the HTML parser?
- Re: Should MutationObservers be able to observe work done by the HTML parser?
- Re: Should MutationObservers be able to observe work done by the HTML parser?
- Re: Should MutationObservers be able to observe work done by the HTML parser?
- Re: Should MutationObservers be able to observe work done by the HTML parser?
- Re: Should MutationObservers be able to observe work done by the HTML parser?
- Re: Should MutationObservers be able to observe work done by the HTML parser?
- Re: Should MutationObservers be able to observe work done by the HTML parser?
- Re: Should MutationObservers be able to observe work done by the HTML parser?
- Re: Should MutationObservers be able to observe work done by the HTML parser?
- Re: Should MutationObservers be able to observe work done by the HTML parser?
- Re: Should MutationObservers be able to observe work done by the HTML parser?
Updates to Selectors API
[Bug 17486] New: Whatsapp application can not connect to server
[Bug 17485] New: Whatsapp application can not connect to server
[IndexedDB] Exception inconsistency
[Bug 14569] URL object should not return DOMTokenList
www-dom vs public-webapps WAS: [DOM4] Mutation algorithm imposed order on document children
- RE: www-dom vs public-webapps WAS: [DOM4] Mutation algorithm imposed order on document children
- Re: www-dom vs public-webapps WAS: [DOM4] Mutation algorithm imposed order on document children
Web Activities: counter-proposal to Web Intents
- Re: Web Activities: counter-proposal to Web Intents
- Re: Web Activities: counter-proposal to Web Intents
[Bug 17467] New: Established in 2003, http://www.fashionskateshoes.com, was born out of the streets desire for urban biased fashion. When SUPRA,NIKE NEW BALANCE,GUCCI were causing waves in the early 2000's the fashion of hip hop and urban shoes came to the fore in a big w
[DOM4] Mutation algorithm imposed order on document children
- Re: [DOM4] Mutation algorithm imposed order on document children
- [DOM4] Mutation algorithm imposed order on document children
[IndexedDB] WebIDL-related spec nits
[Bug 17449] New: It is unclear to set type to be lower case in Blob constructor.
[QUOTA] Misleading example in Quota handling in storage API section
[IndexedDB] Key paths need to be specified better
[Bug 16557] Figure out bytes to code point mapping for statusText
[Bug 17437] New: Doc/mim70$slowac speed x 20(x20)mack test3.Gophertext.Rouder don't it Id!
CfC: publish FPWD of Quota Management API; deadline June 13
[webcomponents] Progress Update
[Bug 17321] New: Implementors should be aware that this specification is not stable. Implementors who are not taking part in the discussions are likely to find the specification changing out from under them in incompatible ways. Vendors interested in implementing this spe
[Bug 17311] New: The dictionary for GamepadEvent's ctor isn't defined
[Bug 17310] New: The target of gamepad(dis)connected events is not defined
[Bug 17309] New: It is not defined what the value of Gamepad.index should be after disconnecting the gamepad
[Bug 17308] New: Gamepad.id should be DOMString, not string
[Bug 17307] New: Investigate if double[] should be used for axes and buttons
[Bug 17306] New: The initial value of timestamp is not defined
Standards for Web applications on mobile devices: May 2012 updates
[Bug 17303] New: Fix editorial issues from Tobie
[IME] WebIDL bugs
[Bug 17300] New: the title of the section
[Bug 17299] New: the title of the section
Fullscreen events dispatched to elements
- Re: Fullscreen events dispatched to elements
[Bug 17277] New: [FileAPI] It have no clear behavior about negative index of FileList.item
[Bug 17276] New: Step 8 in versionchange transaction algorithm is wrong.
[Bug 17258] can range object support text/word/sentence based range setting?
[Bug 17266] New: You don't have permission to access /trouves on this server.
[Bug 17264] New: Add attributes to use ping/pong frames effectively
[Bug 17263] New: Keep on having send(ArrayBuffer data) interface in addition to send(ArrayBufferView data)
[Bug 17262] New: send function should have async interface
- [Bug 17262] send function should have async interface
- [Bug 17262] send function should have async interface
[Bug 17253] New: IDL typo
[IndexedDB] Normative content arguably informative in IndexedDB LC draft
[File API] Blob URI creation
[gamepad] events and misc.
[Bug 17242] New: Consider doing anonymous requests as a constructor argument rather than as a separate constructor
[Bug 17241] New: Editing API spec needs to be aware of PRE contents
CfC: Publish FPWD of Web Intents spec; deadline June 12
- RE: Publish FPWD of Web Intents spec; deadline June 12
- RE: Publish FPWD of Web Intents spec; deadline June 12
- Re: CfC: Publish FPWD of Web Intents spec; deadline June 12
IndexedDB: use of TypeError
[Bug 17236] New: Ambiguity in IDBTransaction.error around 'done' state
[admin] Mail List Policy, Usage, Etiquette, etc. & Top-posting
- Re: [admin] Mail List Policy, Usage, Etiquette, etc. & Top-posting
- Re: [admin] Mail List Policy, Usage, Etiquette, etc. & Top-posting
- Re: [admin] Mail List Policy, Usage, Etiquette, etc. & Top-posting
[Bug 17224] New: Possible typo in section 6: Ping and Pong Frames
[Bug 17222] New: treat status code 308 consistently with 301, 302, and 307
CfC: publish WD of DOM 3 Events; deadline June 4
IndexedDB: ambiguity around IDBTransaction.error
[Bug 17198] New: Remove mention of IDBVersionChangeRequest
[Bug 17196] New: (Note: Your IP address and user agent will be publicly recorded for spam prevention purposes.)
RE: DOM3 Events - additional editing help to move the spec forward
- Re: DOM3 Events - additional editing help to move the spec forward
[Bug 17192] New: Trying to find the music i downloaded
[Bug 17184] New: Please don't use section numbers as these tend to change rapidly and make your feedback harder to understand.
Proposal: Document.parse() [AKA: Implied Context Parsing]
- Re: Proposal: Document.parse() [AKA: Implied Context Parsing]
- Re: Proposal: Document.parse() [AKA: Implied Context Parsing]
- Re: Proposal: Document.parse() [AKA: Implied Context Parsing]
- Re: Proposal: Document.parse() [AKA: Implied Context Parsing]
http://www.w3.org/TR/2012/WD-url-20120524
RfC: LCWD of WebSocket API; deadline June 14
- Re: RfC: LCWD of WebSocket API; deadline June 14
- Reminder: RfC: LCWD of WebSocket API; deadline June 14
RfC: LCWD of Indexed Database; deadline June 21
- Reminder: RfC: LCWD of Indexed Database; deadline June 21
- Re: RfC: LCWD of Indexed Database; deadline June 21
Non-persistent in-memory storage accessible by same domain tabs
URL spec parameter-related methods use "parameter" in a way inconsistent with the URI RFC
- Re: URL spec parameter-related methods use "parameter" in a way inconsistent with the URI RFC
- Re: URL spec parameter-related methods use "parameter" in a way inconsistent with the URI RFC
Push API draft uploaded
- Re: Push API draft uploaded
- Re: Push API draft uploaded
- Re: Push API draft uploaded
- RE: Push API draft uploaded
- Re: Push API draft uploaded
- RE: Push API draft uploaded
- Re: Push API draft uploaded
- Re: Push API draft uploaded
- Re: Push API draft uploaded
- Re: Push API draft uploaded
- Re: Push API draft uploaded
- Re: Push API draft uploaded
- RE: Push API draft uploaded
- Re: Push API draft uploaded
- [Process] Publishing use cases and requirements as official docs
- Re: [Process] Publishing use cases and requirements as official docs
- Re: [Process] Publishing use cases and requirements as official docs
- Re: [Process] Publishing use cases and requirements as official docs
- Re: [Process] Publishing use cases and requirements as official docs
- Re: [Process] Publishing use cases and requirements as official docs
- Re: [Process] Publishing use cases and requirements as official docs
- Re: Push API draft uploaded
- RE: Push API draft uploaded
- Re: Push API draft uploaded
- RE: Push API draft uploaded
Re: [XHR] chunked
DOMParser Errors Should Be Exceptions
New list: System Applications
Howto spec
[wbs] response to 'Call for Review: Widget Interface is W3C Proposed Recommendation'
[wbs] response to 'Call for Review: Widget Interface is W3C Proposed Recommendation'
[wbs] response to 'Call for Review: Widget Interface is W3C Proposed Recommendation'
[File API] File behavior under modification
- Re: [File API] File behavior under modification
- Re: [File API] File behavior under modification
- Re: [File API] File behavior under modification
IndexedDB: Binary Keys
[Bug 17125] New: Add a FileList.drop(index) method
Proposal: add websocket close codes for "server not found" and/or "too many websockets open"
- Proposal: add websocket close codes for "server not found" and/or "too many websockets open"
- Re: Proposal: add websocket close codes for "server not found" and/or "too many websockets open"
- Re: Proposal: add websocket close codes for "server not found" and/or "too many websockets open"
[fullscreen] fullscreenEnabled and the fullscreen enabled flag
CfC: publish FPWD of Fullscreen spec; deadline May 24
- Re: CfC: publish FPWD of Fullscreen spec; deadline May 24
- Re: CfC: publish FPWD of Fullscreen spec; deadline May 24
- Re: CfC: publish FPWD of Fullscreen spec; deadline May 24
- Re: CfC: publish FPWD of Fullscreen spec; deadline May 24
- Re: CfC: publish FPWD of Fullscreen spec; deadline May 24
- Re: CfC: publish FPWD of Fullscreen spec; deadline May 24
- Re: CfC: publish FPWD of Fullscreen spec; deadline May 24
- Re: CfC: publish FPWD of Fullscreen spec; deadline May 24
- Re: CfC: publish FPWD of Fullscreen spec; deadline May 24
- Re: CfC: publish FPWD of Fullscreen spec; deadline May 24
- RE: CfC: publish FPWD of Fullscreen spec; deadline May 24
- Re: CfC: publish FPWD of Fullscreen spec; deadline May 24
- Re: CfC: publish FPWD of Fullscreen spec; deadline May 24
- RE: CfC: publish FPWD of Fullscreen spec; deadline May 24
- Re: CfC: publish FPWD of Fullscreen spec; deadline May 24
- Re: CfC: publish FPWD of Fullscreen spec; deadline May 24
- Re: CfC: publish FPWD of Fullscreen spec; deadline May 24
- Re: CfC: publish FPWD of Fullscreen spec; deadline May 24
- Re: CfC: publish FPWD of Fullscreen spec; deadline May 24
- Re: CfC: publish FPWD of Fullscreen spec; deadline May 24
Shrinking existing libraries as a goal
- Re: Shrinking existing libraries as a goal
- Re: Shrinking existing libraries as a goal
- Re: Shrinking existing libraries as a goal
- Re: Shrinking existing libraries as a goal
- Re: Shrinking existing libraries as a goal
- Re: Shrinking existing libraries as a goal
- Re: Shrinking existing libraries as a goal
- Re: Shrinking existing libraries as a goal
- Re: Shrinking existing libraries as a goal
- Re: Shrinking existing libraries as a goal
- Re: Shrinking existing libraries as a goal
- Re: Shrinking existing libraries as a goal
- Re: Shrinking existing libraries as a goal
- Re: Shrinking existing libraries as a goal
- Re: Shrinking existing libraries as a goal
- Re: Shrinking existing libraries as a goal
- Re: Shrinking existing libraries as a goal
- Re: Shrinking existing libraries as a goal
- Re: Shrinking existing libraries as a goal
- Spec Bugs and Test Suites [Was: Re: Shrinking existing libraries as a goal]
- Comments, Spec Bugs and Test Case are Always Welcome! [Was: Re: Shrinking existing libraries as a goal]
- Re: Shrinking existing libraries as a goal
- Re: Shrinking existing libraries as a goal
- Re: Shrinking existing libraries as a goal
- Re: Shrinking existing libraries as a goal
- Re: Shrinking existing libraries as a goal
- Re: Shrinking existing libraries as a goal
- Re: Shrinking existing libraries as a goal
- Re: Shrinking existing libraries as a goal
[Bug 17073] New: Dygear@gmail.com - Mark 'Dygear' Tomlin With the View Data Specification gaining maturity, I wanted to add something to it that I feel would make a huge impact on the power of Binary Data and Web Sockets. I was hoping that someone with quite a lot more kn
WebApps May F2F Minutes
Feedback on Quota Management API
- Re: Feedback on Quota Management API
- Re: Feedback on Quota Management API
- Re: Feedback on Quota Management API
- Re: Feedback on Quota Management API
- Re: Feedback on Quota Management API
- Re: Feedback on Quota Management API
- Re: Feedback on Quota Management API
- Re: Feedback on Quota Management API
- Re: Feedback on Quota Management API
- Re: Feedback on Quota Management API
- Re: Feedback on Quota Management API
- Re: Feedback on Quota Management API
- Re: Feedback on Quota Management API
- Re: Feedback on Quota Management API
- Re: Feedback on Quota Management API
- Re: Feedback on Quota Management API
- Re: Feedback on Quota Management API
- Re: Feedback on Quota Management API
- Re: Feedback on Quota Management API
- Re: Feedback on Quota Management API
- Re: Feedback on Quota Management API
- Re: Feedback on Quota Management API
- Re: Feedback on Quota Management API
- Re: Feedback on Quota Management API
- Re: Feedback on Quota Management API
- Re: Feedback on Quota Management API
- Re: Feedback on Quota Management API
exposing CANVAS or something like it to Web Workers
- Re: exposing CANVAS or something like it to Web Workers
- Re: exposing CANVAS or something like it to Web Workers
- Re: exposing CANVAS or something like it to Web Workers
- Re: exposing CANVAS or something like it to Web Workers
- Re: exposing CANVAS or something like it to Web Workers
- Re: exposing CANVAS or something like it to Web Workers
- Re: exposing CANVAS or something like it to Web Workers
- Re: exposing CANVAS or something like it to Web Workers
- Re: exposing CANVAS or something like it to Web Workers
- Re: exposing CANVAS or something like it to Web Workers
- Re: exposing CANVAS or something like it to Web Workers
- Re: exposing CANVAS or something like it to Web Workers
- Re: exposing CANVAS or something like it to Web Workers
- Re: exposing CANVAS or something like it to Web Workers
- Re: exposing CANVAS or something like it to Web Workers
- Re: exposing CANVAS or something like it to Web Workers
- Re: exposing CANVAS or something like it to Web Workers
- Re: exposing CANVAS or something like it to Web Workers
- Re: exposing CANVAS or something like it to Web Workers
- Re: exposing CANVAS or something like it to Web Workers
- Re: exposing CANVAS or something like it to Web Workers
- Re: exposing CANVAS or something like it to Web Workers
- Re: exposing CANVAS or something like it to Web Workers
[Bug 15494] Should Content-Transfer-Encoding be forbidden?
[Bug 17046] New: Implement redirect audit functionality for XHR
Re: Working with FormData as an object
[Bug 15765] Replaceable interface
[Bug 17042] New: Last-Event-ID is not a simple header
Review of Web Application Manifest Format and Management APIs
- Re: Review of Web Application Manifest Format and Management APIs
- [manifest] Parsing origins, was Re: Review of Web Application Manifest Format and Management APIs
- [manifest] screen sizes, Re: Review of Web Application Manifest Format and Management APIs
- RE: [manifest] screen sizes, Re: Review of Web Application Manifest Format and Management APIs
- Re: [manifest] screen sizes, Re: Review of Web Application Manifest Format and Management APIs
- Re: [manifest] screen sizes, Re: Review of Web Application Manifest Format and Management APIs
- Re: [manifest] screen sizes, Re: Review of Web Application Manifest Format and Management APIs
- Re: [manifest] screen sizes, Re: Review of Web Application Manifest Format and Management APIs
- RE: [manifest] screen sizes, Re: Review of Web Application Manifest Format and Management APIs
- Re: [manifest] screen sizes, Re: Review of Web Application Manifest Format and Management APIs
- RE: [manifest] screen sizes, Re: Review of Web Application Manifest Format and Management APIs
- Re: [manifest] screen sizes, Re: Review of Web Application Manifest Format and Management APIs
- Re: [manifest] screen sizes, Re: Review of Web Application Manifest Format and Management APIs
- Re: [manifest] screen sizes, Re: Review of Web Application Manifest Format and Management APIs
- Re: [manifest] screen sizes, Re: Review of Web Application Manifest Format and Management APIs
- Re: [manifest] screen sizes, Re: Review of Web Application Manifest Format and Management APIs
- Re: [manifest] screen sizes, Re: Review of Web Application Manifest Format and Management APIs
- Re: [manifest] screen sizes, Re: Review of Web Application Manifest Format and Management APIs
- Re: [manifest] screen sizes, Re: Review of Web Application Manifest Format and Management APIs
- RE: [manifest] screen sizes, Re: Review of Web Application Manifest Format and Management APIs
- Re: [manifest] screen sizes, Re: Review of Web Application Manifest Format and Management APIs
- Re: [manifest] screen sizes, Re: Review of Web Application Manifest Format and Management APIs
- Re: [manifest] screen sizes, Re: Review of Web Application Manifest Format and Management APIs
- Re: [manifest] screen sizes, Re: Review of Web Application Manifest Format and Management APIs
App Manifest & API Proposal
- Re: App Manifest & API Proposal
- Re: App Manifest & API Proposal
- RE: App Manifest & API Proposal
- Re: App Manifest & API Proposal
- Re: App Manifest & API Proposal
- [manifest] Is the Webapp Manifest spec ready for FPWD?
- Re: [manifest] Is the Webapp Manifest spec ready for FPWD?
- RE: [manifest] Is the Webapp Manifest spec ready for FPWD?
- Re: [manifest] Is the Webapp Manifest spec ready for FPWD?
- Re: [manifest] Is the Webapp Manifest spec ready for FPWD?
- Re: [manifest] Is the Webapp Manifest spec ready for FPWD?
Implied Context Parsing (DocumentFragment.innerHTML, or similar) proposal details to be sorted out
- Re: Implied Context Parsing (DocumentFragment.innerHTML, or similar) proposal details to be sorted out
- Re: Implied Context Parsing (DocumentFragment.innerHTML, or similar) proposal details to be sorted out
- Re: Implied Context Parsing (DocumentFragment.innerHTML, or similar) proposal details to be sorted out
- Re: Implied Context Parsing (DocumentFragment.innerHTML, or similar) proposal details to be sorted out
- Re: Implied Context Parsing (DocumentFragment.innerHTML, or similar) proposal details to be sorted out
- Re: Implied Context Parsing (DocumentFragment.innerHTML, or similar) proposal details to be sorted out
- Re: Implied Context Parsing (DocumentFragment.innerHTML, or similar) proposal details to be sorted out
- Re: Implied Context Parsing (DocumentFragment.innerHTML, or similar) proposal details to be sorted out
- Re: Implied Context Parsing (DocumentFragment.innerHTML, or similar) proposal details to be sorted out
- Re: Implied Context Parsing (DocumentFragment.innerHTML, or similar) proposal details to be sorted out
- Re: Implied Context Parsing (DocumentFragment.innerHTML, or similar) proposal details to be sorted out
- Re: Implied Context Parsing (DocumentFragment.innerHTML, or similar) proposal details to be sorted out
- Re: Implied Context Parsing (DocumentFragment.innerHTML, or similar) proposal details to be sorted out
- Re: Implied Context Parsing (DocumentFragment.innerHTML, or similar) proposal details to be sorted out
- Re: Implied Context Parsing (DocumentFragment.innerHTML, or similar) proposal details to be sorted out
- Re: Implied Context Parsing (DocumentFragment.innerHTML, or similar) proposal details to be sorted out
- Re: Implied Context Parsing (DocumentFragment.innerHTML, or similar) proposal details to be sorted out
- Re: Implied Context Parsing (DocumentFragment.innerHTML, or similar) proposal details to be sorted out
- Re: Implied Context Parsing (DocumentFragment.innerHTML, or similar) proposal details to be sorted out
- Re: Implied Context Parsing (DocumentFragment.innerHTML, or similar) proposal details to be sorted out
- Re: Implied Context Parsing (DocumentFragment.innerHTML, or similar) proposal details to be sorted out
- Re: Implied Context Parsing (DocumentFragment.innerHTML, or similar) proposal details to be sorted out
- Re: Implied Context Parsing (DocumentFragment.innerHTML, or similar) proposal details to be sorted out
- Re: Implied Context Parsing (DocumentFragment.innerHTML, or similar) proposal details to be sorted out
- Re: Implied Context Parsing (DocumentFragment.innerHTML, or similar) proposal details to be sorted out
- Re: Implied Context Parsing (DocumentFragment.innerHTML, or similar) proposal details to be sorted out
- Re: Implied Context Parsing (DocumentFragment.innerHTML, or similar) proposal details to be sorted out
- Re: Implied Context Parsing (DocumentFragment.innerHTML, or similar) proposal details to be sorted out
- Re: Implied Context Parsing (DocumentFragment.innerHTML, or similar) proposal details to be sorted out
- Re: Implied Context Parsing (DocumentFragment.innerHTML, or similar) proposal details to be sorted out
Media File System API
[admin] New wiki about Spec Editing
[Bug 10894] [pending URL spec] Reflecting an IDL attribute with a URL should try to canonicalize whatever value is set
[Bug 15765] Replaceable interface
[Bug 15254] Don't forbid underscore in host names in URLs
[Bug 14210] Reflecting href with a URL that doesn't resolve doesn't return the empty string in browsers (at least opera/moz, don't know what URL would fail to resolve in webkit). Instead it returns the value without resolving.
[Bug 14832] Check whether the encoding problems for query components applies to mailto: URLs and other non-HTTP URLs and see if we can change the definition of "valid URL" accordingly
[Bug 15684] [URL] Replacing backslash with forward slash in URIs doesn't seem to be necessitated by web compat
[Bug 11379] [pending URL spec] definition of hierarchical URL inconsistent with rfc 3986
[Bug 15718] Need to decide if URLs can ever fail to parse
[Bug 11587] [pending URL spec] window.location.hostname should remove brackets of IPv6 host
File constructor
[Bug 17032] New: IndexedDB: Editorial - use of phrase "explicit key" is confusing
XHR's setRequestHeader and the Do Not Track (DNT) header
- Re: XHR's setRequestHeader and the Do Not Track (DNT) header
- Re: XHR's setRequestHeader and the Do Not Track (DNT) header
[webcomponents] Use x:: instead of x-?
Adding a paint event to HTMLElement to support Web Components / Shadow DOM
- Re: Adding a paint event to HTMLElement to support Web Components / Shadow DOM
- Re: Adding a paint event to HTMLElement to support Web Components / Shadow DOM
Re: [EventSource] Question on event type
Re: [EventSource] Is the field name "event" supported in current browsers?
[Bug 16999] New: Clarify JS type for empty close reason
[admin] short-names and 1-liners for our 7 new FPWDs
- Re: [admin] short-names and 1-liners for our 7 new FPWDs
- Re: [admin] short-names and 1-liners for our 7 new FPWDs
Draft Minutes: 2 May 2012 f2f meeting
Draft Minutes: 1 May 2012 f2f meeting
RfC: 2 LCWDs "Performance Timeline" and "User Timing"; deadline June 7
CfC: publish LCWD of Indexed Database; deadline May 15
- Re: CfC: publish LCWD of Indexed Database; deadline May 15
- RE: CfC: publish LCWD of Indexed Database; deadline May 15
[Bug 14404] Version of an IDBDatabase from an aborted version change transaction needs to be specified
[Bug 16953] New: createObjectURL and oneTimeOnly behavior should be defined in terms of stable state
[Bug 16952] New: Add a Blob.close()
[Bug 16950] New: Throw SyntaxError instead of InvalidStateError for invalid content-type
Re: New tests submitted by Microsoft for WebApps specs
RE: [IndexedDB] Bug 14404: What happens when a versionchange transaction is aborted?
Typo in NotReadableError defintion?
[Bug 16933] New: In a good manner, sir/madaam, i am very disapointed that for how many months always asking my self what can i do my computer, and how to fixed it, shortly im not expert of computer.. my technician and my freind partners in crime.. my account was hacked si
[Bug 16934] New: In a good manner, sir/madaam, i am very disapointed that for how many months always asking my self what can i do my computer, and how to fixed it, shortly im not expert of computer.. my technician and my freind partners in crime.. my account was hacked si
[Bug 16932] New: In a good manner, sir/madaam, i am very disapointed that for how many months always asking my self what can i do my computer, and how to fixed it, shortly im not expert of computer.. my technician and my freind partners in crime.. my account was hacked si
[Bug 16931] New: In a good manner, sir/madaam, i am very disapointed that for how many months always asking my self what can i do my computer, and how to fixed it, shortly im not expert of computer.. my technician and my freind partners in crime.. my account was hacked si
[Bug 16930] New: I don't like public data
[Bug 16927] New: HTML reference was changed from W3C version to WHATWG version
[websockets] Moving Web Sockets back to LCWD; is 15210 a showstopper?
- Re: [websockets] Moving Web Sockets back to LCWD; is 15210 a showstopper?
- Re: [websockets] Moving Web Sockets back to LCWD; is 15210 a showstopper?
- CfC: publish LCWD of Web Sockets; deadline May 18
[admin] A Method for Writing Testable Conformance Requirements
Re: Offline Web Applications status
[IndexedDB] Bug 14404: What happens when a versionchange transaction is aborted?
- Re: [IndexedDB] Bug 14404: What happens when a versionchange transaction is aborted?
- Re: [IndexedDB] Bug 14404: What happens when a versionchange transaction is aborted?
CfC: publish FPWD of URL spec; deadline May 9
CfC: publish FPWD of Screen Orientation ; deadline May 9
CfC: publish FPWD of Input Method Editor (IME); deadline May 9
GamepadObserver (ie. MutationObserver + Gamepad)
- Re: GamepadObserver (ie. MutationObserver + Gamepad)
[Bug 16465] [IndexedDB] Error handling of db.transaction('mystore', 'some invalid value here') should be defined
[IndexedDB] Checked in fix for ReSpec issue
CfC: publish a FPWD of Web Components Explainer; deadline May 9
- Re: CfC: publish a FPWD of Web Components Explainer; deadline May 9
- Re: CfC: publish a FPWD of Web Components Explainer; deadline May 9
CfC: publish FPWD of Shadow DOM; deadline May 9
[Bug 16708] s/ArrayBuffer/ArrayBufferView/ - See http://lists.w3.org/Archives/Public/public-webapps/2012AprJun/0177.html
CfC: publish FPWD of Pointer Lock spec; deadline May 9
CfC: publish FPWD of Gamepad spec; deadline May 9
[Bug 16157] WebSocket shouldn't throw SyntaxError on unpaired surrogates
[Bug 15400] WebSocket Protocol reference needs updating
[Bug 16134] This spec should point out how to actually receive data. Afaik you need to access the message event's data property, but the spec doesn't mention that anywhere.
[Bug 15595] The abstract could be improved by pointing out that "WebSocket protocol" is defined by the IETF, while this API specifies the browser API to use that protocol. "The send(data) method transmits data using the connection. If the readyState attribute is CONN
CfC: to stop work on From-Origin spec; deadline May 8
ReSpec biblio
CfC: to stop work on XBL2; deadline May 8
- Re: CfC: to stop work on XBL2; deadline May 8
- Re: CfC: to stop work on XBL2; deadline May 8
- RE: CfC: to stop work on XBL2; deadline May 8
[webcomponents] Custom Elements Spec
- Re: [webcomponents] Custom Elements Spec
- Re: [webcomponents] Custom Elements Spec
- Re: [webcomponents] Custom Elements Spec
- Re: [webcomponents] Custom Elements Spec
- Re: [webcomponents] Custom Elements Spec
- Re: [webcomponents] Custom Elements Spec
- Re: [webcomponents] Custom Elements Spec
- Re: [webcomponents] Custom Elements Spec
- Re: [webcomponents] Custom Elements Spec
- Re: [webcomponents] Custom Elements Spec
- Re: [webcomponents] Custom Elements Spec
- Re: [webcomponents] Custom Elements Spec
- Re: [webcomponents] Custom Elements Spec
- Re: [webcomponents] Custom Elements Spec
- Re: [webcomponents] Custom Elements Spec
- Re: [webcomponents] Custom Elements Spec
- Re: [webcomponents] Custom Elements Spec
- Re: [webcomponents] Custom Elements Spec
- Re: [webcomponents] Custom Elements Spec
- Re: [webcomponents] Custom Elements Spec
- Re: [webcomponents] Custom Elements Spec
- Re: [webcomponents] Custom Elements Spec
- Re: [webcomponents] Custom Elements Spec
- Re: [webcomponents] Custom Elements Spec
- Re: [webcomponents] Custom Elements Spec
Clipboard API spec should specify beforecopy, beforecut, and beforepaste events
- Re: Clipboard API spec should specify beforecopy, beforecut, and beforepaste events
- Re: Clipboard API spec should specify beforecopy, beforecut, and beforepaste events
- Re: Clipboard API spec should specify beforecopy, beforecut, and beforepaste events
- Re: Clipboard API spec should specify beforecopy, beforecut, and beforepaste events
- Re: Clipboard API spec should specify beforecopy, beforecut, and beforepaste events
- Re: Clipboard API spec should specify beforecopy, beforecut, and beforepaste events
- Re: Clipboard API spec should specify beforecopy, beforecut, and beforepaste events
- Re: Clipboard API spec should specify beforecopy, beforecut, and beforepaste events
- Re: Clipboard API spec should specify beforecopy, beforecut, and beforepaste events
- Re: Clipboard API spec should specify beforecopy, beforecut, and beforepaste events
- Re: Clipboard API spec should specify beforecopy, beforecut, and beforepaste events
- Re: Clipboard API spec should specify beforecopy, beforecut, and beforepaste events
- Re: Clipboard API spec should specify beforecopy, beforecut, and beforepaste events
- Re: Clipboard API spec should specify beforecopy, beforecut, and beforepaste events
- Re: Clipboard API spec should specify beforecopy, beforecut, and beforepaste events
- Re: Clipboard API spec should specify beforecopy, beforecut, and beforepaste events
- Re: Clipboard API spec should specify beforecopy, beforecut, and beforepaste events
- Re: Clipboard API spec should specify beforecopy, beforecut, and beforepaste events
- Re: Clipboard API spec should specify beforecopy, beforecut, and beforepaste events
- Re: Clipboard API spec should specify beforecopy, beforecut, and beforepaste events
- Re: Clipboard API spec should specify beforecopy, beforecut, and beforepaste events
- Re: Clipboard API spec should specify beforecopy, beforecut, and beforepaste events
- Re: Clipboard API spec should specify beforecopy, beforecut, and beforepaste events
- Re: Clipboard API spec should specify beforecopy, beforecut, and beforepaste events
- Re: Clipboard API spec should specify beforecopy, beforecut, and beforepaste events
- Re: Clipboard API spec should specify beforecopy, beforecut, and beforepaste events
- Re: Clipboard API spec should specify beforecopy, beforecut, and beforepaste events
Re: Colliding FileWriters
Call for Implementations: HTML5 Web Messaging Candidate Recommendation
Call for Implementations: Web Workers Candidate Recommendation
[Bug 16894] New: Provide a high-level summary with examples
Invitation to connect on LinkedIn
[Server-Sent Events] Network connection clarification
[Bug 16883] New: Consider supporting some commands in plaintext editors
WebApps' new charter has been approved
CORS in Google App Engine
CORS in Google App Engine
[Bug 14086] 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
CfC: publish Candidate Recommendation of Widget Updates; deadline May 2
RfC: LCWD of Server-sent Events; deadline May 17
[Bug 16866] EOF is no longer valid as newline so "and the end of the file being the four ways in which a line can end" should be removed.
CORS: joint meeting of WebApps and WebAppSec next week?
- Re: CORS: joint meeting of WebApps and WebAppSec next week?
- Re: CORS: joint meeting of WebApps and WebAppSec next week?
[Bug 16846] New: cześc to ja rodzyn i wydaje mi się ze jestem na dość dobrej pozycji i w ogóle jestem super i jestem zajebisty ale nie czaje o co chodzi ty wszystklim ludzą skoro to ma tak wyglądać no to wydaje mi się że to będzie już koniec co wyu na no to ;;;
[DOM3 Events/DOM4] re-dispatching trusted events with initEvent
- Re: [DOM3 Events/DOM4] re-dispatching trusted events with initEvent
- Re: [DOM3 Events/DOM4] re-dispatching trusted events with initEvent
- RE: [DOM3 Events/DOM4] re-dispatching trusted events with initEvent
- Re: [DOM3 Events/DOM4] re-dispatching trusted events with initEvent
- Re: [DOM3 Events/DOM4] re-dispatching trusted events with initEvent
- Re: [DOM3 Events/DOM4] re-dispatching trusted events with initEvent
- Re: [DOM3 Events/DOM4] re-dispatching trusted events with initEvent
- Re: [DOM3 Events/DOM4] re-dispatching trusted events with initEvent
- Re: [DOM3 Events/DOM4] re-dispatching trusted events with initEvent
- Re: [DOM3 Events/DOM4] re-dispatching trusted events with initEvent
- RE: [DOM3 Events/DOM4] re-dispatching trusted events with initEvent
- Re: [DOM3 Events/DOM4] re-dispatching trusted events with initEvent
- Re: [DOM3 Events/DOM4] re-dispatching trusted events with initEvent
[Bug 16840] New: i vear shiad but lagbar mypassword
[Bug 16833] New: consider always exposing a "length" property for objects with indexed properties
[webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- History Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
- Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML
Custom Tags and Local Semantics
CfC: publish Proposed Recommendation of Widget Interface; deadline April 26
[widgets] HTML5 dependency blocking Widget Interface Proposed Recommendation
- Re: [widgets] HTML5 dependency blocking Widget Interface Proposed Recommendation
- Re: [widgets] HTML5 dependency blocking Widget Interface Proposed Recommendation
- Re: [widgets] HTML5 dependency blocking Widget Interface Proposed Recommendation
- Re: [widgets] HTML5 dependency blocking Widget Interface Proposed Recommendation
- Re: [widgets] HTML5 dependency blocking Widget Interface Proposed Recommendation
- Re: [widgets] HTML5 dependency blocking Widget Interface Proposed Recommendation
- Re: [widgets] HTML5 dependency blocking Widget Interface Proposed Recommendation
- Re: [widgets] HTML5 dependency blocking Widget Interface Proposed Recommendation
- Re: [widgets] HTML5 dependency blocking Widget Interface Proposed Recommendation
- Re: [widgets] HTML5 dependency blocking Widget Interface Proposed Recommendation
- Re: [widgets] HTML5 dependency blocking Widget Interface Proposed Recommendation
- Re: [widgets] HTML5 dependency blocking Widget Interface Proposed Recommendation
- Re: [widgets] HTML5 dependency blocking Widget Interface Proposed Recommendation
- Re: [widgets] HTML5 dependency blocking Widget Interface Proposed Recommendation
- Re: [widgets] HTML5 dependency blocking Widget Interface Proposed Recommendation
- Re: [widgets] HTML5 dependency blocking Widget Interface Proposed Recommendation
[XHR] Authentication prompt during send()
[CORS] Applying preflight cache to an entire domain?
Request for FormData.remove() method
- Re: Request for FormData.remove() method
- Re: Request for FormData.remove() method
[Server-Sent Events] Infinite reconnection clarification
- [EventSource] Make it available in Worker
- Re: [Server-Sent Events] Infinite reconnection clarification
- Re: [Server-Sent Events] Infinite reconnection clarification
Re: IndexedDB: Retrieving A Slice Of A Record Value.
IndexedDB: Retrieving a slice of a record value.
[Bug 16749] New: Remove note about old slice
CfC: publish LCWD of Server-sent Events; deadline April 23
[Bug 16746] New: Syntax check 'type' in Blob constructor
[Bug 16733] New: Drop 'endings'?
[Bug 16732] New: Use ArrayBufferView instead of ArrayBuffer in Blob constructor
[Bug 16731] New: Define when "native" ending conversion happens
[Bug 16730] New: Shared workers - use .source instead of .ports[0] ?
[Bug 16729] New: Make endings an enum
[Bug 16728] New: Blob.type
[Bug 16727] New: Remove "If an invalid key is used or if the dictionary argument is invalid, user agents MUST throw an InvalidStateError."
[Bug 16726] New: Remove quotes in "transparent" and "native" values
[Bug 16724] New: Blob without arguments underdefined
[Bug 16723] New: Bogus requirement in Blob constructor
[Bug 16722] New: Add references to bugzilla from the spec
[Bug 16721] New: Blob constructor with wrong args
BlobBuilder.append() should take ArrayBufferView in addition to ArrayBuffer
- Re: BlobBuilder.append() should take ArrayBufferView in addition to ArrayBuffer
- Re: BlobBuilder.append() should take ArrayBufferView in addition to ArrayBuffer
- Re: BlobBuilder.append() should take ArrayBufferView in addition to ArrayBuffer
- Re: BlobBuilder.append() should take ArrayBufferView in addition to ArrayBuffer
- Re: BlobBuilder.append() should take ArrayBufferView in addition to ArrayBuffer
- Re: BlobBuilder.append() should take ArrayBufferView in addition to ArrayBuffer
- Re: BlobBuilder.append() should take ArrayBufferView in addition to ArrayBuffer
- Re: BlobBuilder.append() should take ArrayBufferView in addition to ArrayBuffer
- Re: BlobBuilder.append() should take ArrayBufferView in addition to ArrayBuffer
- Re: BlobBuilder.append() should take ArrayBufferView in addition to ArrayBuffer
- Re: BlobBuilder.append() should take ArrayBufferView in addition to ArrayBuffer
- Re: BlobBuilder.append() should take ArrayBufferView in addition to ArrayBuffer
- Re: BlobBuilder.append() should take ArrayBufferView in addition to ArrayBuffer
- Re: BlobBuilder.append() should take ArrayBufferView in addition to ArrayBuffer
- Re: BlobBuilder.append() should take ArrayBufferView in addition to ArrayBuffer
- Re: BlobBuilder.append() should take ArrayBufferView in addition to ArrayBuffer
- Re: BlobBuilder.append() should take ArrayBufferView in addition to ArrayBuffer
- Re: BlobBuilder.append() should take ArrayBufferView in addition to ArrayBuffer
- Re: BlobBuilder.append() should take ArrayBufferView in addition to ArrayBuffer
- Re: BlobBuilder.append() should take ArrayBufferView in addition to ArrayBuffer
[Bug 16715] New: IndexedDB: Spec nit in steps for evaluating key path
[Bug 16714] New: IndexedDB: creating an object store with Array-type key path and key generator should be forbidden
IndexedDB user's feedback
Reminder: RfC: LCWD of Widget Updates; deadline April 19
Speech API: first editor's draft posted
[Bug 16708] s/ArrayBuffer/ArrayBufferView/ - See http://lists.w3.org/Archives/Public/public-webapps/2012AprJun/0177.html
[Bug 16303] meaning of "all" charset parameters of content-type header
[Bug 16303] meaning of "all" charset parameters of content-type header
[Bug 16707] New: user/password set to undefined means missing
[Bug 16303] meaning of "all" charset parameters of content-type header
IndexedDB: Key generators (autoIncrement) and Array-type key paths
[Bug 16703] New: I am suggesting a default value for the "code" argument to the close method. I am currently experimenting with this method and noticed that Chrome and Firefox seem to use different default values. If I do not specify a code, Chrome appears to use 1005 (
Should send() be able to take an ArrayBufferView?
- Re: Should send() be able to take an ArrayBufferView?
- Re: Should send() be able to take an ArrayBufferView?
- Re: Should send() be able to take an ArrayBufferView?
- Re: Should send() be able to take an ArrayBufferView?
- Re: Should send() be able to take an ArrayBufferView?
[XHR2] undefined as user/password arguments
[XHR] XMLHttpRequest.send("")
- Re: [XHR] XMLHttpRequest.send("")
[DOM4] Question about collections versus maps
Exceptions for DOM-XPath
Re: informal survey - on spec philosophy
Re: Delay in File * spec publications in /TR/ [Was: CfC: publish LCWD of File API; deadline March 3]
- Re: Delay in File * spec publications in /TR/ [Was: CfC: publish LCWD of File API; deadline March 3]
New public mailing list for discussions on potential NFC work at W3C
RE: File API "oneTimeOnly" is too poorly defined
[Bug 16665] New: kk gd df d fgd f gd gdg
Reminder: May 1-2 f2f meeting: registration deadline is April 16
- Web Intents on WebApps' May 1-2 f2f meeting agenda?
- Re: Reminder: May 1-2 f2f meeting: registration deadline is April 16
- Reminder: May 1-2 f2f meeting: registration deadline is April 16
[IndexedDB] Full text search?
[Bug 16653] New: IndexedDB: Define overloads for IDBDatabase.transaction()
Draft report for offline apps workshop
[Bug 8406] Stricter Specifications on Mouse Events Specifically primary, auxillary, and secondary default actions
[Bug 16451] Clarify the order of the documents
[Bug 16449] requestFullScreen() terminates at the wrong place
Fwd: ACTION-623: Notify TAG when a Last Call Working Draft of CORS or UMP is published (Web Applications Working Group)
[Bug 16639] New: tr hrt hrt rth rt trr tr rt
[editing] input event should have a data property WAS: [D3E] Where did textInput go?
Shared workers - use .source instead of .ports[0] ?
- Re: Shared workers - use .source instead of .ports[0] ?
- Re: Shared workers - use .source instead of .ports[0] ?
- Re: Shared workers - use .source instead of .ports[0] ?
- Re: Shared workers - use .source instead of .ports[0] ?
- Re: Shared workers - use .source instead of .ports[0] ?
- Re: Shared workers - use .source instead of .ports[0] ?
- Re: Shared workers - use .source instead of .ports[0] ?
- Re: Shared workers - use .source instead of .ports[0] ?
- Re: Shared workers - use .source instead of .ports[0] ?
- Re: Shared workers - use .source instead of .ports[0] ?
- Re: Shared workers - use .source instead of .ports[0] ?
- Re: Shared workers - use .source instead of .ports[0] ?
- Re: Shared workers - use .source instead of .ports[0] ?
- Re: Shared workers - use .source instead of .ports[0] ?
- Re: Shared workers - use .source instead of .ports[0] ?
- Re: Shared workers - use .source instead of .ports[0] ?
CfC: publish Candidate Recommendation of HTML5 Web Messaging; deadline April 11
CfC: publish Candidate Recommendation of Web Workers; deadline April 11
Warnings for old DOM specifications
- Re: Warnings for old DOM specifications
- CfC: Add warnings to old DOM specifications; deadline April 18
Workshop IHM
TransAnn: CORS published as Last Call Working Draft
Speech API Community Group
FYI: Speech API Community Group Proposed
[Clipboard] Mathematical Proofs in HTML5 Documents
Re: Adding Web Intents to the Webapps WG deliverables
Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
- Re: [webcomponents] HTML Parsing and the <template> element
[Bug 16469] storage event for clear() is defined to have |key| set to null, but |key| is not nullable
Reminder: May face-to-face meetings for HTML and WebApps
Re: [XHR] Constructor behavior seems to be underdefined
- Re: [XHR] Constructor behavior seems to be underdefined
- Re: [XHR] Constructor behavior seems to be underdefined
- Re: [XHR] Constructor behavior seems to be underdefined
- Re: [XHR] Constructor behavior seems to be underdefined
- Re: [XHR] Constructor behavior seems to be underdefined
- Re: [XHR] Constructor behavior seems to be underdefined
- Re: [XHR] Constructor behavior seems to be underdefined
- Re: [XHR] Constructor behavior seems to be underdefined
- Re: [XHR] Constructor behavior seems to be underdefined
- Re: [XHR] Constructor behavior seems to be underdefined
- Re: [XHR] Constructor behavior seems to be underdefined
- Re: [XHR] Constructor behavior seems to be underdefined
- Re: [XHR] Constructor behavior seems to be underdefined
- Re: [XHR] Constructor behavior seems to be underdefined
- Re: [XHR] Constructor behavior seems to be underdefined
- Re: [XHR] Constructor behavior seems to be underdefined
- Re: [XHR] Constructor behavior seems to be underdefined
- Re: [XHR] Constructor behavior seems to be underdefined
- Re: [XHR] Constructor behavior seems to be underdefined