[Bug 5823] New: Scope allowable on a td
[Bug 5822] New: The headers attribute should be able to reference a td
Five things that are still broken in browsers, ten years later
[Bug 5821] New: meta/@scheme missing
Re: Dangers of non-UTF-8 Re: Details on internal encoding declarations
[Bug 5820] New: Work on WebSockets
Spaces in URLs
Re: Whitespace in attribute values
Re: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM
- RE: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM
- Re: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM
- Re: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM
- RE: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM
- Re: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM
- Re: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM
- Re: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM
- Re: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM
- Re: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM
- Re: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM
- Re: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM
- Re: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM
- encoding of characters in query parameters, was: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM
- RE: encoding of characters in query parameters, was: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM
- Re: encoding of characters in query parameters, was: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM
- Re: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM
- Re: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM
- Re: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM
- Re: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM
- Re: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM
- Re: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM
- URIs in HTML5 and issues arising
- Re: URIs in HTML5 and issues arising
- Re: URIs in HTML5 and issues arising
- Re: URIs in HTML5 and issues arising
- Re: URIs in HTML5 and issues arising
- Re: URIs in HTML5 and issues arising
- Re: URIs in HTML5 and issues arising
- Re: URIs in HTML5 and issues arising
- Re: URIs in HTML5 and issues arising
- Re: URIs in HTML5 and issues arising
- Re: URIs in HTML5 and issues arising
- Re: URIs in HTML5 and issues arising
- Re: URIs in HTML5 and issues arising
- Re: URIs in HTML5 and issues arising
- Re: URIs in HTML5 and issues arising
- Re: URIs in HTML5 and issues arising
- URIs in HTML5 and issues arising
Re: Spec review: "URI (or IRI)"
[Bug 5815] New: foreignObject in the SVG namespace should be scoping
heads-up about "new" URLs section in HTML5 editor's draft
- Re: heads-up about "new" URLs section in HTML5 editor's draft
- Re: heads-up about "new" URLs section in HTML5 editor's draft
- Re: heads-up about "new" URLs section in HTML5 editor's draft
- Re: heads-up about "new" URLs section in HTML5 editor's draft
- Re: heads-up about "new" URLs section in HTML5 editor's draft
[Bug 5814] New: Resolve the callback issue
expected results for URI encoding tests?
- Re: expected results for URI encoding tests?
- adohoc URI test results for IE7, Re: expected results for URI encoding tests?
- Re: expected results for URI encoding tests?
@headers on th too or just td?
- Re: @headers on th too or just td?
- Re: @headers on th too or just td?
- Re: @headers on th too or just td?
- Re: @headers on th too or just td?
Strict version description is wrong
Request for PFWG WAI review of @summary for tabular data
[Bug 5809] New: Mitigate data loss when conforming documents are coerced to XML 1.0
[Bug 5808] New: Define a way to coerce HTML5 parser output to an XML 1.0 4th ed. + Namespaces 1.0 infoset
asking for UA developer's feedback on Content-Disposition filename I18N issue
ISSUE-55 (head-profile): head/@profile missing, but used in other specifications/formats
[Bug 5807] New: User Agent display of title attribute content not defined
- [Bug 5807] User Agent display of title attribute content not defined
- [Bug 5807] User Agent display of title attribute content not defined
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]
[Bug 5803] New: HTML5 serialization is not compatible with XSLT
[Bug 5802] New: No mention of %uXXXX escapes
[Bug 5801] New: Conformance rules for xmlns unintuitively different for HTML and foreign content
ProgressEvent and unreachable networkState LOADED in HTMLMediaElement
Proposed Final Review of W3C TAG Finding "Passwords in the Clear"
[Bug 5798] New: Deferring end tag eating to after head gives weird errors
[Bug 5796] New: <li><div><p><li> no longer matches IE
Canvas miscellaneous comments
[Bug 5793] New: Editorial: "Act as if" hard to follow
[Bug 5792] New: li/dd/dt end tag in body when no corresponding elt on stack
Re: In body other end tag handling convoluted to get at most one error
URI parsing
The header element's textual content
[Bug 5787] New: Rename "script that will execute as soon as the parser resumes"
Re: SVG in HTML5 draft proposal
ISSUE-53 (mediatypereg): Need to update media type registrations [HTML 5 spec]
Percent-encoded fragment identfiers and id matching - (was: Fragment Identifiers for HTML5)
Empty attribute syntax and the DOM and CSS
Fragment Identifiers for HTML5
Missing src on img/audio/video and fallback content
[Bug 5777] New: referencing subordinate text or asides should be through an alternate attribute
[Bug 5776] New: Authors need more control over handling of linked resources
Re: Canvas path transformations
Trying out SVG and MathML parsing
[Bug 5773] New: Authors need more control over handling of linked resources
[Bug 5772] New: ID value types too restrictive and inflexible for some use cases
RE: DOM Storage feedback
[Bug 5769] New: HTMLMediaElement.currentLoop readonly?
<scene>
[Bug 5768] New: content sniffing should be allowed on link elements with a relationship type of icon
favicon content-type sniffing
Re: Outline algorithm
[Bug 5766] New: priority request: reply to outline e-mail
Re-entrant invocation of the tree builder
HTML WG f2f at October W3C TPAC: Registration open
What about backward compatibility?
drastic reduction of HTML WG issue tracker contributors: explanation please?
- Re: drastic reduction of HTML WG issue tracker contributors: explanation please?
- Re: drastic reduction of HTML WG issue tracker contributors: explanation please?
bugzilla fyi - gmail marks new account confirmation as spam
[Bug 5759] New: Newly introduced void elements are not mentioned in "Writing HTML Documents" section
[Bug 5758] New: insufficient accessibility fallback for <audio> or <video>
[Bug 5757] New: MediaElement features are needed on OBJECT element
[Bug 5756] New: Need UA norms for exposing (non-displayed) HTML document data
[Bug 5755] New: Need to expose media metadata properties
[Bug 5754] New: List elements content model issues
responding to bugzilla: Do's and Don'ts
notification of new bugzilla issues Cc'ed here
[Bug 5753] New: parsing issues with legacy UAs
[Bug 5752] New: Parsing should be specified for future updates
[Bug 5751] New: IGNORE ME (sorry for noise...)
Why public-html-bugzilla@w3.org? Why bugzilla?
new list: public-html-bugzilla@w3.org
[Fwd: [Bug 5744] Improved Fragment Identifiers]
[Fwd: [Bug 5744] Improved Fragment Identifiers]
Clarification on chairing for the group
[Fwd: [Bug 5744] Improved Fragment Identifiers]
[Bug 5744] Improved Fragment Identifiers
[CfP] process proposal for a special meeting or meetings for fact-finding on issues related to @alt in HTML5
Unsupported transport-layer encodings
dataset case issue
isContentEditable is a boolean
Re: Canvas line style comments
Re: Canvas gradient comments
changes in HTML5 draft regarding XHTML1
Re: several messages about radial gradients
Re: Canvas ImageData comments
Re: Canvas arc comments
Re: Canvas security comments
Re: Canvas shadows should not be optional
Re: [canvas] 2d context fillRect() negative values for width/height
[author-guide] Describing the Syntax
ARIA and CURIE "clarification"
Failing To Understand The Creating An Outline Section
HTML WG co-chair, issues process
Adjusting MathML attributes: definitionURL
mechanism to provide a summary of high density information easily discernible from a cursory visual glance
Completed logging of issues with HTML5 draft
Questions on HTML 5 differences from HTML 4
Race conditions in HTML 5?
How to add features to HTML5 (Was: tracker already has ternary state - RAISED)
Space characters in map name
Events and disabled form controls
Re: X(HT)ML Fragment Identifiers
Questions on <datatemplate> (ref. call for exclusions)
improved HTML fragment identifiers
- Re: improved HTML fragment identifiers
- Re: improved HTML fragment identifiers
- Re: improved HTML fragment identifiers
beforeprint / afterprint
Re: Placement of <base> & xml:base interaction
Other aria representations [was: Re: ARIA as stop-gap]
a @name [was: ISSUE-47, Markup support for bookmark and clipping support of documents]
<canvas> JPEG quality
- Re: <canvas> JPEG quality
- Re: <canvas> JPEG quality
- Re: <canvas> JPEG quality
- Re: <canvas> JPEG quality
Is now a good time to start writing validator test cases systematically?
Re: Text presentation of image maps with <object> (detailed review of Semantics)
We will have a telecon this week [was: No teleconference next week]
Re: ARIA as stop-gap (was Re: Next steps for the ARIA syntax discussion)
- RE: ARIA as stop-gap (was Re: Next steps for the ARIA syntax discussion)
- Re: ARIA as stop-gap (was Re: Next steps for the ARIA syntax discussion)
namespace-well-formedness and setting innerHTML in XML
Prefixes and setting innerHTML in XML
DOM-level conformance discrepancies between HTML5 and XHTML5
Proposal: ARIA-ROLE & CSS definition integration
- Re: Proposal: ARIA-ROLE & CSS definition integration
- Re: Proposal: ARIA-ROLE & CSS definition integration
Proposal: Default style definitions for elements
- Re: Proposal: Default style definitions for elements
- Re: Proposal: Default style definitions for elements
Handling of undefined in createPattern()
Re: section 3.5.3 scrollIntoView
Re: 3.5.2. Focus
Spec review results I
Re: List Of Numbers Produces Incorrect Output (part of detailed review of common microsyntaxes)
Common validation problems since last similar report
Re: No teleconference next week
TAG concensus reached on ARIA implementation.
Re: ISSUE-47, Markup support for bookmark and clipping support of documents
Re: ISSUE-48 (marks-content-markup-attribute): 'marks' content markup attribute for Q (quotation) and BLOCKQUOTE [HTML 5 spec]
- Re: ISSUE-48 (marks-content-markup-attribute): 'marks' content markup attribute for Q (quotation) and BLOCKQUOTE [HTML 5 spec]
Is EBCDIC support needed for not breaking the Web?
- Re: [whatwg] Is EBCDIC support needed for not breaking the Web?
RE: Liaison with CSS WG to provide a mechanism for expressing the style of document semantics
- Re: Liaison with CSS WG to provide a mechanism for expressing the style of document semantics
- RE: Liaison with CSS WG to provide a mechanism for expressing the style of document semantics
- Re: Liaison with CSS WG to provide a mechanism for expressing the style of document semantics
- RE: Liaison with CSS WG to provide a mechanism for expressing the style of document semantics
- Re: Liaison with CSS WG to provide a mechanism for expressing the style of document semantics
- RE: Liaison with CSS WG to provide a mechanism for expressing the style of document semantics
- Re: Liaison with CSS WG to provide a mechanism for expressing the style of document semantics
- RE: Liaison with CSS WG to provide a mechanism for expressing the style of document semantics
- Re: Liaison with CSS WG to provide a mechanism for expressing the style of document semantics
- RE: Liaison with CSS WG to provide a mechanism for expressing the style of document semantics
- Re: Liaison with CSS WG to provide a mechanism for expressing the style of document semantics
- RE: Liaison with CSS WG to provide a mechanism for expressing the style of document semantics
- Re: Liaison with CSS WG to provide a mechanism for expressing the style of document semantics
- RE: Liaison with CSS WG to provide a mechanism for expressing the style of document semantics
When can a node's prefix or localName contain a colon?
- Re: When can a node's prefix or localName contain a colon?
- Re: When can a node's prefix or localName contain a colon?
RE: UA norm for redirects (both META and http)
- RE: UA norm for redirects (both META and http)