public-html@w3.org from April 2010 by date

Friday, 30 April 2010

• Re: CfC: Close ISSUE-82 profile-disambiguation by amicable resolution Jonas Sicking
• Re: CfC: Close ISSUE-82 profile-disambiguation by amicable resolution Maciej Stachowiak
• Re: CfC: Close ISSUE-82 profile-disambiguation by amicable resolution Ian Hickson
• Re: ISSUES 90, 91, 93, 96, 97 -- if you DON'T support these change proposals, support zero-change instead Lachlan Hunt
• Re: Transition to HTML5 Sam Ruby
• Re: Transition to HTML5 Tab Atkins Jr.
• Re: Transition to HTML5 Jasper Magick
• Re: Gloss standard terminology for resource/representation (ISSUE-81 Change Proposal) Maciej Stachowiak
• Re: Updated ISSUES 90, 91, 93, 96, 97 Change proposal Maciej Stachowiak
• Re: Updated ISSUES 90, 91, 93, 96, 97 Change proposal Jonas Sicking
• Re: Updated ISSUES 90, 91, 93, 96, 97 Change proposal Maciej Stachowiak
• Re: Updated ISSUES 90, 91, 93, 96, 97 Change proposal Jonas Sicking
• Updated ISSUES 90, 91, 93, 96, 97 Change proposal Jonas Sicking
• RE: ISSUE 88 - Change proposal (new update) CE Whitehead
• Re: Transition to HTML5 Jonas Sicking
• Re: Transition to HTML5 Tab Atkins Jr.
• Re: ISSUE-66 image-analysis: informal consensus check Steve Axthelm
• Transition to HTML5 Jasper Magick
• Re: ISSUE-66 image-analysis: informal consensus check Maciej Stachowiak
• Re: ISSUES 90, 91, 93, 96, 97 -- if you DON'T support these change proposals, support zero-change instead Sam Ruby
• Re: ISSUES 90, 91, 93, 96, 97 -- if you DON'T support these change proposals, support zero-change instead Shelley Powers
• Re: ISSUES 90, 91, 93, 96, 97 -- if you support these change proposals Tab Atkins Jr.
• Re: ISSUES 90, 91, 93, 96, 97 -- if you DON'T support these change proposals, support zero-change instead Tab Atkins Jr.
• Re: ISSUES 90, 91, 93, 96, 97 -- if you support these change proposals Laura Carlson
• Re: ISSUES 90, 91, 93, 96, 97 -- if you DON'T support these change proposals, support zero-change instead Shelley Powers
• Re: ISSUES 90, 91, 93, 96, 97 -- if you DON'T support these change proposals, support zero-change instead Tab Atkins Jr.
• RE: ISSUE-66 image-analysis: informal consensus check John Foliot
• Re: ISSUE-66 image-analysis: informal consensus check Shelley Powers
• Re: ISSUES 90, 91, 93, 96, 97 -- if you DON'T support these change proposals, support zero-change instead Shelley Powers
• Re: ISSUES 90, 91, 93, 96, 97 -- if you support these change proposals Tab Atkins Jr.
• Re: ISSUE-66 image-analysis: informal consensus check Julian Reschke
• Re: ISSUES 90, 91, 93, 96, 97 -- if you DON'T support these change proposals, support zero-change instead Shelley Powers
• Re: ISSUES 90, 91, 93, 96, 97 -- if you DON'T support these change proposals, support zero-change instead Bruce Lawson
• Re: ISSUE-66 image-analysis: informal consensus check Tab Atkins Jr.
• Re: Gloss standard terminology for resource/representation (ISSUE-81 Change Proposal) Julian Reschke
• Re: ISSUES 90, 91, 93, 96, 97 -- if you DON'T support these change proposals, support zero-change instead Sam Ruby
• Re: ISSUES 90, 91, 93, 96, 97 -- if you DON'T support these change proposals, support zero-change instead Shelley Powers
• Re: ISSUE-66 image-analysis: informal consensus check Sam Ruby
• Re: ISSUES 90, 91, 93, 96, 97 -- if you support these change proposals Laura Carlson
• Re: ISSUE-66 image-analysis: informal consensus check James Graham
• RE: ISSUE-66 image-analysis: informal consensus check John Foliot
• Re: ISSUE-66 image-analysis: informal consensus check Anne van Kesteren
• RE: ISSUE-88 content-language: informal consensus check Leif Halvard Silli
• Re: ISSUES 90, 91, 93, 96, 97 -- if you support these change proposals Edward O'Connor
• Re: ISSUE 88 - Change proposal (new update) Leif Halvard Silli
• Re: ISSUES 90, 91, 93, 96, 97 -- if you support these change proposals Shelley Powers
• Re: ISSUES 90, 91, 93, 96, 97 -- if you support these change proposals Laura Carlson
• Re: ISSUES 90, 91, 93, 96, 97 -- if you support these change proposals Tab Atkins Jr.

Thursday, 29 April 2010

• RE: ISSUE-88 content-language: informal consensus check Leif Halvard Silli
• Re: ISSUES 90, 91, 93, 96, 97 -- if you support these change proposals Shelley Powers
• Re: ISSUES 90, 91, 93, 96, 97 -- if you support these change proposals Shelley Powers
• Re: ISSUES 90, 91, 93, 96, 97 -- if you support these change proposals Jonas Sicking
• Re: ISSUES 90, 91, 93, 96, 97 -- if you support these change proposals Jonas Sicking
• Re: ISSUES 90, 91, 93, 96, 97 -- if you support these change proposals Maciej Stachowiak
• Re: ISSUES 90, 91, 93, 96, 97 -- if you support these change proposals Laura Carlson
• Re: ISSUES 90, 91, 93, 96, 97 -- if you support these change proposals Maciej Stachowiak
• Re: ISSUES 90, 91, 93, 96, 97 -- if you support these change proposals Laura Carlson
• Re: ISSUES 90, 91, 93, 96, 97 -- if you support these change proposals Jonas Sicking
• Re: ISSUES 90, 91, 93, 96, 97 -- if you support these change proposals Laura Carlson
• Test Message--Please Ignore Janina Sajka
• ISSUES 90, 91, 93, 96, 97 -- if you support these change proposals Shelley Powers
• Someone else will need to do change proposal for Issue 106 Shelley Powers
• Re: ISSUE-112 (meta-keywords-not): Chairs Solicit Proposals Maciej Stachowiak
• RE: HTML WG F2F meeting, Nov 4-5 at TPAC 2010, Lyon, France Paul Cotton
• Re: ISSUE-112 (meta-keywords-not): Chairs Solicit Proposals Julian Reschke
• Re: ISSUE-66 image-analysis: informal consensus check Tab Atkins Jr.
• RE: ISSUE-88 content-language: informal consensus check Richard Ishida
• Re: <!DOCTYPE html> vs (polyglot) spec Henri Sivonen
• ISSUE-27, was: I-D Action:draft-nottingham-http-link-header-09.txt Julian Reschke
• Re: ISSUE-88 content-language: informal consensus check Leif Halvard Silli
• Re: URL parsing Julian Reschke
• Re: ISSUE-109 (aria-section-title): Chairs Solicit Proposals Steven Faulkner
• Re: ISSUE-66 image-analysis: informal consensus check Joshue O Connor
• Re: Gloss standard terminology for resource/representation (ISSUE-81 Change Proposal) Julian Reschke
• Re: ISSUE-66 image-analysis: informal consensus check Steven Faulkner
• Re: Gloss standard terminology for resource/representation (ISSUE-81 Change Proposal) Maciej Stachowiak
• Re: CfC: Close ISSUE-82 profile-disambiguation by amicable resolution Maciej Stachowiak
• Re: CfC: Close ISSUE-82 profile-disambiguation by amicable resolution Jonas Sicking
• Re: ISSUE-66 image-analysis: informal consensus check Charles McCathieNevile
• Re: Proposal to make Content-Language pragma non-conforming altogether for ISSUE-88 (mark I) Julian Reschke
• Re: CfC: Close ISSUE-82 profile-disambiguation by amicable resolution Julian Reschke
• Re: Gloss standard terminology for resource/representation (ISSUE-81 Change Proposal) Julian Reschke
• Re: Proposal to make Content-Language pragma non-conforming altogether for ISSUE-88 (mark I) Julian Reschke
• Re: Proposal to make Content-Language pragma non-conforming altogether for ISSUE-88 (mark I) Anne van Kesteren
• RE: Proposal to make Content-Language pragma non-conforming altogether for ISSUE-88 (mark I) Richard Ishida
• Re: CfC: Close ISSUE-82 profile-disambiguation by amicable resolution Maciej Stachowiak
• Re: Proposal to make Content-Language pragma non-conforming altogether for ISSUE-88 (mark I) Julian Reschke
• Re: Gloss standard terminology for resource/representation (ISSUE-81 Change Proposal) Maciej Stachowiak
• Re: Proposal to make Content-Language pragma non-conforming altogether for ISSUE-88 (mark I) Maciej Stachowiak
• Re: ISSUE-66 image-analysis: informal consensus check Julian Reschke
• Re: Gloss standard terminology for resource/representation (ISSUE-81 Change Proposal) Julian Reschke
• Re: CfC: Close ISSUE-82 profile-disambiguation by amicable resolution Julian Reschke
• Re: ISSUE-114 (rel-canonical-organization): Chairs Solicit Proposals Maciej Stachowiak
• Re: Proposal to make Content-Language pragma non-conforming altogether for ISSUE-88 (mark I) Julian Reschke
• Re: ISSUE-114 (rel-canonical-organization): Chairs Solicit Proposals Toby Inkster
• Re: ISSUE-109 (aria-section-title): Chairs Solicit Proposals Steven Faulkner
• ISSUE-66 image-analysis: informal consensus check Maciej Stachowiak
• Re: Change definition of URL to normatively reference IRI specification using a well-defined interface Maciej Stachowiak
• Re: ISSUE 86 and removing atom transform section - focusing Maciej Stachowiak
• Re: CfC: Close ISSUE-82 profile-disambiguation by amicable resolution Maciej Stachowiak
• Re: ISSUE-95 removing hidden proposal edited Maciej Stachowiak
• Re: ISSUE-93 edited Maciej Stachowiak
• Re: CfC: Close ISSUE-81 representation-vs-resource without prejudice Maciej Stachowiak
• Re: CORRECTION ISSUE-78 (urls-terminology): Chairs Solicit Proposals Maciej Stachowiak
• ISSUE-88 content-language: informal consensus check Maciej Stachowiak
• ISSUE-115 (rel-canonical-human): Chairs Solicit Proposals Maciej Stachowiak
• ISSUE-114 (rel-canonical-organization): Chairs Solicit Proposals Maciej Stachowiak
• ISSUE-113 (forced-fragment): Chairs Solicit Proposals Maciej Stachowiak
• ISSUE-112 (meta-keywords-not): Chairs Solicit Proposals Maciej Stachowiak
• ISSUE-111 (checkbox-required): Chairs Solicit Proposals Maciej Stachowiak
• ISSUE-109 (aria-section-title): Chairs Solicit Proposals Maciej Stachowiak

Wednesday, 28 April 2010

• Re: ISSUE-107 Change Proposal: Replace <object> fallback example Maciej Stachowiak
• Re: Proposal to make Content-Language pragma non-conforming altogether for ISSUE-88 (mark I) Phillips, Addison
• [Bug 7918] prefetching: allow site to deny bugzilla@jessica.w3.org
• Re: URL parsing Jonas Sicking
• RE: URL parsing Larry Masinter
• Re: URL parsing Adam Barth
• Re: URL parsing Julian Reschke
• Re: URL parsing Adam Barth
• Re: URL parsing Julian Reschke

Tuesday, 27 April 2010

• Re: <!DOCTYPE html> vs (polyglot) spec Leif Halvard Silli
• ISSUE-95 removing hidden proposal edited Shelley Powers
• Re: <!DOCTYPE html> vs (polyglot) spec Henri Sivonen

Monday, 26 April 2010

• Re: <!DOCTYPE html> vs (polyglot) spec Leif Halvard Silli
• Re: ISSUE-41: Facebook open graph protocol Manu Sporny
• Re: <!DOCTYPE html> vs (polyglot) spec Maciej Stachowiak
• Minutes of HTML WG meeting, Apr 22 2010 Paul Cotton
• <!DOCTYPE html> vs (polyglot) spec Leif Halvard Silli
• ISSUE-93 edited Shelley Powers

Sunday, 25 April 2010

• [Bug 9589] HTML5 should give examples for how to present @title when the user can't use a pointing device bugzilla@jessica.w3.org

Saturday, 24 April 2010

• Re: Request for Volunteers: Polyglot spec Leif Halvard Silli
• Re: ISSUE-41: Facebook open graph protocol Leif Halvard Silli
• Re: Request for Volunteers: Polyglot spec Leif Halvard Silli
• Re: Request for Volunteers: Polyglot spec Leif Halvard Silli

Friday, 23 April 2010

• Re: hidden meta data and bolt on attributes David Singer
• RE: ISSUE-41: Facebook open graph protocol Ennals, Robert
• Re: Timed tracks Boris Zbarsky
• Re: TAG ACTION-407 -- text/html media type and legacy Leif Halvard Silli
• RE: charset attribute on a, link and script elements Richard Ishida
• RE: Timed tracks Sean Hayes
• Re: ISSUE-107 Change Proposal: Replace <object> fallback example Julian Reschke
• RE: ISSUE-107 Change Proposal: Replace <object> fallback example Leonard Rosenthol
• Re: charset attribute on a, link and script elements Martin J. Dürst
• Re: Timed tracks Robert O'Callahan
• Re: ISSUE-107 Change Proposal: Replace <object> fallback example Julian Reschke
• RE: Timed tracks Sean Hayes
• Re: Timed tracks Maciej Stachowiak
• Re: Timed tracks Philip Jägenstedt
• RE: Timed tracks John Foliot
• Re: Timed tracks Maciej Stachowiak
• Re: Timed tracks Tab Atkins Jr.
• RE: Timed tracks John Foliot
• Re: Timed tracks Robert O'Callahan
• Re: Timed tracks Boris Zbarsky
• RE: Timed tracks John Foliot
• Re: ISSUE-107 Change Proposal: Replace <object> fallback example Joe D Williams
• Re: Timed tracks Robert O'Callahan
• Re: hidden meta data and bolt on attributes Robert O'Callahan
• Re: Request for Volunteers: Polyglot spec Sam Ruby
• RE: Request for Volunteers: Polyglot spec Leif Halvard Silli
• Re: hidden meta data and bolt on attributes Shelley Powers
• Re: ISSUE-107 Change Proposal: Replace <object> fallback example Ian Hickson
• Re: ISSUE-41: Facebook open graph protocol Maciej Stachowiak
• Re: ISSUE-41: Facebook open graph protocol Maciej Stachowiak
• Re: ISSUE-107 Change Proposal: Replace <object> fallback example Maciej Stachowiak
• Re: hidden meta data and bolt on attributes Robert O'Callahan

Thursday, 22 April 2010

