Sunday, 31 August 2008
- Re: Are new void elements really a good idea?
- Editors (was Re: @headers issue resolved...)
- Re: Are new void elements really a good idea?
- Re: @headers issue resolved - allowing a td to be referenced by a header to be in the HTMl5 spec.
- Re: Are new void elements really a good idea?
- Re: @headers issue resolved - allowing a td to be referenced by a header to be in the HTMl5 spec.
- Re: Comparing conformance requirements against real-world docs
- Re: @headers issue resolved - allowing a td to be referenced by a header to be in the HTMl5 spec.
- Re: Are new void elements really a good idea?
- Re: @headers issue resolved - allowing a td to be referenced by a header to be in the HTMl5 spec.
- Re: Are new void elements really a good idea?
- Re: @headers issue resolved - allowing a td to be referenced by a header to be in the HTMl5 spec.
- Re: @headers issue resolved - allowing a td to be referenced by a header to be in the HTMl5 spec.
- Re: Are new void elements really a good idea?
- Re: @headers issue resolved - allowing a td to be referenced by a header to be in the HTMl5 spec.
- Re: Are new void elements really a good idea?
- Re: @headers issue resolved - allowing a td to be referenced by a header to be in the HTMl5 spec.
- Re: @headers issue resolved - allowing a td to be referenced by a header to be in the HTMl5 spec.
- Re: Are new void elements really a good idea?
- Re: @headers issue resolved - allowing a td to be referenced by a header to be in the HTMl5 spec.
- Re: Are new void elements really a good idea?
- Re: Are new void elements really a good idea?
- Re: Are new void elements really a good idea?
- Re: Are new void elements really a good idea?
- Re: Are new void elements really a good idea?
- Re: Are new void elements really a good idea?
- Re: Are new void elements really a good idea?
- Re: Are new void elements really a good idea?
- Re: Are new void elements really a good idea?
- Re: Are new void elements really a good idea?
- Re: @headers issue resolved - allowing a td to be referenced by a header to be in the HTML5 spec.
Saturday, 30 August 2008
- Re: Are new void elements really a good idea?
- Re: Are new void elements really a good idea?[1]
- Re: Are new void elements really a good idea?
- Are new void elements really a good idea?
- Re: @headers issue resolved - allowing a td to be referenced by a header to be in the HTMl5 spec.
- Re: Comparing conformance requirements against real-world docs
- Re: Comparing conformance requirements against real-world docs
- Re: Comparing conformance requirements against real-world docs
- Re: Comparing conformance requirements against real-world docs
- Re: Comparing conformance requirements against real-world docs
- Comparing conformance requirements against real-world docs
Friday, 29 August 2008
- Re: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec]
- Re: Postscript is not scriptable? (2.7.4 Content-Type sniffing)
- Postscript is not scriptable? (2.7.4 Content-Type sniffing)
- Re: About video & audio elements
- Re: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec]
- RE: @headers issue resolved - allowing a td to be referenced by a header to be in the HTMl5 spec.
- RE: [whatwg] Is EBCDIC support needed for not breaking the Web?
- Re: About video & audio elements
- Re: About video & audio elements
- Re: @headers issue resolved - allowing a td to be referenced by a header to be in the HTMl5 spec.
- Re: table headers - clear description of problem
- Re: @headers issue resolved - allowing a td to be referenced by a header to be in the HTMl5 spec.
- RE: <bb> - typo, rename?
- Re: About video & audio elements
- Re: <bb> - typo, rename?
- Re: @headers issue resolved - allowing a td to be referenced by a header to be in the HTMl5 spec.
- Re: table headers - clear description of problem
- Re: Adjusting MathML attributes: definitionURL
- Re: @headers issue resolved - allowing a td to be referenced by a header to be in the HTMl5 spec.
- Re: table headers - clear description of problem
- Re: <bb> - typo, rename?
- @headers issue resolved - allowing a td to be referenced by a header to be in the HTMl5 spec.
- Re: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec]
- Re: The alt="" attribute
- Re: <bb> - typo, rename?
- Re: namespace-well-formedness and setting innerHTML in XML
- Re: Prefixes and setting innerHTML in XML
- Re: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec]
- Re: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec]
- Re: [whatwg] Is EBCDIC support needed for not breaking the Web?
- Re: [whatwg] Is EBCDIC support needed for not breaking the Web?
- Re: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec]
- Re: Tree construction: Coalescing text nodes
- Re: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec]
- Re: Quotes in attribute names after a boolean attribute
- Re: Parsing: Equals sign in unquoted attributes
- Re: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec]
- Re: Validating XHTML5 with XML entities
- Re: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec]
- Re: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec]
- Re: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec]
Thursday, 28 August 2008
- Re: Status of <a>
- Re: About video & audio elements
- Re: on getting meta-data from images etc.
- on getting meta-data from images etc.
- Re: <bb> - typo, rename?
- Re: Clarification of case where 'there simply is no text that can do justice to an image'
- Re: The alt="" attribute
- Status of <a>
- Re: <bb> - typo, rename?
- <bb> - typo, rename?
- Re: Mandatory and Important
- Re: Deliverable for Action 72 @headers
- Re: Validating XHTML5 with XML entities
- Re: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec]
- Re: The alt="" attribute
- Re: [author-guide] Character Entity References Chart
- Re: Validating XHTML5 with XML entities
- [Bug 5997] New: Define script execution for XHTML5
- Re: Feedback on SVGWG's SVG-in-text/html proposal
- Re: Detailed review of 3.18.3. The command and 3.18.4. the menu elements
- Re: Feedback on SVGWG's SVG-in-text/html proposal
- Using usemap for purposes other than image maps, and related questions
- Re: Feedback on SVGWG's SVG-in-text/html proposal
- Re: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec]
- Re: meta content-language
- Re: meta content-language
- RE: meta content-language
- Re: Validating XHTML5 with XML entities
- Re: Validating XHTML5 with XML entities
- Feedback on SVGWG's SVG-in-text/html proposal
- Re: EXIF metadata
- Re: Validating XHTML5 with XML entities
- Re: EXIF metadata
- Re: meta content-language
- Re: EXIF metadata
- Re: EXIF metadata
Wednesday, 27 August 2008
- Re: EXIF metadata (was: The alt="" attribute)
- Re: The alt="" attribute
- Re: The alt="" attribute
- RE: table headers - clear description of problem
- Re: Validating XHTML5 with XML entities
- Re: Validating XHTML5 with XML entities
- Re: Validating XHTML5 with XML entities
- Re: Validating XHTML5 with XML entities
- Re: Validating XHTML5 with XML entities
- Re: Validating XHTML5 with XML entities
- Re: Validating XHTML5 with XML entities
- Re: The alt="" attribute
- RE: meta content-language
- Re: Validating XHTML5 with XML entities
- RE: Workers
- RE: meta content-language
- The alt="" attribute
- Re: test cases Re: xml:lang="" and lang=""
- Re: Validating XHTML5 with XML entities
- RE: meta content-language
- Re: table headers - clear description of problem
- Re: Workers
- RE: Workers
- language declaration stats (was Re: meta content-language)
- Re: The alt="" attribute
- Re: Validating XHTML5 with XML entities
- Re: Validating XHTML5 with XML entities
- Re: meta content-language
- Re: meta content-language
- RE: meta content-language
- Re: The alt="" attribute
- Re: Acessibility of <audio> and <video>
- Re: The alt="" attribute
- Re: The alt="" attribute
- Re: table headers - clear description of problem
- Re: Validating XHTML5 with XML entities
- Re: table headers - clear description of problem
Tuesday, 26 August 2008
- Re: Validating XHTML5 with XML entities
- Re: Acessibility of <audio> and <video>
- Re: The alt="" attribute
- Re: The alt="" attribute
- RE: The alt="" attribute
- Re: The alt="" attribute
- Re: The alt="" attribute
- Re: Validating XHTML5 with XML entities
- Re: Validating XHTML5 with XML entities
- Re: The alt="" attribute
- Validating XHTML5 with XML entities
- Re: The alt="" attribute
- [Bug 5994] New: add note in syntax section
- Re: table headers - clear description of problem
- Re: The alt="" attribute
- RE: The alt="" attribute
- Re: table headers - clear description of problem
- Re: The alt="" attribute
- Re: table headers - clear description of problem
- RE: The alt="" attribute
- Re: img issue: should we restrict the URI
- Re: The alt="" attribute
- Re: HTML5 parser integrated in W3C Markup Validator
- RE: meta content-language
- Re: table headers - clear description of problem
- RE: table headers - clear description of problem
- Re: The alt="" attribute
- Re: table headers - clear description of problem
- Re: table headers - clear description of problem
- Re: table headers - clear description of problem
- Re: table headers - clear description of problem
- Re: table headers - clear description of problem
- Re: table headers - clear description of problem
- Re: table headers - clear description of problem
- Re: Acessibility of <audio> and <video>
- Re: table headers - clear description of problem
- Re: Deliverable for Action 72 @headers
- Re: The alt="" attribute
- Re: Deliverable for Action 72 @headers
- Re: The alt="" attribute
- Re: HTML5 parser integrated in W3C Markup Validator
- Re: table headers - clear description of problem
- Re: table headers - clear description of problem
- Re: table headers - clear description of problem
- Re: Deliverable for Action 72 @headers
- Re: table headers - clear description of problem
- Re: table headers - clear description of problem
- Re: table headers - clear description of problem
- Re: table headers - clear description of problem
- The alt="" attribute
- Re: table headers - clear description of problem
- Re: table headers - clear description of problem
- Re: table headers - clear description of problem
- [Bug 5991] New: workers
- [Bug 5990] New: SVG in HTML
- [Bug 5989] New: alt=""
- Re: HTML5 parser integrated in W3C Markup Validator
- Re: HTML5 parser integrated in W3C Markup Validator
- Re: meta content-language
Monday, 25 August 2008
- Re: Mandatory and Important
- Re: Acessibility of <audio> and <video>
- Re: Mandatory and Important
- Re: HTML5 parser integrated in W3C Markup Validator
- Re: HTML5 parser integrated in W3C Markup Validator
- HTML5 parser integrated in W3C Markup Validator
- Re: Acessibility of <audio> and <video>
- Re: Acessibility of <audio> and <video>
- Re: Acessibility of <audio> and <video>
- Re: Acessibility of <audio> and <video>
- Re: Acessibility of <audio> and <video>
- Re: Acessibility of <audio> and <video>
- Re: Acessibility of <audio> and <video>
- Re: Acessibility of <audio> and <video>
- Re: Acessibility of <audio> and <video>
- Re: Acessibility of <audio> and <video>
- RE: Acessibility of <audio> and <video>
- Re: Acessibility of <audio> and <video>
- Re: Acessibility of <audio> and <video>
- Re: Acessibility of <audio> and <video>
- Re: Acessibility of <audio> and <video>
- Re: Acessibility of <audio> and <video>
- Re: Acessibility of <audio> and <video>
- Re: ***DHSPAM*** Re: Request for clarification of the case where 'the image isn't discussed by the surrounding text, but it has some relevance'
- Re: Acessibility of <audio> and <video>
- Re: Acessibility of <audio> and <video>
- Re: Acessibility of <audio> and <video>
- Re: Acessibility of <audio> and <video>
- Re: Acessibility of <audio> and <video>
- Re: Acessibility of <audio> and <video>
- Re: Acessibility of <audio> and <video>
- Re: Acessibility of <audio> and <video>
- Re: Acessibility of <audio> and <video>
- Re: ***DHSPAM*** Re: Request for clarification of the case where 'the image isn't discussed by the surrounding text, but it has some relevance'
- Re: Acessibility of <audio> and <video>
- Re: Mandatory and Important
- Re: Acessibility of <audio> and <video>
- Re: Acessibility of <audio> and <video>
- Re: Acessibility of <audio> and <video>
- RE: Mandatory and Important
- Re: meta content-language
- Re: Acessibility of <audio> and <video>
- Re: Acessibility of <audio> and <video>
- Re: Acessibility of <audio> and <video>
- Re: table headers - clear description of problem
- Re: Acessibility of <audio> and <video>
- Re: Acessibility of <audio> and <video>
- Re: Acessibility of <audio> and <video>
- Re: Acessibility of <audio> and <video>
- Re: About video & audio elements
- Re: table headers - clear description of problem
- Re: ***DHSPAM*** Re: Request for clarification of the case where 'the image isn't discussed by the surrounding text, but it has some relevance'
- Acessibility of <audio> and <video>
- RE: table headers - clear description of problem
- Re: table headers - clear description of problem
- Re: table headers - clear description of problem
- Re: table headers - clear description of problem
- Re: ***DHSPAM*** Re: Request for clarification of the case where 'the image isn't discussed by the surrounding text, but it has some relevance'
- Re: ***DHSPAM*** Re: Request for clarification of the case where 'the image isn't discussed by the surrounding text, but it has some relevance'
- Re: About video & audio elements
- Re: ***DHSPAM*** Re: Request for clarification of the case where 'the image isn't discussed by the surrounding text, but it has some relevance'
- Re: ***DHSPAM*** Re: Request for clarification of the case where 'the image isn't discussed by the surrounding text, but it has some relevance'
- Re: table headers - clear description of problem
- Re: Request for clarification of the case where 'the image isn't discussed by the surrounding text, but it has some relevance'
- Re: Request for clarification of the case where 'the image isn't discussed by the surrounding text, but it has some relevance'
- Re: table headers - clear description of problem
- Re: About video & audio elements
- About video & audio elements
- Re: table headers - clear description of problem
- Re: HTML5 and XML
- table headers - clear description of problem
- Re: Request for clarification of the case where 'the image isn't discussed by the surrounding text, but it has some relevance'
- Re: Request for clarification of the case where 'the image isn't discussed by the surrounding text, but it has some relevance'
- Re: meta content-language
- HTML5 and XML (was: Re: meta content-language)
- Lose Focus When Hidden? (SVG ISSUE-2031)
Sunday, 24 August 2008
- Re: Mandatory and Important
- Re: Flickr and alt
- Re: Mandatory and Important
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Deliverable for Action 72 @headers
- Re: Deliverable for Action 72 @headers
- Re: Deliverable for Action 72 @headers
- Re: Deliverable for Action 72 @headers
- Re: Deliverable for Action 72 @headers
- Re: Deliverable for Action 72 @headers
- RE: Mandatory and Important
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Deliverable for Action 72 @headers
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Mandatory and Important
- Re: Deliverable for Action 72 @headers
- Re: Flickr and alt
- RE: some reflections on @alt usage (and summary of research so far)
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Flickr and alt
- Re: requiring the alt attribute
- requiring the alt attribute [was Re: Another HTML5 alt conformance question for clarification]
- Re: SVG in HTML proposal
- Re: SVG in HTML proposal
- Re: SVG in HTML proposal
Saturday, 23 August 2008
- Re: Deliverable for Action 72 @headers
- Re: Deliverable for Action 72 @headers
- Re: Deliverable for Action 72 @headers
- Re: Deliverable for Action 72 @headers
- Re: Deliverable for Action 72 @headers
- Re: Mandatory and Important
- Re: Mandatory and Important
- Re: Flickr and alt
- Re: Mandatory and Important
- Re: some reflections on @alt usage (and summary of research so far)
- Re: Request for clarification of 'In many cases, the image is actually just supplementary'
- Re: Flickr and alt
- Re: Another HTML5 alt conformance question for clarification
- Re: Request for clarification of 'In many cases, the image is actually just supplementary'
- Re: some reflections on @alt usage (and summary of research so far)
- Re: some reflections on @alt usage (and summary of research so far)
- Re: some reflections on @alt usage (and summary of research so far)
- Re: some reflections on @alt usage (and summary of research so far)
- Re: some reflections on @alt usage (and summary of research so far)
- Re: Request for clarification of the case where 'the image isn't discussed by the surrounding text, but it has some relevance'
- Re: Request for clarification of 'In many cases, the image is actually just supplementary'
- Re: Another HTML5 alt conformance question for clarification
- Re: Clarification of case where 'there simply is no text that can do justice to an image'
- Re: some reflections on @alt usage (and summary of research so far)
- Re: Mandatory and Important
- Re: Mandatory and Important
- Re: some reflections on @alt usage (and summary of research so far)
- Re: Mandatory and Important
- Re: Mandatory and Important
- Re: some reflections on @alt usage
- Re: Flickr and alt
Friday, 22 August 2008
- Re: Mandatory and Important
- Re: some reflections on @alt usage (and summary of research so far)
- embedded media norms and two separate text equivalents: alt text and descriptive text
- Re: some reflections on @alt usage (and summary of research so far)
- Re: Mandatory and Important
- Re: some reflections on @alt usage
- Re: some reflections on @alt usage
- Re: Mandatory and Important
- Re: Mandatory and Important
- Re: Mandatory and Important
- Re: some reflections on @alt usage
- Re: Mandatory and Important
- Re: ***DHSPAM*** Re: some reflections on @alt usage
- Re: some reflections on @alt usage
- Re: some reflections on @alt usage
- Re: some reflections on @alt usage
- Re: some reflections on @alt usage
- Re: some reflections on @alt usage
- Re: meta content-language
- Re: meta content-language
- Re: some reflections on @alt usage
- Re: Mandatory and Important
- Re: Mandatory and Important
- Re: Mandatory and Important
- embedded media norms
- Re: Mandatory and Important
- Re: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec]
- Re: Mandatory and Important
- RE: HTML5 URL vs. IRI vs. URI...
- Re: HTML5 URL vs. IRI vs. URI...
- Re: Mandatory and Important
- Re: Deliverable for Action 72 @headers
- Re: meta content-language
- Re: meta content-language
- Re: meta content-language
- Re: meta content-language
- Re: meta content-language
- Re: Mandatory and Important
- Re: meta content-language
- Re: Mandatory and Important
- Re: Mandatory and Important
- Re: Deliverable for Action 72 @headers
- Re: Mandatory and Important
- RE: [LIKELY JUNK]Insight into the assumption that informs the HTML5 editors thinking on what constitutes an appropriate text alternative
- Re: Deliverable for Action 72 @headers
- Insight into the assumption that informs the HTML5 editors thinking on what constitutes an appropriate text alternative
- Re: Mandatory and Important
- Re: meta content-language
- Re: Mandatory and Important
- Re: meta content-language
- Re: HTML5 URL vs. IRI vs. URI...
- Re: Interactiveness of <details>
- Re: Detailed review of 3.18.1 The details element
- Re: meta content-language
- Re: meta content-language
- Re: meta content-language
- Re: meta content-language
- Re: meta content-language
- Re: Mandatory and Important
- Re: Alt Use Cases ACTION 54 (was Re: Mandatory and Important)
- RE: Mandatory and Important
- Re: Alt Use Cases ACTION 54 (was Re: Mandatory and Important)
- Re: html5 nitpicks
- Re: meta content-language
- Re: Deliverable for Action 72 @headers
- Re: meta content-language
- Re: meta content-language
Thursday, 21 August 2008
- Alt Use Cases ACTION 54 (was Re: Mandatory and Important)
- Re: Lack Of Definition Of A Valid Ratio (part of detailed review of common microsyntaxes)
- Re: meta content-language
- Re: <style scoped> and semi-transparent content models
- Re: <style scoped> and semi-transparent content models
- Re: meta content-language
- Re: meta content-language
- Re: Mandatory and Important
- Re: meta content-language
- Re: Mandatory and Important
- Re: Request for PFWG WAI review of @summary for tabular data
- Re: meta content-language
- HTML5 URL vs. IRI vs. URI...
- RE: meta content-language
- RE: Mandatory and Important
- Re: meta content-language
- Re: meta content-language
- Re: Deliverable for Action 72 @headers
- Re: Mandatory and Important
- Re: some reflections on @alt usage
- Deliverable for Action 72 @headers
- Re: some reflections on @alt usage
- [Bug 5979] New: unclear whether new Audio(url) should throw
- Re: Mandatory and Important
- Re: Request for PFWG WAI review of @summary for tabular data
- Re: Request for PFWG WAI review of @summary for tabular data
- RE: Mandatory and Important
- Re: Request for PFWG WAI review of @summary for tabular data
- Re: Mandatory and Important
- RE: Request for PFWG WAI review of @summary for tabular data
- Re: Mandatory and Important
- Mandatory and Important
- Re: Request for PFWG WAI review of @summary for tabular data
- Re: Request for PFWG WAI review of @summary for tabular data
- Re: Validation error frequencies in Alexa top 500 front pages
- Re: meta content-language
- Re: meta content-language
- RE: Flickr and alt
- Optional But Important (was: alt attribute - a very simple proposal)
- test cases Re: xml:lang="" and lang=""
Wednesday, 20 August 2008
Tuesday, 19 August 2008
Thursday, 21 August 2008
Wednesday, 20 August 2008
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Flickr and alt
- Re: alt attribute - a very simple proposal
- Re: alt attribute - a very simple proposal
- Re: Flickr and alt
- Re: alt attribute - a very simple proposal
- Re: alt attribute - a very simple proposal
- Re: Flickr and alt
- Re: alt attribute - a very simple proposal
- Re: alt attribute - a very simple proposal
- RE: Flickr and alt
- Re: meta content-language
- Re: meta content-language
- Re: alt attribute - a very simple proposal
- Re: Flickr and alt
- RE: meta content-language
- Re: Flickr and alt
- Re: Flickr and alt
Tuesday, 19 August 2008
- Re: isContentEditable: boolean
- Re: alt attribute - a very simple proposal
- Re: alt attribute - a very simple proposal
- removeformat feedback
- Re: several messages about contentEditable, text selection, and related subjects
- Re: Event listeners and designMode (was: Re: several messages about contentEditable, ...)
- RE: Flickr and alt
- RE: Flickr and alt
- Re: alt attribute - a very simple proposal
- Re: Flickr and alt
- Re: Fwd: Flickr and alt
- RE: alt attribute - a very simple proposal
- Re: Flickr and alt
- RE: meta content-language
- Re: alt attribute - a very simple proposal
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Flickr and alt
- Re: alt attribute - a very simple proposal
- Re: Flickr and alt
- Re: Flickr and alt
- Re: alt attribute - a very simple proposal
- Re: alt attribute - a very simple proposal
- Re: alt attribute - a very simple proposal
- Re: Flickr and alt
- Re: alt attribute - a very simple proposal
- Re: alt attribute - a very simple proposal
- Re: alt attribute - a very simple proposal
- Re: alt attribute - a very simple proposal
- Re: alt attribute - a very simple proposal
- Re: Flickr and alt
- Re: alt attribute - a very simple proposal
- Re: alt attribute - a very simple proposal
- Re: alt attribute - a very simple proposal
- Re: alt attribute - a very simple proposal
- Re: alt attribute - a very simple proposal
- Re: meta content-language
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Request for clarification of the case where 'the image isn't discussed by the surrounding text, but it has some relevance'
- Re: Dealing with conflict in lang and xml:lang
- Dealing with conflict in lang and xml:lang
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Flickr and alt
- Re: [Bug 5974] New: Language tag sameness should probably be ASCII case-insensitive
- Re: [Bug 5974] New: Language tag sameness should probably be ASCII case-insensitive
- Re: Flickr and alt
- alt attribute - a very simple proposal
- Comparing Websites against a Checklist (Research)
- [Bug 5974] New: Language tag sameness should probably be ASCII case-insensitive
- Re: Flickr and alt
- Re: targeting August for next working draft of HTML5
- Re: Flickr and alt
- Re: Flickr and alt
- RE: Flickr and alt
- Re: Flickr and alt
- RE: Flickr and alt
- RE: meta content-language
- Re: Flickr and alt
- Re: Flickr and alt
Monday, 18 August 2008
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Fwd: Flickr and alt
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Flickr and alt
- Fwd: Flickr and alt
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Flickr and alt
- RE: meta content-language
- Re: DOM traversal ambiguity question
- RE: Flickr and alt (was: Re: HTML5 alt conformance criteria clarifications requested)
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Flickr and alt
- Re: Request for clarification of the case where 'the image isn't discussed by the surrounding text, but it has some relevance'
- Re: Flickr and alt
- Re: Request for clarification of the case where 'the image isn't discussed by the surrounding text, but it has some relevance'
- Re: Flickr and alt
- Re: DOM traversal ambiguity question
- Re: Flickr and alt (was: Re: HTML5 alt conformance criteria clarifications requested)
- Re: Flickr and alt (was: Re: HTML5 alt conformance criteria clarifications requested)
- Re: DOM traversal ambiguity question
- Collections of Interesting Web Pages (Research)
- Flickr and alt (was: Re: HTML5 alt conformance criteria clarifications requested)
- Request for clarification of the case where 'the image isn't discussed by the surrounding text, but it has some relevance'
- Re: Request for clarification of 'In many cases, the image is actually just supplementary'
- Re: Request for clarification of 'In many cases, the image is actually just supplementary'
- Request for clarification of 'In many cases, the image is actually just supplementary'
- Re: DOM traversal ambiguity question
- Re: DOM traversal ambiguity question
- Re: type parameter of Document.open() (detailed review of the DOM)
Sunday, 17 August 2008
- Re: Content-Type sniffing: unknown type mask including 00 at end
- Another HTML5 alt conformance question for clarification
- Re: HTML5 alt conformance criteria clarifications requested
- Re: HTML5 alt conformance criteria clarifications requested
- Re: What namespace features popular SVG tools really emit (ISSUE-37)
- Re: HTML5 alt conformance criteria clarifications requested
Saturday, 16 August 2008
- Re: HTML5 alt conformance criteria clarifications requested
- Re: HTML5 alt conformance criteria clarifications requested
- Re: HTML5 alt conformance criteria clarifications requested
- Re: HTML5 alt conformance criteria clarifications requested
- Re: HTML5 alt conformance criteria clarifications requested
- Clarification of case where 'there simply is no text that can do justice to an image'
- HTML5 alt conformance criteria clarifications requested
- Re: meta content-language
- RE: Images and alternative text
- Re: meta content-language
- Re: meta content-language
Friday, 15 August 2008
Sunday, 10 August 2008
Friday, 15 August 2008
- RE: meta content-language
- RE: meta content-language
- RE: meta content-language
- Re: meta content-language
- RE: meta content-language
- HTML Audio typo
- Re: meta content-language
Thursday, 14 August 2008
Friday, 15 August 2008
Thursday, 14 August 2008
- Re: type parameter of Document.open() (detailed review of the DOM)
- RE: meta content-language
- RE: meta content-language
- Re: type parameter of Document.open() (detailed review of the DOM)
- Re: img issue: should we restrict the URI
Wednesday, 13 August 2008
- Re: img issue: should we restrict the URI
- [Bug 5964] New: getting width/height on <embed>, <iframe>, <object> and <video>
- [Bug 5963] New: Editorial: xrefs in media event summary table
- Re: type parameter of Document.open() (detailed review of the DOM)
- AUTO: Aaron M Leventhal is out of the office. (returning 08/20/2008)
- ISSUE-58 (curly alt): Use of "curly brackets" to identify a graphical image by its use or type by inserting a generic identifier / descriptor in curly braces as the @alt value for an IMG, [HTML 5 spec]
- Re: Images and alternative text
- Re: type parameter of Document.open() (detailed review of the DOM)
- Re: document.location and no Window
- Re: Order of nodes from getElementsByClassName
- Re: Why HTML should be taught as HTML without pretending it is XML
- Re: document.title (detailed review of the DOM)
Tuesday, 12 August 2008
- Re: type parameter of Document.open() (detailed review of the DOM)
- Re: Deprecated language tags and document conformance
- Re: xml:lang in the light of error frequencies
- Re: Deprecated language tags and document conformance
- Re: <script src=javascript:"..."> should do nothing
- Re: xml:lang in the light of error frequencies
- Re: Deprecated language tags and document conformance
- Re: <script src=javascript:"..."> should do nothing
- Re: xml:lang in the light of error frequencies
- Re: meta content-language
- Re: <script src=javascript:"..."> should do nothing
- Re: <script src=javascript:"..."> should do nothing
- Re: <script src=javascript:"..."> should do nothing
- Re: Effect of bogus lang on determining natural language
- Re: <script src=javascript:"..."> should do nothing
- Re: <script src=javascript:"..."> should do nothing
- Re: <script src=javascript:"..."> should do nothing
- Re: <script src=javascript:"..."> should do nothing
- RE: <script src=javascript:"..."> should do nothing
- RE: <script src=javascript:"..."> should do nothing
- Re: Copypaste error in vague date parsing algorithm
- Re: Images and alternative text
- Re: <script src=javascript:"..."> should do nothing
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: alt curly braces proposal in the editor's HTML5 draft
Monday, 11 August 2008
- Re: <script src=javascript:"..."> should do nothing
- Re: Images and alternative text
- Re: <script src=javascript:"..."> should do nothing
- Re: Images and alternative text
- RE: <script src=javascript:"..."> should do nothing
- Re: <script src=javascript:"..."> should do nothing
- Re: <script src=javascript:"..."> should do nothing
- Re: Images and alternative text
- alt curly braces proposal in the editor's HTML5 draft
- RE: <script src=javascript:"..."> should do nothing
- Re: <script src=javascript:"..."> should do nothing
- Re: <script src=javascript:"..."> should do nothing
- Re: Images and alternative text
- Re: <script src=javascript:"..."> should do nothing
- Re: Images and alternative text
- Re: Images and alternative text
- Re: Images and alternative text
Sunday, 10 August 2008
- [Bug 5946] New: execCommand('insertHTML') should throw in xml
- Re: Images and alternative text
- Re: Images and alternative text
- Re: Images and alternative text
- Re: Images and alternative text
- RE: Workers
- RE: Images and alternative text
Saturday, 9 August 2008
Friday, 8 August 2008
- Re: Images and alternative text
- Re: Images and alternative text
- Re: Images and alternative text
- Re: Images and alternative text
- Re: Images and alternative text
- Re: Images and alternative text
- RE: Images and alternative text
- Re: Images and alternative text
- Re: Images and alternative text
- Re: Images and alternative text
- Re: Images and alternative text
- Re: Images and alternative text
- Re: Images and alternative text
- Re: Images and alternative text
- RE: Images and alternative text
- Re: Images and alternative text
- Re: Images and alternative text
Thursday, 7 August 2008
Friday, 8 August 2008
Thursday, 7 August 2008
- Re: Images and alternative text
- Re: Images and alternative text
- Re: Images and alternative text
- Re: Images and alternative text
- Re: Images and alternative text
- [Bug 5941] New: <video>.width/height should have default values defined
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Is it time for eRDF 1.1?
- RE: GRDDL
- RE: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- RE: GRDDL (was: RE: Extensibility strategies)
- [Bug 5937] New: make cache manifest syntax more extensible
- [Bug 5936] New: Offline cache syntax section needs an example
Wednesday, 6 August 2008
- Re: GRDDL
- RE: DOMStringMap - get keys, et length?
- Re: DOMStringMap - get keys, et length?
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: GRDDL
- Re: ***DHSPAM*** Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: ***DHSPAM*** Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Extensibility strategies
- Re: question about the draft:
- Re: Extensibility strategies
- DOMStringMap - get keys, et length?
- Re: question about the draft:
- Re: Request for PFWG WAI review of @summary for tabular data
- RE: question about the draft:
- Re: question about the draft:
- Re: Extensibility strategies
- Re: GRDDL (and the rule of least power)
- Re: Extensibility strategies
- Re: GRDDL (and the rule of least power)
- [Bug 5933] New: <video muted> issues
- Re: GRDDL
- Re: Extensibility strategies
- Re: Extensibility strategies
- Re: GRDDL
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: GRDDL
- Re: GRDDL
- Re: GRDDL
- Re: GRDDL
- Re: GRDDL
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: GRDDL (was: RE: Extensibility strategies)
- Re: Speed of specs (was: RE: Extensibility strategies)
- Speed of specs (was: RE: Extensibility strategies)
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- RE: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- RE: GRDDL (was: RE: Extensibility strategies)
- Re: Determining Script Type
Tuesday, 5 August 2008
- Re: GRDDL (was: RE: Extensibility strategies)
- Re: Detailed review of 3.18.3. The command and 3.18.4. the menu elements
- Re: Document conformance and non-empty <script src>
- Re: Interactiveness of <video controls> and <audio controls>
- Re: Please clarify that type=text/javascript is optional
- Re: Document conformance and non-empty <script src>
- Re: The script language attribute
- Re: Determining Script Type
- Re: Validation error frequencies in Alexa top 500 front pages
- Re: HTML5 object element - classid or not classid?
- GRDDL (was: RE: Extensibility strategies)
- RE: Translation control in HTML5
- Re: alt image replacement and replacement style
- RE: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: HTML5 object element - classid or not classid?
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: alt image replacement and replacement style
- RE: question about the draft:
- Re: HTML5 object element - classid or not classid?
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- RE: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Canvas miscellaneous comments
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: question about the draft:
- Re: Extensibility strategies
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Extensibility strategies
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: question about the draft:
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Translation control in HTML5
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Extensibility strategies
- Re: Canvas line style comments
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: <canvas> JPEG quality
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: <canvas> JPEG quality
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: question about the draft:
- Re: alt image replacement and replacement style
- Re: question about the draft:
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- RE: question about the draft:
- Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- RE: question about the draft:
- Re: question about the draft:
- RE: question about the draft:
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- RE: question about the draft:
- RE: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: question about the draft:
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
Monday, 4 August 2008
- [Bug 5927] New: HTMLInputElement need some improvements
- RE: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: question about the draft:
- Re: question about the draft:
- Re: question about the draft:
- Re: question about the draft:
- Re: question about the draft:
- Re: Extensibility strategies
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- question about the draft:
- alt image replacement and replacement style
- Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: HTML5 object element - classid or not classid?
- Re: HTML5 object element - classid or not classid?
- Re: Comments on the recent changes to the alt attribute section
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Comments on the recent changes to the alt attribute section
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Images and alternative text
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: What namespace features popular SVG tools really emit (ISSUE-37)
- Re: What namespace features popular SVG tools really emit (ISSUE-37)
- Re: What namespace features popular SVG tools really emit (ISSUE-37)
- Re: What namespace features popular SVG tools really emit (ISSUE-37)
- Re: What namespace features popular SVG tools really emit (ISSUE-37)
- Re: HTML5 object element - classid or not classid?
- Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- What namespace features popular SVG tools really emit (ISSUE-37)
- Re: HTML5 object element - classid or not classid?
- HTML5 object element - classid or not classid?
- Comments on the recent changes to the alt attribute section
- Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Translation control in HTML5
- Re: Translation control in HTML5
- Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
Sunday, 3 August 2008
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Translation control in HTML5
- Re: Translation control in HTML5
- Re: Translation control in HTML5
- Re: Translation control in HTML5
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Translation control in HTML5
- RE: Pseudo-namespaces
Saturday, 2 August 2008
- Re: Translation control in HTML5
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Translation control in HTML5
- Re: Translation control in HTML5
- Re: Pseudo-namespaces
- Pseudo-namespaces (was: RE: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal))
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- RE: Extensibility strategies
- RE: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- RE: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- RE: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- RE: Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
Friday, 1 August 2008
- Re: Image intrinsic aspect ratio and replaced element box aspect ratio
- Re: Translation control in HTML5
- Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- RE: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Translation control in HTML5
- Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- RE: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Extensibility strategies, was: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- RE: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- FW: Content Transformation Guidelines: Last Call Working Draft
- Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Image intrinsic aspect ratio and replaced element box aspect ratio
- Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Translation control in HTML5
- Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Translation control in HTML5
- Re: Translation control in HTML5
- Re: Translation control in HTML5
- Re: Translation control in HTML5
- Re: Translation control in HTML5
- Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Translation control in HTML5
- Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Translation control in HTML5
- Re: Translation control in HTML5
- Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal)
- Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal)