Wednesday, 30 September 2009
- Re: ISSUE-41/ACTION-97 decentralized-extensibility
- Re: ISSUE-41/ACTION-97 decentralized-extensibility
- Re: ISSUE-41/ACTION-97 decentralized-extensibility
- RE: ISSUE-41/ACTION-97 decentralized-extensibility
- Integrated Philip Taylor's RDFa tests for XHTML, HTML4, HTML5
- RE: Create HTML Accessibility Task Force
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 1)
- [Bug 7776] rename appcache events?
- [Bug 7765] Maybe progress should be named fetchcachefile or some such
- Re: CfC: Create HTML Accessibility Task Force
- RE: Create HTML Accessibility Task Force
- Re: Agenda for HTML WG telcon 2009-09-24 - CfCs, Accessibility TF, Testing TF, etc.
- RE: Agenda for HTML WG telcon 2009-09-24 - CfCs, Accessibility TF, Testing TF, etc.
- Re: [Bug 7727] legacy doc type does not need to be discouraged by "SHOULD NOT"
- Re: [Bug 7727] legacy doc type does not need to be discouraged by "SHOULD NOT"
- [Bug 7727] legacy doc type does not need to be discouraged by "SHOULD NOT"
- Call for volunteers: Testing task force facilitator
- Call for volunteers: Accessiblity task force facilitator
Tuesday, 29 September 2009
- CfC: Create HTML Accessibility Task Force
- CfC: Create Testing Task Force
- Re: ISSUE-81 (resource vs representation)
- [Bug 7760] appcache event summary for error is wrong
- [Bug 7757] The "application cache update process" does not take a browsing context as argument. Do you mean the pass the active document as cache host? It should be more explicit about what is what.
- [Bug 7759] The "application cache update process" does not take a single application cache as argument. It takes an application cache group. This means the "If document was loaded from an application cache" step is wrong.
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 1)
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 1)
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 1)
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 1)
- [Bug 7727] legacy doc type does not need to be discouraged by "SHOULD NOT"
- [Bug 7734] open being an attribute of the section rather than the content area means you can never use this to mark up content which has multiple control/detail areas which are opened or closed independently like tabs or accordion
- [Bug 7735] perhaps open could be an int rather than boolean, indicating which content area was open to make using this model for tabs easier
- [Bug 7736] add tooltip attribute & keep title for other uses
- [Bug 7740] Authoring advice for canvas is bad for accessibility
- [Bug 7744] Is sniffing required?
- [Bug 7746] <link rel=search> should be used instead of <input type=search> for backwards-compatibility and beacuse the search input type poses no additional input restrictions.
- Re: ISSUE-81 (resource vs representation)
- Re: ISSUE-81 (resource vs representation)
- Re: ISSUE-81 (resource vs representation)
- [Bug 7633] The use of @summary should be encouraged when circumstances warrant
- [Bug 7512] suggested "replacement" for head/@profile does not work
- [Bug 7657] Redefining dt and dd
- Re: ISSUE-81 (resource vs representation)
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 1)
- Re: ISSUE-81 (resource vs representation)
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 1)
- Re: ISSUE-81 (resource vs representation)
Monday, 28 September 2009
- Re: ISSUE-81 (resource vs representation)
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 1)
- Re: ISSUE-81 (resource vs representation)
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 1)
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 1)
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 1)
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 1)
- Re: ISSUE-81 (resource vs representation)
- Re: ISSUE-81 (resource vs representation)
- New Scripting Coordination List Set Up
- Re: ISSUE-81 (resource vs representation)
- Re: ISSUE-81 (resource vs representation)
- Re: ISSUE-81 (resource vs representation)
- Re: ISSUE-81 (resource vs representation)
- Re: ISSUE-81 (resource vs representation)
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 1)
- Re: ISSUE-81 (resource vs representation)
- Re: ISSUE-81 (resource vs representation)
- Re: ISSUE-81 (resource vs representation)
- [Bug 7011] [in off-bug discussion] canvas accessible fallback provision is under specified
- Re: ISSUE-81 (resource vs representation)
- Re: ISSUE-81 (resource vs representation)
- Re: ISSUE-81 (resource vs representation)
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 1)
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 1)
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 1)
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 1)
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 1)
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 1)
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 1)
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 1)
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 1)
- Re: ISSUE-81 (resource vs representation)
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 1)
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 1)
- Re: ISSUE-81 (resource vs representation)
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 1)
- Re: ISSUE-81 (resource vs representation)
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 1)
- Re: ISSUE-81 (resource vs representation)
- Re: ISSUE-81 (resource vs representation)
- Re: ISSUE-81 (resource vs representation)
- Re: Localized decimal separator for numbers in <meter> textContent
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 1)
- Localized decimal separator for numbers in <meter> textContent
- Re: ISSUE-81 (resource vs representation)
- Re: ISSUE-81 (resource vs representation)
- RE: ISSUE-81 (resource vs representation)
- Re: ISSUE-81 (resource vs representation)
- Re: ISSUE-81 (resource vs representation)
- ISSUE-55: Re-enable @profile in HTML5 (draft 1)
Sunday, 27 September 2009
- Re: Web IDL Garden Hose (was: ECMA TC 39 / W3C HTML and WebApps WG coordination)
- Re: ISSUE-81 (resource vs representation)
- Re: Cross posting madness must stop.
- Re: Web IDL Garden Hose
- Re: Web IDL Garden Hose (was: ECMA TC 39 / W3C HTML and WebApps WG coordination)
- Re: Web IDL Garden Hose
- Re: Web IDL Garden Hose (was: ECMA TC 39 / W3C HTML and WebApps WG coordination)
- Re: Cross posting madness must stop.
- Fwd: Cross posting madness must stop.
- Re: Web IDL Garden Hose
- Re: Cross posting madness must stop.
- Re: ISSUE-81 (resource vs representation)
- Re: Web IDL Garden Hose (was: ECMA TC 39 / W3C HTML and WebApps WG coordination)
- Fwd: Web IDL Garden Hose
- Re: Web IDL Garden Hose
- Re: Web IDL Garden Hose (was: ECMA TC 39 / W3C HTML and WebApps WG coordination)
- Cross posting madness must stop.
- Re: Web IDL Garden Hose
- Re: ISSUE-81 (resource vs representation)
- Re: Web IDL Garden Hose (was: ECMA TC 39 / W3C HTML and WebApps WG coordination)
- Re: ISSUE-81 (resource vs representation)
- Re: Web IDL Garden Hose
- Re: ISSUE-81 (resource vs representation)
- Re: ISSUE-81 (resource vs representation)
- Re: ISSUE-81 (resource vs representation)
- Re: ISSUE-81 (resource vs representation)
- Very nice talk about HTML5
- Re: ISSUE-81 (resource vs representation)
- Re: ISSUE-81 (resource vs representation)
- Re: ISSUE-81 (resource vs representation)
- Re: Web IDL Garden Hose (was: ECMA TC 39 / W3C HTML and WebApps WG coordination)
- Re: ISSUE-81 (resource vs representation)
- Re: ISSUE-81 (resource vs representation)
- ISSUE-81 (resource vs representation)
- W3C process: was: ECMA TC 39 / W3C HTML and WebApps WG coordination
- Re: Web IDL Garden Hose (was: ECMA TC 39 / W3C HTML and WebApps WG coordination)
- Re: Web IDL Garden Hose (was: ECMA TC 39 / W3C HTML and WebApps WG coordination)
- Re: Web IDL Garden Hose (was: ECMA TC 39 / W3C HTML and WebApps WG coordination)
- Re: Web IDL Garden Hose (was: ECMA TC 39 / W3C HTML and WebApps WG coordination)
- Re: Web IDL Garden Hose (was: ECMA TC 39 / W3C HTML and WebApps WG coordination)
- RE: Web IDL Garden Hose (was: ECMA TC 39 / W3C HTML and WebApps WG coordination)
- Re: Removing <source> should make resource selection not fire 'error' on it
- Re: Web IDL Garden Hose (was: ECMA TC 39 / W3C HTML and WebApps WG coordination)
- Re: Web IDL Garden Hose (was: ECMA TC 39 / W3C HTML and WebApps WG coordination)
- Re: Web IDL Garden Hose (was: ECMA TC 39 / W3C HTML and WebApps WG coordination)
- RE: Web IDL Garden Hose (was: ECMA TC 39 / W3C HTML and WebApps WG coordination)
Saturday, 26 September 2009
- Re: WebIDL
- Re: Web IDL Garden Hose (was: ECMA TC 39 / W3C HTML and WebApps WG coordination)
- Re: Web IDL Garden Hose (was: ECMA TC 39 / W3C HTML and WebApps WG coordination)
- Re: Web IDL Garden Hose (was: ECMA TC 39 / W3C HTML and WebApps WG coordination)
- Re: Web IDL Garden Hose (was: ECMA TC 39 / W3C HTML and WebApps WG coordination)
- Re: Web IDL Garden Hose (was: ECMA TC 39 / W3C HTML and WebApps WG coordination)
- Re: Web IDL Garden Hose (was: ECMA TC 39 / W3C HTML and WebApps WG coordination)
- Re: Web IDL Garden Hose (was: ECMA TC 39 / W3C HTML and WebApps WG coordination)
- Re: Web IDL Garden Hose (was: ECMA TC 39 / W3C HTML and WebApps WG coordination)
- Re: Web IDL Garden Hose (was: ECMA TC 39 / W3C HTML and WebApps WG coordination)
- Re: WebIDL
- RE: Web IDL Garden Hose (was: ECMA TC 39 / W3C HTML and WebApps WG coordination)
- Re: WebIDL
- Re: WebIDL
- Re: Web IDL Garden Hose (was: ECMA TC 39 / W3C HTML and WebApps WG coordination)
- Re: WebIDL
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
- Re: Web IDL Garden Hose (was: ECMA TC 39 / W3C HTML and WebApps WG coordination)
- Re: Moving HTML+RDFa draft issues to HTML WG bug tracker
- RE: Web IDL Garden Hose (was: ECMA TC 39 / W3C HTML and WebApps WG coordination)
- Moving HTML+RDFa draft issues to HTML WG bug tracker
- Re: WebIDL
- Re: WebIDL
- Re: Web IDL Garden Hose (was: ECMA TC 39 / W3C HTML and WebApps WG coordination)
- Re: WebIDL
- Re: WebIDL
- Re: Web IDL Garden Hose (was: ECMA TC 39 / W3C HTML and WebApps WG coordination)
- Re: WebIDL
- Re: Web IDL Garden Hose (was: ECMA TC 39 / W3C HTML and WebApps WG coordination)
- Re: WebIDL
- Re: Web IDL Garden Hose (was: ECMA TC 39 / W3C HTML and WebApps WG coordination)
- Re: Web IDL Garden Hose (was: ECMA TC 39 / W3C HTML and WebApps WG coordination)
- Re: WebIDL
- Re: WebIDL
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
- Re: WebIDL
- Re: WebIDL
- Re: WebIDL
- Re: Web IDL Garden Hose (was: ECMA TC 39 / W3C HTML and WebApps WG coordination)
- Re: Web IDL Garden Hose (was: ECMA TC 39 / W3C HTML and WebApps WG coordination)
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
- Re: WebIDL
- Re: Web IDL Garden Hose (was: ECMA TC 39 / W3C HTML and WebApps WG coordination)
- WebIDL
- RE: ECMA TC 39 / W3C HTML and WebApps WG coordination
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
Friday, 25 September 2009
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
- RE: <keygen> element
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
- RE: aria mappings
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
- RE: ECMA TC 39 / W3C HTML and WebApps WG coordination
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
- Re: ACTION-137 on URI/IRI/URL
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
Thursday, 24 September 2009
- Re: Web IDL Garden Hose
- Re: Web IDL Garden Hose (was: ECMA TC 39 / W3C HTML and WebApps WG coordination)
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
- Web IDL Garden Hose (was: ECMA TC 39 / W3C HTML and WebApps WG coordination)
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
- Re: ACTION-137 on URI/IRI/URL
- Re: Protocol feature sets and specification clarity
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
- ACTION-137 on URI/IRI/URL
- Re: ECMA TC 39 / W3C HTML and WebApps WG coordination
- ECMA TC 39 / W3C HTML and WebApps WG coordination
- [Bug 7542] Remove Section 5. Microdata
- [Bug 7687] Use "representation" instead of "resource" in �6.9
- [Bug 7688] 'input type=time' forbids legitimate use case
- [Bug 7689] Cache-defeating semantics are not defined
- [Bug 7690] Incompletely defined priority of fallback over explicit entries
- [Bug 6853] restore meta keywords, search engines use them
- [Bug 7704] It is better to implement canvas.clear() method and allow to resize canvas without clearing it
- Re: How to track issues that block PR but not Last Call (was Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03)
- Re: ISSUE-13: handling-http-401-status - suggest closing on 2009-08-20
- Re: CfC: declare WebSockets out of scope
- Protocol feature sets and specification clarity
- Re: aria mappings
- Re: aria mappings
- Re: aria mappings
- [Bug 7715] Tests not archived
Wednesday, 23 September 2009
- RE: HTML WG Testing Task Force
- Re: Pre-TPAC HTML5 Video Accessibility Workshop November 1
- additional aria native semantics
- Re: dt/dd in figure/details has killer rendering issues in ie6 and
- (aria-*) role and other values
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: dt/dd in figure/details has killer rendering issues in ie6 and
- aria and multiple roles
- Re: Accessibility Task Force
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: aria mappings
- Aria-* vs html attributes and reflection
- RE: Pre-TPAC HTML5 Video Accessibility Workshop November 1
- WindowProxy
- Re: section/article grouping and CSS [was: Re: what is dt?]
- section/article grouping and CSS [was: Re: what is dt?]
- RE: <keygen> element
- Re: What attributes are required on the <sytle> element?
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: What attributes are required on the <sytle> element?
- Re: What attributes are required on the <sytle> element?
- What attributes are required on the <sytle> element?
- Re: dt/dd in figure/details has killer rendering issues in ie6 and
- Re: dt/dd in figure/details has killer rendering issues in ie6 and
- Re: Accessibility Task Force
- draft agenda for IRI working group BOF, and draft charter for IRI
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- [Bug 7709] Prevent PUT/DELETE cross-origin
- Re: Accessibility Task Force
- Pre-TPAC HTML5 Video Accessibility Workshop November 1
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: <keygen> element
Tuesday, 22 September 2009
Wednesday, 23 September 2009
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: HTML5 RDFa Test Suite (was Re: Request to publish HTML+RDFa (draft 3) as FPWD)
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: aria mappings
- Re: aria mappings
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: itemheader names <h>
- Re: itemheader names <h>
- Re: aria mappings
- Re: dt/dd in figure/details has killer rendering issues in ie6 and
- Re: itemheader names <h>
- Re: itemheader names <h>
- aria mappings
Tuesday, 22 September 2009
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: HTML5 RDFa Test Suite (was Re: Request to publish HTML+RDFa (draft 3) as FPWD)
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- FW: Agenda for HTML WG telcon 2009-09-24 - CfCs, Accessibility TF, Testing TF, etc.
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- RE: Accessibility Task Force
- Re: itemheader names <h>
- Re: itemheader names <h>
- itemheader names <h>
- Re: dt/dd in figure/details has killer rendering issues in ie6 and ie7
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: dt/dd in figure/details has killer rendering issues in ie6 and ie7
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: dt/dd in figure/details has killer rendering issues in ie6 and ie7
- [Fwd: Re: Request to publish HTML+RDFa (draft 3) as FPWD]
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Bug 7470 -- mention aria-* attributes in element definitions.
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: HTML5 RDFa Test Suite (was Re: Request to publish HTML+RDFa (draft 3) as FPWD)
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: On testing HTML
- HTML5 RDFa Test Suite (was Re: Request to publish HTML+RDFa (draft 3) as FPWD)
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: The Complexity Argument
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
Monday, 21 September 2009
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- proposed update to IRI document posted
- Re: Complexity of HTML5 (was Re: The Complexity Argument)
- [TAG post:] "Ten Use-Cases of Individual Content Authors Requiring Rights/Commerce Metadata..."
- Re: Complexity of HTML5 (was Re: The Complexity Argument)
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Moving Form Events from DOM3 Events to HTML5 (was: Removing Form Events?)
- Resending Re: Application Cache review
- Re: what is dt?
- Re: FPWD Review Request: HTML+RDFa
- Re: FPWD Review Request: HTML+RDFa
- Re: Drag and Drop API
- Drag and Drop API
- Re: The Complexity Argument (was: Re: Request to publish HTML+RDFa (draft 3) as FPWD)
- Re: FPWD Review Request: HTML+RDFa
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- [Bug 7682] link tag: rel: associate pages about the same organization across many sites
- [Bug 7681] link tag: rel: associate pages about the same person across many sites
- [Bug 7362] inclusion of the title as a case where the alt may be omitted is problematic
Sunday, 20 September 2009
- Re: [html5] input type=time & min/max.
- Re: [html5] input type=time & min/max.
- Re: Complexity of HTML5 (was Re: The Complexity Argument)
- Re: what is dt?
- RE: Complexity of HTML5 (was Re: The Complexity Argument)
- Re: Complexity of HTML5 (was Re: The Complexity Argument)
- Re: what is dt?
- Re: what is dt?
- Re: [whatwg] fyi: Strict Transport Security specification
- Re: Complexity of HTML5 (was Re: The Complexity Argument)
- [Bug 7400] "as part" instead of "sa part"
- Re: Complexity of HTML5 (was Re: The Complexity Argument)
- Reopening bugs (Was: The Complexity Argument)
- Re: [html5] input type=time & min/max.
- [Bug 7674] are the chunks for inputs having the content-type header for each chunk specified appropriately? e.g. file inputs should set the header according to the file selected by the user
- [Bug 7677] Is there any behavior defined for setting the src property. For example, is the expectation that object should (A) load the src if autobuffer is true (B) stop playing if currently playing (C) something else (D) nothing at all?
- Re: Serialization of PI misses ending question mark
- [Bug 7680] Add an 'angle' element to HTML5
- Complexity of HTML5 (was Re: The Complexity Argument)
- Re: The Complexity Argument (was: Re: Request to publish HTML+RDFa (draft 3) as FPWD)
Saturday, 19 September 2009
- fyi: Strict Transport Security specification
- Re: [html5] input type=time & min/max.
- Re: Serialization of PI misses ending question mark
- Re: Serialization of PI misses ending question mark
- Re: Serialization of PI misses ending question mark
- Re: [html5] input type=time & min/max.
- Re: Serialization of PI misses ending question mark
- [html5] input type=time & min/max.
- Re: Serialization of PI misses ending question mark
- Re: what is dt?
- Re: dt/dd in figure/details has killer rendering issues in ie6 and ie7
- Re: Serialization of PI misses ending question mark
- Re: what is dt?
- Serialization of PI misses ending question mark
- Re: what is dt?
- Re: ACTION-103 Follow up on the about: scheme Registration
- Re: dt/dd in figure/details has killer rendering issues in ie6 and ie7
- Re: ACTION-103 Follow up on the about: scheme Registration
- Re: ACTION-103 Follow up on the about: scheme Registration
- Re: The Complexity Argument (was: Re: Request to publish HTML+RDFa (draft 3) as FPWD)
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: The Complexity Argument (was: Re: Request to publish HTML+RDFa (draft 3) as FPWD)
- Re: dt/dd in figure/details has killer rendering issues in ie6 and ie7
Friday, 18 September 2009
- Re: video size when aspect ratio is not 1
- Re: ACTION-103 Follow up on the about: scheme Registration
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: CfC: Publish HTML+RDFa as First Public Working Draft
- Re: ACTION-103 Follow up on the about: scheme Registration
- The Complexity Argument (was: Re: Request to publish HTML+RDFa (draft 3) as FPWD)
- Re: dt/dd in figure/details has killer rendering issues in ie6 and ie7
- dt/dd in figure/details has killer rendering issues in ie6 and ie7
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: what is dt?
- Re: what is dt?
- Re: head/@profile, profile link relation, was: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: ACTION-103 Follow up on the about: scheme Registration
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: ACTION-103 Follow up on the about: scheme Registration
- Re: CfC: Publish HTML+RDFa as First Public Working Draft
- [Bug 7659] Clarify what "other applicable specifications" means to say http://lists.w3.org/Archives/Public/www-tag/2009Sep/0045.html
- Re: what is dt?
- [Bug 7672] </p> shouldn't be ignored in "before html", "before head", "in head", "in head noscript", "after head". It should be reprocessed through to "in body" like </br>.
- [Bug 7662] When images are disabled arguably fallback content of the <canvas> element should be shown.
- [Bug 7668] 7.9.6 should explain which events are actually dispatched when copying/cutting/pasting
- [Bug 7669] Redefining dt and dd, recommend new element as caption for Figure
- Re: what is dt?
- [Bug 7670] Use of prefixes is too complicated for a Web technology
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: CfC: Publish HTML+RDFa as First Public Working Draft
- Re: what is dt?
- Re: CfC: Publish HTML+RDFa as First Public Working Draft
- Re: what is dt?
- Re: what is dt?
- Bindings instead of video, audio, canvas and img
- Re: CfC: Publish HTML+RDFa as First Public Working Draft
Thursday, 17 September 2009
- Re: CfC: Publish HTML+RDFa as First Public Working Draft
- CfC: Publish HTML+RDFa as First Public Working Draft
- Re: what is dt?
- Re: what is dt?
- Re: HTML WG Testing Task Force
- On testing HTML
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: DIALOG Issues Which Have Already Been Submitted as Proposals (includes DL)
- Re: what is dt?
- Re: DIALOG Issues Which Have Already Been Submitted as Proposals (includes DL)
- DIALOG Issues Which Have Already Been Submitted as Proposals (includes DL)
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: The <who> element (Was: Change back the semantics of <cite>)
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: what is dt?
- X3D references for HTML5 draft
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: what is dt?
- Re: what is dt?
- ACTION-127: establish process for "official WG response" to other WG's RFC on LC drafts
- <summary> [was: Re: what is dt?]
- Re: what is dt?
- Re: what is dt? use of summary in Figure
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: what is dt? use of summary in Figure
- RE: HTML WG Testing Task Force
- Re: what is dt?
- Re: what is dt?
- ACTION-103 Follow up on the about: scheme Registration
- Removing <source> should make resource selection not fire 'error' on it
- Re: what is dt?
- Re: what is dt?
- Re: what is dt? focusing on Figure
- Re: what is dt?
- Re: what is dt?
- [Bug 7660] The resource selection algorithm should set currentSrc in the sync section before invoking resource fetch instead of being set in the async resource fetch. Otherwise checking currentSrc in onloadstart is not reliable.
- [Bug 7632] Should resource selection algorithm be run when src="" is removed?
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- [Bug 7628] The later 'block' box container should simply map to the first/last dd element. This makes UA implementations easier and script emulation of the feature in contemporary UAs as well. Both can simply toggle the display property between block and none.
- RE: <keygen> element
- [Bug 7629] When the dd element is used inside figure and details it should probably not have margin by default.
- [Bug 7631] Don't invoke resource selection algorithm when inserting <source> if src="" is present
- [Bug 7633] The use of @summary should be encouraged when circumstances warrant
- [Bug 7646] Media Queries
- [Bug 7649] It would be useful to see an example of how section works when it's not in the context of an article, in the example text (chapters, tabs, etc) all of those would sit inside a wrapping article element.
- [Bug 7651] Articles and sections
- [Bug 7656] Describe differences between easily confused new elements to assist authors
- [Bug 7599] Either drop the two places that set the "Origin" HTTP header, or update HTML5 to match the Sec-From/Origin I-D (if the latter is stable enough yet).
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: Accessibility Task Force
- [Bug 7657] Redefining dt and dd
Wednesday, 16 September 2009
- Re: Accessibility Task Force
- Re: Change back the semantics of <cite>
- Re: what is dt?
- {agenda} HTML WG telcon 2009-09-17
- IDNA, IRI, HTML5 coordination
- Re: Change back the semantics of <cite>
- Re: head/@profile, profile link relation, was: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- head/@profile, profile link relation, was: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Request to publish HTML+RDFa (draft 3) as FPWD
- Re: Google to pay for HTMLWG invited experts at TPAC 2009
- Re: what is dt?
- Re: Change back the semantics of <cite>
- Re: The <who> element (Was: Change back the semantics of <cite>)
- Re: <details>
- Request to publish HTML+RDFa (draft 3) as FPWD
- Speakers in Dialogues; citations
- Re: Change back the semantics of <cite>
- Re: what is dt?
- Re: Change back the semantics of <cite>
- Re: aria-describedby vs longdesc [was: Re: Opera 10.10 recently added longdesc support]
- Re: Change back the semantics of <cite>
- [Bug 7643] Why not use display:none instead of overflow:hidden; height:0? display:none seems to have the desired behavior in terms of exposure to AT and keyboard navigation in browsers.
- [Bug 7642] which attribute wins if both pointsize and size are specified?
- [Bug 7645] associate printable pages and less-convenient-to-print pages with link rel value "print"
- Re: Opera 10.10 recently added longdesc support
- Conformance of SVG content in HTML
- Re: <keygen> element
- Re: video size when aspect ratio is not 1
Tuesday, 15 September 2009
- Re: Speakers in Dialogues (Was: what is dt?)
- Re: Speakers in Dialogues (Was: what is dt?)
- Re: Speakers in Dialogues (Was: what is dt?)
- Re: Speakers in Dialogues (Was: what is dt?)
- RE: Speakers in Dialogues (Was: what is dt?)
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: Speakers in Dialogues (Was: what is dt?)
- Re: Speakers in Dialogues (Was: what is dt?)
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: Opera 10.10 recently added longdesc support
- Re: what is dt?
- please don't cross-post to the pfwg-comments (Was: aria-describedby vs longdesc [was: Re: Opera 10.10 recently added longdesc support])
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- Re: what is dt?
- RE: aria-describedby vs longdesc [was: Re: Opera 10.10 recently added longdesc support]
- [Bug 7639] Please remove "dc" and "ds" from the parser
- Re: aria-describedby vs longdesc [was: Re: Opera 10.10 recently added longdesc support]
- Re: aria-describedby vs longdesc [was: Re: Opera 10.10 recently added longdesc support]
- Re: what is dt?
- Re: aria-describedby vs longdesc [was: Re: Opera 10.10 recently added longdesc support]
- Re: what is dt?
- Re: aria-describedby vs longdesc [was: Re: Opera 10.10 recently added longdesc support]
- aria-describedby vs longdesc [was: Re: Opera 10.10 recently added longdesc support]
- Re: FW: [html] Summary draft
- Re: Opera 10.10 recently added longdesc support
- Re: Opera 10.10 recently added longdesc support
- RE: Opera 10.10 recently added longdesc support
- what is dt?
- Re: Opera 10.10 recently added longdesc support
- Re: Opera 10.10 recently added longdesc support
- Re: Opera 10.10 recently added longdesc support
- Re: Opera 10.10 recently added longdesc support
- Re: Opera 10.10 recently added longdesc support
- Re: FW: [html] Summary draft
- Opera 10.10 recently added longdesc support
- Re: what is dt?
- Re: FW: [html] Summary draft
- Re: what is dt?
- what is dt?
- Re: Change back the semantics of <cite>
- Re: <details>
- Re: Change back the semantics of <cite>
- Re: <details>
- Re: <details>
- Re: <details>
- Re: <details>
- Re: <details>
- Re: <details>
- Re: [html] Summary draft
- Re: [html] Summary draft
- RE: [html] Summary draft
- Re: [html] Summary draft
- Re: [html] Summary draft
- RE: [html] Summary draft
- Re: [html] Summary draft
- Re: [html] Summary draft
- Re: [html] Summary draft
- RE: FW: [html] Summary draft
- Re: FW: [html] Summary draft
Monday, 14 September 2009
- Re: [html] Summary draft
- FW: [html] Summary draft
- Re: 4.10.4.1.5 E-mail state
- Re: <keygen> element
- Re: <keygen> element
- Re: video size when aspect ratio is not 1
- [Bug 7615] Whitespace in doctype
- [Bug 7616] Move requirement about obsolete doctypes
- Re: Accessibility Task Force
- Re: guidance location? [was: Re: <details> ]
- Re: guidance location? [was: Re: <details> ]
- guidance location? [was: Re: <details> ]
- Re: 4.10.4.1.5 E-mail state
- Re: Feature detection (was: <details>)
- Re: <details>
- Re: <details>
- Re: <details>
- Re: Implementor feedback on new elements in HTML5
- Re: 4.10.4.1.5 E-mail state
- <details>
- Re: Implementor feedback on new elements in HTML5
- Re: [TAG post:] "HTML 5's proposed basis in DOM/JS skews web control and monetization..."
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: <keygen> element
Friday, 11 September 2009
Monday, 14 September 2009
- Re: Implementor feedback on new elements in HTML5
- Re: video size when aspect ratio is not 1
- Re: video size when aspect ratio is not 1
- Re: [TAG post:] "HTML 5's proposed basis in DOM/JS skews web control and monetization..."
- Re: [TAG post:] "HTML 5's proposed basis in DOM/JS skews web control and monetization..."
- [TAG post:] "HTML 5's proposed basis in DOM/JS skews web control and monetization..."
Sunday, 13 September 2009
- Re: Change back the semantics of <cite>
- Re: Change back the semantics of <cite>
- Re: Change back the semantics of <cite>
- Re: ARIA's role="" attribute (was Re: [Bug 7509] Consider <dl type="dialog"> instead of <dialog>)
- Re: aria-role vs role -- from SVG
- aria-role vs role -- from SVG
Saturday, 12 September 2009
Friday, 11 September 2009
- Re: Change back the semantics of <cite>
- Re: Pedagogic validation
- Re: Change back the semantics of <cite>
- Re: Change back the semantics of <cite>
- Re: Change back the semantics of <cite>
- Re: Pedagogic validation
- Re: Change back the semantics of <cite>
- Re: Change back the semantics of <cite>
- Re: Change back the semantics of <cite>
- Re: Change back the semantics of <cite>
- Re: Change back the semantics of <cite>
- Re: Accessibility Task Force
- Re: Accessibility Task Force
- Re: Accessibility Task Force
Thursday, 10 September 2009
Friday, 11 September 2009
- Re: HTML WG Testing Task Force
- Re: Accessibility Task Force
- Re: Accessibility Task Force
- Re: Pedagogic validation
- RE: Example of Good Summary???
- Re: The <who> element (Was: Change back the semantics of <cite>)
- The <who> element (Was: Change back the semantics of <cite>)
- Re: Accessibility Task Force
- Re: Accessibility Task Force
- Example of Good Summary???
- Re: [Bug 7509] Consider <dl type="dialog"> instead of <dialog>
- Re: Accessibility Task Force
- Re: Change back the semantics of <cite>
- Re: Change back the semantics of <cite>
Thursday, 10 September 2009
- Re: Change back the semantics of <cite>
- Re: ARIA's role="" attribute (was Re: [Bug 7509] Consider <dl type="dialog"> instead of <dialog>)
- Re: ARIA's role="" attribute (was Re: [Bug 7509] Consider <dl type="dialog"> instead of <dialog>)
- Re: [Bug 7509] Consider <dl type="dialog"> instead of <dialog>
- Re: how many URL issues do we need/want?
- Re: Accessibility Task Force
- Re: Change back the semantics of <cite>
- Re: ARIA's role="" attribute (was Re: [Bug 7509] Consider <dl type="dialog"> instead of <dialog>)
- Re: Change back the semantics of <cite>
- Re: Accessibility Task Force
- RE: ARIA's role="" attribute (was Re: [Bug 7509] Consider <dl type="dialog"> instead of <dialog>)
- Re: Accessibility Task Force
- Re: Pedagogic validation
- Re: Accessibility Task Force
- Re: Accessibility Task Force
- Re: Accessibility Task Force
- Re: Accessibility Task Force
- Re: ARIA's role="" attribute (was Re: [Bug 7509] Consider <dl type="dialog"> instead of <dialog>)
- Re: Accessibility Task Force
- Re: [Bug 7509] Consider <dl type="dialog"> instead of <dialog>
- Re: Accessibility Task Force
- Re: Accessibility Task Force
- Change back the semantics of <cite>
- Re: Accessibility Task Force
- Re: Accessibility Task Force
- Re: Accessibility Task Force
- Re: Accessibility Task Force
- Re: Accessibility Task Force
- Re: HTML WG Testing Task Force
- Re: how many URL issues doe we need/want? Re: Agenda for HTML WG telcon 2009-09-10 - Accessibility TF, Testing TF, etc
- how many URL issues doe we need/want? Re: Agenda for HTML WG telcon 2009-09-10 - Accessibility TF, Testing TF, etc
- Re: Pedagogic validation
- Re: [Bug 7508] <dialog> needs a way to add non-speech related information
- Re: [Bug 7508] <dialog> needs a way to add non-speech related information
- Scripts that promise not to document.write()
- Re: [Bug 7509] Consider <dl type="dialog"> instead of <dialog>
- Re: [Bug 7509] Consider <dl type="dialog"> instead of <dialog>
- Re: ARIA's role="" attribute (was Re: [Bug 7509] Consider <dl type="dialog"> instead of <dialog>)
- Re: [Bug 7509] Consider <dl type="dialog"> instead of <dialog>
- Re: ARIA's role="" attribute (was Re: [Bug 7509] Consider <dl type="dialog"> instead of <dialog>)
- Re: ISSUE-73
- Re: [Bug 7509] Consider <dl type="dialog"> instead of <dialog>
- Re: ARIA's role="" attribute (was Re: [Bug 7509] Consider <dl type="dialog"> instead of <dialog>)
- Re: [Bug 7509] Consider <dl type="dialog"> instead of <dialog>
- Re: [Bug 7509] Consider <dl type="dialog"> instead of <dialog>
- Re: [Bug 7509] Consider <dl type="dialog"> instead of <dialog>
- Re: ARIA's role="" attribute (was Re: [Bug 7509] Consider <dl type="dialog"> instead of <dialog>)
- Re: ARIA's role="" attribute (was Re: [Bug 7509] Consider <dl type="dialog"> instead of <dialog>)
- Re: ARIA's role="" attribute (was Re: [Bug 7509] Consider <dl type="dialog"> instead of <dialog>)
- CfC: declare WebSockets out of scope
- Re: [Bug 7508] <dialog> needs a way to add non-speech related information
- Re: More on SVG within HTML pages
- Re: [Bug 7509] Consider <dl type="dialog"> instead of <dialog>
- Re: More on SVG within HTML pages
- [Bug 7551] People are using <section> incorrectly
- Re: More on SVG within HTML pages
- [Bug 7556] Where is it defined that only the first <base> element is to be taken into account? Surely that should not be part of iri-bis.
- Re: ARIA's role="" attribute (was Re: [Bug 7509] Consider <dl type="dialog"> instead of <dialog>)
- RE: ARIA's role="" attribute (was Re: [Bug 7509] Consider <dl type="dialog"> instead of <dialog>)
- Re: More on SVG within HTML pages
Wednesday, 9 September 2009
- Re: Pedagogic validation
- Pedagogic validation
- ARIA's role="" attribute (was Re: [Bug 7509] Consider <dl type="dialog"> instead of <dialog>)
- Re: [Bug 7508] <dialog> needs a way to add non-speech related information
- Re: [Bug 7509] Consider <dl type="dialog"> instead of <dialog>
- [Bug 7557] add "type" attribute to <nav> distinguish between primary and secondary navigation
- Re: HTML WG Testing Task Force
- Re: Accessibility Task Force
- Re: <keygen> element
- ISSUE-73 (was: Agenda for HTML WG telcon 2009-09-10)
- FW: Agenda for HTML WG telcon 2009-09-10 - Accessibility TF, Testing TF, etc
- HTML WG Testing Task Force
- RE: Accessibility Task Force
- Example of Good Summary
- Re: [Bug 7508] <dialog> needs a way to add non-speech related information
- Re: [Bug 7508] <dialog> needs a way to add non-speech related information
- Re: [Bug 7508] <dialog> needs a way to add non-speech related information
- Re: [Bug 7508] <dialog> needs a way to add non-speech related information
- Re: More on SVG within HTML pages
- [Bug 7550] The invalid event does have a default action. Namely to display UI. However, UAs should probably not be forbidden to show that a field is invalid before submitting, but how can page author suppress the UI for that?
- Re: <keygen> element
- Re: More on SVG within HTML pages
- [Bug 7547] on .drawImage() negative widths or heights should flip/mirror the image. There's no easy way of fliping images in canvas
- [Bug 7546] "HTML 5" Editor's draft misnamed and suboptimal for HTML content authors unless refactored into HTML (main) and DOM API (appendix).
- Re: <video> and <audio>
- [Bug 7543] Consensus on ietf-http-wg was that repetition of relations is meaningless and we should rather use numbering (e.g. "up2"), names (e.g. "great-grandparent") or an attribute (e.g. level="3").
- [Bug 7542] Remove Section 5. Microdata
- [Bug 7540] Spec for metadata extensions does not define which states are allowed/conforming
- [Bug 7527] Allow implementations to generate meaningful default, implied headings for some sections.
- [Bug 7525] meta/@name=keywords should be specified (and made conforming)
- [Bug 7512] suggested "replacement" for head/@profile does not work
- [Bug 7510] Allow elements beyond just HTML, MathML, and SVG into SVG element
- [Bug 7509] Consider <dl type="dialog"> instead of <dialog>
- [Bug 7508] <dialog> needs a way to add non-speech related information
Tuesday, 8 September 2009
- RE: <keygen> element
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- Re: <keygen> element
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- RE: <keygen> element
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- RE: <video> and <audio>
- Re: More on SVG within HTML pages
- Re: FPWD Review Request: HTML+RDFa
- Re: FPWD Review Request: HTML+RDFa
- Re: FPWD Review Request: HTML+RDFa
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- <dialog> bugs (was: Implementor feedback (dialog and datepickers))
- Re: 4.10.4.1.5 E-mail state
- Re: 4.10.4.1.5 E-mail state
- [Bug 7392] Please use some term other than "URL" for Web Addresses
- Re: XMLLiterals and c14n
- Re: More on SVG within HTML pages
- 4.10.4.1.5 E-mail state
- Re: <keygen> element
Monday, 7 September 2009
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- Re: XMLLiterals and c14n
- Re: More on SVG within HTML pages
- Re: XMLLiterals and c14n
- XMLLiterals and c14n (was: HTML+RDFa (2nd draft))
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- Re: <video> and <audio>
- Re: <keygen> element
- Re: More on SVG within HTML pages
- Re: FPWD Review Request: HTML+RDFa
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- Re: Authoring Requirements for Using SVG and MathML in HTML Documents
- HTML+RDFa (2nd draft)
- Re: <keygen> element
- Re: <keygen> element
Sunday, 6 September 2009
- Re: More on SVG within HTML pages
- Re: More on SVG within HTML pages
- More on SVG within HTML pages
- Re: [HTML5] DOMContentLoaded fires before CSS resources loaded?
- Re: Implementor feedback (dialog and datepickers)
- Re: HTML5 feedback from prominent designers
- Re: HTML5 feedback from prominent designers
- Re: HTML5 feedback from prominent designers
- Authoring Requirements for Using SVG and MathML in HTML Documents
- Re: <keygen> element
- Re: <keygen> element
- Re: <keygen> element
- Re: <keygen> element
- Re: <keygen> element
Saturday, 5 September 2009
- Re: <keygen> element
- Re: <keygen> element
- Re: <keygen> element
- Re: <keygen> element
- Re: <keygen> element
- Re: <keygen> element
- Re: <keygen> element
- Re: <keygen> element
- Re: <keygen> element
- Re: FPWD Review Request: HTML+RDFa
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: <keygen> element
- Re: FPWD Review Request: HTML+RDFa
- Re: <keygen> element
- Re: <keygen> element
Friday, 4 September 2009
- Re: Questions arising from ARIA/HTML5 integration
- Re: Where people have discussions (was Re: The History of <aside> for sidebars)
- Re: The History of <aside> for sidebars
- Re: <keygen> element
- Where people have discussions (was Re: The History of <aside> for sidebars)
- Re: The History of <aside> for sidebars
- Re: The History of <aside> for sidebars
- RE: The History of <aside> for sidebars
- Re: The History of <aside> for sidebars
- Re: The History of <aside> for sidebars
- Re: FPWD Review Request: HTML+RDFa
- RE: The History of <aside> for sidebars
- Re: tweaking meter
- Re: The History of <aside> for sidebars
- Re: meter changes [was: Re: Implementor feedback on new elements in HTML5]
- Re: HTML5 feedback from prominent designers
- Re: noscript in HTML fragment serialization algorithm
- Re: The History of <aside> for sidebars
- Re: FPWD Review Request: HTML+RDFa
- RE: The History of <aside> for sidebars
- Re: FPWD Review Request: HTML+RDFa
- Re: Questions arising from ARIA/HTML5 integration
- Re: Implementor feedback (dialog and datepickers)
- Re: Implementor feedback (dialog and datepickers)
- [Bug 7499] <keygen> should not be defined as a requirement for a conforming HTML5 user agent and should be removed from the spec
- Re: The History of <aside> for sidebars (was: Re: HTML5 feedback from prominent designers)
- Re: HTML5 feedback from prominent designers
- Re: FPWD Review Request: HTML+RDFa
- Re: The History of <aside> for sidebars (was: Re: HTML5 feedback from prominent designers)
- The History of <aside> for sidebars (was: Re: HTML5 feedback from prominent designers)
- Re: Questions arising from ARIA/HTML5 integration
- Re: FPWD Review Request: HTML+RDFa
- Re: FPWD Review Request: HTML+RDFa
- Re: <keygen> element
- Re: HTML5 feedback from prominent designers
- Re: Questions arising from ARIA/HTML5 integration
- Re: FPWD Review Request: HTML+RDFa
- Re: FPWD Review Request: HTML+RDFa
- Re: FPWD Review Request: HTML+RDFa
- Re: Implementor feedback on new elements in HTML5
- Re: Questions arising from ARIA/HTML5 integration
- Re: FPWD Review Request: HTML+RDFa
- Re: FPWD Review Request: HTML+RDFa
- Re: Questions arising from ARIA/HTML5 integration
- Re: <keygen> element
- Re: [html5] Event handler DOM attributes
- Re: Implementor feedback on new elements in HTML5
- Re: HTML5 feedback from prominent designers
- Re: FPWD Review Request: HTML+RDFa
- Re: HTML5 feedback from prominent designers
- Re: Issues arising from not reparsing
- Re: HTML5 feedback from prominent designers
- Re: HTML5 feedback from prominent designers
- Re: The formatblock command
Thursday, 3 September 2009
- Re: what is the spec telling authors about missing link/@rel?
- Re: Please Specify Behavior for @rel="next | prev"
- Re: FPWD Review Request: HTML+RDFa
- Re: FPWD Review Request: HTML+RDFa
- Re: FPWD Review Request: HTML+RDFa
- Re: FPWD Review Request: HTML+RDFa
- Re: aria vs native alternatives [was: Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document]
- Re: what is the spec telling authors about missing link/@rel?
- Re: what is the spec telling authors about missing link/@rel?
- Re: what is the spec telling authors about missing link/@rel?
- Re: what is the spec telling authors about missing link/@rel?
- Re: FPWD Review Request: HTML+RDFa
- Re: what is the spec telling authors about missing link/@rel?
- what is the spec telling authors about missing link/@rel?
- Re: FPWD Review Request: HTML+RDFa
- Re: FPWD Review Request: HTML+RDFa
- Re: aria vs native alternatives [was: Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document]
- Re: ISSUE-48: UA-q-quotes - suggest closing on 2009-09-03
- Re: Please Specify Behavior for @rel="next | prev"
- Re: FPWD Review Request: HTML+RDFa
- Re: aria vs native alternatives [was: Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document]
- Re: ISSUE-48: UA-q-quotes - suggest closing on 2009-09-03
- Re: ISSUE-48: UA-q-quotes - suggest closing on 2009-09-03
- Re: FPWD Review Request: HTML+RDFa
- [Bug 7491] Unspecified: quotation punctuation in the blockquote element
- Re: ISSUE-48: UA-q-quotes - suggest closing on 2009-09-03
- Re: FPWD Review Request: HTML+RDFa
- Re: FPWD Review Request: HTML+RDFa
- Re: tweaking meter [was: Re: <meter> and <progress> (was RE: Implementor feedback on new elements in HTML5)]
- Re: FPWD Review Request: HTML+RDFa
- Re: Implementor feedback on new elements in HTML5
- [Bug 7484] head/@profile holds a white-space separated list of URIs
- [Bug 7483] The footer element desperately needs to be able to contain sectioning content descendents, most importantly "nav". Under the current specification, I will just end up using div class="footer" so my footers can contain sectioning content.
- Re: HTML5 feedback from prominent designers
- Re: FPWD Review Request: HTML+RDFa
- Re: video size when aspect ratio is not 1
- Re: Please Specify Behavior for @rel="next | prev"
- Re: aria vs native alternatives [was: Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document]
- Re: video size when aspect ratio is not 1
- Re: video: earliest possible position changes
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: FPWD Review Request: HTML+RDFa
- Re: aria vs native alternatives [was: Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document]
- Re: aria vs native alternatives [was: Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document]
- Re: aria vs native alternatives [was: Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document]
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: aria vs native alternatives [was: Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document]
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: Proposal: <content> element
- Re: FPWD Review Request: HTML+RDFa
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: Agenda for HTML WG telcon 2009-08-20 - Accessibility TF, HTML5 Test Suite, etc
- Re: aria vs native alternatives [was: Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document]
- Re: Agenda for HTML WG telcon 2009-08-20 - Accessibility TF, HTML5 Test Suite, etc
- Re: tweaking meter [was: Re: <meter> and <progress> (was RE: Implementor feedback on new elements in HTML5)]
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: Review comments on HTML+RDFa (was Re: FPWD Review Request: HTML+RDFa)
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: Implementor feedback (dialog and datepickers)
- Re: Implementor feedback (dialog and datepickers)
Wednesday, 2 September 2009
- Re: HTML5 feedback from prominent designers
- Re: Implementor feedback (dialog and datepickers)
- Re: HTML5 feedback from prominent designers
- Re: HTML5 feedback from prominent designers
- Re: aria vs native alternatives [was: Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document]
- Re: [html5] Event handler DOM attributes
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: Implementor feedback (dialog and datepickers)
- Re: drawImage() shouldn't throw INVALID_STATE_ERR
- Re: Proposal: <content> element
- Re: Implementor feedback (dialog and datepickers)
- Re: aria vs native alternatives [was: Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document]
- Re: Implementor feedback (dialog and datepickers)
- Re: <keygen> element
- Re: tweaking meter [was: Re: <meter> and <progress> (was RE: Implementor feedback on new elements in HTML5)]
- RE: <keygen> element
- Elements used to scope <address>
- [aapi] RE: picking up on some comments in IRC on ARIA
- Re: picking up on some comments in IRC on ARIA
- Re: closing issue-30 longdesc in favor of aria-describedby [was: Consolidated issues ...]
- Re: Review comments on HTML+RDFa (was Re: FPWD Review Request: HTML+RDFa)
- Re: Review comments on HTML+RDFa (was Re: FPWD Review Request: HTML+RDFa)
- Re: <keygen> element
- Re: tweaking meter [was: Re: <meter> and <progress> (was RE: Implementor feedback on new elements in HTML5)]
- Re: aria vs native alternatives [was: Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document]
- Re: picking up on some comments in IRC on ARIA
- Re: Review comments on HTML+RDFa (was Re: FPWD Review Request: HTML+RDFa)
- Re: tweaking meter [was: Re: <meter> and <progress> (was RE: Implementor feedback on new elements in HTML5)]
- Re: closing issue-30 longdesc in favor of aria-describedby [was: Consolidated issues ...]
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: Implementor feedback (dialog and datepickers)
- Re: Review comments on HTML+RDFa (was Re: FPWD Review Request: HTML+RDFa)
- Re: tweaking meter [was: Re: <meter> and <progress> (was RE: Implementor feedback on new elements in HTML5)]
- Re: HTML5 feedback from prominent designers
- Re: tweaking meter [was: Re: <meter> and <progress> (was RE: Implementor feedback on new elements in HTML5)]
- Re: aria vs native alternatives [was: Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document]
- Re: tweaking meter [was: Re: <meter> and <progress> (was RE: Implementor feedback on new elements in HTML5)]
- Re: Implementor feedback (dialog and datepickers)
- Re: HTML5 feedback from prominent designers
- Re: picking up on some comments in IRC on ARIA
- Re: FPWD Review Request: HTML+RDFa
- tweaking meter [was: Re: <meter> and <progress> (was RE: Implementor feedback on new elements in HTML5)]
- Re: HTML5 feedback from prominent designers
- meter changes [was: Re: Implementor feedback on new elements in HTML5]
- Re: aria vs native alternatives [was: Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document]
- Re: aria vs native alternatives [was: Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document]
Tuesday, 1 September 2009
Wednesday, 2 September 2009
- Re: HTML5 feedback from prominent designers
- aria vs native alternatives [was: Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document]
- Costs and clear guidance [was: Recording teleconferences?]
- Re: <meter> and <progress> (was RE: Implementor feedback on new elements in HTML5)
- Re: <meter> and <progress> (was RE: Implementor feedback on new elements in HTML5)
- Re: <meter> and <progress> (was RE: Implementor feedback on new elements in HTML5)
- Re: <meter> and <progress> (was RE: Implementor feedback on new elements in HTML5)
- Re: HTML5 feedback from prominent designers
- [Bug 7480] use of keygen should trigger a warning.
- Re: <keygen> element
- Re: Implementor feedback (dialog and datepickers)
- Re: HTML5 feedback from prominent designers
- Re: Review comments on HTML+RDFa (was Re: FPWD Review Request: HTML+RDFa)
- Re: <meter> and <progress> (was RE: Implementor feedback on new elements in HTML5)
- Re: picking up on some comments in IRC on ARIA
- Re: picking up on some comments in IRC on ARIA
- Re: picking up on some comments in IRC on ARIA
- Re: Review comments on HTML+RDFa (was Re: FPWD Review Request: HTML+RDFa)
- picking up on some comments in IRC on ARIA
- Re: FPWD Review Request: HTML+RDFa
- Re: Agenda for HTML WG telcon 2009-08-20 - Accessibility TF, HTML5 Test Suite, etc
- Re: <keygen> element
- Re: noscript in HTML fragment serialization algorithm
- Re: <meter> and <progress> (was RE: Implementor feedback on new elements in HTML5)
- Re: <keygen> element
- Re: <meter> and <progress> (was RE: Implementor feedback on new elements in HTML5)
- Re: noscript in HTML fragment serialization algorithm
- Re: FPWD Review Request: HTML+RDFa
- Re: <meter> and <progress> (was RE: Implementor feedback on new elements in HTML5)
- Re: <meter> and <progress> (was RE: Implementor feedback on new elements in HTML5)
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: aria implicit roles exposed?
- Re: Review comments on HTML+RDFa (was Re: FPWD Review Request: HTML+RDFa)
- Re: aria implicit roles exposed?
- aria implicit roles exposed?
- Re: <meter> and <progress> (was RE: Implementor feedback on new elements in HTML5)
- Re: <meter> and <progress> (was RE: Implementor feedback on new elements in HTML5)
- Re: <meter> and <progress> (was RE: Implementor feedback on new elements in HTML5)
- Re: Review comments on HTML+RDFa (was Re: FPWD Review Request: HTML+RDFa)
- Re: Review comments on HTML+RDFa (was Re: FPWD Review Request: HTML+RDFa)
- Re: HTML5 feedback from prominent designers
- Re: <meter> and <progress> (was RE: Implementor feedback on new elements in HTML5)
- Re: Review comments on HTML+RDFa (was Re: FPWD Review Request: HTML+RDFa)
- Re: question about ARIA in HTML 5 spec text - implied use on elements not listed
- Re: <meter> and <progress> (was RE: Implementor feedback on new elements in HTML5)
- Review comments on HTML+RDFa (was Re: FPWD Review Request: HTML+RDFa)
- Re: noscript in HTML fragment serialization algorithm
Tuesday, 1 September 2009
- Re: <keygen> element (was RE: Implementor feedback on new elements in HTML5)
- Re: <meter> and <progress> (was RE: Implementor feedback on new elements in HTML5)
- Re: Implementor feedback on new elements in HTML5
- Re: <keygen> element (was RE: Implementor feedback on new elements in HTML5)
- Re: <meter> and <progress> (was RE: Implementor feedback on new elements in HTML5)
- Re: <keygen> element (was RE: Implementor feedback on new elements in HTML5)
- Re: <meter> and <progress> (was RE: Implementor feedback on new elements in HTML5)
- Re: <meter> and <progress> (was RE: Implementor feedback on new elements in HTML5)
- Re: HTML5 feedback from prominent designers
- Re: Implementor feedback on new elements in HTML5
- FPWD Review Request: HTML+RDFa
- Re: Implementor feedback on new elements in HTML5
- Re: Implementor feedback on new elements in HTML5
- Re: <keygen> element (was RE: Implementor feedback on new elements in HTML5)
- Re: Implementor feedback on new elements in HTML5
- Re: Implementor feedback on new elements in HTML5
- Re: Implementor feedback on new elements in HTML5
- RE: <keygen> element (was RE: Implementor feedback on new elements in HTML5)
- Re: Questions arising from ARIA/HTML5 integration
- Re: up up up, was: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard
- Re: <keygen> element (was RE: Implementor feedback on new elements in HTML5)
- Re: Questions arising from ARIA/HTML5 integration
- Re: Questions arising from ARIA/HTML5 integration
- Re: Questions arising from ARIA/HTML5 integration
- Re: Questions arising from ARIA/HTML5 integration
- <video> and <audio> (was RE: Implementor feedback on new elements in HTML5)
- Re: <meter> and <progress> (was RE: Implementor feedback on new elements in HTML5)
- New <input> types (was RE: Implementor feedback on new elements in HTML5)
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- <meter> and <progress> (was RE: Implementor feedback on new elements in HTML5)
- Re: Implementor feedback on new elements in HTML5
- <keygen> element (was RE: Implementor feedback on new elements in HTML5)
- RE: Implementor feedback on new elements in HTML5
- <dialog> element (was RE: Implementor feedback on new elements in HTML5)
- Re: Implementor feedback on new elements in HTML5
- Re: Implementor feedback on new elements in HTML5
- Re: Questions arising from ARIA/HTML5 integration
- Re: Implementor feedback on new elements in HTML5
- Re: Questions arising from ARIA/HTML5 integration
- Re: Implementor feedback on new elements in HTML5
- Re: Implementor feedback on new elements in HTML5
- Re: Implementor feedback on new elements in HTML5
- Re: Implementor feedback on new elements in HTML5
- Re: Implementor feedback on new elements in HTML5
- Re: Implementor feedback on new elements in HTML5
- Re: Implementor feedback on new elements in HTML5
- Re: Implementor feedback on new elements in HTML5
- Re: up up up, was: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard
- Re: Questions arising from ARIA/HTML5 integration
- Re: Implementor feedback on new elements in HTML5
- Re: Questions arising from ARIA/HTML5 integration
- Re: Implementor feedback on new elements in HTML5
- Re: Implementor feedback on new elements in HTML5
- Re: Implementor feedback on new elements in HTML5
- Re: Implementor feedback on new elements in HTML5
- Re: up up up, was: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard
- Re: Implementor feedback on new elements in HTML5
- Re: Implementor feedback on new elements in HTML5
- Re: Implementor feedback on new elements in HTML5
- Re: Implementor feedback on new elements in HTML5
- Re: Implementor feedback on new elements in HTML5
- Re: Implementor feedback on new elements in HTML5
- RE: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: Implementor feedback on new elements in HTML5
- Re: Implementor feedback on new elements in HTML5
- Re: Implementor feedback on new elements in HTML5
- Implementor feedback on new elements in HTML5
- Re: HTML5 feedback from prominent designers
- not specifying UI [was: Re: Please Specify Behavior for @rel="next | prev"]
- Re: ISSUE-37 - html-svg-mathml - suggest closing on 2009-08-20
- needed updates: RE: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Rel="first" and "index" breaks specs and implementations
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03