Monday, 31 August 2009
- Re: HTML5 feedback from prominent designers
- RE: HTML5 feedback from prominent designers
- Re: HTML5 feedback from prominent designers
- HTML5 feedback from prominent designers
- Re: Current PFWG thinking on ARIA integration in host languages
- Re: up up up, was: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard
- Re: Please Specify Behavior for @rel="next | prev"
- Re: really?
- really?
- Re: Accessibility: Re: Path to Last Call (was closing various issues)
- Re: Accessibility: Re: Path to Last Call (was closing various issues)
- Re: Accessibility: Re: Path to Last Call (was closing various issues)
- RE: HTML5 Issue 11 (encoding detection): I18N WG response...
- Re: Accessibility: Re: Path to Last Call (was closing various issues)
- Accessibility: Re: Path to Last Call (was closing various issues)
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- [Bug 7468] make <table border="1" cellpadding="10" cellspacing="0"> conforming
- Re: drawImage() shouldn't throw INVALID_STATE_ERR
- Re: loadedmetadata and layout
- 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: 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: 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: 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: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- [Bug 7466] This section forbids exposing rel=feed but not exposing e.g. rel=copyright. I think that is wrong. The specification should not dictate UI for this.
- Re: Please Specify Behavior for @rel="next | prev"
- 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: 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: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: up up up, was: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: HTML5 Issue 11 (encoding detection): I18N WG response...
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: up up up, was: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard
- Re: up up up, was: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard
- Feedback about pubdate=""
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- RE: <progress> element and attributes vs. content
- Re: up up up, was: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard
- Re: up up up, was: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard
- Re: loadedmetadata and layout
- Re: Remove canvas createImageData(imagedata)
- Re: Remove canvas createImageData(imagedata)
- Re: video size when aspect ratio is not 1
- Re: video: earliest possible position changes
- Re: Stepping down
- Re: Please Specify Behavior for @rel="next | prev"
- Re: URL decomposition attributes on <a>, confusingness of references
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: URL decomposition attributes on <a>, confusingness of references
- Re: ISSUE-37 - html-svg-mathml - suggest closing on 2009-08-20
- Re: URL decomposition attributes on <a>, confusingness of references
- Re: URL decomposition attributes on <a>, confusingness of references
Sunday, 30 August 2009
- [Bug 7461] List of space characters should include U+000B LINE TABULATION (VT) or should note why it is not included.
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: ISSUE-37 - html-svg-mathml - suggest closing on 2009-08-20
- Re: Remove canvas createImageData(imagedata)
- Re: video size when aspect ratio is not 1
- Re: URL decomposition attributes on <a>, confusingness of references
- Re: ISSUE-37 - html-svg-mathml - suggest closing on 2009-08-20
- up up up, was: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard
- Re: HTML5 Issue 11 (encoding detection): I18N WG response...
- Re: video: earliest possible position changes
- Re: Comments on HTML5 Drag and Drop by Francisco Tolmasky
Saturday, 29 August 2009
Friday, 28 August 2009
- Re: another example of HTMl 5 canvas with interactive UI elements.
- Re: xmp missing from list of elements with special parsing rules
- Re: several messages
- Re: several messages
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: <header> / <footer> & ARIA
- Re: Proposal: <content> element
- Re: [html5] Event handler DOM attributes
- Re: Proposal: <content> element
- Re: definitions [was: closing on 2009-09-03]
- Re: <header> / <footer> & ARIA
- Re: <header> / <footer> & ARIA
- Re: <header> / <footer> & ARIA
- Re: Proposal: <content> element
- Re: <header> / <footer> & ARIA (was: Re: Proposal: <content> element)
- Re: Proposal: <content> element
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: <header> / <footer> & ARIA (was: Re: Proposal: <content> element)
- Re: Proposal: <content> element
- Re: <header> / <footer> & ARIA (was: Re: Proposal: <content> element)
- Re: <header> / <footer> & ARIA (was: Re: Proposal: <content> element)
- Re: Proposal: <content> element
- Re: <header> / <footer> & ARIA (was: Re: Proposal: <content> element)
- Re: Proposal: <content> element
- Re: <header> / <footer> & ARIA (was: Re: Proposal: <content> element)
- Re: Proposal: <content> element
- Re: drawImage() shouldn't throw INVALID_STATE_ERR
- <header> / <footer> & ARIA (was: Re: Proposal: <content> element)
- Re: Proposal: <content> element
- Re: Proposal: <content> element
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: ISSUE-9: video-synchronization - suggest closing on 2009-08-27 - param
- Re: author view of HTML 5 spec - static copy (2nd try)
- Re: ISSUE-9: video-synchronization - suggest closing on 2009-08-27 - param
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: Proposal: <content> element
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: Proposal: <content> element
- Re: Proposal: <content> element
- [Bug 7059] [blocked on xpathwg] Forking XPath
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: [html5] Event handler DOM attributes
- Re: drawImage() shouldn't throw INVALID_STATE_ERR
- Re: Proposal: <content> element
- Application Cache review
Thursday, 27 August 2009
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: definitions [was: closing on 2009-09-03]
- Re: definitions [was: closing on 2009-09-03]
- Re: definitions [was: closing on 2009-09-03]
- definitions [was: 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: ISSUE-61: conformance-language - suggest closing on 2009-09-03
- Please Trim CC List (was: Normative Dependency and the Seven Drafts)
- Re: [HTML5] 2.8 Character encodings
- 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: author view of HTML 5 spec - static copy (2nd try)
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: author view of HTML 5 spec - static copy (2nd try)
- Re: author view of HTML 5 spec - static copy (2nd try)
- [Bug 7444] EUC-JP and ISO-2022-JP also need replacement encodings: CP51932 (or eucJP-ms) and CP50221.
- {minutes} HTML WG telcon 2009-08-27
- [Bug 7441] The specification only ever uses the prefix:localName convention for some attributes in the XML namespace and whenever it does it is pretty explicit about it. xml:id is never mentioned outside this section and the prefixes svg and html are never used.
- [Bug 7442] Java applets are never conforming, and sometimes don't work
- Re: ISSUE-48: UA-q-quotes - suggest closing on 2009-09-03
- Re: author view of HTML 5 spec - static copy (2nd try)
- Re: author view of HTML 5 spec - static copy (2nd try)
- Re: author view of HTML 5 spec - static copy (2nd try)
- Re: Normative Dependency and the Seven Drafts
- Re: ISSUE-37 - html-svg-mathml - suggest closing on 2009-08-20
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: Normative Dependency and the Seven Drafts
- Re: ISSUE-37 - html-svg-mathml - suggest closing on 2009-08-20
- Re: Normative Dependency and the Seven Drafts
- Re: ISSUE-37 - html-svg-mathml - suggest closing on 2009-08-20
- Re: question about ARIA in HTML 5 spec text - implied use on elements not listed
- [Bug 7438] refine Status section to clarify difference between editor's bug list and the working-group issue list
- [Bug 7437] The link for "mutable" points to textareas - no mention made of radio, button, input, password types
- Re: Normative Dependency and the Seven Drafts
- Re: question about ARIA in HTML 5 spec text - implied use on elements not listed
- Re: Normative Dependency and the Seven Drafts
- Re: question about ARIA in HTML 5 spec text - implied use on elements not listed
- Re: question about ARIA in HTML 5 spec text - implied use on elements not listed
- Re: ISSUE-37 - html-svg-mathml - suggest closing on 2009-08-20
- Re: ISSUE-37 - html-svg-mathml - suggest closing on 2009-08-20
Wednesday, 26 August 2009
- Re: What a <time> element represents
- URL decomposition attributes on <a>, confusingness of references
- Re: Stepping down
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: question about ARIA in HTML 5 spec text - implied use on elements not listed
- Re: author view of HTML 5 spec - static copy (2nd try)
- Re: New co-chairs for HTML Working Group
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: Stepping down
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- author view of HTML 5 spec - static copy (2nd try)
- noscript in HTML fragment serialization algorithm
- [Bug 7434] Everything with role=heading should also have an associated aria-level that indicates the level of the heading. The level of the heading should probably be based on the outline algorithm.
- New co-chairs for HTML Working Group
- Re: question about ARIA in HTML 5 spec text - implied use on elements not listed
- Re: question about ARIA in HTML 5 spec text - implied use on elements not listed
- Stepping down
- Re: question about ARIA in HTML 5 spec text - implied use on elements not listed
- Re: question about ARIA in HTML 5 spec text - implied use on elements not listed
- Re: question about ARIA in HTML 5 spec text - implied use on elements not listed
- Re: question about ARIA in HTML 5 spec text - implied use on elements not listed
- Re: question about ARIA in HTML 5 spec text - implied use on elements not listed
- 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: 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
- [Bug 7428] Safari 4 preloads media and FF 3.5 doesn't in <audio> tag; perhaps HTML5 sections 4.8.10.5 4.8.10.8 are unclear or need a 'preloading' attribute added.
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: ISSUE-37 - html-svg-mathml - suggest closing on 2009-08-20
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
Tuesday, 25 August 2009
- 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: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: HTML 4.02
- 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: 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
- [Bug 7427] When the maxlength attribute is omitted it should return -1 like Opera and Firefox and not 0. (Alternatively it could return the maximum value like Chrome and presumably Safari do, but that seems less nice.
- Re: ISSUE-9: video-synchronization - suggest closing on 2009-08-27
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: The cite and pubdate attributes
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- [Bug 7422] Add definition of <a name>
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: ISSUE-9: video-synchronization - suggest closing on 2009-08-27
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: Feedback on the current editor's draft
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- [Bug 7409] It's not clear what labeled control is in cases with > 1 control as a child of the <label>
- 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
- [Bug 7417] Why use radians as opposed to degrees? Does this mean I can never draw a complete circle because I don't have enough bits to represent 2pi?
- Re: ISSUE-9: video-synchronization - suggest closing on 2009-08-27
- RE: ISSUE-56: urls-webarch - 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: <progress> element and attributes vs. content
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: The cite and pubdate attributes
- RE: <progress> element and attributes vs. content
- Re: ISSUE-56: urls-webarch - suggest closing on 2009-09-03
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: Path to Last Call (was closing various issues)
- Re: <progress> element and attributes vs. content
- [Bug 7414] Please add a history section
- [Bug 7413] Add definition of <html profile>
- Re: ISSUE-56: urls-webarch - suggest closing on 2009-09-03
- [Bug 7412] Add definition of <meta scheme>
Monday, 24 August 2009
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: Feedback on the current editor's draft
- Re: Feedback on the current editor's draft
- Re: Feedback on the current editor's draft
- care with subject lines, please RE: Path to Last Call ...
- Microdata
- [Bug 7411] :invalid and :out-of-range shouldn't match until the user has consciously interacted with the form. Roughly, after the input fires a change event. If, say, <input required> matches :invalid immediately on pageload, it becomes basically useless.
- RE: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: HTML 4.02
- Re: Spec with issue markers [was: Re: HTML5-warnings - request to publish as next heartbeat WD]
- Re: HTML 4.02
- Re: Path to Last Call (was closing various issues)
- Re: Spec with issue markers [was: Re: HTML5-warnings - request to publish as next heartbeat WD]
- Re: ISSUE-9: video-synchronization - suggest closing on 2009-08-27
- RE: Path to Last Call (was closing various issues)
- Re: Path to Last Call (was closing various issues)
- Re: Please Specify Behavior for @rel="next | prev"
- Re: Please Specify Behavior for @rel="next | prev"
- Re: Path to Last Call (was closing various issues)
- Re: Path to Last Call (was closing various issues)
- Re: Spec with issue markers [was: Re: HTML5-warnings - request to publish as next heartbeat WD]
- Re: Spec with issue markers [was: Re: HTML5-warnings - request to publish as next heartbeat WD]
- Re: Spec with issue markers [was: Re: HTML5-warnings - request to publish as next heartbeat WD]
- 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-9: video-synchronization - suggest closing on 2009-08-27
- Re: ISSUE-56: urls-webarch - suggest closing on 2009-09-03
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: loadedmetadata and layout
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: Spec with issue markers [was: Re: HTML5-warnings - request to publish as next heartbeat WD]
- Re: Spec with issue markers [was: Re: HTML5-warnings - request to publish as next heartbeat WD]
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: Questions arising from ARIA/HTML5 integration
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: Questions arising from ARIA/HTML5 integration
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: Spec with issue markers [was: Re: HTML5-warnings - request to publish as next heartbeat WD]
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: Spec with issue markers [was: Re: HTML5-warnings - request to publish as next heartbeat WD]
- Re: Spec with issue markers [was: Re: HTML5-warnings - request to publish as next heartbeat WD]
- Re: Please Specify Behavior for @rel="next | prev"
- Re: Please Specify Behavior for @rel="next | prev"
- Re: Please Specify Behavior for @rel="next | prev"
- 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: HTML 4.02
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: UI chrome behavior in language spec?
Sunday, 23 August 2009
- RE: Issue-4/Action-108 html-versioning - suggest closing
- UI chrome behavior in language spec?
- Default styling recommendations (was Re: Please Specify Behavior for @rel="next | prev")
- RE: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: HTML 4.02
- Re: State of HTML WG Unresolved Issues
- Re: HTML 4.02
- Re: HTML 4.02
- Re: HTML 4.02
- Re: HTML 4.02
- Re: Path to Last Call (was closing various issues)
- Re: Path to Last Call (was closing various issues)
- HTML 4.02
- Re: Please Specify Behavior for @rel="next | prev"
- Re: Please Specify Behavior for @rel="next | prev"
- Re: Path to Last Call (was closing various issues)
- Re: Path to Last Call (was closing various issues)
- Re: Path to Last Call (was closing various issues)
- Re: Path to Last Call (was closing various issues)
- Re: Please Specify Behavior for @rel="next | prev"
- Re: Path to Last Call (was closing various issues)
- Re: question about ARIA in HTML 5 spec text - implied use on elements not listed
- Re: Path to Last Call (was closing various issues)
- Re: Path to Last Call (was closing various issues)
- ISSUE-9: video-synchronization - suggest closing on 2009-08-27
- Re: Please Specify Behavior for @rel="next | prev"
- Please Specify Behavior for @rel="next | prev"
- How to track issues that block PR but not Last Call (was Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03)
- Re: Path to Last Call (was closing various issues)
- Proposal for Lazy Consensus: Details of Media Type Registration
- ISSUE-8 (was Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03)
- Re: Path to Last Call (was closing various issues)
- Path to Last Call (was closing various issues)
Saturday, 22 August 2009
- Re: question about ARIA in HTML 5 spec text - implied use on elements not listed
- question about ARIA in HTML 5 spec text - implied use on elements not listed
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- 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
- Issue-4/Action-108 html-versioning - suggest closing
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: loadedmetadata and layout
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: ISSUE-56: urls-webarch - 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: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Questions arising from ARIA/HTML5 integration
Friday, 21 August 2009
- RE: ISSUE-56: urls-webarch - suggest closing on 2009-09-03
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: ISSUE-56: urls-webarch - suggest closing on 2009-09-03
- Re: ISSUE-66: image analysis heuristics - suggest closing on 2009-09-03
- Minutes: HTML Canvas Accessibility Meeting August 21, 2009
- Re: ISSUE-66: image analysis heuristics - suggest closing on 2009-09-03
- Minutes: HTML Canvas Accessibility Meeting August 21, 2009
- Re: ISSUE-66: image analysis heuristics - suggest closing on 2009-09-03
- Re: ISSUE-66: image analysis heuristics - suggest closing on 2009-09-03
- Re: ISSUE-54: doctype-legacy-compat - suggest closing on 2009-09-03
- Re: ISSUE-54: doctype-legacy-compat - suggest closing on 2009-09-03
- Re: ISSUE-61: conformance-language - suggest closing on 2009-09-03
- Suggested conflict-resolution process for DRFa vs. Microdata using global metadata goals
- Re: ISSUE-66: image analysis heuristics - suggest closing on 2009-09-03
- Re: change "URL" to "web address" throughout the HTML 5 spec (Issue-56 urls-webarch)
- Re: ISSUE-13: suggest closing
- Re: ISSUE-13: suggest closing
- Re: ARIA document conformance matrix
- [Bug 7391] Reference to WEBADDRESS should be replaced with reference to IRIbis
- [Bug 7392] Please use some term other than "URL" for Web Addresses
- Re: ISSUE-13: suggest closing
- Remove canvas createImageData(imagedata)
- Re: ISSUE-61: conformance-language - suggest closing on 2009-09-03
- Re: ISSUE-61: conformance-language - suggest closing on 2009-09-03
- Re: ARIA document conformance matrix
- Re: ISSUE-13: suggest closing
- re: ARIA document conformance matrix
- video size when aspect ratio is not 1
- Re: ISSUE-54: doctype-legacy-compat - suggest closing on 2009-09-03
- Re: ISSUE-54: doctype-legacy-compat - suggest closing on 2009-09-03
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: ISSUE-54: doctype-legacy-compat - 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: ISSUE-56: urls-webarch - 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: ISSUE-56: urls-webarch - suggest closing on 2009-09-03
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: ISSUE-54: doctype-legacy-compat - suggest closing on 2009-09-03
- Re: New Version Notification for draft-duerst-iri-bis-06
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: ISSUE-56: urls-webarch - suggest closing on 2009-09-03
- Re: ISSUE-56: urls-webarch - 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: ISSUE-54: doctype-legacy-compat - suggest closing on 2009-09-03
- Re: ISSUE-56: urls-webarch - suggest closing on 2009-09-03
- Re: ISSUE-54: doctype-legacy-compat - suggest closing on 2009-09-03
- Re: ISSUE-56: urls-webarch - suggest closing on 2009-09-03
- Re: ISSUE-54: doctype-legacy-compat - suggest closing on 2009-09-03
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- Re: ISSUE-56: urls-webarch - suggest closing on 2009-09-03
- Re: ISSUE-54: doctype-legacy-compat - suggest closing on 2009-09-03
- Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- ISSUE-75: microsoft-review - suggest closing on 2009-09-03
- ISSUE-66: image analysis heuristics - suggest closing on 2009-09-03
- ISSUE-61: conformance-language - suggest closing on 2009-09-03
- ISSUE-64: web-sockets-scope-req - suggest closing on 2009-09-03
- ISSUE-60: html5-xhtml-namespace - suggest closing on 2009-09-03
- ISSUE-56: urls-webarch - suggest closing on 2009-09-03
- ISSUE-54: doctype-legacy-compat - suggest closing on 2009-09-03
- ISSUE-51: aria-curie - suggest closing on 2009-09-03
- ISSUE-53: mediatypereg - suggest closing on 2009-09-03
- ISSUE-48: UA-q-quotes - suggest closing on 2009-09-03
- State of HTML WG Unresolved Issues
- Issues closed
Thursday, 20 August 2009
- Re: HTML5 Issue 11 (encoding detection): I18N WG response...
- Re: HTML5 Issue 11 (encoding detection): I18N WG response...
- [Bug 7386] SharedWorkerGlobalScope
- [Bug 7387] small element should have same content model as a, ins, del
- RE: ISSUE-41/ACTION-97 decentralized-extensibility
Wednesday, 19 August 2009
Thursday, 20 August 2009
- Re: Publishing a new draft (HTML5+RDFa)
- Re: ISSUE-13: suggest closing
- change "URL" to "web address" throughout the HTML 5 spec (Issue-56 urls-webarch)
- RE: Bug 7381 (default encoding selection)
- Re: ISSUE-41/ACTION-97 decentralized-extensibility
- ISSUE-41/ACTION-97 decentralized-extensibility
- RE: HTML5 Issue 11 (encoding detection): I18N WG response...
- Re: ISSUE-13: suggest closing
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: [Bug 6853] New: restore meta keywords, search engines use them
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: [Bug 6853] New: restore meta keywords, search engines use them
- Re: [Bug 6853] New: restore meta keywords, search engines use them
- Bug 7381 (default encoding selection)
- [Bug 7382] U+000D CARRIAGE RETURN in escaping text spans
- Re: HTML5 Issue 11 (encoding detection): I18N WG response...
- [Bug 7381] Clarify default encoding wording and add some examples for non-latin locales.
- Re: HTML5 Issue 11 (encoding detection): I18N WG response...
- [Bug 7380] Suggest heuristic detection of UTF-8
- Re: HTML5 Issue 11 (encoding detection): I18N WG response...
- Re: HTML5 Issue 11 (encoding detection): I18N WG response...
- Re: HTML5 Issue 11 (encoding detection): I18N WG response...
- RE: HTML5 Issue 11 (encoding detection): I18N WG response...
- RE: HTML5 Issue 11 (encoding detection): I18N WG response...
- Re: HTML5 Issue 11 (encoding detection): I18N WG response...
- RE: HTML5 Issue 11 (encoding detection): I18N WG response...
- Re: HTML5 Issue 11 (encoding detection): I18N WG response...
- RE: HTML5 Issue 11 (encoding detection): I18N WG response...
- Re: ISSUE-37 - html-svg-mathml - suggest closing on 2009-08-20
- Re: ISSUE-37 - html-svg-mathml - suggest closing on 2009-08-20
- [Bug 7378] element name case fixup table is missing two SVG1.2T entries
- [Bug 7379] HTML5 should reference SVG1.1 as well as SVG1.2T
- Re: HTML5 Issue 11 (encoding detection): I18N WG response...
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: ISSUE-37 - html-svg-mathml - suggest closing on 2009-08-20
- Re: HTML5 Issue 11 (encoding detection): I18N WG response...
- HTML5 Issue 11 (encoding detection): I18N WG response...
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- [Bug 7373] Need to fix "If a Document or image was returned by the XMLHttpRequest API" now that the document pointer concept is gone.
- [Bug 7374] legend as child of details, figure is unstylable and thus unusable
- [Bug 7375] Incorrect specification for window.postMessage()'s handling of unentangled ports
Wednesday, 19 August 2009
- Re: [Bug 6853] New: restore meta keywords, search engines use them
- Please file bugs for issues
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: {agenda} HTML WG telcon 2009-08-20
- Comments on HTML5 Drag and Drop by Francisco Tolmasky
- 4.2.4 The link element -- link types
- 6.12.1 Hyperlink elements
- Re: meta/@name=description
- Re: Current PFWG thinking on ARIA integration in host languages
- video: earliest possible position changes
- Re: [Bug 6853] New: restore meta keywords, search engines use them
- Re: [Bug 6853] New: restore meta keywords, search engines use them
- Re: The cite and pubdate attributes
- Re: [Bug 6853] New: restore meta keywords, search engines use them
- Re: [Bug 6853] New: restore meta keywords, search engines use them
- Re: meta/@name=description
- Re: meta/@name=description
- Re: [Bug 6853] New: restore meta keywords, search engines use them
- Re: The cite and pubdate attributes
- meta/@name=description
- Re: Spec with issue markers [was: Re: HTML5-warnings - request to publish as next heartbeat WD]
- Re: Spec with issue markers [was: Re: HTML5-warnings - request to publish as next heartbeat WD]
- Re: Spec with issue markers [was: Re: HTML5-warnings - request to publish as next heartbeat WD]
- Re: [Bug 6853] New: restore meta keywords, search engines use them
- Re: Spec with issue markers [was: Re: HTML5-warnings - request to publish as next heartbeat WD]
- Re: Spec with issue markers [was: Re: HTML5-warnings - request to publish as next heartbeat WD]
- [Bug 7367] The HTMLEmbedElement interface needs to have the name and align DOM attributes as well. Web browsers do too.
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: Spec with issue markers [was: Re: HTML5-warnings - request to publish as next heartbeat WD]
- RE: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: Spec with issue markers [was: Re: HTML5-warnings - request to publish as next heartbeat WD]
Tuesday, 18 August 2009
- Re: Spec with issue markers [was: Re: HTML5-warnings - request to publish as next heartbeat WD]
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: Withdrawal of HTML5-warnings draft
- Re: Current PFWG thinking on ARIA integration in host languages
- Re: Current PFWG thinking on ARIA integration in host languages
- Re: Current PFWG thinking on ARIA integration in host languages
- Re: Current PFWG thinking on ARIA integration in host languages
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: Current PFWG thinking on ARIA integration in host languages
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: HTML5/SMIL integration [was: Re: ISSUE-10: suggest closing]
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Current PFWG thinking on ARIA integration in host languages
- Re: role vs aria-role
- Re: role vs aria-role
- Re: HTML5/SMIL integration [was: Re: ISSUE-10: suggest closing]
- Re: HTML5/SMIL integration [was: Re: ISSUE-10: suggest closing]
- Re: ISSUE-37 - html-svg-mathml - suggest closing on 2009-08-20
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: Normative Dependency and the Seven Drafts (was: Canvas API Editors)
- Re: Withdrawal of HTML5-warnings draft
- Re: role vs aria-role
- xmp missing from list of elements with special parsing rules
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: Separate Draft of Canvas API Uploaded to CVS
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: role vs aria-role
- Re: Normative Dependency and the Seven Drafts
- Re: The cite and pubdate attributes
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: Withdrawal of HTML5-warnings draft
- Re: role vs aria-role
- Re: Normative Dependency and the Seven Drafts
- Re: Normative Dependency and the Seven Drafts
- Re: Normative Dependency and the Seven Drafts
- Re: Normative Dependency and the Seven Drafts
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: Withdrawal of HTML5-warnings draft
- Re: role vs aria-role
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: Withdrawal of HTML5-warnings draft
- Withdrawal of HTML5-warnings draft
- role vs aria-role
- Normative Dependency and the Seven Drafts (was: Canvas API Editors)
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: Canvas API Editors
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: Canvas API Editors
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
Monday, 17 August 2009
- Re: feedback requested on WAI CG Consensus Resolutions on Text
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: Separate Draft of Canvas API Uploaded to CVS
- Re: Canvas API Editors (was: who would be interested in working with a Canvas object/2D API separate group)
- Re: Canvas API Editors (was: who would be interested in working with a Canvas object/2D API separate group)
- Re: 'loadend' event on media elements
- Re: Separate Draft of Canvas API Uploaded to CVS
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Canvas API Editors (was: who would be interested in working with a Canvas object/2D API separate group)
- Re: Separate Draft of Canvas API Uploaded to CVS
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: Separate Draft of Canvas API Uploaded to CVS
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: Separate Draft of Canvas API Uploaded to CVS
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- [html5] Event handler DOM attributes
- Re: Separate Draft of Canvas API Uploaded to CVS
- Re: Separate Draft of Canvas API Uploaded to CVS
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Separate Draft of Canvas API Uploaded to CVS
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: Proposal: <content> element
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: Proposal: <content> element
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: Proposal: <content> element
- Re: Proposal: <content> element
- Re: Proposal: <content> element
- Re: Proposal: <content> element
- Re: drawImage() shouldn't throw INVALID_STATE_ERR
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: <progress> element and attributes vs. content
- Re: Proposal: <content> element
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: Proposal: <content> element
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: Proposal: <content> element
- Re: Proposal: <content> element
- Re: Proposal: <content> element
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: Proposal: <content> element
- Proposal: <content> element
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: HTML5/SMIL integration [was: Re: ISSUE-10: suggest closing]
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
Sunday, 16 August 2009
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: The cite and pubdate attributes
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: What a <time> element represents
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
Saturday, 15 August 2009
Sunday, 16 August 2009
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: Recording teleconferences?
- Re: <canvas> Usage (Was: Begin discussions for pushing Last Call into 2010)
- Re: [HTML5] 2.8 Character encodings
- Re: What a <time> element represents
- Re: [HTML5] 2.8 Character encodings
- Re: What a <time> element represents
- Re: --!> comment ends [was: RE: HTML5-warnings - request to publish as next heartbeat WD]
- Re: The cite and pubdate attributes
- HTML5/SMIL integration [was: Re: ISSUE-10: suggest closing]
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- wording of messages [was: Re: Movement on @summary]
Saturday, 15 August 2009
- Re: Recording teleconferences?
- Re: The cite and pubdate attributes
- --!> comment ends [was: RE: HTML5-warnings - request to publish as next heartbeat WD]
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: Recording teleconferences?
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- RE: Recording teleconferences?
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- RE: Recording teleconferences?
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: Recording teleconferences?
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: <canvas> Usage (Was: Begin discussions for pushing Last Call into 2010)
- Re: <canvas> Usage (Was: Begin discussions for pushing Last Call into 2010)
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- RE: Recording teleconferences?
- Re: Recording teleconferences?
- RE: Recording teleconferences?
- Re: Recording teleconferences?
- Re: Recording teleconferences?
- RE: Recording teleconferences?
- Re: Recording teleconferences?
- Re: Recording teleconferences?
- Re: ISSUE-20: table-headers - suggest closing on 2009-08-20
- Re: Recording teleconferences?
- Re: The cite and pubdate attributes
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- <canvas> Usage (Was: Begin discussions for pushing Last Call into 2010)
- Re: ISSUE-28: http-mime-override - suggest closing on 2009-08-20
- Re: More suggestions for issues to be closed (http-mime-override)
- Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- RE: <bb> element
- HTML 5 canvas accessibility - discussion happening on public-canvas-api@w3.org
- feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document
- Re: canvas text: ctx.font='inherit'
- Re: The cite and pubdate attributes
- Re: update on ACTION-103 (Register about: URI scheme)
- Re: Recording teleconferences?
- Re: <progress> element and attributes vs. content
- Re: Recording teleconferences?
- RE: Recording teleconferences?
- Re: <progress> element and attributes vs. content
- Re: Recording teleconferences?
- RE: Recording teleconferences?
- Re: <progress> element and attributes vs. content
- RE: <progress> element and attributes vs. content
- Re: before head/in head/after head treatment of /p should match /br
Friday, 14 August 2009
- Re: Recording teleconferences?
- Re: Recording teleconferences?
- Re: <progress> element and attributes vs. content
- Re: Recording teleconferences?
- Re: <progress> element and attributes vs. content
- Re: ISSUE-11: default-encoding - suggest closing on 2009-08-20
- Re: <progress> element and attributes vs. content
- Re: Recording teleconferences?
- Re: <progress> element and attributes vs. content
- Re: Recording teleconferences?
- Re: <progress> element and attributes vs. content
- Re: Recording teleconferences?
- Re: <progress> element and attributes vs. content
- Re: Recording teleconferences?
- Re: Recording teleconferences?
- Re: Recording teleconferences?
- RE: Recording teleconferences?
- Re: <progress> element and attributes vs. content
- RE: Recording teleconferences?
- Re: Recording teleconferences?
- RE: Recording teleconferences?
- Re: Recording teleconferences?
- RE: <progress> element and attributes vs. content
- Re: <progress> element and attributes vs. content
- Re: Recording teleconferences?
- RE: Recording teleconferences?
- <progress> element and attributes vs. content
- Re: Recording teleconferences?
- Re: Recording teleconferences?
- Re: Recording teleconferences?
- Re: Recording teleconferences?
- Re: Recording teleconferences?
- Re: Recording teleconferences?
- Re: Recording teleconferences?
- Re: Recording teleconferences?
- Re: Recording teleconferences?
- Re: Recording teleconferences?
- Re: Feedback on the current editor's draft
- Re: Recording teleconferences?
- [wbs] response to 'Publish HTML 5 update with or without warnings?'
- Re: problems connecting to the teleconference
- Re: Recording teleconferences?
- Re: Recording teleconferences?
- Re: Recording teleconferences?
- Re: Feedback on the current editor's draft
- Re: Spec with issue markers [was: Re: HTML5-warnings - request to publish as next heartbeat WD]
- Spec with issue markers [was: Re: HTML5-warnings - request to publish as next heartbeat WD]
- RE: <bb> element
- Re: Feedback on the current editor's draft
- Re: Feedback on the current editor's draft
- Re: Feedback on the current editor's draft
- Re: 'progress' events for media elements
- Re: NEW DRAFT: HTML5-warnings - now with consistent warnings
- Re: NEW DRAFT: HTML5-warnings - now with consistent warnings
- Re: NEW DRAFT: HTML5-warnings - now with consistent warnings
- Re: ISSUE-11: default-encoding - suggest closing on 2009-08-20
- Re: loadedmetadata and layout
- Re: HTML5-warnings - request to publish as next heartbeat WD
- Re: ISSUE-11: default-encoding - suggest closing on 2009-08-20
- ISSUE-43 - client-side image maps - suggest closing on 2009-08-20
- ISSUE-38 - style-attr-syntax - suggest closing on 2009-08-20
- ISSUE-37 - html-svg-mathml - suggest closing on 2009-08-20
- ISSUE-36 - client-side-storage-sql
- ISSUE-34: commonality - suggest closing on 2009-08-20
- ISSUE-28: http-mime-override - suggest closing on 2009-08-20
- ISSUE-26: accessibility/usability of HTML5 and W3C default stylesheets - suggest closing on 2009-08-20
- ISSUE-20: table-headers - suggest closing on 2009-08-20
- ISSUE-17: media-queries-tab-preprocessing - suggest closing on 2009-08-20
- ISSUE-16: offline-applications-sql - suggest closing on 2009-08-20
- ISSUE-13: handling-http-401-status - suggest closing on 2009-08-20
- ISSUE-11: - suggest closing on 2009-08-20
- ISSUE-12: test-case-file-names - suggest closing on 2009-08-20
- ISSUE-10: video-smil (should we make <video> attributes more similar to SMIL?) - suggest closing on 2009-08-20
- ISSUE-9: video-synchronization - suggest closing on 2009-08-20
- ISSUE-6: videoaudio (Pros and cons of keeping video and audio in scope) - suggest closing on 2009-08-20
- ISSUE-5: button-type-radio - suggest closing on 2009-08-20
- Re: NEW DRAFT: HTML5-warnings - now with consistent warnings
- NEW DRAFT: HTML5-warnings - now with consistent warnings
- Re: 'loadend' event on media elements
- Re: 'loadend' event on media elements
- Re: drawImage() shouldn't throw INVALID_STATE_ERR
- Re: loadedmetadata and layout
Thursday, 13 August 2009
- Re: pause when media playback has ended
- Re: ISSUE-6: suggest closing (keeping video and audio in the scope of the HTML working group)
- Re: Infinite loop in fragment case
- Re: postMessage: origin serialized too early
- Re: ISSUE-10: suggest closing: how similar should SMIL and <video> attribute names be?
- Re: ISSUE-11: suggest closing (default character encoding)
- Re: ISSUE-11: suggest closing (default character encoding)
- Re: ISSUE-10: suggest closing: how similar should SMIL and <video> attribute names be?
- Re: ISSUE-6: suggest closing (keeping video and audio in the scope of the HTML working group)
- Re: ISSUE-10: suggest closing: how similar should SMIL and <video> attribute names be?
- Re: HTML5-warnings - request to publish as next heartbeat WD
- {minutes} HTML WG telcon 2009-08-13 for review
- Author view of the spec
- Re: HTML5-warnings - request to publish as next heartbeat WD
- Re: who would be interested in working with a Canvas object/2D API separate group
- RE: HTML5-warnings - request to publish as next heartbeat WD
- Re: who would be interested in working with a Canvas object/2D API separate group
- Re: who would be interested in working with a Canvas object/2D API separate group
- Re: who would be interested in working with a Canvas object/2D API separate group
- Re: who would be interested in working with a Canvas object/2D API separate group
- [Registration] 2009-11 F2F meeting of the HTML WG
- Re: Recording teleconferences?
- Re: who would be interested in working with a Canvas object/2D API separate group
- Re: <canvas> and the 2D context API
- who would be interested in working with a Canvas object/2D API separate group
- Re: <canvas> and the 2D context API
- Re: <canvas> and the 2D context API
- Re: <canvas> and the 2D context API
- Re: <canvas> and the 2D context API
- Re: Recording teleconferences?
- Re: <canvas> and the 2D context API (was RE: Begin discussions for pushing Last Call into 2010)
- Re: <canvas> and the 2D context API
- Re: Recording teleconferences?
- Recording teleconferences?
- Re: <canvas> and the 2D context API (was RE: Begin discussions for pushing Last Call into 2010)
- Re: More suggestions for issues to be closed (http-mime-override)
- change policy for HTML namespace (ISSUE-60 html5-xhtml-namespace)
- Re: Begin discussions for pushing Last Call into 2010
- Re: Begin discussions for pushing Last Call into 2010
- Re: Begin discussions for pushing Last Call into 2010
- Re: Begin discussions for pushing Last Call into 2010
- Re: Begin discussions for pushing Last Call into 2010
- Re: Begin discussions for pushing Last Call into 2010
- Re: Begin discussions for pushing Last Call into 2010
- Re: <canvas> and the 2D context API (was RE: Begin discussions for pushing Last Call into 2010)
- Accessibility Procedure (was Re: HTML5-warnings - request to publish as next heartbeat WD)
- Re: HTML5-warnings - request to publish as next heartbeat WD
- Re: Issues arising from not reparsing
- Re: Issues arising from not reparsing
- RE: Issue-74/Action-133 canvas-accessibility
- Re: <canvas> and the 2D context API (was RE: Begin discussions for pushing Last Call into 2010)
- Re: <canvas> and the 2D context API (was RE: Begin discussions for pushing Last Call into 2010)
- Re: <canvas> and the 2D context API (was RE: Begin discussions for pushing Last Call into 2010)
- Re: <canvas> and the 2D context API (was RE: Begin discussions for pushing Last Call into 2010)
- Re: <canvas> and the 2D context API (was RE: Begin discussions for pushing Last Call into 2010)
- Re: Begin discussions for pushing Last Call into 2010
- Re: Begin discussions for pushing Last Call into 2010
- <canvas> and the 2D context API (was RE: Begin discussions for pushing Last Call into 2010)
Wednesday, 12 August 2009
- Re: Begin discussions for pushing Last Call into 2010
- Re: [HTML5] DOMContentLoaded fires before CSS resources loaded?
- Re: Begin discussions for pushing Last Call into 2010
- Re: Begin discussions for pushing Last Call into 2010
- Re: Begin discussions for pushing Last Call into 2010
- Re: The script element
- Re: Begin discussions for pushing Last Call into 2010
- Re: Begin discussions for pushing Last Call into 2010
- Re: Begin discussions for pushing Last Call into 2010
- Re: Begin discussions for pushing Last Call into 2010
- Re: Issues arising from not reparsing
- Re: [http-state] cookie dates [was Re: Status update]
- Re: [http-state] cookie dates [was Re: Status update]
- Re: closing issue-30 longdesc in favor of aria-describedby [was: Consolidated issues ...]
- Re: closing issue-30 longdesc in favor of aria-describedby [was: Consolidated issues ...]
- Re: closing issue-30 longdesc in favor of aria-describedby [was: Consolidated issues ...]
- Re: Issue-74/Action-133 canvas-accessibility and ISSUE-15 immediate-mode-graphics [was: {agenda} HTML WG telcon 2009-08-13]
- Re: <bb> element (was RE: Feedback on the current editor's draft)
- Re: Issues arising from not reparsing
- Re: Consolidated issues that may qualify as "controversial"
- [wbs] response to 'Publish HTML 5 update with or without warnings?'
- Re: closing issue-30 longdesc in favor of aria-describedby [was: Consolidated issues ...]
- Re: closing issue-30 longdesc in favor of aria-describedby [was: Consolidated issues ...]
- Re: Begin discussions for pushing Last Call into 2010
- Re: Begin discussions for pushing Last Call into 2010
- Re: Begin discussions for pushing Last Call into 2010
- Re: HTML5-warnings - request to publish as next heartbeat WD
- Re: closing issue-30 longdesc in favor of aria-describedby [was: Consolidated issues ...]
- Begin discussions for pushing Last Call into 2010
- Re: Issue-74/Action-133 canvas-accessibility and ISSUE-15 immediate-mode-graphics [was: {agenda} HTML WG telcon 2009-08-13]
- Re: HTML5-warnings - request to publish as next heartbeat WD
- Re: update on ACTION-125 (Coordinate with LMM and DanC to get an Internet Draft that addresses some HTML 5 href issues)
- update on ACTION-103 (Register about: URI scheme)
- Re: Consolidated issues that may qualify as "controversial"
- Re: Feedback on the current editor's draft
- Re: Consolidated issues that may qualify as "controversial"
- Re: Issues arising from not reparsing
- Re: [http-state] cookie dates [was Re: Status update]
- Re: Consolidated issues that may qualify as "controversial"
- Re: Consolidated issues that may qualify as "controversial"
- Re: [http-state] cookie dates [was Re: Status update]
- Re: Consolidated issues that may qualify as "controversial"
- Re: Issues arising from not reparsing
- Re: Consolidated issues that may qualify as "controversial"
- Re: Feedback on the current editor's draft
- Re: <bb> element (was RE: Feedback on the current editor's draft)
- [Bug 7264] make <% start a bogus comment
- Re: Issues arising from not reparsing
- Re: Consolidated issues that may qualify as "controversial"
- Re: Regarding closing issues
- Re: Consolidated issues that may qualify as "controversial"
- Re: Regarding closing issues
- Consolidated issues that may qualify as "controversial"
- More suggested issues to close
- Re: Feedback on the current editor's draft
- Re: [HTML5] 2.8 Character encodings
- RE: [HTML5] 2.8 Character encodings
- [wbs] response to 'Publish HTML 5 update with or without warnings?'
- Regarding closing issues
Tuesday, 11 August 2009
- [wbs] response to 'Publish HTML 5 update with or without warnings?'
- [wbs] response to 'Publish HTML 5 update with or without warnings?'
- [wbs] response to 'Publish HTML 5 update with or without warnings?'
- Re: ISSUE-20: table-headers test cases from Chaals? (was Re: More suggestions for issues to be closed)
- Re: HTML5-warnings - request to publish as next heartbeat WD
- Re: HTML5-warnings - request to publish as next heartbeat WD
- Re: [POLL]: Publish HTML 5 update with or without warnings?
- Re: HTML5-warnings - request to publish as next heartbeat WD
- Re: ISSUE-5: please close this issue (button-type-radio)
- Re: [POLL]: Publish HTML 5 update with or without warnings?
- [wbs] response to 'Publish HTML 5 update with or without warnings?'
- [wbs] response to 'Publish HTML 5 update with or without warnings?'
- Re: HTML5-warnings - request to publish as next heartbeat WD
- Re: HTML5-warnings - request to publish as next heartbeat WD
- Re: HTML5-warnings - request to publish as next heartbeat WD
- Re: HTML5-warnings - request to publish as next heartbeat WD
- [wbs] response to 'Publish HTML 5 update with or without warnings?'
- [wbs] response to 'Publish HTML 5 update with or without warnings?'
- Re: HTML5-warnings - request to publish as next heartbeat WD
- Re: Feedback on the current editor's draft
- Re: Feedback on the current editor's draft
- [Bug 7260] Create testsuite for table headers association
- Re: Feedback on the current editor's draft
- Re: [POLL]: Publish HTML 5 update with or without warnings?
- Re: Feedback on the current editor's draft
- Re: [POLL]: Publish HTML 5 update with or without warnings?
- Re: ISSUE-5: please close this issue (button-type-radio)
- Re: [POLL]: Publish HTML 5 update with or without warnings?
- RE: Feedback on the current editor's draft
- [POLL]: Publish HTML 5 update with or without warnings?
- HTML 5 and canvas
- Re: ISSUE-20: table-headers test cases from Chaals? (was Re: More suggestions for issues to be closed)
- Re: ISSUE-20: table-headers test cases from Chaals? (was Re: More suggestions for issues to be closed)
- ISSUE-20: table-headers test cases from Chaals? (was Re: More suggestions for issues to be closed)
- Re: What a <time> element represents
- Re: What a <time> element represents
- Re: ISSUE-10: suggest closing
- Re: ISSUE-10: suggest closing
- What a <time> element represents
- Re: ISSUE-13: suggest closing
- More suggestions for issues to be closed
- Re: <a ping>
- Re: ISSUE-13: suggest closing
- Re: HTML5-warnings - motivations (was: HTML5-warnings - request to publish as next heartbeat WD)
- controversial issue candidates in issues 1-15
- ISSUE-13: suggest closing
- ISSUE-12: suggest closing
- <a ping>
- ISSUE-6: suggest closing
- ISSUE-9: suggest closing
- ISSUE-10: suggest closing
- ISSUE-11: suggest closing
- Re: HTML5-warnings - request to publish as next heartbeat WD
- ISSUE-5: please close this issue
- Re: HTML5-warnings - request to publish as next heartbeat WD
- Re: HTML5-warnings - request to publish as next heartbeat WD
- Re: <bb> element (was RE: Feedback on the current editor's draft)
- RE: HTML5-warnings - request to publish as next heartbeat WD
- Re: <bb> element (was RE: Feedback on the current editor's draft)
- RE: <datagrid> element (was RE: Feedback on the current editor's draft)
- Re: HTML5-warnings - request to publish as next heartbeat WD
- RE: <bb> element (was RE: Feedback on the current editor's draft)
- Re: HTML5-warnings - request to publish as next heartbeat WD
- Re: canvas text: ctx.font='inherit'
- Re: HTML5-warnings - request to publish as next heartbeat WD
- Re: HTML5-warnings - request to publish as next heartbeat WD
- Re: HTML5-warnings - request to publish as next heartbeat WD
- Re: Format for type attribute value
Monday, 10 August 2009
- Re: [DRAFT] Heartbeat poll - update 6 - on to implementation
- Re: lang and RFC3066
- Re: [DRAFT] Heartbeat poll - update 6 - on to implementation
- Re: RFC 2396 v. RFC 3986 v. RFC 3987 (general comment, part of detailed review of spec)
- Re: HTML5-warnings - request to publish as next heartbeat WD
- Re: [DRAFT] Heartbeat poll - update 6 - on to implementation
- Re: [DRAFT] Heartbeat poll - update 6 - on to implementation
- Re: [DRAFT] Heartbeat poll - update 6 - on to implementation
- [DRAFT] Heartbeat poll - update 6 - on to implementation
- Re: HTML5-warnings - motivations (was: HTML5-warnings - request to publish as next heartbeat WD)
- Re: HTML5-warnings - request to publish as next heartbeat WD
- Re: HTML5-warnings - motivations
- Re: HTML5-warnings - request to publish as next heartbeat WD
- Re: HTML5-warnings - request to publish as next heartbeat WD
- Re: HTML5-warnings - motivations (was: HTML5-warnings - request to publish as next heartbeat WD)
- Re: how do we get permission to raise issues in the issues tracker?
- Re: HTML5-warnings - motivations
- Re: HTML5-warnings - request to publish as next heartbeat WD
- Re: how do we get permission to raise issues in the issues tracker?
- Re: HTML5-warnings - motivations
- Re: HTML5-warnings - motivations (was: HTML5-warnings - request to publish as next heartbeat WD)
- Re: HTML5-warnings - motivations
- Re: HTML5-warnings - request to publish as next heartbeat WD
- Re: HTML5-warnings - motivations
- Re: The cite and pubdate attributes
- Re: HTML5-warnings - motivations
- Re: HTML5-warnings - request to publish as next heartbeat WD
- Re: HTML5-warnings - motivations
- Re: how do we get permission to raise issues in the issues tracker?
- Re: The cite and pubdate attributes
- Re: HTML5-warnings - motivations
- Re: how do we get permission to raise issues in the issues tracker?
- Re: HTML5-warnings - motivations
- how do we get permission to raise issues in the issues tracker?
- Re: HTML5-warnings - request to publish as next heartbeat WD
- Re: HTML5-warnings - motivations
- Re: HTML5-warnings - motivations (was: HTML5-warnings - request to publish as next heartbeat WD)
- Re: HTML5-warnings - request to publish as next heartbeat WD
- Re: HTML5-warnings - motivations (was: HTML5-warnings - request to publish as next heartbeat WD)
- Re: Test results for xmlns:foo attribute preservation across all browsers
- Re: Issues arising from not reparsing
- Re: Bogus note in "before head"
- Re: HTML5-warnings - request to publish as next heartbeat WD
- Re: The cite and pubdate attributes
- Re: Issues arising from not reparsing
- The cite and pubdate attributes
- Re: Addendum to the new <audio> tag.
- Re: Addendum to the new <audio> tag.
- Issues arising from not reparsing
- before head/in head/after head treatment of /p should match /br
- Bogus note in "before head"
- Re: HTML5-warnings - minimum supporters requirement met
- Re: Addendum to the new <audio> tag.
- Re: HTML5-warnings - minimum supporters requirement met
- Re: HTML5-warnings - request to publish as next heartbeat WD
- Re: HTML5-warnings - request to publish as next heartbeat WD
- Re: Addendum to the new <audio> tag.
- Re: Addendum to the new <audio> tag.
- Re: HTML5-warnings - request to publish as next heartbeat WD
- Re: Addendum to the new <audio> tag.
- Re: HTML5-warnings - request to publish as next heartbeat WD
- Addendum to the new <audio> tag.
Friday, 7 August 2009
Monday, 10 August 2009
- Re: HTML5-warnings - request to publish as next heartbeat WD
- Re: Feedback on the current editor's draft
- Re: HTML5-warnings - minimum supporters requirement met
- Re: HTML5-warnings - request to publish as next heartbeat WD
- Re: HTML5-warnings - request to publish as next heartbeat WD
- Re: Feedback on the current editor's draft
- Re: HTML5-warnings - minimum supporters requirement met
- Re: HTML5-warnings - request to publish as next heartbeat WD
- Re: HTML5-warnings - minimum supporters requirement met
- Re: HTML5-warnings - request to publish as next heartbeat WD
- Re: [whatwg] HTML5-warnings - request to publish as next heartbeat WD
- HTML5-warnings - minimum supporters requirement met (was: HTML5-warnings - request to publish as next heartbeat WD)
Sunday, 9 August 2009
- Re: HTML5-warnings - request to publish as next heartbeat WD
- RE: HTML5-warnings - request to publish as next heartbeat WD
- Re: HTML5-warnings - request to publish as next heartbeat WD
- Re: HTML5-warnings - request to publish as next heartbeat WD
- RE: HTML5-warnings - request to publish as next heartbeat WD
- Re: HTML5-warnings - request to publish as next heartbeat WD
- RE: HTML5-warnings - request to publish as next heartbeat WD
- Re: HTML5-warnings - request to publish as next heartbeat WD
- Re: HTML5-warnings - request to publish as next heartbeat WD
- Re: HTML5-warnings - request to publish as next heartbeat WD
- Re: How did the summary attribute become part of HTML 4.0?
- Re: How did the summary attribute become part of HTML 4.0?
- Re: [whatwg] HTML5-warnings - request to publish as next heartbeat WD
- Re: HTML5-warnings - request to publish as next heartbeat WD
- HTML5-warnings - request to publish as next heartbeat WD
Saturday, 8 August 2009
- Re: Feedback on the current editor's draft
- Re: Feedback on the current editor's draft
- Re: How did the summary attribute become part of HTML 4.0?
- epub (xhtml) indexing Re: Scope of HTML5...
- Re: How did the summary attribute become part of HTML 4.0?
- Re: How did the summary attribute become part of HTML 4.0?
- Re: Scope of HTML5...
- Re: How did the summary attribute become part of HTML 4.0?
- Re: How did the summary attribute become part of HTML 4.0?
- Re: How did the summary attribute become part of HTML 4.0?
- Re: Google to pay for HTMLWG invited experts at TPAC 2009
- Re: How did the summary attribute become part of HTML 4.0?
- Re: How did the summary attribute become part of HTML 4.0?
- Re: How did the summary attribute become part of HTML 4.0?
- Re: How did the summary attribute become part of HTML 4.0?
- Re: How did the summary attribute become part of HTML 4.0?
- Re: How did the summary attribute become part of HTML 4.0?
- Re: How did the summary attribute become part of HTML 4.0?
Friday, 7 August 2009
- RE: Google to pay for HTMLWG invited experts at TPAC 2009
- Re: Feedback on the current editor's draft
- Re: Google to pay for HTMLWG invited experts at TPAC 2009
- Feedback on the current editor's draft
- RE: Google to pay for HTMLWG invited experts at TPAC 2009
- RE: Google to pay for HTMLWG invited experts at TPAC 2009
- Re: Google to pay for HTMLWG invited experts at TPAC 2009
- RE: Google to pay for HTMLWG invited experts at TPAC 2009
- RE: Scope of HTML5...
- Re: 'loadend' event on media elements
- 'progress' events for media elements
- Scope of HTML5...
- Re: How did the summary attribute become part of HTML 4.0?
- Re: How did the summary attribute become part of HTML 4.0?
- Re: MIME type for WAVE with PCM?
- Re: How did the summary attribute become part of HTML 4.0?
- Re: How did the summary attribute become part of HTML 4.0?
- Re: How did the summary attribute become part of HTML 4.0?
- Re: How did the summary attribute become part of HTML 4.0?
- How did the summary attribute become part of HTML 4.0?
- RE: Moving Forward with @summary
- Re: Movement on @summary
- File API features in HTML5
- Re: Google to pay for HTMLWG invited experts at TPAC 2009
Thursday, 6 August 2009
Friday, 7 August 2009
Thursday, 6 August 2009
- Re: Google to pay for HTMLWG invited experts at TPAC 2009
- Re: summary attribute compromise proposal
- Re: Google to pay for HTMLWG invited experts at TPAC 2009
- RE: summary attribute compromise proposal
- Re: Google to pay for HTMLWG invited experts at TPAC 2009
- Re: Test results for xmlns:foo attribute preservation across all browsers
- Re: Test results for xmlns:foo attribute preservation across all browsers
- Re: [whatwg] Test results for xmlns:foo attribute preservation across all browsers
- Re: WG comments, Working Drafts, and Last Call -- clarification please?
- Re: WG comments, Working Drafts, and Last Call -- clarification please?
- Re: WG comments, Working Drafts, and Last Call -- clarification please?
- Re: WG comments, Working Drafts, and Last Call -- clarification please?
- Re: WG comments, Working Drafts, and Last Call -- clarification please?
- Re: WG comments, Working Drafts, and Last Call -- clarification please?
- Re: WG comments, Working Drafts, and Last Call -- clarification please?
- Re: Test results for xmlns:foo attribute preservation across all browsers
- Re: WG comments, Working Drafts, and Last Call -- clarification please?
- Re: WG comments, Working Drafts, and Last Call -- clarification please?
- Re: WG comments, Working Drafts, and Last Call -- clarification please?
- Re: WG comments, Working Drafts, and Last Call -- clarification please?
- Test results for xmlns:foo attribute preservation across all browsers
- Re: WG comments, Working Drafts, and Last Call -- clarification please?
- Re: WG comments, Working Drafts, and Last Call -- clarification please?
- Re: WG comments, Working Drafts, and Last Call -- clarification please?
- Re: Movement on @summary
- Re: WG comments, Working Drafts, and Last Call -- clarification please?
- Re: WG comments, Working Drafts, and Last Call -- clarification please?
- Re: WG comments, Working Drafts, and Last Call -- clarification please?
- Re: WG comments, Working Drafts, and Last Call -- clarification please?
- Re: Movement on @summary
- Re: WG comments, Working Drafts, and Last Call -- clarification please?
- Re: WG comments, Working Drafts, and Last Call -- clarification please?
- Re: WG comments, Working Drafts, and Last Call -- clarification please?
- Re: [DRAFT] Heartbeat poll - update 4
- Re: WG comments, Working Drafts, and Last Call -- clarification please?
- Re: [DRAFT] Heartbeat poll - update 4
- Re: WG comments, Working Drafts, and Last Call -- clarification please?
- WG comments, Working Drafts, and Last Call -- clarification please?
- Re: Movement on @summary
- minutes: HTML WG telecon 2009-08-06 [draft]
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: Movement on @summary
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- 'loadend' event on media elements
- Re: summary attribute compromise proposal
- Re: Canvas at the HTML Caucus -first meeting 7 August 2009
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Canvas at the HTML Caucus -first meeting 7 August 2009
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: Helping Canvas Tag Be Accessible
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: [whatwg] Stripping newlines from URI attributes (fwd)
- Re: [whatwg] Stripping newlines from URI attributes (fwd)
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- [Bug 7232] add <iframe> to list of CDATA elements in the "Writing HTML documents" section
- drawImage() shouldn't throw INVALID_STATE_ERR
- loadedmetadata and layout
- [Bug 7229] input.files should return the same object
- Re: Helping Canvas Tag Be Accessible
- Re: Helping Canvas Tag Be Accessible
- Re: [whatwg] Stripping newlines from URI attributes (fwd)
- Re: summary attribute compromise proposal
- Re: Helping Canvas Tag Be Accessible
- Re: Intranet pages
- Re: Helping Canvas Tag Be Accessible
- Re: Helping Canvas Tag Be Accessible
- Re: Helping Canvas Tag Be Accessible
- Re: summary attribute compromise proposal
- Movement on @summary
- Re: summary attribute compromise proposal
Wednesday, 5 August 2009
- Re: Helping Canvas Tag Be Accessible
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: Helping Canvas Tag Be Accessible
- Re: [whatwg] Stripping newlines from URI attributes (fwd)
- Re: {agenda} HTML WG telcon 2009-08-05
- Re: summary attribute compromise proposal
- Re: [whatwg] Stripping newlines from URI attributes (fwd)
- Re: summary attribute compromise proposal
- XHTML namespace
- FW: versioning, robustness principle, doctypes etc
- Re: [DRAFT] Heartbeat poll - update 4
- [DRAFT] Heartbeat poll - update 4
- Re: Publishing a new draft (HTML5+RDFa)
- Re: Helping Canvas Tag Be Accessible
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- update on ACTION-13 (Register about: URI scheme)
- update on ACTION-125 (Coordinate with LMM and DanC to get an Internet Draft that addresses some HTML 5 href issues)
- Re: Thoughts regarding Maciej's compromise and the heartbeat publication
- Re: Helping Canvas Tag Be Accessible
- Re: Intranet pages
- Re: Helping Canvas Tag Be Accessible
- Re: Intranet pages
- [Bug 7215] character encodings and XML
- Re: Intranet pages
- Re: summary attribute compromise proposal
- Re: Intranet pages
- Re: Intranet pages
- pause when media playback has ended
- Re: Intranet pages
- Re: Intranet pages
- Re: Intranet pages
- Re: Intranet pages
- Re: Infinite loop in fragment case
- Re: Intranet pages
- Re: Intranet pages
- Re: summary attribute compromise proposal
- Re: postMessage: origin serialized too early
- Re: Intranet pages
- Re: summary attribute compromise proposal
- Re: Intranet pages
- Intranet pages
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: Breaking Dependencies - @summary (FW: Call for Review: German WCAG 2.0 Candidate Authorized Translation)
- Thoughts regarding Maciej's compromise and the heartbeat publication
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: canvas text: ctx.font='inherit'
- Re: [whatwg] Stripping newlines from URI attributes (fwd)
- Re: summary attribute compromise proposal
- Re: canvas text: ctx.font='inherit'
Tuesday, 4 August 2009
- Re: Infinite loop in fragment case
- Re: canvas text: ctx.font='inherit'
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: Breaking Dependencies - @summary (FW: Call for Review: German WCAG 2.0 Candidate Authorized Translation)
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: Breaking Dependencies - @summary (FW: Call for Review: German WCAG 2.0 Candidate Authorized Translation)
- Re: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: Breaking Dependencies - @summary (FW: Call for Review: German WCAG 2.0 Candidate Authorized Translation)
- RE: summary attribute compromise proposal
- Re: summary attribute compromise proposal
- Re: Breaking Dependencies - @summary (FW: Call for Review: German WCAG 2.0 Candidate Authorized Translation)
- Re: Breaking Dependencies - @summary (FW: Call for Review: German WCAG 2.0 Candidate Authorized Translation)
- summary attribute compromise proposal
- Re: Breaking Dependencies - @summary (FW: Call for Review: German WCAG 2.0 Candidate Authorized Translation)
- Re: Breaking Dependencies - @summary (FW: Call for Review: German WCAG 2.0 Candidate Authorized Translation)
- RE: Breaking Dependencies - @summary (FW: Call for Review: German WCAG 2.0 Candidate Authorized Translation)
- Re: Breaking Dependencies - @summary (FW: Call for Review: German WCAG 2.0 Candidate Authorized Translation)
- Re: My final attempt on explanation (was RE: [DRAFT] Heartbeat poll - update 2)
- Re: My final attempt on explanation (was RE: [DRAFT] Heartbeat poll - update 2)
- Re: Breaking Dependencies - @summary (FW: Call for Review: German WCAG 2.0 Candidate Authorized Translation)
- Re: Breaking Dependencies - @summary (FW: Call for Review: German WCAG 2.0 Candidate Authorized Translation)
- RE: Breaking Dependencies - @summary (FW: Call for Review: German WCAG 2.0 Candidate Authorized Translation)
- Re: Breaking Dependencies - @summary (FW: Call for Review: German WCAG 2.0 Candidate Authorized Translation)
- Breaking Dependencies - @summary (FW: Call for Review: German WCAG 2.0 Candidate Authorized Translation)
- RE: My final attempt on explanation (was RE: [DRAFT] Heartbeat poll - update 2)
- Re: New HTML5 spec-editing tools released
- RE: [DRAFT] Heartbeat poll - update 2
- Re: My final attempt on explanation (was RE: [DRAFT] Heartbeat poll - update 2)
- Re: heartbeat poll and an abstain option
- Re: heartbeat poll and an abstain option
- Re: heartbeat poll and an abstain option
- Re: heartbeat poll and an abstain option
- heartbeat poll and an abstain option
- Re: [DRAFT] Heartbeat poll - update 2
- Re: My final attempt on explanation (was RE: [DRAFT] Heartbeat poll - update 2)
- Re: My final attempt on explanation (was RE: [DRAFT] Heartbeat poll - update 2)
- Re: My final attempt on explanation (was RE: [DRAFT] Heartbeat poll - update 2)
- [Bug 7211] define "positive integer" and use it consistently, instead of "non-negative integer greater than zero"
- Re: [DRAFT] Heartbeat poll - update 2
- Re: Normative warnings (was: Re: ACTION-128: Draft @summary voting text in conjunction with PF)
- RE: [DRAFT] Heartbeat poll - update 2
- RE: [DRAFT] Heartbeat poll - update 2
- RE: [DRAFT] Heartbeat poll - update 2
- RE: [DRAFT] Heartbeat poll - update 2
- RE: [DRAFT] Heartbeat poll - update 2
- Re: Selecting multiple options in a select element without multiple
- Re: My final attempt on explanation (was RE: [DRAFT] Heartbeat poll - update 2)
- Invitation to connect on LinkedIn
- Re: My final attempt on explanation (was RE: [DRAFT] Heartbeat poll - update 2)
- Re: My final attempt on explanation (was RE: [DRAFT] Heartbeat poll - update 2)
- Re: [DRAFT] Heartbeat poll - update 2
- Re: My final attempt on explanation (was RE: [DRAFT] Heartbeat poll - update 2)
- Re: My final attempt on explanation (was RE: [DRAFT] Heartbeat poll - update 2)
- Re: My final attempt on explanation (was RE: [DRAFT] Heartbeat poll - update 2)
- Re: My final attempt on explanation (was RE: [DRAFT] Heartbeat poll - update 2)
- Re: My final attempt on explanation (was RE: [DRAFT] Heartbeat poll - update 2)
- Re: My final attempt on explanation (was RE: [DRAFT] Heartbeat poll - update 2)
- Re: My final attempt on explanation (was RE: [DRAFT] Heartbeat poll - update 2)
- Re: My final attempt on explanation (was RE: [DRAFT] Heartbeat poll - update 2)
- Re: My final attempt on explanation (was RE: [DRAFT] Heartbeat poll - update 2)
- Re: My final attempt on explanation (was RE: [DRAFT] Heartbeat poll - update 2)
- Re: My final attempt on explanation (was RE: [DRAFT] Heartbeat poll - update 2)
- Re: [DRAFT] Heartbeat poll - update 3
- RE: My final attempt on explanation (was RE: [DRAFT] Heartbeat poll - update 2)
- Re: [DRAFT] Heartbeat poll - update 2
Monday, 3 August 2009
- Re: [DRAFT] Heartbeat poll - update 2
- Re: My final attempt on explanation (was RE: [DRAFT] Heartbeat poll - update 2)
- Re: New HTML5 spec-editing tools released
- Re: Obsolete, deprecated, et al
- Re: Obsolete, deprecated, et al
- Re: Publishing a new draft (HTML5+RDFa)
- Re: Publishing a new draft (HTML5+RDFa)
- My final attempt on explanation (was RE: [DRAFT] Heartbeat poll - update 2)
- prior surveys
- New HTML5 spec-editing tools released
- Re: [DRAFT] Heartbeat poll - update 2
- Re: The script element
- Re: [HTML5] DOMContentLoaded fires before CSS resources loaded?
- Re: [DRAFT] Heartbeat poll - update 2
- Re: [DRAFT] Heartbeat poll - update 2
- Re: Spam:*****, Re: [DRAFT] Heartbeat poll
- Re: [DRAFT] Heartbeat poll
- The script element
- Re: [DRAFT] Heartbeat poll
- Re: [DRAFT] Heartbeat poll - update 2
- Re: Media elements may never load, may load the wrong source, etc
- Re: My position (was RE: [DRAFT] Heartbeat poll - update 2)
- Re: [DRAFT] Heartbeat poll
- Re: My position (was RE: [DRAFT] Heartbeat poll - update 2)
- Re: My position (was RE: [DRAFT] Heartbeat poll - update 2)
- Re: My position (was RE: [DRAFT] Heartbeat poll - update 2)
- RE: My position (was RE: [DRAFT] Heartbeat poll - update 2)
- Re: My position (was RE: [DRAFT] Heartbeat poll - update 2)
- Re: My position (was RE: [DRAFT] Heartbeat poll - update 2)
- Re: [DRAFT] Heartbeat poll - update 2
- RE: My position (was RE: [DRAFT] Heartbeat poll - update 2)
- Re: [DRAFT] Heartbeat poll - update 2
- Re: [DRAFT] Heartbeat poll - update 2
- Re: My position (was RE: [DRAFT] Heartbeat poll - update 2)
- Re: My position (was RE: [DRAFT] Heartbeat poll - update 2)
Sunday, 2 August 2009
- RE: [DRAFT] Heartbeat poll - update 2
- Re: [DRAFT] Heartbeat poll - update 2
- Re: [DRAFT] Heartbeat poll - update 2
- Re: My position (was RE: [DRAFT] Heartbeat poll - update 2)
- Re: My position (was RE: [DRAFT] Heartbeat poll - update 2)
- Re: My position (was RE: [DRAFT] Heartbeat poll - update 2)
- Re: My position (was RE: [DRAFT] Heartbeat poll - update 2)
- Re: My position (was RE: [DRAFT] Heartbeat poll - update 2)
- Re: My position (was RE: [DRAFT] Heartbeat poll - update 2)
- Re: My position (was RE: [DRAFT] Heartbeat poll - update 2)
- My position (was RE: [DRAFT] Heartbeat poll - update 2)
- Re: [DRAFT] Heartbeat poll - update 2
- Re: Publishing Design Principles in Addition to Publishing the HTML5 Spec or Specs
- Re: [DRAFT] Heartbeat poll - update 2
- Re: Obsolete, deprecated, et al
- Re: [DRAFT] Heartbeat poll
- Re: Obsolete, deprecated, et al
- Re: [DRAFT] Heartbeat poll
- Re: Publishing Design Principles in Addition to Publishing the HTML5 Spec or Specs
- Re: [DRAFT] Heartbeat poll - update 2
- Re: [DRAFT] Heartbeat poll - update 2
- Re: [DRAFT] Heartbeat poll - update 2
- [Bug 7190] Since all "specially focusable" elements have an activation behaviour, the Action of accesskey-laden commands is to _not_ focus them if they are focusable. Instead, such elements should probably always be focused if focusable, then be activated.
- Re: Activation Behavior of video and audio
- Publishing Design Principles in Addition to Publishing the HTML5 Spec or Specs
- Re: Activation Behavior of video and audio
- Re: [HTML5] DOMContentLoaded fires before CSS resources loaded?
- Re: [DRAFT] Heartbeat poll
- Re: [DRAFT] Heartbeat poll
- RE: [DRAFT] Heartbeat poll
- Re: [DRAFT] Heartbeat poll
- Re: [DRAFT] Heartbeat poll
- Re: Obsolete, deprecated, et al
- Re: The meaning of "obsolete" in HTML5 (was Re: [DRAFT] Heartbeat poll)
- Re: [DRAFT] Heartbeat poll
- @summary yet again :( Re: [DRAFT] Heartbeat poll
- RE: The meaning of "obsolete" in HTML5 (was Re: [DRAFT] Heartbeat poll)
- Re: The meaning of "obsolete" in HTML5 (was Re: [DRAFT] Heartbeat poll)
- Obsolete, deprecated, et al
- Re: The meaning of "obsolete" in HTML5 (was Re: [DRAFT] Heartbeat poll)
- The meaning of "obsolete" in HTML5 (was Re: [DRAFT] Heartbeat poll)
- Re: [DRAFT] Heartbeat poll
- Re: [DRAFT] Heartbeat poll
- RE: [DRAFT] Heartbeat poll
- Re: [DRAFT] Heartbeat poll
- Re: [DRAFT] Heartbeat poll
- Re: [DRAFT] Heartbeat poll
Saturday, 1 August 2009
- Re: Poll on technical substance rather than procedural mechanism
- Re: canvas text: ctx.font='inherit'
- Re: [DRAFT] Heartbeat poll
- Re: [DRAFT] Heartbeat poll
- RE: [DRAFT] Heartbeat poll - update
- RE: [DRAFT] Heartbeat poll
- RE: [DRAFT] Heartbeat poll
- RE: [DRAFT] Heartbeat poll
- Poll on technical substance rather than procedural mechanism
- Re: canvas text: ctx.font='inherit'
- Re: canvas text: ctx.font='inherit'
- Re: [DRAFT] Heartbeat poll
- Re: [DRAFT] Heartbeat poll
- Re: Publishing a new draft (HTML5+RDFa)
- Re: Fwd: Progress on video accessibility
- Re: [DRAFT] Heartbeat poll
- Re: ARIA integration in HTML 5
- Re: ARIA integration in HTML 5
- Re: ARIA integration in HTML 5
- Re: linking other elements to a "command"
- Re: @accesskey and multiple characters
- Re: canvas text: ctx.font='inherit'
- Re: Publishing a new draft (HTML5+RDFa)
- Re: Publishing a new draft (HTML5+RDFa)
- Re: canvas text: ctx.font='inherit'
- Re: canvas text: ctx.font='inherit'
- RE: [DRAFT] Heartbeat poll
- Re: canvas text: ctx.font='inherit'
- Re: Publishing a new draft (HTML5+RDFa)
- Re: [DRAFT] Heartbeat poll
- RE: [DRAFT] Heartbeat poll
- Re: [DRAFT] Heartbeat poll
- Re: [DRAFT] Heartbeat poll
- Re: [DRAFT] Heartbeat poll
- RE: [DRAFT] Heartbeat poll
- Re: [DRAFT] Heartbeat poll
- Re: canvas text: ctx.font='inherit'
- Re: [DRAFT] Heartbeat poll
- Re: [DRAFT] Heartbeat poll
- Re: [DRAFT] Heartbeat poll
- Re: [DRAFT] Heartbeat poll
- Re: canvas text: ctx.font='inherit'
- RE: [DRAFT] Heartbeat poll
- Re: Publishing a new draft (HTML5+RDFa)