• RE: ISSUE-41: Facebook open graph protocol Leif Halvard Silli
• Re: ISSUE-41: Facebook open graph protocol Sam Ruby
• Re: ISSUE-107 Change Proposal: Replace <object> fallback example Julian Reschke
• Re: ISSUE-41: Facebook open graph protocol Steven Roussey
• RE: Request for Volunteers: Polyglot spec Tony Ross
• Re: ISSUE-107 Change Proposal: Replace <object> fallback example Ian Hickson
• URL parsing Adam Barth
• Re: Final thoughts (Was RE: General Response to the Accessibility Task force on Issues 90, 91, 93, 96, 97) Sam Ruby
• Final thoughts (Was RE: General Response to the Accessibility Task force on Issues 90, 91, 93, 96, 97) John Foliot
• Re: ISSUE-41: Facebook open graph protocol Steven Roussey
• Re: ISSUE-41: Facebook open graph protocol Sam Ruby
• Re: General Response to the Accessibility Task force on Issues 90, 91, 93, 96, 97 Laura Carlson
• Re: ISSUE-41: Facebook open graph protocol Sam Ruby
• Re: ISSUE-41: Facebook open graph protocol Steven Roussey
• Re: General Response to the Accessibility Task force on Issues 90, 91, 93, 96, 97 Laura Carlson
• Re: ISSUE-41: Facebook open graph protocol Sam Ruby
• Re: ISSUE-41: Facebook open graph protocol Leif Halvard Silli
• Re: Zero-edit Change Proposal for ISSUE-90 figure, ISSUE-91 aside, ISSUE-93 details, ISSUE-95 hidden, ISSUE-96 progress, and ISSUE-97 meter Shelley Powers
• RE: Zero-edit Change Proposal for ISSUE-90 figure, ISSUE-91 aside, ISSUE-93 details, ISSUE-95 hidden, ISSUE-96 progress, and ISSUE-97 meter John Foliot
• Re: hidden meta data and bolt on attributes Shelley Powers
• RE: hidden meta data and bolt on attributes Leonard Rosenthol
• Re: General Response to the Accessibility Task force%2 Shelley Powers
• Re: ISSUE-41: Facebook open graph protocol Maciej Stachowiak
• Re: General Response to the Accessibility Task force%2 Shelley Powers
• ISSUE-41: Facebook open graph protocol Philippe Le Hegaret
• Re: Zero-edit Change Proposal for ISSUE-90 figure, ISSUE-91 aside, ISSUE-93 details, ISSUE-95 hidden, ISSUE-96 progress, and ISSUE-97 meter Tab Atkins Jr.
• Re: General Response to the Accessibility Task force%2 Janina Sajka
• Re: TAG ACTION-407 -- text/html media type and legacy Dan Connolly
• Re: General Response to the Accessibility Task force%2 Joshue O Connor
• Re: Zero-edit Change Proposal for ISSUE-90 figure, ISSUE-91 aside, ISSUE-93 details, ISSUE-95 hidden, ISSUE-96 progress, and ISSUE-97 meter Shelley Powers
• Re: Timed tracks Ian Hickson
• Re: TAG ACTION-407 -- text/html media type and legacy Leif Halvard Silli
• Re: Zero-edit Change Proposal for ISSUE-90 figure, ISSUE-91 aside, ISSUE-93 details, ISSUE-95 hidden, ISSUE-96 progress, and ISSUE-97 meter Maciej Stachowiak
• Re: General Response to the Accessibility Task force%2 Shelley Powers
• Re: TAG ACTION-407 -- text/html media type and legacy Maciej Stachowiak
• Re: Timed tracks Jonas Sicking
• Re: TAG ACTION-407 -- text/html media type and legacy Henry S. Thompson
• Re: Zero-edit Change Proposal for ISSUE-90 figure, ISSUE-91 aside, ISSUE-93 details, ISSUE-95 hidden, ISSUE-96 progress, and ISSUE-97 meter Jonas Sicking
• Re: General Response to the Accessibility Task force%2 janina@rednote.net
• Re: Timed tracks Geoff Freed
• Re: TAG ACTION-407 -- text/html media type and legacy Maciej Stachowiak
• RE: Timed tracks Sean Hayes
• Re: TAG ACTION-407 -- text/html media type and legacy Dan Connolly
• hidden meta data and bolt on attributes Shelley Powers
• Re: Zero-edit Change Proposal for ISSUE-90 figure, ISSUE-91 aside, ISSUE-93 details, ISSUE-95 hidden, ISSUE-96 progress, and ISSUE-97 meter Shelley Powers
• Re: Zero-edit Change Proposal for ISSUE-90 figure, ISSUE-91 aside, ISSUE-93 details, ISSUE-95 hidden, ISSUE-96 progress, and ISSUE-97 meter Maciej Stachowiak
• Re: ISSUE-107 Change Proposal: Replace <object> fallback example Maciej Stachowiak
• General Response to the Accessibility Task force on Issues 90, 91, 93, 96, 97 Shelley Powers
• Re: Timed tracks Philippe Le Hegaret
• Re: Zero-edit Change Proposal for ISSUE-90 figure, ISSUE-91 aside, ISSUE-93 details, ISSUE-95 hidden, ISSUE-96 progress, and ISSUE-97 meter Shelley Powers
• Re: ISSUE-107 Change Proposal: Replace <object> fallback example Julian Reschke
• ISSUE-107 Change Proposal: Replace <object> fallback example Lachlan Hunt
• Re: Zero-edit Change Proposal for ISSUE-90 figure, ISSUE-91 aside, ISSUE-93 details, ISSUE-95 hidden, ISSUE-96 progress, and ISSUE-97 meter Shelley Powers
• charset attribute on a, link and script elements Richard Ishida
• Re: Request for Volunteers: Polyglot spec Lachlan Hunt
• Timed tracks Ian Hickson
• Re: Request for Volunteers: Polyglot spec Leif Halvard Silli
• Re: Zero-edit Change Proposal for ISSUE-90 figure, ISSUE-91 aside, ISSUE-93 details, ISSUE-95 hidden, ISSUE-96 progress, and ISSUE-97 meter Maciej Stachowiak
• Re: Zero-edit Change Proposal for ISSUE-90 figure, ISSUE-91 aside, ISSUE-93 details, ISSUE-95 hidden, ISSUE-96 progress, and ISSUE-97 meter Maciej Stachowiak
• Re: Zero-edit Change Proposal for ISSUE-90 figure, ISSUE-91 aside, ISSUE-93 details, ISSUE-95 hidden, ISSUE-96 progress, and ISSUE-97 meter Shelley Powers
• Zero-edit Change Proposal for ISSUE-90 figure, ISSUE-91 aside, ISSUE-93 details, ISSUE-95 hidden, ISSUE-96 progress, and ISSUE-97 meter Edward O'Connor
• Re: ISSUE-92 cleanuptable - Chairs Solicit Alternate Proposals or Counter-Proposals Maciej Stachowiak
• Change Proposal - 4.2.2 The title element / 4.2.5.1 Standard metadata names CE Whitehead

Wednesday, 21 April 2010

• Re: Request for Volunteers: Polyglot spec Sam Ruby
• CfC: Close ISSUE-81 representation-vs-resource without prejudice Maciej Stachowiak
• Re: ISSUE-107 Change Proposal Maciej Stachowiak
• Re: Change definition of URL to normatively reference IRI specification using a well-defined interface Ted Hardie
• RE: Request for Volunteers: Polyglot spec Eliot Graff
• {agenda} HTML WG telcon 2010-04-22: Action items, issues, decision policy, A11Y recommendations, polyglot spec Paul Cotton
• Fwd: HTML-A11Y Task Force Recommendation: ISSUE-30, longdesc Sam Ruby
• Fwd: HTML-A11Y Task Force Recommendation: ISSUE-80 Title Sam Ruby
• Fwd: HTML-A11Y Task Force Recommendation: ISSUE-66 image-analysis Sam Ruby
• Fwd: HTML-A11Y Task Force Recommendation: ISSUES-90, 91, 93, 95, 96, & 97 Sam Ruby
• Re: ISSUE-92 cleanuptable - Chairs Solicit Alternate Proposals or Counter-Proposals Shelley Powers
• Re: ISSUE-92 cleanuptable - Chairs Solicit Alternate Proposals or Counter-Proposals Tab Atkins Jr.
• Re: ISSUE-92 cleanuptable - Chairs Solicit Alternate Proposals or Counter-Proposals Shelley Powers
• Re: ISSUE-107 Change Proposal Lachlan Hunt
• Re: TAG ACTION-407 -- text/html media type and legacy Julian Reschke
• Re: CfC: Close ISSUE-82 profile-disambiguation by amicable resolution Maciej Stachowiak
• Re: CfC: Close ISSUE-82 profile-disambiguation by amicable resolution Anne van Kesteren
• Re: CfC: Close ISSUE-82 profile-disambiguation by amicable resolution Julian Reschke
• Re: CfC: Close ISSUE-82 profile-disambiguation by amicable resolution Maciej Stachowiak
• Re: CfC: Close ISSUE-82 profile-disambiguation by amicable resolution Julian Reschke
• Re: CfC: Close ISSUE-82 profile-disambiguation by amicable resolution Anne van Kesteren
• Re: CfC: Close ISSUE-82 profile-disambiguation by amicable resolution Julian Reschke
• Re: ISSUE-107 plugin-fallback-example - Chairs Solicit Alternate Proposals or Counter-Proposals Joe D Williams
• ISSUE-107 plugin-fallback-example - Chairs Solicit Alternate Proposals or Counter-Proposals Maciej Stachowiak
• ISSUE-103 srcdoc-xml-escaping - Chairs Solicit Alternate Proposals or Counter-Proposals Maciej Stachowiak
• ISSUE-92 cleanuptable - Chairs Solicit Alternate Proposals or Counter-Proposals Maciej Stachowiak
• ISSUE-89 idioms - Chairs Solicit Alternate Proposals or Counter-Proposals Maciej Stachowiak
• CfC: Close ISSUE-82 profile-disambiguation by amicable resolution Maciej Stachowiak
• ISSUE-82 Change Proposal mislabeled (was Re: Status page should be up to date) Maciej Stachowiak
• ISSUE-32 table-summary (was Re: Status page should be up to date) Maciej Stachowiak
• Re: Now sure how to respond to the ally TF response Shelley Powers
• Re: Now sure how to respond to the ally TF response Maciej Stachowiak

Tuesday, 20 April 2010

• Now sure how to respond to the ally TF response Shelley Powers
• Re: TAG ACTION-407 -- text/html media type and legacy Leif Halvard Silli
• [public-html] <none> Eduard Pascual
• Re: TAG ACTION-407 -- text/html media type and legacy Ian Hickson
• Re: Status page should be up to date Ian Hickson
• Re: I-D Action:draft-nottingham-http-link-header-09.txt Julian Reschke
• RE: I-D Action:draft-nottingham-http-link-header-09.txt Paul Cotton
• Re: Status page should be up to date Laura Carlson
• Re: Status page should be up to date Maciej Stachowiak
• Re: Change Proposals toward Issue-9: "how accessibility works for <video> is unclear" Silvia Pfeiffer
• Re: Status page should be up to date Laura Carlson
• Re: TAG ACTION-407 -- text/html media type and legacy Henry S. Thompson
• Status page should be up to date Maciej Stachowiak
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Maciej Stachowiak
• Re: Change Proposal for Issue 110 ("Change Control for text/html-sandboxed media type") Maciej Stachowiak
• Re: ISSUE-107 Change Proposal Maciej Stachowiak
• Re: Change Proposal for ISSUE-82 (Profile-Disambiguation), was: ISSUE-82 - profile-disambiguation - Chairs Solicit Proposals Maciej Stachowiak

Monday, 19 April 2010

