Tuesday, 30 June 2009
- Re: comments on draft-barth-mime-sniffing
- Re: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- Re: Scientific Studies of the Summary Attribute (was: Why I don't attend the weekly teleconference)
- Re: Does anyone like microdata?
- Re: Things in HTML that I disagree with (Was: evidence of harm)
- Re: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- Re: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- Re: comments on draft-barth-mime-sniffing
- Re: Codecs for <video> and <audio>
- Re: Does anyone like microdata?
- Re: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- Re: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- Re: comments on draft-barth-mime-sniffing
- Re: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- Re: Codecs for <video> and <audio>
- Re: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- Why I don't attend the weekly teleconference (Was: Input on the agenda)
- Re: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- Re: Codecs for <video> and <audio>
- Re: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- Re: Codecs for <video> and <audio>
- [Bug 6746] case-insensitivity of other than a-z and A-Z, e.g., diacritics
- [Bug 6774] <mark> element: restrict insertion by other servers
- Re: Codecs for <video> and <audio>
- Re: Codecs for <video> and <audio>
- Codecs for <video> and <audio>
Monday, 29 June 2009
- Re: Does anyone like microdata?
- [Bug 6858] More details needed for "ASCII-compatible encoding"
- RE: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- Re: Does anyone like microdata?
- Re: Does anyone like microdata?
- Re: Does anyone like microdata?
- Re: Does anyone like microdata?
- Re: Does anyone like microdata?
- Re: Does anyone like microdata?
- Re: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- Re: Does anyone like microdata?
- Re: Does anyone like microdata?
- RE: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- Re: Does anyone like microdata?
- Re: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- Re: List tone
- Re: List tone
- Re: List tone
- Re: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- List tone
- Re: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- Re: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- Re: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- Fwd: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- Re: Canvas - SVG Bridge
- Re: Canvas - SVG Bridge
- Re: Canvas - SVG Bridge
- [Bug 6858] More details needed for "ASCII-compatible encoding"
- Re: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- [Bug 6774] <mark> element: restrict insertion by other servers
- [Bug 7062] New: replace terms "CDATA element" and "RCDATA element" with... something better
- Re: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- Re: Why I don't attend the weekly teleconference (Was: Input on the agenda)
Sunday, 28 June 2009
- Re: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- Re: Content sniffing, feed readers, etc. (was HTML interpreter vs. HTML user agent)
- Re: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- RE: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- Re: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- RE: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- [Bug 7061] clarify definition of "sectioning content"
- [Bug 6999] Adding tag <NSFW>
- [Bug 6854] if attribute values enumerated, allow case-sensitivity for meta content values
- [Bug 6853] restore meta keywords, search engines use them
- [Bug 6834] add more number bases to form inputs?
- [Bug 6774] <mark> element: restrict insertion by other servers
- [Bug 6746] case-insensitivity of other than a-z and A-Z, e.g., diacritics
- [Bug 6609] negative keywords-not meta tags
- [Bug 6608] please undeprecate <center> for older browsers
- [Bug 6606] generic 3rd-party <mark>, Smart Tags, and Activities prevention
- [Bug 6976] Image Map Example fails Validation
- [Bug 6858] More details needed for "ASCII-compatible encoding"
- [Bug 7061] New: clarify definition of "sectioning content"
- [Bug 6742] pre-encoded form values should be restorable as submitted
- [Bug 6771] Sectioning Content Use versus DIV
- [Bug 6742] pre-encoded form values should be restorable as submitted
- [Bug 6742] pre-encoded form values should be restorable as submitted
- RE: Why I don't attend the weekly teleconference (Was: Input on the agenda)
Saturday, 27 June 2009
- RE: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- Re: Request for advice on <canvas> accessibility
- [Bug 5833] Work on standalone apps ideas
- [Bug 5866] SVG in HTML
- [Bug 6099] Process notification feedback
- Re: Request for advice on <canvas> accessibility
- Re: Request for advice on <canvas> accessibility
Friday, 26 June 2009
- Re: Example of Good Summary (Was: Issues of @summary and use of data for "decisions")
- Canvas - SVG Bridge
- [Bug 7059] New: Forking XPath
- Re: ARIA integration in HTML 5
- Re: ARIA integration in HTML 5
- Re: ARIA integration in HTML 5
- Re: Issues of @summary and use of data for "decisions"
- Re: [Bug 7056] <caption> and <figure><legend> elements should allow flow content children
- [Bug 7011] canvas accessible fallback provison is under specified
- Re: ARIA integration in HTML 5
- [Bug 6978] Mark eof-terminated script elements as malformed
- [Bug 7011] canvas accessible fallback provison is under specified
- [Bug 7056] <caption> and <figure><legend> elements should allow flow content children
- [Bug 7051] add new extended attribute to IDLs with DOM attributes that reflect content attributes
- [Bug 7030] Define "Text" content model
- [Bug 7051] add new extended attribute to IDLs with DOM attributes that reflect content attributes
- [Bug 7035] clarify what the use case is for first illustration under "3.4 Content models"
- [Bug 7034] authoring conformance requirements in the spec should either be removed or replaced
- [Bug 7032] Sandboxing and Referer
- Re: Does anyone like microdata?
- Re: ARIA integration in HTML 5
- ARIA integration in HTML 5
- [Bug 6784] WebStorage should include Window IDL for Storage APIs
- [Bug 6778] Note the XPath implications of assigning HTML elements into the http://www.w3.org/1999/xhtml namespace
- Re: Does anyone like microdata?
- Re: Does anyone like microdata?
- Re: Summary of Thursday's IRC conversation about @summary
- [Bug 6776] Note the XSLT implications of assigning HTML elements into the http://www.w3.org/1999/xhtml namespace
- Does anyone like microdata?
- Re: Example of Good Summary (Was: Issues of @summary and use of data for "decisions")
- Re: Authoring Guide
Thursday, 25 June 2009
- Re: Things in HTML that I disagree with (Was: evidence of harm)
- Re: Summary of Thursday's IRC conversation about @summary
- Re: Things in HTML that I disagree with (Was: evidence of harm)
- Re: Things in HTML that I disagree with (Was: evidence of harm)
- Re: Things in HTML that I disagree with (Was: evidence of harm)
- Re: Things in HTML that I disagree with (Was: evidence of harm)
- Re: Things in HTML that I disagree with (Was: evidence of harm)
- Re: Things in HTML that I disagree with (Was: evidence of harm)
- Re: Things in HTML that I disagree with (Was: evidence of harm)
- Re: Things in HTML that I disagree with (Was: evidence of harm)
- Re: Things in HTML that I disagree with (Was: evidence of harm)
- Re: Accessibility, disability, all and some Re: Request to Strengthen the HTML5 Accessibility Design Principle
- Re: Things in HTML that I disagree with (Was: evidence of harm)
- Re: Things in HTML that I disagree with (Was: evidence of harm)
- Re: Things in HTML that I disagree with (Was: evidence of harm)
- Things in HTML that I disagree with (Was: evidence of harm)
- Editorial: maybe redundant definition on sectioning content
- document.bgColor and frameset
- Minutes HTML WG telcon 2009-06-24
- canvas and accessibility Re: consensus and last call
- Re: consensus and last call
- Re: consensus and last call
- AppCache to Widget Converter
- Re: Advice about framesets
- Re: Advice about framesets
- [Bug 7056] New: <caption> and <figure><legend> elements should allow flow content children
- Re: Data and Expertise (Was: Issues of @summary and use of data for "decisions")
- Accessibility, disability, all and some Re: Request to Strengthen the HTML5 Accessibility Design Principle
- Re: Case-sensitivity of attribute values wrt Selectors
- Re: Advice about framesets
- Re: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- Re: Summary of Thursday's IRC conversation about @summary
Wednesday, 24 June 2009
- Re: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- Re: Request to Strengthen the HTML5 Accessibility Design Principle
- Rendering: border on table
- ch/chOff should be char/charoff
- Re: Request to Strengthen the HTML5 Accessibility Design Principle
- Re: Request to Strengthen the HTML5 Accessibility Design Principle
- Advice about framesets
- "HTML: The Markup Language" draft [was: Why I don't attend the weekly teleconference]
- Re: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- Re: command Label and <img alt>
- Re: Issues of @summary and use of data for "decisions"
- Re: Issues of @summary and use of data for "decisions"
- Re: Data and Expertise (Was: Issues of @summary and use of data for "decisions")
- Example of Good Summary (Was: Issues of @summary and use of data for "decisions")
- Re: use of data for "decisions" (Was: Issues of @summary and use of data for "decisions")
- command Label and <img alt>
- Re: Request to Strengthen the HTML5 Accessibility Design Principle
- Re: Request to Strengthen the HTML5 Accessibility Design Principle
- Re: Request to Strengthen the HTML5 Accessibility Design Principle
- Re: consensus and last call
- Re: use of data for "decisions" (Was: Issues of @summary and use of data for "decisions")
- Re: Request to Strengthen the HTML5 Accessibility Design Principle
- Re: Good Summary Values and Layout Table Detection (Was: Issues of @summary and use of data for "decisions")
- Re: consensus and last call
- Re: Request to Strengthen the HTML5 Accessibility Design Principle
- Re: Request to Strengthen the HTML5 Accessibility Design Principle
- Re: Request to Strengthen the HTML5 Accessibility Design Principle
- consensus and last call
- Re: Request to Strengthen the HTML5 Accessibility Design Principle
- Re: Request to Strengthen the HTML5 Accessibility Design Principle
- Re: Request to Strengthen the HTML5 Accessibility Design Principle
- Re: Request to Strengthen the HTML5 Accessibility Design Principle
- Re: Request to Strengthen the HTML5 Accessibility Design Principle
- Re: Request to Strengthen the HTML5 Accessibility Design Principle
- Re: Request to Strengthen the HTML5 Accessibility Design Principle
- Re: Request to Strengthen the HTML5 Accessibility Design Principle
- Request to Strengthen the HTML5 Accessibility Design Principle
- Re: MIME type for WAVE with PCM?
- RE: (HTML5 Parsing) Yet another corner-case: parsing into other contexts...
- Re: Editing specs (was: Re: Why I don't attend the weekly teleconference)
- Re: Ultimate gatekeeper for document-conformance decisions [was: Why I don't attend the weekly teleconference]
- Re: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- Editing specs (was: Re: Why I don't attend the weekly teleconference)
- Re: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- Re: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- Ultimate gatekeeper for document-conformance decisions [was: Why I don't attend the weekly teleconference]
- RE: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- Re: Issues of @summary and use of data for "decisions"
- Re: Issues of @summary and use of data for "decisions"
- RE: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- Re: (HTML5 Parsing) Yet another corner-case: parsing into other contexts...
- Re: Issues of @summary and use of data for "decisions"
- Re: (HTML5 Parsing) Yet another corner-case: parsing into other contexts...
- Re: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- Re: (HTML5 Parsing) Yet another corner-case: parsing into other contexts...
- Re: Issues of @summary and use of data for "decisions"
- Re: Issues of @summary and use of data for "decisions"
- Re: Issues of @summary and use of data for "decisions"
- Re: Issues of @summary and use of data for "decisions"
- Re: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- (HTML5 Parsing) Yet another corner-case: parsing into other contexts...
Tuesday, 23 June 2009
- Re: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- Re: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- Re: Issues of @summary and use of data for "decisions"
- RE: Issues of @summary and use of data for "decisions"
- Re: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- Re: Issues of @summary and use of data for "decisions"
- Re: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- Re: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- Re: Issues of @summary and use of data for "decisions"
- Re: Issues of @summary and use of data for "decisions"
- Re: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- Re: Issues of @summary and use of data for "decisions"
- Re: Issues of @summary and use of data for "decisions"
- Re: Issues of @summary and use of data for "decisions"
- Re: Should <video hidden> be muted?
- Re: Issues of @summary and use of data for "decisions"
- Re: Issues of @summary and use of data for "decisions"
- Re: Should <video hidden> be muted?
- Re: Issues of @summary and use of data for "decisions"
- Re: Issues of @summary and use of data for "decisions"
- Why I don't attend the weekly teleconference (Was: Input on the agenda)
- Re: Issues of @summary and use of data for "decisions"
- Re: Issues of @summary and use of data for "decisions"
- Re: Input on the agenda
- Re: Issues of @summary and use of data for "decisions"
- Should <video hidden> be muted?
- Re: Input on the agenda
- Re: Issues of @summary and use of data for "decisions"
- Re: Input on the agenda
- Re: Issues of @summary and use of data for "decisions"
- Re: Issues of @summary and use of data for "decisions"
- Re: Issues of @summary and use of data for "decisions"
- Re: Issues of @summary and use of data for "decisions"
- Re: Issues of @summary and use of data for "decisions"
- Re: Issues of @summary and use of data for "decisions"
- Re: Issues of @summary and use of data for "decisions"
- Re: Issues of @summary and use of data for "decisions"
- Re: Issues of @summary and use of data for "decisions"
- Re: Issues of @summary and use of data for "decisions"
- Re: Issues of @summary and use of data for "decisions"
- Re: Issues of @summary and use of data for "decisions"
- Re: Issues of @summary and use of data for "decisions"
- Re: Issues of @summary and use of data for "decisions"
- Re: Issues of @summary and use of data for "decisions"
- Re: Issues of @summary and use of data for "decisions"
- Issues of @summary and use of data for "decisions"
- Re: Input on the agenda
- Re: <video> toggling video rendering
- Re: <video> toggling video rendering
- Re: <video> toggling video rendering
- Re: <video> toggling video rendering
- [Bug 7051] New: add new extended attribute to IDLs with DOM attributes that reflect content attributes
- Re: <video> toggling video rendering
- Re: <video> toggling video rendering
- <video> toggling video rendering
Monday, 22 June 2009
- Input on the agenda
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: What makes a failure? (@summary, et al)
- Re: accesskey should always define a command
- accesskey should always define a command
- accesskey Action
Saturday, 20 June 2009
Thursday, 18 June 2009
Monday, 22 June 2009
- Re: parsing floating point values - user input for <input type="number"> in different locales
- Re: parsing floating point values - user input for <input type="number"> in different locales
- Re: accesskey feedback
- Re: event.currentTarget and 'this' for listeners registered on the window object
Sunday, 21 June 2009
Saturday, 20 June 2009
- RE: "Outline" algorithm (document length and complexity)
- event.currentTarget and 'this' for listeners registered on the window object
Friday, 19 June 2009
- Re: comments on draft-barth-mime-sniffing
- Re: change "scientific documents" to "basic hypertext" (detailed review of section 1. Introduction)
- <input type="number"> restricting user input to only valid characters
- Re: parsing floating point values - user input for <input type="number"> in different locales
- Re: <font color="blue"> (was ISSUE-32)
- Re: comments on draft-barth-mime-sniffing
- Re: accesskey feedback
- Re: minutes of last meeting?
- Re: WG review of HTML5
- Re: comments on draft-barth-mime-sniffing
- Re: minutes of last meeting?
- Re: minutes of last meeting?
- Re: minutes of last meeting?
- Re: accesskey feedback
- minutes of last meeting?
- Re: comments on draft-barth-mime-sniffing
- Re: typeof document.all
- Re: typeof document.all
- Re: typeof document.all
- typeof document.all
- equals sign in unquoted attribute
- Re: comments on draft-barth-mime-sniffing
- Re: Spec contains "content model" serving no purpose
- [Bug 7035] New: clarify what the use case is for first illustration under "3.4 Content models"
- Re: comments on draft-barth-mime-sniffing
- [Bug 7034] change "conformance checker" to "ideology checker" or "loyalty checker"
- Spec contains "content model" serving no purpose
- Re: parsing floating point values - user input for <input type="number"> in different locales
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
Thursday, 18 June 2009
- [Bug 7034] change "conformance checker" to "ideology checker" or "loyalty checker"
- parsing floating point values - user input for <input type="number"> in different locales
- Re: comments on draft-barth-mime-sniffing
- TAG work on versioning
- [Bug 7034] New: change "conformance checker" to "ideology checker" or "loyalty checker"
- Re: comments on draft-barth-mime-sniffing
Wednesday, 17 June 2009
- [Bug 7032] New: Sandboxing and Referer
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: question about XML and HTML5
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: &foo= in attribute values (and why defining conformance matters)
- Re: comments on draft-barth-mime-sniffing
- Re: &foo= in attribute values (and why defining conformance matters)
- Re: comments on draft-barth-mime-sniffing
- Re: On telling end users "the input is broken" [was: comments on draft-barth-mime-sniffing]
- Re: comments on draft-barth-mime-sniffing
- On telling end users "the input is broken" [was: comments on draft-barth-mime-sniffing]
- accesskey feedback
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: MIME type for WAVE with PCM?
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: MIME type for WAVE with PCM?
- Re: MIME type for WAVE with PCM?
- Re: MIME type for WAVE with PCM?
- Re: comments on draft-barth-mime-sniffing
Tuesday, 16 June 2009
- {agenda} HTML WG telcon 2009-06-18
- Re: comments on draft-barth-mime-sniffing
- Re: MIME type for WAVE with PCM?
- [Bug 7030] New: Define "Text" content model
- Re: MIME type for WAVE with PCM?
- [Bug 7003] Typos
- [Bug 6993] Tell authoring tools to use UTF-8
- [Bug 6992] Title of Web IDL misspelled as WebIDL
- Re: MIME type for WAVE with PCM?
- Re: comments on draft-barth-mime-sniffing
- Re: DOM tree accessors
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: MIME type for WAVE with PCM?
- Re: DOM tree accessors
- MIME type for WAVE with PCM?
- DOM tree accessors
Monday, 15 June 2009
- Input on the agenda
- Re: &foo= in attribute values (and why defining conformance matters)
- RE: On validation
- Re: On validation
- Re: &foo= in attribute values (and why defining conformance matters)
- Re: <font color="blue"> (was ISSUE-32)
- Editorial: issues with the PDF version
- Re: On validation
- Re: On validation
- Re: <font color="blue"> (was ISSUE-32)
- On validation
- Re: &foo= in attribute values (and why defining conformance matters)
- Re: Auto-detect and encodings in HTML5
- Re: <font color="blue"> (was ISSUE-32)
- Re: <font color="blue"> (was ISSUE-32)
- Re: <font color="blue"> (was ISSUE-32)
- Re: comments on draft-barth-mime-sniffing
- Re: <font color="blue"> (was ISSUE-32)
Sunday, 14 June 2009
- Re: <font color="blue"> (was ISSUE-32)
- Re: <font color="blue"> (was ISSUE-32)
- Re: <font color="blue"> (was ISSUE-32)
- Re: <font color="blue"> (was ISSUE-32)
- Re: <font color="blue"> (was ISSUE-32)
- Re: &foo= in attribute values (and why defining conformance matters)
- Re: Disambiguating @summary from a long descriptor
- Re: Disambiguating @summary from a long descriptor
- Re: &foo= in attribute values (and why defining conformance matters)
- Re: Disambiguating @summary from a long descriptor
- Re: Disambiguating @summary from a long descriptor
- Re: <font color="blue"> (was ISSUE-32)
- Re: <font color="blue"> (was ISSUE-32)
- Re: postMessage: origin serialized too early
- Re: <font color="blue"> (was ISSUE-32)
- Re: <object> element - Global Attributes
- Re: <object> element - Global Attributes
Saturday, 13 June 2009
- Re: <object> element - Global Attributes
- Re: <object> element - Global Attributes
- Re: <object> element - Global Attributes
- Re: document[id] and document.id to <element id="id"> matching
- Re: [WF2] new attributes that often conflict with actual pages
- Re: document[id] and document.id to <element id="id"> matching
- Re: document[id] and document.id to <element id="id"> matching
- Re: <font color="blue"> (was ISSUE-32)
- Re: <font color="blue"> (was ISSUE-32)
- Re: Auto-detect and encodings in HTML5
Friday, 12 June 2009
- Re: What is the value of conformance? (was RE: <font color="blue"> (was ISSUE-32))
- Re: <font color="blue"> (was ISSUE-32)
- Re: <font color="blue"> (was ISSUE-32)
- Re: What is the value of conformance? (was RE: <font color="blue"> (was ISSUE-32))
- Re: Editorial: Usage of "HTML5" in the spec
- Re: <font color="blue"> (was ISSUE-32)
- Re: What is the value of conformance? (was RE: <font color="blue"> (was ISSUE-32))
- Re: &foo= in attribute values (and why defining conformance matters)
- RE: <font color="blue"> (was ISSUE-32)
- RE: <font color="blue"> (was ISSUE-32)
- Re: <font color="blue"> (was ISSUE-32)
- Re: &foo= in attribute values (and why defining conformance matters)
- [Bug 6670] Allow unescaped &s, at least in attributes that accept URLs
- Re: <isindex> parsing
- &foo= in attribute values (and why defining conformance matters)
- What is the value of conformance? (was RE: <font color="blue"> (was ISSUE-32))
- Re: <font color="blue"> (was ISSUE-32)
- Re: <font color="blue"> (was ISSUE-32)
- RE: Content sniffing, feed readers, etc. (was HTML interpreter vs. HTML user agent)
- Re: <font color="blue"> (was ISSUE-32)
- Re: <font color="blue"> (was ISSUE-32)
- Re: <font color="blue"> (was ISSUE-32)
- RE: <font color="blue"> (was ISSUE-32)
- Re: Auto-detect and encodings in HTML5
- Re: comments on draft-barth-mime-sniffing
- Re: <font color="blue"> (was ISSUE-32)
- Re: Auto-detect and encodings in HTML5
- Re: .spellcheck = 'inherit' should work
- RE: Section 1.6.1 relationship to HTML 4.01
Thursday, 11 June 2009
Friday, 12 June 2009
- Re: Canvas getImageData with negative size violates invariant
- Re: Auto-detect and encodings in HTML5
- Re: .spellcheck = 'inherit' should work
- Re: postMessage: origin serialized too early
- Re: Events and <video controls>
- Re: .spellcheck = 'inherit' should work
Thursday, 11 June 2009
- Re: Running "Zombie" Script Elements
- Re: Auto-detect and encodings in HTML5
- forwarding: WAI CG Consensus Resolutions on Text alternatives in HTML 5
- Re: Running "Zombie" Script Elements
- Re: [WF2] new attributes that often conflict with actual pages
- Re: Summary of Thursday's IRC conversation about @summary
- Re: HTML 5 suggestion for TABLE element
- RE: HTML 5 suggestion for TABLE element
- Re: Summary of Thursday's IRC conversation about @summary
- Re: Summary of Thursday's IRC conversation about @summary
- Re: <font color="blue"> (was ISSUE-32)
- Re: Foster-parenting and taint
- Re: <font color="blue"> (was ISSUE-32)
- Re: Disambiguating @summary from a long descriptor
- Re: Disambiguating @summary from a long descriptor
Wednesday, 10 June 2009
- RE: Disambiguating @summary from a long descriptor
- RE: Disambiguating @summary from a long descriptor
- Re: Disambiguating @summary from a long descriptor
- Re: canvas: globalAlpha should not throw
- RE: Disambiguating @summary from a long descriptor
- Re: Summary of Thursday's IRC conversation about @summary
- Re: Summary of Thursday's IRC conversation about @summary
- Re: Disambiguating @summary from a long descriptor
- Re: Summary of Thursday's IRC conversation about @summary
- Re: Origin header in loading external scripts (ISSUE-63)
- Re: getElementsByName should match any element
- Re: <frameset onload>
- Re: canvas: globalAlpha should not throw
- [Bug 7011] New: canvas accessible fallback provison is under specified
- Re: Rendering: contenteditable
- [Bug 7010] Making <applet> non-conforming may hinder royalty-free <video> adoption
- Disambiguating @summary from a long descriptor
- Re: Summary of Thursday's IRC conversation about @summary
- ISSUE-73 (Overlap of "predefined vocabularies" with other specifications), was: Concerns about new section "predefined vocabularies"
- Re: Media elements may never load, may load the wrong source, etc
- [Bug 7010] New: Making <applet> non-conforming may hinder royalty-free <video> adoption
- Re: <frameset onload>
- Re: Rendering: contenteditable
- Re: Non-character NCRs treated differently from literal non-characters
- Re: canvas: globalAlpha should not throw
- Re: <font color="blue"> (was ISSUE-32)
- Re: Rendering: contenteditable
- Re: Non-character NCRs treated differently from literal non-characters
- The a element (content and semantic model)
- Re: <font color="blue"> (was ISSUE-32)
- Re: <font color="blue"> (was ISSUE-32)
- Re: Rendering: contenteditable
- Re: getElementsByName should match any element
- Re: Outline algorithm and empty sections
- Re: getElementsByName should match any element
Tuesday, 9 June 2009
- Re: Editorial: event handler attributes
- Re: getElementsByName should match any element
- Re: Summary of Thursday's IRC conversation about @summary
- Re: Concerns about new section "predefined vocabularies"
- Re: <font color="blue"> (was ISSUE-32)
- Re: <font color="blue"> (was ISSUE-32)
- Re: Comments about microdata
- Re: <font color="blue"> (was ISSUE-32)
- Re: Summary of Thursday's IRC conversation about @summary
- Re: What makes a failure? (@summary, et al)
- Re: What makes a failure? (@summary, et al)
- Re: What makes a failure? (@summary, et al)
- Re: <font color="blue"> (was ISSUE-32)
- Re: <font color="blue"> (was ISSUE-32)
- Re: <font color="blue"> (was ISSUE-32)
- Media type for Atom feeds
- Re: <font color="blue"> (was ISSUE-32)
- Re: <font color="blue"> (was ISSUE-32)
- Re: <font color="blue"> (was ISSUE-32)
- Re: <font color="blue"> (was ISSUE-32)
- Re: <font color="blue"> (was ISSUE-32)
- Re: Summary of Thursday's IRC conversation about @summary
- Re: Summary of Thursday's IRC conversation about @summary
- <font color="blue"> (was ISSUE-32)
- Re: Summary of Thursday's IRC conversation about @summary
- Re: Summary of Thursday's IRC conversation about @summary
- Re: HTML 4.01 Strict table attributes and downplayed errors
- Re: HTML 4.01 Strict table attributes and downplayed errors
- Re: Summary of Thursday's IRC conversation about @summary
- The <summary> proposal
- Re: first couple of use cases
- Re: first couple of use cases
- Re: <font color="blue"> (was ISSUE-32)
- RE: <font color="blue"> (was ISSUE-32)
- Re: microdata use cases and Getting data out of poorly written Web pages
- Re: first couple of use cases
Monday, 8 June 2009
- Re: <font color="blue"> (was ISSUE-32)
- Re: <font color="blue"> (was ISSUE-32)
- RE: Firing media events early for throttled downloads
- RE: <font color="blue"> (was ISSUE-32)
- Re: Example canvas element use - accessibility concerns
- Re: Firing media events early for throttled downloads
- Re: Summary of Thursday's IRC conversation about @summary
- Safe ways of implementing limits on buffer sizes in the parser
- Re: Summary of Thursday's IRC conversation about @summary
- Re: Summary of Thursday's IRC conversation about @summary
- Re: Summary of Thursday's IRC conversation about @summary
- Re: Summary of Thursday's IRC conversation about @summary
- Re: Spam:******, What makes a failure? (@summary, et al)
- Re: What makes a failure? (@summary, et al)
- Re: Summary of Thursday's IRC conversation about @summary
- Re: Summary of Thursday's IRC conversation about @summary
- Re: Summary of Thursday's IRC conversation about @summary
- Re: Firing media events early for throttled downloads
- <font color="blue"> (was ISSUE-32)
- Re: Summary of Thursday's IRC conversation about @summary
- Re: Opportunity costs ... Re: Summary of Thursday's IRC conversation about @summary
- Re: Summary of Thursday's IRC conversation about @summary
- Re: Summary of Thursday's IRC conversation about @summary
- Opportunity costs ... Re: Summary of Thursday's IRC conversation about @summary
- <details> as a child of <caption> or <figure><legend> [was: Re: Summary of Thursday's IRC conversation about @summary]
- Re: What makes a failure? (@summary, et al)
- Merge NETWORK_NO_SOURCE and NETWORK_EMPTY
- What makes a failure? (@summary, et al)
- Re: What makes a failure? (@summary, et al)
- Re: What makes a failure? (@summary, et al)
- Re: What makes a failure? (@summary, et al)
- Re: Summary of Thursday's IRC conversation about @summary
- What makes a failure? (@summary, et al)
- Re: Firing media events early for throttled downloads
- Re: Firing media events early for throttled downloads
- Re: Firing media events early for throttled downloads
- Re: Summary of Thursday's IRC conversation about @summary
- Re: Summary of Thursday's IRC conversation about @summary
- Re: HTML 4.01 Strict table attributes and downplayed errors
- Re: Summary of Thursday's IRC conversation about @summary
- Re: HTML 4.01 Strict table attributes and downplayed errors
- Re: Summary of Thursday's IRC conversation about @summary
- Re: Summary of Thursday's IRC conversation about @summary
- Re: Firing media events early for throttled downloads
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
Sunday, 7 June 2009
- Re: Firing media events early for throttled downloads
- [Bug 7003] New: Typos
- value of IRC conversations [was: Summary of Thursday's IRC conversation about @summary]
Saturday, 6 June 2009
- RE: Firing media events early for throttled downloads
- Re: Firing media events early for throttled downloads
- Re: Summary of Thursday's IRC conversation about @summary
- RE: Firing media events early for throttled downloads
- Re: Parsing: "<" inside tags
- Re: Firing media events early for throttled downloads
- RE: Firing media events early for throttled downloads
- Re: Summary of Thursday's IRC conversation about @summary
- Re: Firing media events early for throttled downloads
- RE: Firing media events early for throttled downloads
- Re: Summary of Thursday's IRC conversation about @summary
- Re: Firing media events early for throttled downloads
- Re: Summary of Thursday's IRC conversation about @summary
- Re: <section><hgroup><h1><h2> styling
- Re: Accesskey issues
- Re: Summary of Thursday's IRC conversation about @summary
- Re: Parsing: "<" inside tags
- Re: <section><hgroup><h1><h2> styling
- Re: Summary of Thursday's IRC conversation about @summary
- Re: Summary of Thursday's IRC conversation about @summary
- Re: Summary of Thursday's IRC conversation about @summary
- Re: Media elements may never load, may load the wrong source, etc
- Re: Footnotes and sectioning roots. <figure> and <table>
- Re: Events on window
Friday, 5 June 2009
- RE: Summary of Thursday's IRC conversation about @summary
- RE: Firing media events early for throttled downloads
- Re: Summary of Thursday's IRC conversation about @summary
- Re: Summary of Thursday's IRC conversation about @summary
- Quirks mode vs. standards mode
- RE: Firing media events early for throttled downloads
- Re: Accesskey issues
- RE: Firing media events early for throttled downloads
- Re: Footnotes and sectioning roots. <figure> and <table>
- Re: Summary of Thursday's IRC conversation about @summary
- Re: Summary of Thursday's IRC conversation about @summary
- Re: Times, dates, and related topics
- Re: Summary of Thursday's IRC conversation about @summary
- Re: Summary of Thursday's IRC conversation about @summary
- Re: HTML 4.01 Strict table attributes and downplayed errors
- Re: Summary of Thursday's IRC conversation about @summary
- Re: Summary of Thursday's IRC conversation about @summary
- Re: Firing media events early for throttled downloads
- RE: Summary of Thursday's IRC conversation about @summary
- [Bug 6999] New: Adding tag <NSFW>
- Re: Summary of Thursday's IRC conversation about @summary
- Re: Summary of Thursday's IRC conversation about @summary
- Re: Summary of Thursday's IRC conversation about @summary
- Re: Summary of Thursday's IRC conversation about @summary
- Re: Summary of Thursday's IRC conversation about @summary
- Summary of Thursday's IRC conversation about @summary
- Re: R2866 : better talk about "CSS display" instead of "CSS tables"
- Re: A generalized <summary> element
- A generalized <summary> element
- [webstorage] IndexGetter Methods Should Not Throw Exception
- Re: PF Response: @Summary
- Re: PF Response: @Summary
- Re: comments on draft-barth-mime-sniffing
- Re: PF Response: @Summary
- RE: PF Response: @Summary
- Re: PF Response: @Summary
Thursday, 4 June 2009
- RE: PF Response: @Summary
- Re: R2866 : better talk about "CSS display" instead of "CSS tables"
- Re: Reparsing of comments, escaped text spans, and --!>
- RE: PF Response: @Summary
- Re: PF Response: @Summary
- Re: {agenda} HTML WG telcon 2009-06-04 -- minutes enclosed
- Re: Why Design Principles?
- Re: PF Response: @Summary
- Re: PF Response: @Summary
- Re: PF Response: @Summary
- Re: document[id] and document.id to <element id="id"> matching
- Re: document[id] and document.id to <element id="id"> matching
- Re: PF Response: @Summary
- Re: PF Response: @Summary
- Re: PF Response: @Summary
- Re: PF Response: @Summary
- Re: Documenting Web app assumptions, and HTML
- Re: {agenda} HTML WG telcon 2009-06-04
- Re: Documenting Web app assumptions, and HTML
- Re: Why Design Principles?
- Re: PF Response: @Summary
- Documenting Web app assumptions, and HTML
- Re: document[id] and document.id to <element id="id"> matching
- Re: Why Design Principles?
- Re: Why Design Principles?
- Re: Why Design Principles?
- Re: image width & height, summary
- Re: Adjusting the definition of fallback-free object
Wednesday, 3 June 2009
- Re: Why Design Principles?
- Re: Fragment Identifiers and Focus
- Re: Value of HTMLElement::id when no id="" attribute is present
- Re: Why Design Principles?
- Re: Why Design Principles?
- Re: feedback on 4.10.4.2.8 The pattern attribute
- RE: Why Design Principles?
- Re: Adjusting the definition of fallback-free object
- Re: document[id] and document.id to <element id="id"> matching
- {agenda} HTML WG telcon 2009-06-04
- Re: image width & height, summary
- Re: Updating the IRI spec to include "web addresses"
- Re: The formatblock command
- Re: Updating the IRI spec to include "web addresses"
- Updated RDFa-in-text/html tests
- Re: Black-box equivalence of parsing fragments directly into context node
- The formatblock command
- [Bug 6993] New: Tell authoring tools to use UTF-8
- Re: Auto-detect and encodings in HTML5
- Editorial: Usage of "HTML5" in the spec
- RE: image width & height, summary
- Re: image width & height, summary
- RE: image width & height, summary
- [Bug 6992] New: Title of Web IDL misspelled as WebIDL
- Re: image width & height, summary
- Re: Why Design Principles?
- Re: image width & height, summary
- Re: image width & height, summary
- Re: Why Design Principles?
- Re: Why Design Principles?
- image width & height, summary
- RE: Why Design Principles?
- Re: Why Design Principles?
- Re: Why Design Principles?
- Re: Why Design Principles?
- Re: Why Design Principles?
Tuesday, 2 June 2009
- Re: Why Design Principles?
- Re: Why Design Principles?
- Re: Why Design Principles?
- Re: Why Design Principles?
- Re: Why Design Principles?
- Re: Why Design Principles?
- Re: Why Design Principles?
- Re: Why Design Principles?
- Re: Why Design Principles?
- Re: several messages
- Re: Why Design Principles?
- Re: Origin header in loading external scripts (ISSUE-63)
- RE: several messages
- Re: several messages
- Re: Updating the IRI spec to include "web addresses"
- Re: Auto-detect and encodings in HTML5
- RE: several messages
- RE: Auto-detect and encodings in HTML5
- Re: Auto-detect and encodings in HTML5
- Re: several messages
- Re: <object> element
- Re: Auto-detect and encodings in HTML5
- RE: Auto-detect and encodings in HTML5
- Re: several messages
- Re: Why Design Principles?
- Re: Auto-detect and encodings in HTML5
- Re: Why Design Principles?
- Re: Auto-detect and encodings in HTML5
- Re: Why Design Principles?
- Re: Why Design Principles?
- Re: Auto-detect and encodings in HTML5
- [Bug 6670] Allow unescaped &s, at least in attributes that accept URLs
- Re: several messages
- <isindex> parsing
- Re: several messages
- Re: several messages
- Re: Why Design Principles?
- Re: Why Design Principles?
- [Bug 6978] Mark eof-terminated script elements as malformed
- [Bug 6778] Note the XPath implications of assigning HTML elements into the http://www.w3.org/1999/xhtml namespace
- Re: Why Design Principles?
- Re: Concerns about new section "predefined vocabularies" (ACTION-123)
- [Bug 6776] Note the XSLT implications of assigning HTML elements into the http://www.w3.org/1999/xhtml namespace
- Re: Why Design Principles?
- Re: Auto-detect and encodings in HTML5
- Re: DOMStringMap - get keys, et length?
- Re: Handling of undefined in createPattern()
- Re: Concerns about new section "predefined vocabularies" (ACTION-123)
- Re: <object> element
- Re: <object> element
- Re: Why Design Principles?
- Re: Why Design Principles?
- Why Design Principles?
- [Bug 6973] Support <textarea>.textLength
- [Bug 6974] Please be explicit about inheritance of scripting flag when setting innerHTML
- [Bug 6978] Mark eof-terminated script elements as malformed
- [Bug 6977] Unnecessary sentence in <cite> presentation
- [Bug 6949] Don't use colon shorthand when talking about language-related attributes
- [Bug 6942] Define how to handle failed 'resolve a url' steps in microdata algorithms
- [Bug 6937] BibTeX author and editor don't fit DRY HTML
- Re: Auto-detect and encodings in HTML5
- Re: Auto-detect and encodings in HTML5
- RE: Auto-detect and encodings in HTML5
- Re: Auto-detect and encodings in HTML5
- Re: Auto-detect and encodings in HTML5
- [Bug 6902] Note incompatibilities with RDF serializations
Monday, 1 June 2009
- Input on the agenda
- Re: <object> element
- Re: Auto-detect and encodings in HTML5
- [Bug 6898] Case shifting terminology is confusing
- [Bug 6894] add statement that the "checked" attribute on <input> is a boolean attribute
- [Bug 6842] make it possible/easy to link to tables documenting <input> element keywords/states and attributes/methods
- [Bug 6835] The multiple attribute on datagrid
- [Bug 6833] Datagrid minor comments
- [Bug 6832] <datagrid> content model is silly
- Re: Design Principles, Section 1.6.1 relationship to HTML 4.01
- Re: Auto-detect and encodings in HTML5
- RE: Auto-detect and encodings in HTML5
- Re: unescaped ampersands was: several messages
- [Bug 6812] Typo: JavsScript
- [Bug 6796] <keygen> in <select>
- [Bug 6790] object element with usemap attribute should be in "Interactive content" category
- [Bug 6779] Clarify the difference between elements and tags
- [Bug 6770] Term emphasis inconsistencies in Terminology section
- [Bug 6778] Note the XPath implications of assigning HTML elements into the http://www.w3.org/1999/xhtml namespace
- [Bug 6776] Note the XSLT implications of assigning HTML elements into the http://www.w3.org/1999/xhtml namespace
- RE: Content sniffing, feed readers, etc. (was HTML interpreter vs. HTML user agent)
- Re: unescaped ampersands was: several messages
- unescaped ampersands was: several messages
- Re: <object> element
- Re: Content sniffing, feed readers, etc. (was HTML interpreter vs. HTML user agent)
- Re: several messages
- Re: Design Principles, Section 1.6.1 relationship to HTML 4.01
- RE: Auto-detect and encodings in HTML5
- Re: Updating the IRI spec to include "web addresses"
- Re: Auto-detect and encodings in HTML5
- RE: Auto-detect and encodings in HTML5
- Re: Design Principles, Section 1.6.1 relationship to HTML 4.01
- Re: <object> element
- Re: Design Principles, Section 1.6.1 relationship to HTML 4.01
- RE: Auto-detect and encodings in HTML5
- Re: Design Principles, Section 1.6.1 relationship to HTML 4.01
- Re: Updating the IRI spec to include "web addresses"
- Re: Design Principles, Section 1.6.1 relationship to HTML 4.01
- Re: Design Principles, Section 1.6.1 relationship to HTML 4.01
- Re: Design Principles, Section 1.6.1 relationship to HTML 4.01
- Re: [Bug 6670] Allow unescaped &s, at least in attributes that accept URLs
- Re: Design Principles, Section 1.6.1 relationship to HTML 4.01
- Re: Content sniffing, feed readers, etc. (was HTML interpreter vs. HTML user agent)
- Re: [Bug 6670] Allow unescaped &s, at least in attributes that accept URLs
- Re: comments on draft-barth-mime-sniffing
- [Bug 6769] Grammar mistake: "element element"?
- [Bug 6768] 4.8.10.3 Media types -- unclear note
- RE: Auto-detect and encodings in HTML5
- Re: Auto-detect and encodings in HTML5
- [Bug 6767] <time> warning regarding Gregorian calendar
- Re: comments on draft-barth-mime-sniffing
- Re: Design Principles, Section 1.6.1 relationship to HTML 4.01
- RE: Auto-detect and encodings in HTML5
- Re: Auto-detect and encodings in HTML5
- Re: <object> element
- Re: HTML interpreter vs. HTML user agent
- Re: <object> element
- RE: Updating the IRI spec to include "web addresses"
- Re: Auto-detect and encodings in HTML5
- Re: Auto-detect and encodings in HTML5
- Re: Design Principles, Section 1.6.1 relationship to HTML 4.01
- Re: Section 1.6.1 relationship to HTML 4.01
- Re: Design Principles
- Re: Design Principles, Section 1.6.1 relationship to HTML 4.01