• Re: Change Proposal for ISSUE-82 (Profile-Disambiguation), was: ISSUE-82 - profile-disambiguation - Chairs Solicit Proposals Jonas Sicking
• Re: Change Proposal for ISSUE-82 (Profile-Disambiguation), was: ISSUE-82 - profile-disambiguation - Chairs Solicit Proposals Ian Hickson
• RE: W3C Bug Torture Dailey, David P.
• Re: W3C Bug Torture Carlos Cardona
• W3C Bug Torture Shelley Powers
• [Bug 7059] Forking XPath bugzilla@jessica.w3.org
• Re: Old resolved bugs (and sorry for the spam) Maciej Stachowiak
• [Bug 7543] Consensus on ietf-http-wg was that repetition of relations is meaningless and we should rather use numbering (e.g. "up2"), names (e.g. "great-grandparent") or an attribute (e.g. level="3"). bugzilla@jessica.w3.org
• Re: sorry for bugzilla message flood Maciej Stachowiak
• [Bug 7527] Allow implementations to generate meaningful default, implied headings for some sections. bugzilla@jessica.w3.org
• [Bug 7524] The list of forbidden Unicode characters in the authoring requirements does not match the list that generates parse errors in #tokenizing-character-references bugzilla@jessica.w3.org
• sorry for bugzilla message flood Michael(tm) Smith
• [Bug 7506] Clarify that the warning about "The presence of an obsolete permitted DOCTYPE" only applies to HTML, not XHTML which has no restriction on what DOCTYPEs may be used bugzilla@jessica.w3.org
• [Bug 7545] Atom (RFC 4287) defines a "logo" in addition to the "icon": "The image SHOULD have an aspect ratio of 2 (horizontal) to 1 (vertical)". Consider doing the same here. bugzilla@jessica.w3.org
• [Bug 7522] <math> should also be phrasing and flow content, like <img> and <svg>. bugzilla@jessica.w3.org
• [Bug 7524] The list of forbidden Unicode characters in the authoring requirements does not match the list that generates parse errors in #tokenizing-character-references bugzilla@jessica.w3.org
• [Bug 7340] add examples here bugzilla@jessica.w3.org
• [Bug 7591] disabled <fieldset> bugzilla@jessica.w3.org
• [Bug 7263] this thing really heavy, tried solution: switch to user mode css, after all rendered, return to author mode, scrolling is heavy though,,, try open panel & add info, heavy too.. bugzilla@jessica.w3.org
• [Bug 7700] define abort event bugzilla@jessica.w3.org
• [Bug 7558] "MIME type" not xreffed in "and any MIME type ending ..." bugzilla@jessica.w3.org
• [Bug 7348] add examples for <menu type=context> and contextmenu= bugzilla@jessica.w3.org
• [Bug 7351] The note ("The point of hgroup is to mask an h2 element (that acts as a secondary title) from the outline algorithm.") should be explicitly associated with the example below it that it applies to. (in general, a hgroup could mask an h3, h4, h5, etc.). bugzilla@jessica.w3.org
• [Bug 7364] The contents attribute is declared as read/write, however the following description only gives information about getting the value of the attribute. Should the contents attribute be marked as readonly? bugzilla@jessica.w3.org
• [Bug 7347] add examples for <command> bugzilla@jessica.w3.org
• [Bug 7368] The suggested UI for the mark element does not match the description and the examples. E.g. code highlighting is not something you want to see marked in the scrollbar. Personally I think code highlighting should just be done with strong. bugzilla@jessica.w3.org
• [Bug 7373] Need to fix "If a Document or image was returned by the XMLHttpRequest API" now that the document pointer concept is gone. bugzilla@jessica.w3.org
• [Bug 7374] legend as child of details, figure is unstylable and thus unusable bugzilla@jessica.w3.org
• [Bug 7393] парпрп bugzilla@jessica.w3.org
• [Bug 7387] small element should have same content model as a, ins, del bugzilla@jessica.w3.org
• [Bug 7377] s/Dahltröm/Dahlström/ bugzilla@jessica.w3.org
• [Bug 7606] the current behaviour in firefox on a disable input type='submit' is not to show the tooltip, in IE it will appear and then disappear but only when hovering over the text. Should the behaviour of the tooltip be more specifically defined when the element bugzilla@jessica.w3.org
• [Bug 7608] Rendering–Introduction: s/normaly/normally bugzilla@jessica.w3.org
• [Bug 7627] Cross-reference more occurrences of "being rendered". bugzilla@jessica.w3.org
• [Bug 7343] add examples here bugzilla@jessica.w3.org
• [Bug 7621] editorial: add example for pushState() - it's not clear what to use as the data bugzilla@jessica.w3.org
• [Bug 7619] "Document objects also implement the document-level interface of any other namespaces found in the document that the UA supports." - drop "found in the document" since it doesn't make sense to implement another interface on-the-fly when finding another na bugzilla@jessica.w3.org
• [Bug 7623] It'd be really nice if you specified if the angle argument to context.rotate accepts degrees, radians, or what. bugzilla@jessica.w3.org
• [Bug 7346] add examples here bugzilla@jessica.w3.org
• [Bug 7357] That ApplicationCache implements EventTarget should be a line in the IDL, not in prose: "ApplicationCache implements EventTarget;". This might apply to other sections too. bugzilla@jessica.w3.org
• [Bug 7344] add examples here bugzilla@jessica.w3.org
• [Bug 7349] add examples here bugzilla@jessica.w3.org
• [Bug 7643] Why not use display:none instead of overflow:hidden; height:0? display:none seems to have the desired behavior in terms of exposure to AT and keyboard navigation in browsers. bugzilla@jessica.w3.org
• [Bug 7628] The later 'block' box container should simply map to the first/last dd element. This makes UA implementations easier and script emulation of the feature in contemporary UAs as well. Both can simply toggle the display property between block and none. bugzilla@jessica.w3.org
• [Bug 7369] if context font is set to '' or null, the font from the css should be used. In this case, you have no idea what font is being use, so measureText should return a height of the font, as well as the width so that proper displaying can be done. bugzilla@jessica.w3.org
• [Bug 7396] shouldn't it be "if the defer attribute is specified, the src attribute must also be specified bugzilla@jessica.w3.org
• [Bug 7640] The definition of the "isindex" element here makes such elements' main interface be HTMLElement rather than HTMLUnknownElement. I suppose that's not intended bugzilla@jessica.w3.org
• [Bug 7618] "Whether a document is an HTML document or an XML document affects the behavior of certain APIs, as well as a few CSS rendering rules." - actually, i think it doesn't affect CSS rendering anymore, just selector matching bugzilla@jessica.w3.org
• [Bug 7641] The rendering of <details> says everything but the first dt will be hidden, but the element definition says the first dd represents the details. Also, having overflow:hidden when the details are open probably has unintended side-effects like clipping cont bugzilla@jessica.w3.org
• [Bug 7649] It would be useful to see an example of how section works when it's not in the context of an article, in the example text (chapters, tabs, etc) all of those would sit inside a wrapping article element. bugzilla@jessica.w3.org
• [Bug 7383] drawImage(video) and createPattern(video) should say that the aspect-ratio-corrected dimensions must be used bugzilla@jessica.w3.org
• [Bug 7637] Where is HTMLAnchorElement.name defined? I don't see it here nor in the main interface definition bugzilla@jessica.w3.org
• [Bug 7642] which attribute wins if both pointsize and size are specified? bugzilla@jessica.w3.org
• [Bug 7659] Clarify what "other applicable specifications" means to say http://lists.w3.org/Archives/Public/www-tag/2009Sep/0045.html bugzilla@jessica.w3.org
• [Bug 7617] editorial: "reflect" under HTMLDocument should be a link bugzilla@jessica.w3.org
• [Bug 7400] "as part" instead of "sa part" bugzilla@jessica.w3.org
• [Bug 7625] Since "event handler attributes" is an abstract concept it might be better to just call it "event handlers" so attributes is not confused with either IDL or content attributes here. bugzilla@jessica.w3.org
• [Bug 7620] I think Opera has some security checks for location, added because of some Flash vulnerability. If other browsers have similar checks, would be good to specify bugzilla@jessica.w3.org
• [Bug 7622] "There has got to be a better way of doing this, surely." - is there an intent to rewrite this before last call? is there implementor interest? is it considered for removal? bugzilla@jessica.w3.org
• [Bug 7636] shouldn't dom-table-summary be part of the HTMLTableElement interface proper? bugzilla@jessica.w3.org
• [Bug 7635] Include an example with the table rearranged so that it doesn't need a description, and advice that doing so might be more useful than writing a description bugzilla@jessica.w3.org
• [Bug 7639] Please remove "dc" and "ds" from the parser bugzilla@jessica.w3.org
• [Bug 7658] s/the requisite element/the requested element/ bugzilla@jessica.w3.org
• [Bug 7652] Is it fine for <nav> to link to a bunch of external pages? E.g. your Flickr/Facebook/Twitter/etc. profiles? bugzilla@jessica.w3.org
• [Bug 7646] Media Queries bugzilla@jessica.w3.org
• [Bug 7664] The in-memory representation is known as "DOM HTML", or "the DOM" for short. This specification defines version 5 of DOM HTML, known as "DOM5 HTML". bugzilla@jessica.w3.org
• [Bug 7644] The first example for footnotes is actually an example of a dialogue. bugzilla@jessica.w3.org
• [Bug 7726] legacy doctype syntax allows <!DOCTYPE HTML SYSTEM"about:legacy-compat"> bugzilla@jessica.w3.org
• [Bug 7668] 7.9.6 should explain which events are actually dispatched when copying/cutting/pasting bugzilla@jessica.w3.org
• [Bug 7674] are the chunks for inputs having the content-type header for each chunk specified appropriately? e.g. file inputs should set the header according to the file selected by the user bugzilla@jessica.w3.org
• [Bug 7724] I would like to know: what is to become of the A element’s NAME attribute? I validated a HTML5 website that I am working this Wednesday (2009-09-23) which contained an A element with a NAME attribute: the W3C Markup Validator did not mind one bit. Howe bugzilla@jessica.w3.org
• [Bug 7680] Add an 'angle' element to HTML5 bugzilla@jessica.w3.org
• [Bug 7661] status bugzilla@jessica.w3.org
• [Bug 7732] Server crawls (also on Safari), then page's loading slow and in parts, get a bizzare feeling, it's no longer a web page but an app I'am loading, don't like that, resizing causes page blanks of seconds length bugzilla@jessica.w3.org
• [Bug 7745] Shouldn't the spec state that it is the second (or third) versin of XHTML, known as XHTML5 as there haven't been version 3 or 4. bugzilla@jessica.w3.org
• [Bug 7734] open being an attribute of the section rather than the content area means you can never use this to mark up content which has multiple control/detail areas which are opened or closed independently like tabs or accordion bugzilla@jessica.w3.org
• [Bug 7733] Too simplistic to handle used cases with more complex controls than toggle, like carousel, tabs. It could work for accordians. bugzilla@jessica.w3.org
• [Bug 7741] First set of examples of alternative stylesheets have stylesheet titles marked up with href attributes rather than title attributes bugzilla@jessica.w3.org
• [Bug 7723] duplicate word ("first first") should be "first five" bugzilla@jessica.w3.org
• [Bug 7740] Authoring advice for canvas is bad for accessibility bugzilla@jessica.w3.org
• [Bug 7746] <link rel=search> should be used instead of <input type=search> for backwards-compatibility and beacuse the search input type poses no additional input restrictions. bugzilla@jessica.w3.org
• [Bug 7748] Does it have to be an absolute path or can it be a relative one, too? bugzilla@jessica.w3.org
• [Bug 7662] When images are disabled arguably fallback content of the <canvas> element should be shown. bugzilla@jessica.w3.org
• [Bug 7747] Attribute language not allowed on element script at this point bugzilla@jessica.w3.org
• [Bug 7689] Cache-defeating semantics are not defined bugzilla@jessica.w3.org
• [Bug 7717] If the user does not give permission it is not stated explicitly what will happen. It would be nice if the specification did state that the algorithm will be terminated at that point. (Should an event be dispatched?) bugzilla@jessica.w3.org
• [Bug 7686] No need to require user interface in cache update algorithm bugzilla@jessica.w3.org
• [Bug 7714] the diagram image says "tokeniser"; should be "tokenizer" bugzilla@jessica.w3.org
• [Bug 7730] The note starting "The algorithm described..." should end with the word "limitations" or "constraints" or something bugzilla@jessica.w3.org
• [Bug 7697] The type attribute should ammend the Accept header accordingly. HTTP spec is in accordance with the rules here, in terms of the Accept header being non-authorative. script and style elements already ammend accept header (in firefox) but not for other link bugzilla@jessica.w3.org
• [Bug 7710] "Any byte or sequences of bytes [...] that is misinterpreted [...]" - s/sequences/sequence/ bugzilla@jessica.w3.org
• [Bug 7663] search bugzilla@jessica.w3.org
• [Bug 7690] Incompletely defined priority of fallback over explicit entries bugzilla@jessica.w3.org
• [Bug 7725] It should be made more clear that only the "disk representation" is changed, not the "memory representation". I.e. images are not suddenly reloaded etc. bugzilla@jessica.w3.org
• [Bug 7688] 'input type=time' forbids legitimate use case bugzilla@jessica.w3.org
• [Bug 7701] Step 6.2 tells you to remove node from the stack of open elements and then go to step 6.1. 6.1 requires that you set node to be the node above node in the stack of open elements. However node is no longer in the stack of open elements bugzilla@jessica.w3.org
• [Bug 7677] Is there any behavior defined for setting the src property. For example, is the expectation that object should (A) load the src if autobuffer is true (B) stop playing if currently playing (C) something else (D) nothing at all? bugzilla@jessica.w3.org
• [Bug 7694] object@classid is missing from list of Content attributes, even though it is essential bugzilla@jessica.w3.org
• [Bug 7709] Prevent PUT/DELETE cross-origin bugzilla@jessica.w3.org
• [Bug 7708] Include some documentation here (or link to) how the time element with a pubdate attribute applies to article. bugzilla@jessica.w3.org
• [Bug 7691] each of which 'has', not 'have' bugzilla@jessica.w3.org
• [Bug 7712] oncontextmenu bugzilla@jessica.w3.org
• [Bug 7718] "If a Document or image was generated from a data: URL that was returned as the location of an HTTP redirect" ... "If a Document or image was obtained in some other manner (e.g. ... a data: URL returned as the location of an HTTP redirect ...)" - the last bugzilla@jessica.w3.org
• [Bug 7696] zxcszxczxc bugzilla@jessica.w3.org
• [Bug 7704] It is better to implement canvas.clear() method and allow to resize canvas without clearing it bugzilla@jessica.w3.org
• [Bug 7722] Relationship between bugzilla@jessica.w3.org
• [Bug 7703] HTML document conformance should explicitly depend on foreign content conformance bugzilla@jessica.w3.org
• [Bug 7706] This section should reference "matches a fallback namespace" in step 3. bugzilla@jessica.w3.org
• [Bug 7693] The term "Draft Standard" means something different in IETF than meant here, which adds to the confusion. "Editor's Draft" would be better. bugzilla@jessica.w3.org
• [Bug 7367] The HTMLEmbedElement interface needs to have the name and align DOM attributes as well. Web browsers do too. bugzilla@jessica.w3.org
• [Bug 7705] What use of providing both "embed" and "object" elements? They play nearly same role. bugzilla@jessica.w3.org
• [Bug 7629] When the dd element is used inside figure and details it should probably not have margin by default. bugzilla@jessica.w3.org
• [Bug 7395] "value associated with that denominator punctuation character" didn't get xrefed bugzilla@jessica.w3.org
• [Bug 7418] See if we can make popstate more synchronous so that when it fires, the doc is in the expected state, rather than three back-button-steps later. But consider nested calls to history.back(). bugzilla@jessica.w3.org
• [Bug 7699] define reset event bugzilla@jessica.w3.org
• [Bug 7594] "Otherwise, the the body element is null. Append the new value to the root element.": Append it where? At the end? bugzilla@jessica.w3.org
• [Bug 7421] azsxdcfvghjk bugzilla@jessica.w3.org
• [Bug 7405] Looks good! bugzilla@jessica.w3.org
• [Bug 7602] "Note: Playback of any previously " is listed as a step 12 of HTMLMediaElement.load() bugzilla@jessica.w3.org
• [Bug 7397] in xref names, s|td/th|tdth|g in obsolete section bugzilla@jessica.w3.org
• [Bug 7384] editorial: " (either an HTMLImageElement or an HTMLCanvasElement)" is missing HTMLVideoElement bugzilla@jessica.w3.org
• [Bug 7402] The x and y arguments should be better explained. bugzilla@jessica.w3.org
• [Bug 7419] Add replaceState() — e.g. consider panning on a maps application, not all the steps should be new states for back/forward, but we do want to update the url for persistence. bugzilla@jessica.w3.org
• [Bug 7408] "This sample how the getItems() method" is missing a "shows". bugzilla@jessica.w3.org
• [Bug 7375] Incorrect specification for window.postMessage()'s handling of unentangled ports bugzilla@jessica.w3.org
• [Bug 7398] the-basic-syntax bugzilla@jessica.w3.org
• [Bug 7595] editorial: "represents" should be a link bugzilla@jessica.w3.org
• [Bug 7401] Looking For this bugzilla@jessica.w3.org
• [Bug 7425] comments hould be after the root node bugzilla@jessica.w3.org
• [Bug 7593] Use of the "q.v." abbreviation here, while correct, is fairly obscure. Consider dropping "q.v." or rephrasing. bugzilla@jessica.w3.org
• [Bug 7415] "The rules for parsing simple color values are as given in the following algorithm." --> "The rules for parsing simple color values are given in the following algorithm." bugzilla@jessica.w3.org
• [Bug 7422] Add definition of <a name> bugzilla@jessica.w3.org
• [Bug 7403] What should happen when audio does not have controls but author specifies display:inline? Show fallback? Show blank box with the same size as if it had controls? Force display:none? bugzilla@jessica.w3.org
• [Bug 7614] why was this changed again? bugzilla@jessica.w3.org
• [Bug 7433] maybe tiny typo in example with figure: the last <figure> should be </figure> ? bugzilla@jessica.w3.org
• [Bug 7435] Fichier XML de mise à jour mal formé (200) bugzilla@jessica.w3.org
• [Bug 7440] The markup of the example does not use <th> for Legs and Tails like the actual table does. bugzilla@jessica.w3.org
• [Bug 7406] Layout system for HTML bugzilla@jessica.w3.org
• [Bug 7432] 'have been noted as "willful violations"': Other places use the signular, "willful violation". For consistency, non-native english readers and easy text search, use the singular when defining the term. E.g. 'have each been noted as a "willful violation". bugzilla@jessica.w3.org
• [Bug 7599] Either drop the two places that set the "Origin" HTTP header, or update HTML5 to match the Sec-From/Origin I-D (if the latter is stable enough yet). bugzilla@jessica.w3.org
• [Bug 7417] Why use radians as opposed to degrees? Does this mean I can never draw a complete circle because I don't have enough bits to represent 2pi? bugzilla@jessica.w3.org
• [Bug 7409] It's not clear what labeled control is in cases with > 1 control as a child of the <label> bugzilla@jessica.w3.org
• [Bug 7448] editorial: The ":" in "Author requirements:" should also be marked as class=impl bugzilla@jessica.w3.org
• [Bug 7404] "but only if the element is being rendered" needs to take into account <canvas> descendants if we're making them focusable bugzilla@jessica.w3.org
• [Bug 7407] "The examples in the previous section show how information could be marked up on a page that doesn't expect its microdata to be re-used." is not true anymore bugzilla@jessica.w3.org
• [Bug 7581] Should the select() method set focus? MSIE+Opera does not. FF+Chrome sets focus. It should probably be specified to set focus. bugzilla@jessica.w3.org
• [Bug 7579] Could "interactive widget" in the context of a web application be defined, expanded upon or an example provided? This seems too vague. bugzilla@jessica.w3.org
• [Bug 7416] IDNA has not been previously used or defined. It is not an obvious term. Please expand it or reference a definition on first use. bugzilla@jessica.w3.org
• [Bug 7578] "If the defer attribute may be specified": this phrasing is confusing, should "may be specified" be "is specified" bugzilla@jessica.w3.org
• [Bug 7575] <meter> example isn't highlighted bugzilla@jessica.w3.org
• [Bug 7452] "The collection of Documents is the browsing context's session history. " -- What do you mean by "the collection of documents" ? not clear bugzilla@jessica.w3.org
• [Bug 7446] editorial: last paragraph should probably have class=impl bugzilla@jessica.w3.org
• [Bug 7423] why deprecate s, u, strike, acronym? It makes no sense. bugzilla@jessica.w3.org
• [Bug 7428] Safari 4 preloads media and FF 3.5 doesn't in <audio> tag; perhaps HTML5 sections 4.8.10.5 4.8.10.8 are unclear or need a 'preloading' attribute added. bugzilla@jessica.w3.org
• [Bug 7441] The specification only ever uses the prefix:localName convention for some attributes in the XML namespace and whenever it does it is pretty explicit about it. xml:id is never mentioned outside this section and the prefixes svg and html are never used. bugzilla@jessica.w3.org
• [Bug 7590] The sentence about HTMLUnknownElement should s/this specification/this specification (or other appliciable specifications)/ to allow delta specs to define HTML elements bugzilla@jessica.w3.org
• [Bug 7420] dfghjxdcfvbnm,,k sdfghjk gfdsdfgh fghj bugzilla@jessica.w3.org
• [Bug 7455] The example codes don't have double quotes bugzilla@jessica.w3.org
• [Bug 7577] meta/@name=descriptions vs invisible metadata bugzilla@jessica.w3.org
• [Bug 7427] When the maxlength attribute is omitted it should return -1 like Opera and Firefox and not 0. (Alternatively it could return the maximum value like Chrome and presumably Safari do, but that seems less nice. bugzilla@jessica.w3.org
• [Bug 7560] The following sentence could be made more clear, or given an example to indicate what is meant: "The otherwise optional U+000A LINE FEED (LF) character must be included if the element's contents start with that character" bugzilla@jessica.w3.org
• [Bug 7431] "willful double violation of RFC 2046": The word "double" is splitting the defined term "willful violation". This sounds like a new defined term and interferes with document searching. Instead use "willful violation of two aspects of RFC 2046" bugzilla@jessica.w3.org
• [Bug 7436] Fichier XML de mise à jour mal formé (200) bugzilla@jessica.w3.org
• [Bug 7574] The annotation here has 20 tests, but the box for viewing them is bigger than the browser window, hiding the close button. Set a max height and overflow:auto on the popup box. bugzilla@jessica.w3.org
• [Bug 7434] Everything with role=heading should also have an associated aria-level that indicates the level of the heading. The level of the heading should probably be based on the outline algorithm. bugzilla@jessica.w3.org
• [Bug 7584] The <meter> example doesn't have any highlighting, whereas all the other elements do bugzilla@jessica.w3.org
• [Bug 7583] IE8 won't run click events on a label's associated input if the input is hidden via CSS with "display:none" or "visibility:hidden". Other browsers will. There doesn't seem to be an appropriate platform behavior to emulate here, so the exact behavior sho bugzilla@jessica.w3.org
• [Bug 7459] Nitpicking: an XML document is always well-formed and therefore cannot have syntax errors (including minor). bugzilla@jessica.w3.org
• [Bug 7559] What happens when an "option" element has its "selected" attribute removed? bugzilla@jessica.w3.org
• [Bug 7445] editorial: This section becomes a subsection of "the xhtml syntax" in the author edition. Maybe either move this section somewhere else or keep the "Rendering" and "Interaction with CSS" headings outside class=impl bugzilla@jessica.w3.org
• [Bug 7449] editorial: hyperlinked "represents" on the id attribute definition bugzilla@jessica.w3.org
• [Bug 7439] Where it says "in the example above" when introducing attributes the example is actually below. bugzilla@jessica.w3.org
• [Bug 7447] "Use the data and type attributes to invoke plugins." should also mention that <param> can be used to pass parameters with these names to the plugin bugzilla@jessica.w3.org
• [Bug 7443] maybe list role and aria-* here bugzilla@jessica.w3.org
• [Bug 7437] The link for "mutable" points to textareas - no mention made of radio, button, input, password types bugzilla@jessica.w3.org
• [Bug 7461] List of space characters should include U+000B LINE TABULATION (VT) or should note why it is not included. bugzilla@jessica.w3.org
• [Bug 7458] inconsistent definition of "up" relation bugzilla@jessica.w3.org
• [Bug 7472] JimJJewett gmail: Annotations for assistive technology products (ARIA) -- add the "ARIA", like 3.4 mentions XPATH and XSLT bugzilla@jessica.w3.org
• [Bug 7453] "preferred name" should be "preferred MIME name" but it should also state that if there is no preferred MIME name for the encoding the name of the encoding should be used. bugzilla@jessica.w3.org
• [Bug 7456] Ogg vorbis realy should be standard since it is open and everything can then support it without patent costs. This is REALLY important. Most other standards need patent money. Apple's H.264 is CERTAINly bad here. bugzilla@jessica.w3.org
• [Bug 7556] Where is it defined that only the first <base> element is to be taken into account? Surely that should not be part of iri-bis. bugzilla@jessica.w3.org
• [Bug 7465] "a IDL attribute" -> "an IDL attribute" (here and elsewhere) bugzilla@jessica.w3.org
• [Bug 7454] Please do not remove these useful features - or are alternative mechanisms planned? bugzilla@jessica.w3.org
• [Bug 7457] Ogg theora needs to be used here as an open standard. Having different standards in different browsers will confuse the matter and it is the only standard to my knowledge that is not patent encumbered. This is seriously important to reinstate. bugzilla@jessica.w3.org
• [Bug 7469] Is it really necessary to have sections on what HTML5 does not cover? bugzilla@jessica.w3.org
• [Bug 7480] use of keygen should trigger a warning. bugzilla@jessica.w3.org
• [Bug 7473] JimJJewett gmail: Mention explicitly that the mapping for foreign content -- including adopted MathML or SVG -- is left to those working groups. (Otherwise, I would have expected some strong native semantics for math to math) bugzilla@jessica.w3.org
• [Bug 7451] "In the example above" should be "In the example below" bugzilla@jessica.w3.org
• [Bug 7475] Semantics of rel=first and rel=index breaks specs and implementations bugzilla@jessica.w3.org
• [Bug 7561] There's no UA conformance criteria for <meta name>, in particular nothing about case-insensitivity. bugzilla@jessica.w3.org
• [Bug 7481] The Form submission algorithm section states "If the submitter is anything but a form element...", yet this section states "validate the constraints of form element form". bugzilla@jessica.w3.org
• [Bug 7489] I wanted to know what a fallback entry is so I clicked on the "fallback entries" link. This took me to a section that describes fallback entries as "Resources that were listed in the cache's manifest as fallback entries". But that's a recursive definition bugzilla@jessica.w3.org
• [Bug 7547] on .drawImage() negative widths or heights should flip/mirror the image. There's no easy way of fliping images in canvas bugzilla@jessica.w3.org
• [Bug 7460] Under "JavaScript": The note containing a "willful violation" doesn't contain the words "willful violation" as promised by section 1.5.2. bugzilla@jessica.w3.org
• [Bug 7470] JimJJewett gmail: The implications of these tables should also appear at element level -- e.g, td model or dom should mention aria- -- unless it is explicitly not exposed, for some reason. bugzilla@jessica.w3.org
• [Bug 7479] The content attribute should be all-lowercase: formnovalidate bugzilla@jessica.w3.org
• [Bug 7466] This section forbids exposing rel=feed but not exposing e.g. rel=copyright. I think that is wrong. The specification should not dictate UI for this. bugzilla@jessica.w3.org
• [Bug 7477] "It is an element with an ID key" makes it sound like "ID" is an adjetive for "key". Consider a phrasing like the previous bullet. Namely, "It is an element with an ID equal to key." bugzilla@jessica.w3.org
• [Bug 7476] typo in the last example of section 4.6.9: "lt;/time>" where "</time>" is intended. -Tantek bugzilla@jessica.w3.org
• [Bug 7543] Consensus on ietf-http-wg was that repetition of relations is meaningless and we should rather use numbering (e.g. "up2"), names (e.g. "great-grandparent") or an attribute (e.g. level="3"). bugzilla@jessica.w3.org
• [Bug 7487] An internal general parsed entity is not XML namespace-well-formed in the general case, since a fragment can have text and multiple elements at the top level bugzilla@jessica.w3.org
• [Bug 7474] Shouldn't the listener be added AFTER the function is defined? bugzilla@jessica.w3.org
• [Bug 7550] The invalid event does have a default action. Namely to display UI. However, UAs should probably not be forbidden to show that a field is invalid before submitting, but how can page author suppress the UI for that? bugzilla@jessica.w3.org
• [Bug 7548] replace <dialog> with advice bugzilla@jessica.w3.org
• [Bug 7501] Change "The value must be a short free-form string THAT giving the name of the Web application that the page represents." It should read- "The value must be a short free-form string giving the name of the Web application that the page represents." bugzilla@jessica.w3.org
• [Bug 7549] define how to parse a MIME type bugzilla@jessica.w3.org
• [Bug 7526] spelling: Before this task is run, *sa* part of the event loop mechanism, the rendering will have been updated to resize the video element if appropriate. bugzilla@jessica.w3.org
• [Bug 7494] It puts together on src etc. of the audio tag and the img tag, and it wants a united method of knowing meta information on src. It is a name of a song, and a name of the singer in case of the song. If it is a photograph, it is GPS informational etc. bugzilla@jessica.w3.org
• [Bug 7545] Atom (RFC 4287) defines a "logo" in addition to the "icon": "The image SHOULD have an aspect ratio of 2 (horizontal) to 1 (vertical)". Consider doing the same here. bugzilla@jessica.w3.org
• [Bug 7544] Atom (RFC 4287) further specifies that "The image SHOULD have an aspect ratio of one (horizontal) to one (vertical) and SHOULD be suitable for presentation at a small size". Consider doing the same here. bugzilla@jessica.w3.org
• [Bug 7505] interface HTMLIFrameElement : HTMLElement { attribute DOMString src; attribute DOMString name; attribute DOMString sandbox; attribute boolean seamless; attribute DOMString width; attribute bugzilla@jessica.w3.org
• [Bug 7546] "HTML 5" Editor's draft misnamed and suboptimal for HTML content authors unless refactored into HTML (main) and DOM API (appendix). bugzilla@jessica.w3.org
• [Bug 7493] I want to know meta information on media src. Name of a song, work name, name of singer, and etc... bugzilla@jessica.w3.org
• [Bug 7484] head/@profile holds a white-space separated list of URIs bugzilla@jessica.w3.org
• [Bug 7527] Allow implementations to generate meaningful default, implied headings for some sections. bugzilla@jessica.w3.org
• [Bug 7521] This table is confusing because it mixes content, IDL attributes, methods, and events. Maybe the various concepts can be grouped and get an appropriate row-group header so it is more clear. The introduction for the table doesn't mention the events and doe bugzilla@jessica.w3.org
• [Bug 7523] Treat <metadata> like <title> in SVG foreign content bugzilla@jessica.w3.org
• [Bug 7511] The implicit mechanism doesn't fire onsubmit or validate as written today. The exception for when the submitter is the form should be changed to just be a flag for .submit() specifically. bugzilla@jessica.w3.org
• [Bug 7509] Consider <dl type="dialog"> instead of <dialog> bugzilla@jessica.w3.org
• [Bug 7497] Add an example to <aside> that shows it being used to hold a blogroll. bugzilla@jessica.w3.org
• [Bug 7485] obsolete permitted DOCTYPEs link is broken in author view bugzilla@jessica.w3.org
• [Bug 7506] Clarify that the warning about "The presence of an obsolete permitted DOCTYPE" only applies to HTML, not XHTML which has no restriction on what DOCTYPEs may be used bugzilla@jessica.w3.org
• [Bug 7499] <keygen> should not be defined as a requirement for a conforming HTML5 user agent and should be removed from the spec bugzilla@jessica.w3.org
• [Bug 7508] <dialog> needs a way to add non-speech related information bugzilla@jessica.w3.org
• [Bug 7482] The maxLength attribute for input elements can be -1, indicating no maxlength attribute present, per DOM Level 2 HTML. HTML 5 has changed that to be "unsigned long", which -1 cannot be. bugzilla@jessica.w3.org
• [Bug 7519] Should rephrase "All the elements in this specification have a defined content model, which describes what nodes are allowed inside the elements, and thus what the structure of an HTML document or fragment must look like." to more explicitly say that HTML bugzilla@jessica.w3.org
• [Bug 7502] The clarification that the footer can be used as a site-wide footer or a section footer is not inherently clear via the spec. I suggest specifically stating just that: use for a section or an entire site. bugzilla@jessica.w3.org
• [Bug 7507] Firefox 3.5 does NOT clear a canvas if its width is set to itself bugzilla@jessica.w3.org
• [Bug 7503] there is no specification for detection of this feature. how do i know whether to use draggable="true" or revert to a drag simulation library like scriptaculous? - jkwon.work@gmail.com bugzilla@jessica.w3.org
• [Bug 7345] add examples here bugzilla@jessica.w3.org
• [Bug 7337] add examples here bugzilla@jessica.w3.org
• [Bug 7339] add examples here bugzilla@jessica.w3.org
• [Bug 7331] add examples here bugzilla@jessica.w3.org
• [Bug 7341] add examples here bugzilla@jessica.w3.org
• [Bug 7342] add examples here bugzilla@jessica.w3.org
• [Bug 7338] add examples here bugzilla@jessica.w3.org
• [Bug 7336] add examples here bugzilla@jessica.w3.org
• [Bug 7335] add examples here bugzilla@jessica.w3.org
• [Bug 7332] add examples here bugzilla@jessica.w3.org
• [Bug 7327] add examples here bugzilla@jessica.w3.org
• [Bug 7333] add examples here bugzilla@jessica.w3.org
• [Bug 7334] add examples here bugzilla@jessica.w3.org
• [Bug 7330] add examples here bugzilla@jessica.w3.org
• [Bug 7324] add examples here bugzilla@jessica.w3.org
• [Bug 7322] add examples here bugzilla@jessica.w3.org
• [Bug 7328] add examples here bugzilla@jessica.w3.org
• [Bug 7326] add examples here bugzilla@jessica.w3.org
• [Bug 7319] add examples here bugzilla@jessica.w3.org
• [Bug 7318] add examples here bugzilla@jessica.w3.org
• [Bug 7329] add examples here bugzilla@jessica.w3.org
• [Bug 7323] add examples here bugzilla@jessica.w3.org
• [Bug 7320] add examples here bugzilla@jessica.w3.org
• [Bug 7321] add examples here bugzilla@jessica.w3.org
• [Bug 7315] add examples here bugzilla@jessica.w3.org
• [Bug 7313] add examples here bugzilla@jessica.w3.org
• [Bug 7304] add examples here bugzilla@jessica.w3.org
• [Bug 7325] add examples here bugzilla@jessica.w3.org
• [Bug 7316] add examples here bugzilla@jessica.w3.org
• [Bug 7311] add examples here bugzilla@jessica.w3.org
• [Bug 7317] add examples here bugzilla@jessica.w3.org
• [Bug 7314] add examples here bugzilla@jessica.w3.org
• [Bug 7310] add examples here bugzilla@jessica.w3.org
• [Bug 7308] add examples here bugzilla@jessica.w3.org
• [Bug 7307] add examples here bugzilla@jessica.w3.org
• [Bug 7300] add examples here bugzilla@jessica.w3.org
• [Bug 7303] add examples here bugzilla@jessica.w3.org
• [Bug 7301] add examples here bugzilla@jessica.w3.org
• [Bug 7305] add examples here bugzilla@jessica.w3.org
• [Bug 7296] add examples here bugzilla@jessica.w3.org
• [Bug 7297] add examples here bugzilla@jessica.w3.org
• [Bug 7312] add examples for tables bugzilla@jessica.w3.org
• [Bug 7309] add examples here bugzilla@jessica.w3.org
• [Bug 7293] add examples here bugzilla@jessica.w3.org
• [Bug 7306] add examples here bugzilla@jessica.w3.org
• [Bug 7299] mark up examples bugzilla@jessica.w3.org
• [Bug 7285] add examples here bugzilla@jessica.w3.org
• [Bug 7302] add examples here bugzilla@jessica.w3.org
• [Bug 7291] add examples here bugzilla@jessica.w3.org
• [Bug 7290] add examples here bugzilla@jessica.w3.org
• [Bug 7281] <script language="javascript" type="text/javascript"> bugzilla@jessica.w3.org
• [Bug 7295] add examples here bugzilla@jessica.w3.org
• [Bug 7294] add examples here bugzilla@jessica.w3.org
• [Bug 7292] add examples here bugzilla@jessica.w3.org
• [Bug 7282] add dummy willValidate() and company to object bugzilla@jessica.w3.org
• [Bug 7288] add examples here bugzilla@jessica.w3.org
• [Bug 7298] add examples here bugzilla@jessica.w3.org
• [Bug 7287] add examples here bugzilla@jessica.w3.org
• [Bug 7286] add examples here bugzilla@jessica.w3.org
• [Bug 7284] add examples here bugzilla@jessica.w3.org
• [Bug 7275] "The markup snippet at the top of this section" should be a link to that snippet; the section is long enough that the snippet will already have scrolled off-screen for some people. (In my case, it had also escaped my short-term memory.) JimJJewett@gmail bugzilla@jessica.w3.org
• [Bug 7283] add examples here bugzilla@jessica.w3.org
• [Bug 7266] Section states twice in green that other specs can define other event loops, can remove one of those bugzilla@jessica.w3.org
• [Bug 7289] add examples here bugzilla@jessica.w3.org
• [Bug 7277] """(This is only a "SHOULD" and not a "MUST" requirement because it has been proven to be impossible.""" There has to be better wording than 'should do the impossible'. Should attempt to verify? Impossible in some cases? JimJJewett@gmail bugzilla@jessica.w3.org
• [Bug 7280] new comment bugzilla@jessica.w3.org
• [Bug 7274] The word "left" should not be part of the link when saying that attributes can be left unquoted. It sounds too much like "left outer join" or such, and might imply that it was legal to unquote only one side, or some such oddness. JimJJewett@gmail bugzilla@jessica.w3.org
• [Bug 7269] user agent requirements: for value=8 max="", step 4 and 11 will cause current value and maximum value to be set to 1, which is destructive (if script wanted to obtain the original value). suggest step 4 change to set maximum to value bugzilla@jessica.w3.org
• [Bug 7273] The word "left" should not be part of the link when saying that attributes can be left unquoted. It sounds too much like "left outer join" or such, and might imply that it was legal to unquote only one side, or some such oddness. JimJJewett@gmail bugzilla@jessica.w3.org
• [Bug 7276] "tree order" -- is this a section that can assume formal compsci training, or should a short (4 nodes?) example be given? JimJJewett@gmail bugzilla@jessica.w3.org
• [Bug 7264] make <% start a bogus comment bugzilla@jessica.w3.org
• [Bug 7278] numbers seem ignorant of i18n - is <meter>10,3</meter> taken as 10? requirements for number may expand to include, i.e.: U+002C COMMA for European № bugzilla@jessica.w3.org
• [Bug 7256] "which is not a real time zone currently" --> which is not currently a real time zone bugzilla@jessica.w3.org
• [Bug 7265] the HTML5 validator says maxlength is not allowed on textarea bugzilla@jessica.w3.org
• [Bug 7256] "which is not a real time zone currently" --> which is not currently a real time zone bugzilla@jessica.w3.org
• [Bug 7254] If <audio> was able to play back multiple source urls without gaps, JavaScript could decode or generate continuous audio to data: urls on the fly. bugzilla@jessica.w3.org
• [Bug 7253] Media elements should provide a "next" property to gaplessly play back another media object after it has finished. This woud allow proper playback of gapless albums and an in-browser implementation of HTTP Adaptive Bitrate Streaming. bugzilla@jessica.w3.org
• [Bug 7261] In the third code example, a code element is opened but a </cite> tag closes it. The opening tag should be <cite>. bugzilla@jessica.w3.org
• [Bug 7272] The explanatory text and the diagram suggest that legs and tails should be th, rather than td -- but the example has td. JimJJewett@gmail bugzilla@jessica.w3.org
• [Bug 7255] "This will either return a year and month" --> "This will return either a year and month" bugzilla@jessica.w3.org
• [Bug 7259] dfgsgdfsg dgf bugzilla@jessica.w3.org
• [Bug 7268] contradicts 4.7.1 wrt implied paragraph boundaries (should not in 4.7.1, not good practice in 4.7.4). dont repeat example or simplify bugzilla@jessica.w3.org
• [Bug 7255] "This will either return a year and month" --> "This will return either a year and month" bugzilla@jessica.w3.org
• [Bug 7241] Need to explain exactly what happens if wrap=hard is specified *without* cols being specified. Should it act like wrap=soft, or like cols=20? bugzilla@jessica.w3.org
• [Bug 7245] canvas bugzilla@jessica.w3.org
• [Bug 7254] If <audio> was able to play back multiple source urls without gaps, JavaScript could decode or generate continuous audio to data: urls on the fly. bugzilla@jessica.w3.org
• [Bug 7246] Add examples for <keygen> bugzilla@jessica.w3.org
• [Bug 7248] sxdfsdf bugzilla@jessica.w3.org
• [Bug 7243] no mension of h3c? bugzilla@jessica.w3.org
• [Bug 7248] sxdfsdf bugzilla@jessica.w3.org
• [Bug 7253] Media elements should provide a "next" property to gaplessly play back another media object after it has finished. This woud allow proper playback of gapless albums and an in-browser implementation of HTTP Adaptive Bitrate Streaming. bugzilla@jessica.w3.org
• [Bug 7258] Should state that a new Date object is returned each time the date/time/timezone attributes are accessed if the intention is for them not to be reflecting datetime="" or the element content. bugzilla@jessica.w3.org
• [Bug 7245] canvas bugzilla@jessica.w3.org
• [Bug 7225] http://www.w3.org/Bugs/Public/show_bug.cgi?id=7224 bugzilla@jessica.w3.org
• [Bug 7241] Need to explain exactly what happens if wrap=hard is specified *without* cols being specified. Should it act like wrap=soft, or like cols=20? bugzilla@jessica.w3.org
• [Bug 7238] more examples bugzilla@jessica.w3.org
• [Bug 7229] input.files should return the same object bugzilla@jessica.w3.org
• [Bug 7224] Crash in application C++ exception Unsupported file format header 46466c17 bugzilla@jessica.w3.org
• [Bug 7237] Let current outlinee be null. (It holds the element whose outline is being created.) Spelling. Outline with one "e" bugzilla@jessica.w3.org
• [Bug 7222] http://abu---wisam.ahlamontada.net bugzilla@jessica.w3.org
• [Bug 7246] Add examples for <keygen> bugzilla@jessica.w3.org
• [Bug 7234] review 123 bugzilla@jessica.w3.org
• [Bug 7227] using both "conforming but obsolete" (12.1) and "obsolete but conforming" (12.1.1) - consistency in terminology may be helpful bugzilla@jessica.w3.org
• [Bug 7226] has enabled --> have enabled bugzilla@jessica.w3.org
• [Bug 7215] character encodings and XML bugzilla@jessica.w3.org
• [Bug 7243] no mension of h3c? bugzilla@jessica.w3.org
• [Bug 7190] Since all "specially focusable" elements have an activation behaviour, the Action of accesskey-laden commands is to _not_ focus them if they are focusable. Instead, such elements should probably always be focused if focusable, then be activated. bugzilla@jessica.w3.org
• [Bug 7221] www.abu---wisam.ahlamontada.net bugzilla@jessica.w3.org
• [Bug 7219] http://abu---wisam.ahlamontada.net bugzilla@jessica.w3.org
• [Bug 7220] http://abu---wisam.ahlamontada.net bugzilla@jessica.w3.org
• [Bug 7179] <xmp> should close <p> (does in IE and WebKit) bugzilla@jessica.w3.org
• [Bug 7214] Typo: "When an input element's type attribute is in the *Telphone* state" bugzilla@jessica.w3.org
• [Bug 7185] itemprop needs to be after item; no longer a-z ordered due to the name change prolly. bugzilla@jessica.w3.org
• [Bug 7213] todataurl bugzilla@jessica.w3.org
• [Bug 7199] microformat bugzilla@jessica.w3.org
• [Bug 7189] how to use "item" in xhtml5? item="item" ?! bugzilla@jessica.w3.org
• [Bug 7186] oppo n iuniu in niun iun lin in liunniuniuniun i bugzilla@jessica.w3.org
• [Bug 7188] how to use "item" in xhtml5? item="item" ?! bugzilla@jessica.w3.org
• [Bug 7154] icon attribute: We can't apply so-called "CSS Sprite" technique for command icons. We need another attribute to specify clip position and size. bugzilla@jessica.w3.org
• [Bug 7176] The link to [GREGORIAN] doesn't seem to work... bugzilla@jessica.w3.org
• [Bug 7183] Hum, ham eu acho que... sei, bom, acho que é isso mesmo, meu comentario é: ronaldo! bugzilla@jessica.w3.org
• [Bug 7171] Is this missing a comment as to how the type attribute is quoted wrt:codecs? "''" + '""' bugzilla@jessica.w3.org
• [Bug 7153] Want standardization of .naturalWidth and .naturalHeight, which some browsers already have bugzilla@jessica.w3.org
• [Bug 7147] s#one of the optional U+002F SOLIDUS (/) characters#the optional U+002F SOLIDUS (/) character# bugzilla@jessica.w3.org
• [Bug 7164] teste bugzilla@jessica.w3.org
• [Bug 7161] If a heading has title text and then an image below it, then more text, how is the figure element handled in header and hgroup elements? bugzilla@jessica.w3.org
• [Bug 7156] I would like to see theora/vorbis as HTML5 standard. I'm tired of codec patents. bugzilla@jessica.w3.org
• [Bug 7145] Valid date strings should accept ambiguous inputs, like "2009" or "2007-01". bugzilla@jessica.w3.org
• [Bug 7144] I am not sure if we are ditching ALT in favour of legend. You don't make this clear here. Some of your alt examples here resemble longdesc, which I am in favour of ditching completely. I'd be interested to see your answer on whatwg list about this bugzilla@jessica.w3.org
• [Bug 7157] I would like to see theora/vorbis as HTML5 standard. I'm tired of codec patents. bugzilla@jessica.w3.org
• [Bug 7143] "attributes marked with an asterisk cannot be specified on body elements" is confusing, since <body onload=""> is pretty common. Of course that's the attribute specified on a tag, but still, I'm just a simple author reading the spec for the first time :) bugzilla@jessica.w3.org
• [Bug 7175] clearTimeout and clearInterval are not in the dom-intro box bugzilla@jessica.w3.org
• [Bug 7152] "When the user agent has completely fetched of the entire media resource, […]" No 'of' and only one of 'completely' or 'entire' should remain in the text. Mentioned one week ago on the list. Taking the opportunity to try this inline review box. bugzilla@jessica.w3.org
• [Bug 7146] goog bugzilla@jessica.w3.org
• [Bug 7142] Shouldn't SERIALISE_ERR be SERIALIZE_ERR ? bugzilla@jessica.w3.org
• [Bug 7141] Typo: "A members..." bugzilla@jessica.w3.org
• [Bug 7030] Define "Text" content model bugzilla@jessica.w3.org
• [Bug 7139] test bugzilla@jessica.w3.org
• [Bug 7089] CDATA escapes need to close upon --\s*!> bugzilla@jessica.w3.org
• [Bug 7151] s/users/user bugzilla@jessica.w3.org
• [Bug 7137] Need to fill in the references section. bugzilla@jessica.w3.org
• [Bug 6993] Tell authoring tools to use UTF-8 bugzilla@jessica.w3.org
• [Bug 7084] <ul><li>A<ul></li>B is parsed backwards-incompatibly bugzilla@jessica.w3.org
• [Bug 7140] test bugzilla@jessica.w3.org
• [Bug 7032] Sandboxing and Referer bugzilla@jessica.w3.org
• [Bug 7059] Forking XPath bugzilla@jessica.w3.org
• [Bug 7138] Need to get window.mediaMode into another spec bugzilla@jessica.w3.org
• [Bug 6949] Don't use colon shorthand when talking about language-related attributes bugzilla@jessica.w3.org
• [Bug 6999] Adding tag <NSFW> bugzilla@jessica.w3.org
• [Bug 7103] Content-Language marked as non-conforming bugzilla@jessica.w3.org
• [Bug 6973] Support <textarea>.textLength bugzilla@jessica.w3.org
• [Bug 6902] Note incompatibilities with RDF serializations bugzilla@jessica.w3.org
• [Bug 7086] <a> should be </a> in section 4.5.3 of the HTML5 specification bugzilla@jessica.w3.org
• [Bug 6898] Case shifting terminology is confusing bugzilla@jessica.w3.org
• [Bug 6974] Please be explicit about inheritance of scripting flag when setting innerHTML bugzilla@jessica.w3.org
• [Bug 6978] Mark eof-terminated script elements as malformed bugzilla@jessica.w3.org
• [Bug 6937] BibTeX author and editor don't fit DRY HTML bugzilla@jessica.w3.org
• [Bug 6942] Define how to handle failed 'resolve a url' steps in microdata algorithms bugzilla@jessica.w3.org
• [Bug 6858] More details needed for "ASCII-compatible encoding" bugzilla@jessica.w3.org
• [Bug 6769] Grammar mistake: "element element"? bugzilla@jessica.w3.org
• [Bug 6766] document.all definition missing bugzilla@jessica.w3.org
• [Bug 6778] Note the XPath implications of assigning HTML elements into the http://www.w3.org/1999/xhtml namespace bugzilla@jessica.w3.org
• [Bug 6977] Unnecessary sentence in <cite> presentation bugzilla@jessica.w3.org
• [Bug 6764] Section 2.4.4.1 Non-negative integers - Step 9.4 refers to incorrect step bugzilla@jessica.w3.org
• [Bug 6776] Note the XSLT implications of assigning HTML elements into the http://www.w3.org/1999/xhtml namespace bugzilla@jessica.w3.org
• [Bug 6832] <datagrid> content model is silly bugzilla@jessica.w3.org
• [Bug 6796] <keygen> in <select> bugzilla@jessica.w3.org
• [Bug 6690] Document.renameNode() is not part of Web DOM bugzilla@jessica.w3.org
• [Bug 6759] event queueing rules for <img> are nonsensical bugzilla@jessica.w3.org
• [Bug 6670] Allow unescaped &s, at least in attributes that accept URLs bugzilla@jessica.w3.org
• [Bug 6662] Make clearer that "the script's encoding" doesn't refer to the encoding of the script file itself bugzilla@jessica.w3.org
• [Bug 6760] "string" misspelled as "stirng" bugzilla@jessica.w3.org
• [Bug 6765] Poor wording in 4.8.2.1.12 General guidelines bugzilla@jessica.w3.org
• [Bug 6812] Typo: JavsScript bugzilla@jessica.w3.org
• [Bug 6689] [blocked on web dom core] Element.setAttributeNode() shouldn't modify the attribute node bugzilla@jessica.w3.org
• [Bug 6656] make clear that Referer headers track the pushState()d URL bugzilla@jessica.w3.org
• [Bug 6729] Attribute getters/setters should lower case argument on HTML elements in HTML docs bugzilla@jessica.w3.org
• [Bug 6606] generic 3rd-party <mark>, Smart Tags, and Accelerators prevention bugzilla@jessica.w3.org
• [Bug 6563] Specify if innerHTML setting should use the quirkiness of the document bugzilla@jessica.w3.org
• [Bug 6736] dfn.js doesn't handle class="impl" bugzilla@jessica.w3.org
• [Bug 6659] textarea also needs text-indent:initial bugzilla@jessica.w3.org
• [Bug 6543] Mint a new element for figure captions bugzilla@jessica.w3.org
• [Bug 6652] spellcheck should allow empty string bugzilla@jessica.w3.org
• [Bug 6630] Optionalness of start tags when element is empty bugzilla@jessica.w3.org
• [Bug 6461] Fix the definition of "Origin" for Documents from javascript: URLs bugzilla@jessica.w3.org
• [Bug 6491] <textarea wrap=off> not supported bugzilla@jessica.w3.org
• [Bug 6628] WebSocket.URL and EventSource.URL should return the absolute URL bugzilla@jessica.w3.org
• [Bug 6618] </body> and </html> early on handled in a Gecko/WebKit/Presto-inconsisten way bugzilla@jessica.w3.org
• [Bug 6437] document.location should update when the browsing context is navigated without the Document changing bugzilla@jessica.w3.org
• [Bug 6536] Time element examples should be in the context of a goal-oriented microformat use case bugzilla@jessica.w3.org
• [Bug 6516] obsolete attributes on HTMLDocument assume there is a body element bugzilla@jessica.w3.org
• [Bug 6529] value DOM attribute for input element in File Upload state bugzilla@jessica.w3.org
• [Bug 6515] the body element event handler attributes and missing Window object bugzilla@jessica.w3.org
• [Bug 6590] character encoding mapping needs to be used for form submission too bugzilla@jessica.w3.org
• [Bug 6457] registerContentHandler() and sniffing bugzilla@jessica.w3.org
• [Bug 6493] Use encoding of POSTing document for POST response if meta prescan fails bugzilla@jessica.w3.org
• [Bug 6460] Handle onerror feedback for Workers bugzilla@jessica.w3.org
• [Bug 6357] <script> start tag parsing bugzilla@jessica.w3.org
• [Bug 6434] plugins inside fallback content shouldn't be instantiated bugzilla@jessica.w3.org
• [Bug 6351] Add event handler attributes for all events defined in HTML5 bugzilla@jessica.w3.org
• [Bug 6423] Names of confidence flag states inconsistent bugzilla@jessica.w3.org
• [Bug 6440] To which elements applies the formatBlock command? bugzilla@jessica.w3.org
• [Bug 6350] Port examples from WF2 to HTML5 bugzilla@jessica.w3.org
• [Bug 6336] XSLT-compat doctype only allowed for use by XSLT bugzilla@jessica.w3.org
• [Bug 6476] cross-origin media element loads and progress events bugzilla@jessica.w3.org
• [Bug 6390] Add a note about reaching after head state and the fragment mode bugzilla@jessica.w3.org
• [Bug 6339] Define how to deal with onload, ononline, and other document/window-level events bugzilla@jessica.w3.org
• [Bug 6389] Avoid double parse error on EOF in DOCTYPE state bugzilla@jessica.w3.org
• [Bug 6349] Rewrite the entire script processing model again bugzilla@jessica.w3.org
• [Bug 6370] Float exponent part unclear about length of sequence bugzilla@jessica.w3.org
• [Bug 6352] Port acknowledgements from WF2 to HTML5 bugzilla@jessica.w3.org
• [Bug 6356] 00:99:00 is a valid time string bugzilla@jessica.w3.org
• [Bug 6257] Please specify document.write()-safe points in the parse bugzilla@jessica.w3.org
• [Bug 6236] scroll bar placement in frames bugzilla@jessica.w3.org
• [Bug 6153] Process <eventsource> feedback bugzilla@jessica.w3.org
• [Bug 6143] Linkify "pending external script" bugzilla@jessica.w3.org
• [Bug 6127] Deal with origin details in WebSocket and postMessage feedback bugzilla@jessica.w3.org
• [Bug 6256] Mutation event behavior on document.open() unspecified bugzilla@jessica.w3.org
• [Bug 6182] WebIDL - strokeStyle and fillStyle should be of type 'any' not 'DOMObject' bugzilla@jessica.w3.org
• [Bug 6103] video section editorial issues bugzilla@jessica.w3.org
• [Bug 6098] input type=foo as an element-level section bugzilla@jessica.w3.org
• [Bug 6102] Please do not break applet element in HTML 5 bugzilla@jessica.w3.org
• [Bug 6177] Process Workers feedback bugzilla@jessica.w3.org
• [Bug 6176] Process WebSocket feedback bugzilla@jessica.w3.org
• [Bug 6258] Changing the encoding doesn't cover non-idempotent navigation bugzilla@jessica.w3.org
• [Bug 6101] media elements - ready states - events should be async bugzilla@jessica.w3.org
• [Bug 6181] Process table feedback (including headers='" issue) bugzilla@jessica.w3.org
• [Bug 6134] Run-on sentence in HTML5 spec bugzilla@jessica.w3.org
• [Bug 6100] Process postMessage feedback bugzilla@jessica.w3.org
• [Bug 6099] Process notification feedback bugzilla@jessica.w3.org
• [Bug 6034] Process <video> feedback bugzilla@jessica.w3.org
• [Bug 6104] <video> and <audio> should prevent cross-origin media loads bugzilla@jessica.w3.org
• [Bug 6035] Process appcache feedback bugzilla@jessica.w3.org
• [Bug 6057] in the audio portion of the spec, at the end of 4.7.8.0 it mentions "If the src argument is present..." but the example given calls it the argument 'url' bugzilla@jessica.w3.org
• [Bug 6052] Should propagate uncaught exceptions from workers to their owner bugzilla@jessica.w3.org
• [Bug 5989] alt="" bugzilla@jessica.w3.org
• [Bug 6038] "noframes", "script", "style", "title" in 'after head' mode pop prematurely bugzilla@jessica.w3.org
• [Bug 6037] Elaborate on Web compat characteristics of task queue interaction bugzilla@jessica.w3.org
• [Bug 6033] Forms section bugzilla@jessica.w3.org
• [Bug 5997] Define script execution for XHTML5 bugzilla@jessica.w3.org
• [Bug 5991] workers bugzilla@jessica.w3.org
• [Bug 5866] SVG in HTML bugzilla@jessica.w3.org
• [Bug 5990] SVG in HTML bugzilla@jessica.w3.org
• [Bug 5944] Unclear wording, section 8.2.3.1 bugzilla@jessica.w3.org
• [Bug 5937] make cache manifest syntax more extensible bugzilla@jessica.w3.org
• [Bug 5974] Language tag sameness should probably be ASCII case-insensitive bugzilla@jessica.w3.org
• [Bug 5909] Need a solution for replaceable properties bugzilla@jessica.w3.org
• [Bug 5936] Offline cache syntax section needs an example bugzilla@jessica.w3.org
• [Bug 5994] add note in syntax section bugzilla@jessica.w3.org
• [Bug 5927] WF2: HTMLInputElement need some improvements bugzilla@jessica.w3.org
• [Bug 5881] Make tokeniser data states headers visible in table of contents bugzilla@jessica.w3.org
• [Bug 5858] Case marked as fragment when it can occur at other times bugzilla@jessica.w3.org
• [Bug 5856] height/width DOM attributes in combination with display:none bugzilla@jessica.w3.org
• [Bug 5883] data: URLs bugzilla@jessica.w3.org
• [Bug 5846] Accessing Object Parameters from an Embedded SVG bugzilla@jessica.w3.org
• [Bug 5863] Tokeniser: "Bogus comment" state unclear bugzilla@jessica.w3.org
• [Bug 5839] Work on Worker Threads bugzilla@jessica.w3.org
• [Bug 5859] Spec doesn't handle unknown schemes bugzilla@jessica.w3.org
• [Bug 5851] Consider adding .toArray() on NodeList and HTMLCollection bugzilla@jessica.w3.org
• [Bug 5830] Work on video bugzilla@jessica.w3.org
• [Bug 5848] Write the "fetching" section bugzilla@jessica.w3.org
• [Bug 5850] JS global object bugzilla@jessica.w3.org
• [Bug 5831] WebIDL: mark up constructors in IDL bugzilla@jessica.w3.org
• [Bug 5835] no apparent mechanism for applying a caption to a fieldset bugzilla@jessica.w3.org
• [Bug 5815] foreignObject in the SVG namespace should be scoping bugzilla@jessica.w3.org
• [Bug 5834] <area alt=""> has no author-level conformance requirement bugzilla@jessica.w3.org
• [Bug 5820] Work on WebSockets bugzilla@jessica.w3.org
• [Bug 5814] WebIDL: Resolve the callback issue bugzilla@jessica.w3.org
• [Bug 5809] Mitigate data loss when conforming documents are coerced to XML 1.0 bugzilla@jessica.w3.org
• [Bug 5807] User Agent display of title attribute content not defined bugzilla@jessica.w3.org
• [Bug 5823] Scope allowable on a td bugzilla@jessica.w3.org
• [Bug 5833] Work on standalone apps ideas bugzilla@jessica.w3.org
• [Bug 5801] Conformance rules for xmlns unintuitively different for HTML and foreign content bugzilla@jessica.w3.org
• [Bug 5793] Cross-reference "as if" bugzilla@jessica.w3.org
• [Bug 5777] referencing subordinate text or asides should be through an alternate attribute bugzilla@jessica.w3.org
• [Bug 5796] <li><div><p><li> no longer matches IE bugzilla@jessica.w3.org
• [Bug 5802] No mention of %uXXXX escapes bugzilla@jessica.w3.org
• [Bug 5798] Deferring end tag eating to after head gives weird errors bugzilla@jessica.w3.org
• [Bug 5773] Authors need more control over handling of linked resources bugzilla@jessica.w3.org
• [Bug 5792] li/dd/dt end tag in body when no corresponding elt on stack bugzilla@jessica.w3.org
• [Bug 5776] Authors need more control over handling of embedded resources bugzilla@jessica.w3.org
• [Bug 5772] [blocked on sandbox="" implementations] ID scoping for content aggregators (<iframe doc="">) bugzilla@jessica.w3.org
• [Bug 5757] MediaElement features are needed on OBJECT element bugzilla@jessica.w3.org
• [Bug 5755] Need to expose media metadata properties bugzilla@jessica.w3.org
• [Bug 5754] List elements content model issues bugzilla@jessica.w3.org
• [Bug 5753] parsing issues with legacy UAs bugzilla@jessica.w3.org

Sunday, 18 April 2010

• Re: computing atom:updated, was: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Julian Reschke
• Re: ISSUE 86 and removing atom transform section - focusing Maciej Stachowiak

Saturday, 17 April 2010

• Re: ISSUE 86 and removing atom transform section - focusing Tab Atkins Jr.
• Re: ISSUE 86 and removing atom transform section - focusing Shelley Powers
• Re: TAG ACTION-407 -- text/html media type and legacy Henry S. Thompson
• Re: ISSUE 86 and removing atom transform section - focusing Julian Reschke
• Re: ISSUE 86 and removing atom transform section - focusing Maciej Stachowiak
• Re: ISSUE 86 and removing atom transform section - focusing Julian Reschke
• Re: ISSUE 86 and removing atom transform section - focusing Maciej Stachowiak
• Re: ISSUE 86 and removing atom transform section - focusing Sam Ruby
• Re: ISSUE 86 and removing atom transform section - focusing Tab Atkins Jr.
• Re: ISSUE 86 and removing atom transform section - focusing Sam Ruby

Friday, 16 April 2010

• Re: ISSUE 86 and removing atom transform section - focusing Shelley Powers
• Re: ISSUE 86 and removing atom transform section - focusing Leif Halvard Silli
• Re: ISSUE 86 and removing atom transform section - focusing Steven Roussey
• Re: ISSUE 86 and removing atom transform section - focusing Maciej Stachowiak
• Re: ISSUE 86 and removing atom transform section - focusing Tab Atkins Jr.
• Re: ISSUE 86 and removing atom transform section - focusing Maciej Stachowiak
• Re: ISSUE 86 and removing atom transform section - focusing Steven Roussey
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Tab Atkins Jr.
• Re: ISSUE 86 and removing atom transform section - focusing Julian Reschke
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Ian Hickson
• ISSUE 86 and removing atom transform section - focusing Shelley Powers
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Ian Hickson
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Maciej Stachowiak
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Steven Roussey
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Toby Inkster
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Julian Reschke
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Tab Atkins Jr.
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Julian Reschke
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Tab Atkins Jr.
• computing atom:updated, was: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Julian Reschke
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Sam Ruby
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Julian Reschke
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Toby Inkster
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Maciej Stachowiak
• Re: Change Proposal for ISSUE-82 (Profile-Disambiguation), was: ISSUE-82 - profile-disambiguation - Chairs Solicit Proposals Maciej Stachowiak
• Re: TAG ACTION-407 -- text/html media type and legacy Noah Mendelsohn
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Tab Atkins Jr.

Thursday, 15 April 2010

• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Ian Hickson
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Edward O'Connor
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Sam Ruby
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Tab Atkins Jr.
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Edward O'Connor
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Sam Ruby
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Julian Reschke
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Ian Hickson
• will write change proposal for ISSUE-106 Shelley Powers
• Re: TAG ACTION-407 -- text/html media type and legacy Ian Hickson
• Re: looking for the use case for HTML->Atom conversion Tantek Celik
• Re: looking for the use case for HTML->Atom conversion Julian Reschke
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Edward O'Connor
• Re: looking for the use case for HTML->Atom conversion Edward O'Connor
• Re: TAG ACTION-407 -- text/html media type and legacy Henry S. Thompson
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Sam Ruby
• Re: looking for the use case for HTML->Atom conversion Tantek Celik
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Edward O'Connor
• Re: looking for the use case for HTML->Atom conversion Maciej Stachowiak
• Re: looking for the use case for HTML->Atom conversion Edward O'Connor
• Re: Change Proposal for Issue 110 ("Change Control for text/html-sandboxed media type") Julian Reschke
• Re: Change Proposal for Issue 110 ("Change Control for text/html-sandboxed media type") Sam Ruby
• HTML WG telcon 2010-04-15 - Testing Task Force Information Kris Krueger
• Re: Change Proposal for Issue 110 ("Change Control for text/html-sandboxed media type") Julian Reschke
• Re: Change Proposal for Issue 110 ("Change Control for text/html-sandboxed media type") Sam Ruby
• Re: Change Proposal for Issue 110 ("Change Control for text/html-sandboxed media type") Julian Reschke
• Re: ISSUE-107 Change Proposal Julian Reschke
• Re: Change Proposal for Issue 110 ("Change Control for text/html-sandboxed media type") Sam Ruby
• Change Proposal for Issue 110 ("Change Control for text/html-sandboxed media type") Julian Reschke
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Shelley Powers
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Sam Ruby
• Re: ISSUE 88 - Change proposal (updated) Sam Ruby
• Re: ISSUE 88 - Change proposal (updated) Leif Halvard Silli
• looking for the use case for HTML->Atom conversion Julian Reschke
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Julian Reschke
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Maciej Stachowiak
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Julian Reschke
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Maciej Stachowiak
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Julian Reschke
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Maciej Stachowiak
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Julian Reschke
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Maciej Stachowiak
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Julian Reschke
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Ian Hickson
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Julian Reschke
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Julian Reschke
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Julian Reschke
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Julian Reschke
• Re: ISSUE-100, ISSUE-89, ISSUE-106 Maciej Stachowiak
• Re: ISSUE-92 being blocked by ISSUE-32 Maciej Stachowiak
• ISSUE-92 being blocked by ISSUE-32 Shelley Powers
• ISSUE-100, ISSUE-89, ISSUE-106 Shelley Powers
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Sam Ruby
• Re: Issue 100 Zero-Edits Counter Proposal Tab Atkins Jr.
• Re: Issue 100 Zero-Edits Counter Proposal Maciej Stachowiak
• Re: Issue 100 Zero-Edits Counter Proposal Shelley Powers
• Re: Issue 100 Zero-Edits Counter Proposal Maciej Stachowiak
• Re: Issue 100 Zero-Edits Counter Proposal Tab Atkins Jr.
• Re: Issue 100 Zero-Edits Counter Proposal Shelley Powers

Wednesday, 14 April 2010

• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Shelley Powers
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Maciej Stachowiak
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Maciej Stachowiak
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Ian Hickson
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Sam Ruby
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Edward O'Connor
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Ian Hickson
• Re: Issue 100 Zero-Edits Counter Proposal Tab Atkins Jr.
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Sam Ruby
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Ian Hickson
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Shelley Powers
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Sam Ruby
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Julian Reschke
• Re: Change Proposal for ISSUE-82 (Profile-Disambiguation), was: ISSUE-82 - profile-disambiguation - Chairs Solicit Proposals Ian Hickson
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Ian Hickson
• Re: ISSUE-107 Change Proposal Ian Hickson
• Re: ISSUE-107 Change Proposal Joe D Williams
• Re: ISSUE-107 Change Proposal Maciej Stachowiak
• RE: ISSUE-107 Change Proposal John Foliot
• Re: ISSUE-107 Change Proposal Joe D Williams
• Re: ISSUE 88 - Change proposal (updated) Sam Ruby
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Sam Ruby
• Re: Change Proposal for ISSUE-82 (Profile-Disambiguation), was: ISSUE-82 - profile-disambiguation - Chairs Solicit Proposals Sam Ruby
• Re: Change definition of URL to normatively reference IRI specification using a well-defined interface Sam Ruby
• ISSUE-80 change proposal updated Steven Faulkner
• Re: ISSUE-107 Change Proposal Julian Reschke
• Re: ISSUE-107 Change Proposal Lachlan Hunt
• [Bug 9503] change controller for text/html-sandboxed media type bugzilla@jessica.w3.org
• Re: Change Proposal - 4.2.2 The title element / 4.2.5.1 Standard metadata names Lachlan Hunt
• Change Proposal - 4.2.2 The title element / 4.2.5.1 Standard metadata names Dean Leigh
• Change Proposal - 4.2.2 The title element / 4.2.5.1 Standard metadata names Dean Leigh
• [Bug 9503] change controller for text/html-sandboxed media type bugzilla@jessica.w3.org
• Re: Issue 100 Zero-Edits Counter Proposal Shelley Powers
• Re: Change Proposals toward Issue-9: "how accessibility works for <video> is unclear" Robert O'Callahan
• Re: ISSUE-92 Change Proposal Shelley Powers

Tuesday, 13 April 2010

• Re: ISSUE 88 - Change proposal (updated) Leif Halvard Silli
• Re: ISSUE-107 Change Proposal Jonas Sicking
• Re: ISSUE-107 Change Proposal Shelley Powers
• ISSUE-107 Change Proposal Julian Reschke
• Re: Issue 100 Zero-Edits Counter Proposal Tab Atkins Jr.
• Re: Issue 100 Zero-Edits Counter Proposal Julian Reschke
• Re: Issue 100 Zero-Edits Counter Proposal Tab Atkins Jr.
• Re: Issue 100 Zero-Edits Counter Proposal Shelley Powers
• Re: Issue 100 Zero-Edits Counter Proposal Tab Atkins Jr.
• Re: Issue 100 Zero-Edits Counter Proposal Tab Atkins Jr.
• Re: Issue 100 Zero-Edits Counter Proposal Shelley Powers
• Re: ISSUE-92 Change Proposal Shelley Powers
• Re: Issue 100 Zero-Edits Counter Proposal Julian Reschke
• Re: Change Proposals toward Issue-9: "how accessibility works for <video> is unclear" Henri Sivonen
• Re: Change Proposal for ISSUE-82 (Profile-Disambiguation), was: ISSUE-82 - profile-disambiguation - Chairs Solicit Proposals Jonas Sicking
• Re: Gloss standard terminology for resource/representation (ISSUE-81 Change Proposal) Julian Reschke
• Re: Gloss standard terminology for resource/representation (ISSUE-81 Change Proposal) Roy T. Fielding
• Re: Change Proposal for ISSUE-82 (Profile-Disambiguation), was: ISSUE-82 - profile-disambiguation - Chairs Solicit Proposals Maciej Stachowiak
• Re: Change Proposal for ISSUE-82 (Profile-Disambiguation), was: ISSUE-82 - profile-disambiguation - Chairs Solicit Proposals Ian Hickson
• Re: Change Proposal for ISSUE-82 (Profile-Disambiguation), was: ISSUE-82 - profile-disambiguation - Chairs Solicit Proposals Maciej Stachowiak
• Re: Gloss standard terminology for resource/representation (ISSUE-81 Change Proposal) Ian Hickson
• Re: Gloss standard terminology for resource/representation (ISSUE-81 Change Proposal) Maciej Stachowiak
• Re: ISSUE-92 Change Proposal Maciej Stachowiak
• Re: ISSUE-92 Change Proposal Tab Atkins Jr.
• Re: ISSUE-92 Change Proposal Shelley Powers
• Re: document.load: History and a proposal timeless
• Re: ISSUE-92 Change Proposal Tab Atkins Jr.
• Re: ISSUE-92 Change Proposal Tab Atkins Jr.
• Issue 100 Zero-Edits Counter Proposal Tab Atkins Jr.

Monday, 12 April 2010

• RE: Null change proposal for ISSUE-88 (mark II): proposed note CE Whitehead
• RE: Change Proposals toward Issue-9: "how accessibility works for <video> is unclear" Sean Hayes
• Re: Gloss standard terminology for resource/representation (ISSUE-81 Change Proposal) Dan Connolly
• Re: ISSUE-90, ISSUE-91, ISSUE-93, ISSUE-95, ISSUE-96, ISSSUE-97: (new semantic elements/attributes) - Chairs Solicit Alternate Proposals or Counter-Proposals Tab Atkins Jr.
• Re: Change Proposals toward Issue-9: "how accessibility works for <video> is unclear" Henri Sivonen
• Re: Change Proposals toward Issue-9: "how accessibility works for <video> is unclear" Maciej Stachowiak
• Re: Change Proposals toward Issue-9: "how accessibility works for <video> is unclear" Silvia Pfeiffer
• Re: ISSUE-90, ISSUE-91, ISSUE-93, ISSUE-95, ISSUE-96, ISSSUE-97: (new semantic elements/attributes) - Chairs Solicit Alternate Proposals or Counter-Proposals Jeremy Keith
• Re: document.write from script-inserted external script Henri Sivonen
• Re: Change Proposals toward Issue-9: "how accessibility works for <video> is unclear" Joe D Williams
• Re: Change Proposals toward Issue-9: "how accessibility works for <video> is unclear" Joe D Williams
• Re: Change Proposals toward Issue-9: "how accessibility works for <video> is unclear" Anne van Kesteren
• Re: Change Proposals toward Issue-9: "how accessibility works for <video> is unclear" Joe D Williams
• RE: Null change proposal for ISSUE-88 (mark II): proposed note Leif Halvard Silli
• Re: Change Proposals toward Issue-9: "how accessibility works for <video> is unclear" Anne van Kesteren
• Re: Change Proposals toward Issue-9: "how accessibility works for <video> is unclear" Joe D Williams
• Re: Change Proposals toward Issue-9: "how accessibility works for <video> is unclear" Anne van Kesteren
• RE: Change Proposals toward Issue-9: "how accessibility works for <video> is unclear" Sean Hayes
• Re: Change Proposals toward Issue-9: "how accessibility works for <video> is unclear" Silvia Pfeiffer
• Re: Change Proposals toward Issue-9: "how accessibility works for <video> is unclear" Joe D Williams
• Re: Change Proposals toward Issue-9: "how accessibility works for <video> is unclear" Silvia Pfeiffer

Sunday, 11 April 2010

• RE: Null change proposal for ISSUE-88 (mark II): proposed note CE Whitehead
• RE: Change Proposals toward Issue-9: "how accessibility works for <video> is unclear" Sean Hayes

Saturday, 10 April 2010

• RE: Null change proposal for ISSUE-88 (mark II): proposed note Leif Halvard Silli
• Re: Change definition of URL to normatively reference IRI specification using a well-defined interface Julian Reschke

Friday, 9 April 2010

• Change Proposals toward Issue-9: "how accessibility works for <video> is unclear" Silvia Pfeiffer
• Re: Change definition of URL to normatively reference IRI specification using a well-defined interface Ian Hickson
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Julian Reschke
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Jonas Sicking
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Maciej Stachowiak
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Sam Ruby
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Shelley Powers
• Re: Change definition of URL to normatively reference IRI specification using a well-defined interface Mark Davis ☕
• Re: Change definition of URL to normatively reference IRI specification using a well-defined interface Julian Reschke
• Re: Change definition of URL to normatively reference IRI specification using a well-defined interface Mark Davis ☕
• Re: Change definition of URL to normatively reference IRI specification using a well-defined interface Erik van der Poel
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Julian Reschke

Sunday, 4 April 2010

• "mail a new topic" - Futures for User Interface Specifications BillClare3@aol.com

Friday, 9 April 2010

• Re: Change definition of URL to normatively reference IRI specification using a well-defined interface Erik van der Poel
• Re: Change definition of URL to normatively reference IRI specification using a well-defined interface Anne van Kesteren
• Re: Change definition of URL to normatively reference IRI specification using a well-defined interface Slim Amamou
• Re: Null change proposal for ISSUE-88 (mark II): proposed note Leif Halvard Silli
• Re: ISSUE 88 - Change proposal (updated) Maciej Stachowiak
• Re: Change definition of URL to normatively reference IRI specification using a well-defined interface Ian Hickson
• Re: Null change proposal for ISSUE-88 (mark II): proposed note Leif Halvard Silli
• RE: Null change proposal for ISSUE-88 (mark II): proposed note Richard Ishida
• Re: Change definition of URL to normatively reference IRI specification using a well-defined interface Julian Reschke
• Re: Null change proposal for ISSUE-88 (mark II): proposed note Julian Reschke
• Re: Change definition of URL to normatively reference IRI specification using a well-defined interface Anne van Kesteren
• ISSUE 88 - Change proposal (updated) Leif Halvard Silli
• Re: Null change proposal for ISSUE-88 (mark II): proposed note Maciej Stachowiak
• Re: Change definition of URL to normatively reference IRI specification using a well-defined interface Maciej Stachowiak
• Re: Null change proposal for ISSUE-88 (mark II): proposed note Julian Reschke
• Re: Change definition of URL to normatively reference IRI specification using a well-defined interface Martin J. Dürst
• ISSUE-88 question to the chairs Leif Halvard Silli
• Re: Null change proposal for ISSUE-88 (mark II): proposed note Leif Halvard Silli
• Re: I-D Action:draft-nottingham-http-link-header-09.txt Mark Nottingham
• Re: Change definition of URL to normatively reference IRI specification using a well-defined interface Ian Hickson
• Re: Proposal to make Content-Language pragma non-conforming altogether for ISSUE-88 (mark I) Leif Halvard Silli
• Re: Null change proposal for ISSUE-88 (mark II): proposed note Ian Hickson
• Re: Null change proposal for ISSUE-88 (mark II): proposed note Leif Halvard Silli
• Proposal to make Content-Language pragma non-conforming altogether for ISSUE-88 (mark I) Ian Hickson
• Null change proposal for ISSUE-88 (mark IV) Ian Hickson

Thursday, 8 April 2010

• Re: Change Proposal for ISSUE-82 (Profile-Disambiguation), was: ISSUE-82 - profile-disambiguation - Chairs Solicit Proposals Ian Hickson
• Re: Null change proposal for ISSUE-88 (mark II): proposed note Ian Hickson
• Null change proposal for ISSUE-88 (mark II): proposed note Richard Ishida
• Re: Fwd: I-D Action:draft-nottingham-http-link-header-09.txt Toby Inkster
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Maciej Stachowiak
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Shelley Powers
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Sam Ruby
• Re: Change definition of URL to normatively reference IRI specification using a well-defined interface Ted Hardie
• Re: ISSUE-99 (meta-scheme): Chairs Solicit Proposals Julian Reschke
• Re: Change Proposal for ISSUE-82 (Profile-Disambiguation), was: ISSUE-82 - profile-disambiguation - Chairs Solicit Proposals Maciej Stachowiak

Wednesday, 7 April 2010

• Re: Styling Controls Mike Taylor

Thursday, 8 April 2010

• Re: ISSUE-99 (meta-scheme): Chairs Solicit Proposals Tantek Celik
• Re: ISSUE-99 (meta-scheme): Chairs Solicit Proposals Julian Reschke
• Re: Change Proposal for ISSUE-82 (Profile-Disambiguation), was: ISSUE-82 - profile-disambiguation - Chairs Solicit Proposals Sam Ruby
• Re: Change Proposal for ISSUE-82 (Profile-Disambiguation), was: ISSUE-82 - profile-disambiguation - Chairs Solicit Proposals Jonas Sicking
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Julian Reschke
• Re: Change Proposal for ISSUE-82 (Profile-Disambiguation), was: ISSUE-82 - profile-disambiguation - Chairs Solicit Proposals Julian Reschke
• Re: Change definition of URL to normatively reference IRI specification using a well-defined interface Martin J. Dürst
• Re: Change Proposal for ISSUE-82 (Profile-Disambiguation) Jonas Sicking
• Re: Gloss standard terminology for resource/representation (ISSUE-81 Change Proposal) Ian Hickson
• Re: Change definition of URL to normatively reference IRI specification using a well-defined interface Maciej Stachowiak
• FW: Second Last Call: draft-duerst-mailto-bis (The 'mailto' URI Scheme) to Proposed Standard Larry Masinter
• RE: Change definition of URL to normatively reference IRI specification using a well-defined interface Ian Hickson
• Re: Gloss standard terminology for resource/representation (ISSUE-81 Change Proposal) Julian Reschke
• Re: Change Proposal for ISSUE-82 (Profile-Disambiguation), was: ISSUE-82 - profile-disambiguation - Chairs Solicit Proposals Maciej Stachowiak
• Re: Change Proposal for ISSUE-82 (Profile-Disambiguation), was: ISSUE-82 - profile-disambiguation - Chairs Solicit Proposals Julian Reschke
• RE: Change definition of URL to normatively reference IRI specification using a well-defined interface Larry Masinter
• Re: Change Proposal for ISSUE-82 (Profile-Disambiguation), was: ISSUE-82 - profile-disambiguation - Chairs Solicit Proposals Jonas Sicking
• Re: Gloss standard terminology for resource/representation (ISSUE-81 Change Proposal) Ian Hickson
• Re: Gloss standard terminology for resource/representation (ISSUE-81 Change Proposal) Maciej Stachowiak
• Re: Gloss standard terminology for resource/representation (ISSUE-81 Change Proposal) Ian Hickson
• Re: Change Proposal for ISSUE-82 (Profile-Disambiguation), was: ISSUE-82 - profile-disambiguation - Chairs Solicit Proposals Maciej Stachowiak
• Re: Change Proposal for ISSUE-82 (Profile-Disambiguation), was: ISSUE-82 - profile-disambiguation - Chairs Solicit Proposals Maciej Stachowiak
• Re: waiting and seeking events in media element seek algorithm Simon Pieters

Wednesday, 7 April 2010

• Re: waiting and seeking events in media element seek algorithm Ian Hickson
• Re: ISSUE-90, ISSUE-91, ISSUE-93, ISSUE-95, ISSUE-96, ISSSUE-97: (new semantic elements/attributes) - Chairs Solicit Alternate Proposals or Counter-Proposals Edward O'Connor
• Re: Styling Controls (was: native elements versus scripted) Maciej Stachowiak
• Re: Change Proposal for ISSUE-82 (Profile-Disambiguation), was: ISSUE-82 - profile-disambiguation - Chairs Solicit Proposals Maciej Stachowiak
• Re: {agenda} HTML WG telcon 2010-04-01: action items, decision policy update, issue status Maciej Stachowiak
• Re: Change Proposal for ISSUE-82 (Profile-Disambiguation), was: ISSUE-82 - profile-disambiguation - Chairs Solicit Proposals Jonas Sicking
• Re: Change Proposal for ISSUE-82 (Profile-Disambiguation) Anne van Kesteren
• Re: Change Proposal for ISSUE-82 (Profile-Disambiguation), was: ISSUE-82 - profile-disambiguation - Chairs Solicit Proposals Jonas Sicking
• Re: Change Proposal for ISSUE-82 (Profile-Disambiguation), was: ISSUE-82 - profile-disambiguation - Chairs Solicit Proposals Julian Reschke
• Re: Change Proposal for ISSUE-82 (Profile-Disambiguation), was: ISSUE-82 - profile-disambiguation - Chairs Solicit Proposals Jonas Sicking
• Change Proposal for ISSUE-82 (Profile-Disambiguation), was: ISSUE-82 - profile-disambiguation - Chairs Solicit Proposals Julian Reschke
• Re: Styling Controls Shelley Powers
• HTML WG F2F meeting, Nov 4-5 at TPAC 2010, Lyon, France Paul Cotton
• Re: native elements versus scripted Leif Halvard Silli
• Re: Null change proposal for ISSUE-88 (mark III) Leif Halvard Silli
• Re: Styling Controls (was: native elements versus scripted) Shelley Powers
• Re: Styling Controls Shelley Powers
• Re: Null change proposal for ISSUE-88 (mark III) Leif Halvard Silli
• Re: Comments to proposal to remove FRAMESET Leif Halvard Silli
• Comments to proposal to remove FRAMESET Kurt Lanzenhofer
• Re: {agenda} HTML WG telcon 2010-04-01: action items, decision policy update, issue status Julian Reschke
• Re: Change Proposal for ISSUE-101 (us-ascii-ref) Sam Ruby
• Re: Change Proposal for ISSUE-101 (us-ascii-ref) Julian Reschke
• styling of video controls/captions (was Re: native elements versus scripted) Maciej Stachowiak
• RE: native elements versus scripted Sean Hayes
• Re: native elements versus scripted Silvia Pfeiffer
• Re: ISSUE-105 (canvas-usemap): Chairs Solicit Proposals Maciej Stachowiak
• Re: native elements versus scripted Maciej Stachowiak
• Re: Change definition of URL to normatively reference IRI specification using a well-defined interface Maciej Stachowiak
• Re: native elements versus scripted Tantek Çelik
• Re: Change definition of URL to normatively reference IRI specification using a well-defined interface Julian Reschke
• Re: Change definition of URL to normatively reference IRI specification using a well-defined interface Julian Reschke
• Re: Change definition of URL to normatively reference IRI specification using a well-defined interface Maciej Stachowiak
• Re: Change definition of URL to normatively reference IRI specification using a well-defined interface Julian Reschke
• Re: native elements versus scripted Doug Schepers
• Re: native elements versus scripted Andrew Fedoniouk
• Re: Styling Controls Jonas Sicking
• Re: Styling Controls (was: native elements versus scripted) Maciej Stachowiak
• Re: Styling Controls Doug Schepers
• Re: native elements versus scripted Maciej Stachowiak
• RE: native elements versus scripted John Foliot
• Re: native elements versus scripted Doug Schepers
• Re: Styling Controls Doug Schepers
• Re: native elements versus scripted Silvia Pfeiffer
• Re: Styling Controls (was: native elements versus scripted) Shelley Powers
• RE: Styling Controls (was: native elements versus scripted) John Foliot
• Re: native elements versus scripted Maciej Stachowiak
• Re: Styling Controls (was: native elements versus scripted) Shelley Powers
• Re: Null change proposal for ISSUE-88 (mark III) Ian Hickson
• Re: native elements versus scripted Doug Schepers
• Styling Controls (was: native elements versus scripted) Doug Schepers
• Re: native elements versus scripted Maciej Stachowiak
• Re: native elements versus scripted Shelley Powers
• Re: Null change proposal for ISSUE-88 (mark III) Leif Halvard Silli
• Re: native elements versus scripted Jonas Sicking
• Re: native elements versus scripted Jonas Sicking
• Re: native elements versus scripted Shelley Powers
• Re: native elements versus scripted Maciej Stachowiak
• Re: ISSUE-90, ISSUE-91, ISSUE-93, ISSUE-95, ISSUE-96, ISSSUE-97: (new semantic elements/attributes) - Chairs Solicit Alternate Proposals or Counter-Proposals Maciej Stachowiak
• RE: Null change proposal for ISSUE-88 (mark II) CE Whitehead
• Re: change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Maciej Stachowiak
• Fwd: accept attribute on file input should allow in-browser upload Jeff Schiller

Tuesday, 6 April 2010

• Re: microdata: the properties of an item Ian Hickson
• Re: Change definition of URL to normatively reference IRI specification using a well-defined interface Ian Hickson
• Re: Gloss standard terminology for resource/representation (ISSUE-81 Change Proposal) Maciej Stachowiak
• Re: Gloss standard terminology for resource/representation (ISSUE-81 Change Proposal) Ian Hickson
• Re: Change definition of URL to normatively reference IRI specification using a well-defined interface Maciej Stachowiak
• Re: Change definition of URL to normatively reference IRI specification using a well-defined interface Maciej Stachowiak
• Re: ISSUE-90, ISSUE-91, ISSUE-93, ISSUE-95, ISSUE-96, ISSSUE-97: (new semantic elements/attributes) - Chairs Solicit Alternate Proposals or Counter-Proposals Maciej Stachowiak
• Re: Microdata to RDF conversion Ian Hickson
• Re: ISSUE-90, ISSUE-91, ISSUE-93, ISSUE-95, ISSUE-96, ISSSUE-97: (new semantic elements/attributes) - Chairs Solicit Alternate Proposals or Counter-Proposals Shelley Powers
• Re: native elements versus scripted Shelley Powers
• Re: ISSUE-90, ISSUE-91, ISSUE-93, ISSUE-95, ISSUE-96, ISSSUE-97: (new semantic elements/attributes) - Chairs Solicit Alternate Proposals or Counter-Proposals Maciej Stachowiak
• Re: native elements versus scripted Jonas Sicking
• Re: ISSUE-105 (canvas-usemap): Chairs Solicit Proposals Steven Faulkner
• Re: ISSUE-90, ISSUE-91, ISSUE-93, ISSUE-95, ISSUE-96, ISSSUE-97: (new semantic elements/attributes) - Chairs Solicit Alternate Proposals or Counter-Proposals Julian Reschke
• Re: Gloss standard terminology for resource/representation (ISSUE-81 Change Proposal) Julian Reschke
• Re: ISSUE-90, ISSUE-91, ISSUE-93, ISSUE-95, ISSUE-96, ISSSUE-97: (new semantic elements/attributes) - Chairs Solicit Alternate Proposals or Counter-Proposals Shelley Powers
• Re: ISSUE-90, ISSUE-91, ISSUE-93, ISSUE-95, ISSUE-96, ISSSUE-97: (new semantic elements/attributes) - Chairs Solicit Alternate Proposals or Counter-Proposals Sam Ruby
• change proposal for issue-86, was: ISSUE-86 - atom-id-stability - Chairs Solicit Proposals Julian Reschke
• Re: ISSUE-90, ISSUE-91, ISSUE-93, ISSUE-95, ISSUE-96, ISSSUE-97: (new semantic elements/attributes) - Chairs Solicit Alternate Proposals or Counter-Proposals Jonas Sicking
• Re: ISSUE-90, ISSUE-91, ISSUE-93, ISSUE-95, ISSUE-96, ISSSUE-97: (new semantic elements/attributes) - Chairs Solicit Alternate Proposals or Counter-Proposals Shelley Powers
• Fwd: native elements versus scripted Shelley Powers
• ISSUE-90, ISSUE-91, ISSUE-93, ISSUE-95, ISSUE-96, ISSSUE-97: (new semantic elements/attributes) - Chairs Solicit Alternate Proposals or Counter-Proposals Maciej Stachowiak
• ISSUE-106 (obsconf): Chairs Solicit Proposals Maciej Stachowiak
• ISSUE-105 (canvas-usemap): Chairs Solicit Proposals Maciej Stachowiak
• Re: Gloss standard terminology for resource/representation (ISSUE-81 Change Proposal) Dan Connolly
• Re: native elements versus scripted Jonas Sicking
• Re: ISSUE-93 Change Proposal Shelley Powers
• Re: ISSUE-93 Change Proposal Maciej Stachowiak
• Re: Change definition of URL to normatively reference IRI specification using a well-defined interface Julian Reschke
• Re: ISSUE-96 Change Proposal Maciej Stachowiak
• Re: ISSUE-97 Change Proposal Maciej Stachowiak
• Re: ISSUE-95 Change Proposal Maciej Stachowiak
• Re: ISSUE-91 Change Proposal Maciej Stachowiak
• Re: ISSUE-90 Change Proposal Maciej Stachowiak
• Re: ISSUE-94 Change Proposal Maciej Stachowiak
• ISSUE-41 decentralized-extensibility: No formal counter-proposal period Maciej Stachowiak
• Re: Reminder of Change Proposal deadlines today Maciej Stachowiak
• Re: Change definition of URL to normatively reference IRI specification using a well-defined interface Ian Hickson
• Deadlines for ISSUE-82 and ISSUE-86 extended; warning about future deadlines Maciej Stachowiak
• Re: Gloss standard terminology for resource/representation (ISSUE-81 Change Proposal) Maciej Stachowiak
• Re: Gloss standard terminology for resource/representation (ISSUE-81 Change Proposal) Maciej Stachowiak
• Re: Gloss standard terminology for resource/representation (ISSUE-81 Change Proposal) Ian Hickson
• Re: Change definition of URL to normatively reference IRI specification using a well-defined interface Julian Reschke
• Re: Gloss standard terminology for resource/representation (ISSUE-81 Change Proposal) Dan Connolly
• Re: Gloss standard terminology for resource/representation (ISSUE-81 Change Proposal) Maciej Stachowiak
• Re: Gloss standard terminology for resource/representation (ISSUE-81 Change Proposal) Ian Hickson
• Re: Gloss standard terminology for resource/representation (ISSUE-81 Change Proposal) Dan Connolly
• Re: Change definition of URL to normatively reference IRI specification using a well-defined interface Ian Hickson
• Re: Gloss standard terminology for resource/representation (ISSUE-81 Change Proposal) Ian Hickson
• Re: native elements versus scripted Shelley Powers
• Re: native elements versus scripted Shelley Powers
• Re: native elements versus scripted Shelley Powers
• Gloss standard terminology for resource/representation (ISSUE-81 Change Proposal) Dan Connolly
• native elements versus scripted Shelley Powers
• [Fwd: Second Last Call: draft-duerst-mailto-bis (The 'mailto' URI Scheme) to Proposed Standard] Alexey Melnikov
• Re: Null change proposal for ISSUE-88 (mark II) Leif Halvard Silli
• RE: Null change proposal for ISSUE-88 (mark II) Leif Halvard Silli
• Re: Change definition of URL to normatively reference IRI specification using a well-defined interface Julian Reschke
• RE: Null change proposal for ISSUE-88 (mark II) CE Whitehead
• Reminder of Change Proposal deadlines today Maciej Stachowiak
• Re: Change definition of URL to normatively reference IRI specification using a well-defined interface Maciej Stachowiak
• Re: Null change proposal for ISSUE-88 (mark III) Maciej Stachowiak
• Re: Change definition of URL to normatively reference IRI specification using a well-defined interface Ian Hickson

Monday, 5 April 2010

• Change definition of URL to normatively reference IRI specification using a well-defined interface Ian Hickson
• Re: Null change proposal for ISSUE-88 (mark II) Leif Halvard Silli
• RE: Trailing dot in email (Was: Re: Possible bug according to Rasmus Leerdorf) Larry Masinter
• RE: Removal of other semantic elements John Foliot
• Re: Removal of other semantic elements Maciej Stachowiak
• RE: Removal of other semantic elements John Foliot
• Fwd: Removal of other semantic elements Shelley Powers
• Re: Trailing dot in email (Was: Re: Possible bug according to Rasmus Leerdorf) Lars Gunther
• Re: Removal of other semantic elements Laura Carlson
• Re: Trailing dot in email (Was: Re: Possible bug according to Rasmus Leerdorf) Thomas Broyer
• Re: Bug stats update - March, 2010 - CORRECTED Maciej Stachowiak
• Re: new dates for issue items based on today's HTML WG teleconference Silvia Pfeiffer
• Bug stats update - March, 2010 Maciej Stachowiak
• Re: new dates for issue items based on today's HTML WG teleconference Maciej Stachowiak
• Re: new dates for issue items based on today's HTML WG teleconference Maciej Stachowiak
• Re: new dates for issue items based on today's HTML WG teleconference Silvia Pfeiffer
• Re: Null change proposal for ISSUE-88 (mark II) Jonas Sicking
• Re: Null change proposal for ISSUE-88 (mark II) Leif Halvard Silli
• Re: Removal of other semantic elements Jonas Sicking
• Re: Removal of other semantic elements Jonas Sicking
• Re: Removal of other semantic elements Shelley Powers
• Re: Removal of other semantic elements Shelley Powers
• Re: Removal of other semantic elements Shelley Powers

Sunday, 4 April 2010

• Re: Removal of other semantic elements Laura Carlson
• Re: Removal of other semantic elements Shelley Powers
• Re: Removal of other semantic elements Maciej Stachowiak
• RE: Request for Volunteers: Polyglot spec Larry Masinter
• Re: Removal of other semantic elements Maciej Stachowiak
• Re: Where is the editor's draft? Ian Hickson
• Where is the editor's draft? Leif Halvard Silli
• Re: Trailing dot in email (Was: Re: Possible bug according to Rasmus Leerdorf) Maciej Stachowiak
• Re: Null change proposal for ISSUE-88 (mark II) Leif Halvard Silli
• Re: Removal of other semantic elements Shelley Powers
• Trailing dot in email (Was: Re: Possible bug according to Rasmus Leerdorf) Lars Gunther
• Re: Removal of other semantic elements Steven Faulkner
• Re: Null change proposal for ISSUE-88 (mark II) Anne van Kesteren
• Re: Make reset button non-conforming Lars Gunther
• Re: Null change proposal for ISSUE-88 (mark II) Leif Halvard Silli
• Re: Null change proposal for ISSUE-88 (mark II) Leif Halvard Silli
• Re: Possible bug according to Rasmus Leerdorf Lars Gunther
• Re: Null change proposal for ISSUE-88 (mark II) Julian Reschke
• Re: Null change proposal for ISSUE-88 (mark II) Anne van Kesteren
• RE: Null change proposal for ISSUE-88 (mark II) Richard Ishida
• Re: Null change proposal for ISSUE-88 (mark II) Leif Halvard Silli
• Re: Null change proposal for ISSUE-88 (mark II) Leif Halvard Silli
• Re: Null change proposal for ISSUE-88 (mark II) Leif Halvard Silli
• Re: Null change proposal for ISSUE-88 (mark II) Leif Halvard Silli
• Null change proposal for ISSUE-88 (mark III) Ian Hickson
• Re: Null change proposal for ISSUE-88 (mark II) Maciej Stachowiak
• RE: Request for Volunteers: Polyglot spec Sebastien Lambla
• Re: Null change proposal for ISSUE-88 (mark II) Ian Hickson

Saturday, 3 April 2010

• Dave Hyatt has resigned as editor Maciej Stachowiak
• Re: Null change proposal for ISSUE-88 (mark II) Ian Hickson
• Re: I-D Action:draft-nottingham-http-link-header-09.txt Julian Reschke
• Re: Null change proposal for ISSUE-88 (mark II) Maciej Stachowiak
• Re: I-D Action:draft-nottingham-http-link-header-09.txt Maciej Stachowiak
• Re: Null change proposal for ISSUE-88 (mark II) Julian Reschke
• The use of MIME on the web: issues, toward a revised "finding" or joint W3C/IETF document Larry Masinter
• Fwd: I-D Action:draft-nottingham-http-link-header-09.txt Mark Nottingham
• Re: Null change proposal for ISSUE-88 (mark II) Kornel Lesinski
• Re: Null change proposal for ISSUE-88 (mark II) Maciej Stachowiak
• Re: Possible bug according to Rasmus Leerdorf Maciej Stachowiak
• RE: MIME registration and usage (WAS {agenda} HTML WG telcon 2010-04-01: action items, decision policy update, issue status) Paul Cotton
• Re: Null change proposal for ISSUE-88 (mark II) Julian Reschke
• Re: Null change proposal for ISSUE-88 (mark II) Sam Ruby
• Re: Null change proposal for ISSUE-88 (mark II) Anne van Kesteren
• Re: Null change proposal for ISSUE-88 (mark II) Leif Halvard Silli
• Re: Null change proposal for ISSUE-88 (mark II) Julian Reschke
• Possible bug according to Rasmus Leerdorf Lars Gunther
• Re: Null change proposal for ISSUE-88 (mark II) Kornel Lesinski

Friday, 2 April 2010

• Re: {agenda} HTML WG telcon 2010-04-01: action items, decision policy update, issue status Julian Reschke
• Re: Removal of other semantic elements Shelley Powers
• Re: Removal of other semantic elements Shelley Powers
• Re: Removal of other semantic elements Jonas Sicking
• Re: {agenda} HTML WG telcon 2010-04-01: action items, decision policy update, issue status Maciej Stachowiak
• Re: Removal of other semantic elements Maciej Stachowiak
• Re: Null change proposal for ISSUE-88 (mark II) Julian Reschke
• RE: Removal of other semantic elements John Foliot
• Removal of other semantic elements Jonas Sicking
• Null change proposal for ISSUE-88 (mark II) Ian Hickson
• Re: {agenda} HTML WG telcon 2010-04-01: action items, decision policy update, issue status Julian Reschke
• Re: ACTION-103 Follow up on the about: scheme Registration Julian Reschke

Thursday, 1 April 2010

• RE: ISSUE-88 / Re: what's the language of a document ? Phillips, Addison

Friday, 2 April 2010

• RE: ISSUE-88 / Re: what's the language of a document ? CE Whitehead
• Re: ISSUE-96 Change Proposal Shelley Powers
• Re: ISSUE-96 Change Proposal Shelley Powers
• Re: Request for Volunteers: Polyglot spec Karl Dubost
• RE: ISSUE-96 Change Proposal John Foliot

Thursday, 1 April 2010

• Re: Request for Volunteers: Polyglot spec Sam Ruby
• RE: ISSUE-88 / Re: what's the language of a document ? Ian Hickson
• Re: ISSUE-96 Change Proposal Shelley Powers
• RE: ISSUE-96 Change Proposal John Foliot
• Re: ISSUE-88 / Re: what's the language of a document ? Ian Hickson
• Re: ISSUE-96 Change Proposal CFIT
• Re: ISSUE-96 Change Proposal Jonas Sicking
• Re: ISSUE-96 Change Proposal Shelley Powers
• Re: ISSUE-96 Change Proposal Maciej Stachowiak
• Re: ISSUE-96 Change Proposal Shelley Powers
• RE: ISSUE-96 Change Proposal John Foliot
• Re: ISSUE-96 Change Proposal Steven Faulkner
• Re: ISSUE-96 Change Proposal CFIT
• Re: ISSUE-96 Change Proposal CFIT
• Re: ISSUE-96 Change Proposal Maciej Stachowiak
• Re: Request for Volunteers: Polyglot spec Jonas Sicking
• Re: ISSUE-88 / Re: what's the language of a document ? Maciej Stachowiak
• RE: ISSUE-88 / Re: what's the language of a document ? Richard Ishida
• Re: Request for Volunteers: Polyglot spec Dan Connolly
• Re: ISSUE-96 Change Proposal Shelley Powers
• Re: ISSUE-96 Change Proposal Shelley Powers
• Re: ISSUE-96 Change Proposal Doug Schepers
• Re: Request for Volunteers: Polyglot spec Jonas Sicking
• Re: Request for Volunteers: Polyglot spec Philip Taylor
• Re: ISSUE-96 Change Proposal Jonas Sicking
• Re: Request for Volunteers: Polyglot spec Jonas Sicking
• Re: ISSUE-96 Change Proposal Shelley Powers
• Re: Mouse-less browsing/Datepicker (was RE: ISSUE-96 Change Proposal) Jonas Sicking
• Re: ISSUE-96 Change Proposal Jonas Sicking
• Re: Request for Volunteers: Polyglot spec Sam Ruby
• Mouse-less browsing/Datepicker (was RE: ISSUE-96 Change Proposal) John Foliot
• Re: ISSUE-96 Change Proposal Shelley Powers
• Re: Request for Volunteers: Polyglot spec Jonas Sicking
• Re: ISSUE-96 Change Proposal Matt May
• Re: Request for Volunteers: Polyglot spec Sam Ruby
• Re: Request for Volunteers: Polyglot spec Dan Connolly
• Re: ISSUE-96 Change Proposal Maciej Stachowiak
• [minutes] 2010-04-01 HTML Teleconference Sam Ruby
• Re: ISSUE-96 Change Proposal Shelley Powers
• Re: Patial Change request proposal for Issue 74 Canvas accessibility Maciej Stachowiak
• Re: ISSUE-96 Change Proposal Shelley Powers
• Re: ISSUE-96 Change Proposal Jonas Sicking
• Re: Request for Volunteers: Polyglot spec Maciej Stachowiak
• Re: ISSUE-96 Change Proposal Bruce Lawson
• RE: Request for Volunteers: Polyglot spec Adrian Bateman
• Re: ISSUE-96 Change Proposal Maciej Stachowiak
• Re: ISSUE-96 Change Proposal Steven Faulkner
• Re: ISSUE-96 Change Proposal Jonas Sicking
• Re: ISSUE-96 Change Proposal Steven Faulkner
• Re: ISSUE-96 Change Proposal Jonas Sicking
• Re: ISSUE-96 Change Proposal Shelley Powers
• Re: ISSUE-92 Change Proposal Laura Carlson
• Re: ISSUE-96 Change Proposal Jonas Sicking
• Re: FW: Request that "conforming document" be better defined and more carefully referenced Michael(tm) Smith
• Re: ISSUE-92 Change Proposal Shelley Powers
• Re: Change proposals uploaded to Wiki - URLs, suggestions on Issue 92 table Maciej Stachowiak
• Re: ISSUE-94 Change Proposal Sam Ruby
• Re: ISSUE-94 Change Proposal Maciej Stachowiak
• Re: ISSUE-92 Change Proposal Laura Carlson
• Re: ISSUE-94 Change Proposal Jonas Sicking

Last message date: Friday, 30 April 2010 23:32:02 UTC