Monday, 30 November 2009
- [Bug 8404] Refocus the figure element back to being a figure
- Re: HTML CHANGE PROPOSAL; change definition of URL to normative reference to IRIBIS
- Re: Param
- [Bug 8401] Remove section 4.12 regarding idioms
- Re: ISSUE-83 ACTION-152 Change Proposal for the use of dt/dd in figure and details
- Re: ISSUE-83 ACTION-152 Change Proposal for the use of dt/dd in figure and details
- Re: Another possible compromise re namespaces in HTML
- Re: Param
Sunday, 29 November 2009
Saturday, 28 November 2009
- RE: HTML CHANGE PROPOSAL; change definition of URL to normative reference to IRIBIS
- Re: Param
- Re: ISSUE-83 ACTION-152 Change Proposal for the use of dt/dd in figure and details
- Re: ISSUE-83 ACTION-152 Change Proposal for the use of dt/dd in figure and details
- Re: Param
- Param
- Re: ISSUE-83 ACTION-152 Change Proposal for the use of dt/dd in figure and details
- Re: ISSUE-83 ACTION-152 Change Proposal for the use of dt/dd in figure and details
- Re: ISSUE-83 ACTION-152 Change Proposal for the use of dt/dd in figure and details
- Re: ISSUE-88: content-language-multiple - Chairs Solicit Proposals
- Re: ISSUE-83 ACTION-152 Change Proposal for the use of dt/dd in figure and details
Friday, 27 November 2009
- Re: ISSUE-83 ACTION-152 Change Proposal for the use of dt/dd in figure and details
- Re: ISSUE-83 ACTION-152 Change Proposal for the use of dt/dd in figure and details
- Re: ISSUE-83 ACTION-152 Change Proposal for the use of dt/dd in figure and details
- Re: ISSUE-83 ACTION-152 Change Proposal for the use of dt/dd in figure and details
- Re: ISSUE-83 ACTION-152 Change Proposal for the use of dt/dd in figure and details
- Re: ISSUE-83 ACTION-152 Change Proposal for the use of dt/dd in figure and details
Thursday, 26 November 2009
Friday, 27 November 2009
- Re: Another possible compromise re namespaces in HTML
- Re: Another possible compromise re namespaces in HTML
Thursday, 26 November 2009
- Re: ISSUE-88: content-language-multiple - Chairs Solicit Proposals
- RE: ISSUE-88: content-language-multiple - Chairs Solicit Proposals
- RE: ISSUE-88: content-language-multiple - Chairs Solicit Proposals
- Re: ISSUE-88: content-language-multiple - Chairs Solicit Proposals
- RE: ISSUE-88: content-language-multiple - Chairs Solicit Proposals
- Re: ISSUE-88: content-language-multiple - Chairs Solicit Proposals
- Re: ISSUE-88: content-language-multiple - Chairs Solicit Proposals
- RE: ISSUE-88: content-language-multiple - Chairs Solicit Proposals
- RE: ISSUE-88: content-language-multiple - Chairs Solicit Proposals
- Re: Change Proposal status and deadlines
- Re: Change Proposal status and deadlines
- Re: Change Proposal status and deadlines
Wednesday, 25 November 2009
- Re: Change Proposal status and deadlines
- Re: HTML CHANGE PROPOSAL; change definition of URL to normative reference to IRIBIS
- RE: Possible Compromise solution for namespaces in HTML5
- Re: Change Proposal status and deadlines
- [Bug 8379] Remove Section 4.11.1 The Details Element
- Re: Another possible compromise re namespaces in HTML
- RE: HTML CHANGE PROPOSAL; change definition of URL to normative reference to IRIBIS
- Re: Change Proposal status and deadlines
- Re: Another possible compromise re namespaces in HTML
- Another possible compromise re namespaces in HTML
- Re: ISSUE-27: rel-ownership - Chairs Solicit Proposals
- Re: ISSUE-1: pingpost - Chairs Solicit Proposals
- Re: ISSUE-27: rel-ownership - Chairs Solicit Proposals
- Change Proposal status and deadlines
- Re: HTML CHANGE PROPOSAL; change definition of URL to normative reference to IRIBIS
- Re: ISSUE-27: rel-ownership - Chairs Solicit Proposals
- Re: ISSUE-1: pingpost - Chairs Solicit Proposals
- Re: ISSUE 14: aria-role - suggest closing on 2009-11-12
Tuesday, 24 November 2009
- [Bug 8368] Remove the Communication Section 8
- RE: Possible Compromise solution for namespaces in HTML5
- RE: Possible Compromise solution for namespaces in HTML5
- [Bug 8365] Remove the Web Browsers Section 6
- RE: Possible Compromise solution for namespaces in HTML5
- Inline figures (<object>) no longer valid
Monday, 23 November 2009
- RE: Possible Compromise solution for namespaces in HTML5
- Re: Possible Compromise solution for namespaces in HTML5
- RE: Possible Compromise solution for namespaces in HTML5
- Re: Possible Compromise solution for namespaces in HTML5
- Re: XMLNS in Inkscape and other editors
- Re: XMLNS in Inkscape and other editors
- Re: Possible Compromise solution for namespaces in HTML5
- Re: XMLNS in Inkscape and other editors
- Re: XMLNS in Inkscape and other editors
- Re: XMLNS in Inkscape and other editors
- Re: XMLNS in Inkscape and other editors
- Re: XMLNS in Inkscape and other editors
- Re: Possible Compromise solution for namespaces in HTML5
- Re: XMLNS in Inkscape and other editors
- Re: XMLNS in Inkscape and other editors
- Re: XMLNS in Inkscape and other editors
- Re: Possible Compromise solution for namespaces in HTML5
- Re: Possible Compromise solution for namespaces in HTML5
- Re: XMLNS in Inkscape and other editors
- Re: XMLNS in Inkscape and other editors
- Re: XMLNS in Inkscape and other editors
- Re: XMLNS in Inkscape and other editors
- Re: XMLNS in Inkscape and other editors
- Re: XMLNS in Inkscape and other editors
- Re: [MathML3-last-call] comments from HTML WG
- Re: [MathML3-last-call] comments from HTML WG
- Re: Possible Compromise solution for namespaces in HTML5
- Re: [MathML3-last-call] comments from HTML WG
Sunday, 22 November 2009
- Re: @caption vs <caption type="figure">
- Re: @caption vs <caption type="figure">
- Re: Possible Compromise solution for namespaces in HTML5
- Re: @caption vs <caption type="figure">
- Re: XML namespaces on the Web
- Re: Possible Compromise solution for namespaces in HTML5
- Re: XMLNS in Inkscape and other editors
- Re: XMLNS in Inkscape and other editors
- Re: XMLNS in Inkscape and other editors
- Re: XMLNS in Inkscape and other editors
- Re: Possible Compromise solution for namespaces in HTML5
- Re: XMLNS in Inkscape and other editors
- Re: XMLNS in Inkscape and other editors
- Re: @caption vs <caption type="figure">
- Re: XMLNS in Inkscape and other editors
- Re: Web Browser Preferences and Internationalisation/Accessibility
Saturday, 21 November 2009
- Re: Possible Compromise solution for namespaces in HTML5
- Re: Possible Compromise solution for namespaces in HTML5
- @caption vs <caption type="figure">
- Re: Possible Compromise solution for namespaces in HTML5
- Re: XMLNS in Inkscape and other editors
- Re: Web Browser Preferences and Internationalisation/Accessibility
- Re: Possible Compromise solution for namespaces in HTML5
- Re: Possible Compromise solution for namespaces in HTML5
- Re: Possible Compromise solution for namespaces in HTML5
- Re: Possible Compromise solution for namespaces in HTML5
- Re: Possible Compromise solution for namespaces in HTML5
- Re: XMLNS in Inkscape and other editors
- Re: Possible Compromise solution for namespaces in HTML5
- Re: XML namespaces on the Web - proposal restated
- Re: Possible Compromise solution for namespaces in HTML5
- Re: XMLNS in Inkscape and other editors
- Re: XML namespaces on the Web - proposal restated
- Re: Possible Compromise solution for namespaces in HTML5
- Re: XMLNS in Inkscape and other editors
- RE: Possible Compromise solution for namespaces in HTML5
- RE: Possible Compromise solution for namespaces in HTML5
- Re: Possible Compromise solution for namespaces in HTML5
Friday, 20 November 2009
- Re: XMLNS in Inkscape and other editors
- Re: Namespace-aware APIs do not need to suck
- Re: Possible Compromise solution for namespaces in HTML5
- Possible Compromise solution for namespaces in HTML5
- Re: old unresolved bug: Bug 5821
- Re: XMLNS in Inkscape and other editors
- Re: XMLNS in Inkscape and other editors
- Re: XMLNS in Inkscape and other editors
- Re: XMLNS in Inkscape and other editors
- Re: XMLNS in Inkscape and other editors
- Re: XMLNS in Inkscape and other editors
- Re: XML namespaces on the Web - proposal restated
- An alternative approach to simplifying namespace binding
- Re: XMLNS in Inkscape and other editors
- XMLNS in Inkscape and other editors
- Re: Web Browser Preferences and Internationalisation/Accessibility
- Re: Web Browser Preferences and Internationalisation/Accessibility
- Re: XML namespaces on the Web - proposal restated
- Re: Namespace-aware APIs do not need to suck
- Re: Namespace-aware APIs do not need to suck
- Re: XML namespaces on the Web - proposal restated
- Re: Web Browser Preferences and Internationalisation/Accessibility
- Re: Moving Window and stuff out of HTML5
- Re: Web Browser Preferences and Internationalisation/Accessibility
Thursday, 19 November 2009
- Re: Web Browser Preferences and Internationalisation/Accessibility
- Re: Web Browser Preferences and Internationalisation/Accessibility
- [minutes] HTML WG call 20091119
- Moving Window and stuff out of HTML5
- Re: ISSUE-88: content-language-multiple - Chairs Solicit Proposals
- Re: [MathML3-last-call] comments from HTML WG
- Re: old unresolved bug: Bug 5821
- old unresolved bug: Bug 5821
- Re: Web Browser Preferences and Internationalisation/Accessibility
- Re: Web Browser Preferences and Internationalisation/Accessibility
- Re: Web Browser Preferences and Internationalisation/Accessibility
- Re: Web Browser Preferences and Internationalisation/Accessibility
- Re: Web Browser Preferences and Internationalisation/Accessibility
- Re: Web Browser Preferences and Internationalisation/Accessibility
- Re: change procedure and dated Bugzilla bugs
- Re: Web Browser Preferences and Internationalisation/Accessibility
- RE: ISSUE-27: rel-ownership - Chairs Solicit Proposals
- Re: change procedure and dated Bugzilla bugs
- change procedure and dated Bugzilla bugs
- Re: Namespace-aware APIs do not need to suck
- Re: XML namespaces on the Web
- ISSUE-88: content-language-multiple - Chairs Solicit Proposals
- ISSUE-87: attr-normalization - Chairs Solicit Proposals
- ISSUE-27: rel-ownership - Chairs Solicit Proposals
- ISSUE-10: video-smil - Chairs Solicit Proposals
- RE: CHANGE PROPOSAL: Table Summary
- Re: Web Browser Preferences and Internationalisation/Accessibility
- Re: [MathML3-last-call] comments from HTML WG
- Re: XML namespaces on the Web
- Re: CfC: Adopt Proposed Decision Policy
- Re: CfC: Adopt Proposed Decision Policy
- Re: ISSUE-1: pingpost - Chairs Solicit Proposals
- Re: XML namespaces on the Web - proposal restated
- ISSUE-2: pingui - Chairs Solicit Proposals
- ISSUE-1: pingpost - Chairs Solicit Proposals
- Re: XML namespaces on the Web - proposal restated
- CHANGE PROPOSAL: Table Summary
- Re: XML namespaces on the Web
- Re: XML namespaces on the Web
- Re: XML namespaces on the Web
- Re: Namespace-aware APIs do not need to suck
- Re: ACTION-103 Follow up on the about: scheme Registration
- Re: X3D comments in Bug 8238.
- Re: Web Browser Preferences and Internationalisation/Accessibility
- Re: Web Browser Preferences and Internationalisation/Accessibility
- Re: XML namespaces on the Web
- Re: Web Browser Preferences and Internationalisation/Accessibility
- Re: XML namespaces on the Web
- Re: Web Browser Preferences and Internationalisation/Accessibility
- Re: Web Browser Preferences and Internationalisation/Accessibility
- Re: Tree construction: Coalescing text nodes
- Re: Tree construction: Coalescing text nodes
- Re: Tree construction: Coalescing text nodes
- Re: XML namespaces on the Web
- Re: XML namespaces on the Web
- Re: XML namespaces on the Web
- Re: XML namespaces on the Web
- Re: Unmangling XML and the XML Core WG (was: XML namespaces on the Web)
- Re: XML namespaces on the Web
- Re: XML namespaces on the Web
- Re: XML namespaces on the Web
- Re: Web Browser Preferences and Internationalisation/Accessibility
- Re: XML namespaces on the Web
- Re: Web Browser Preferences and Internationalisation/Accessibility
- Re: Web Browser Preferences and Internationalisation/Accessibility
- [Bug 8331] Move the Canvas 2D context API into a separate spec
- Re: Web Browser Preferences and Internationalisation/Accessibility
- Re: Web Browser Preferences and Internationalisation/Accessibility
- Re: XML namespaces on the Web
Wednesday, 18 November 2009
- Re: Web Browser Preferences and Internationalisation/Accessibility
- Web Browser Preferences and Internationalisation/Accessibility
- Unmangling XML and the XML Core WG (was: XML namespaces on the Web)
- Re: XML namespaces on the Web
- Re: XML namespaces on the Web
- Re: XML namespaces on the Web
- Re: Webpage breaks as closing span tag doesn't close object
- Re: XML namespaces on the Web
- Re: XML namespaces on the Web
- Re: XML namespaces on the Web
- Webpage breaks as closing span tag doesn't close object
- Re: ISSUE-85 ARIA roles and button/links
- Re: XML namespaces on the Web
- Re: XML namespaces on the Web
- Re: Tree construction: Coalescing text nodes
- Re: XML namespaces on the Web
- Re: XML namespaces on the Web
- Santa Clara F2F Action Items (was: session notes)
- Re: XML namespaces on the Web
- Re: XML namespaces on the Web
- Re: XML namespaces on the Web
- Re: XML namespaces on the Web
- ISSUE-85 ARIA roles and button/links
- Re: XML namespaces on the Web
- Re: XML namespaces on the Web
- Re: XML namespaces on the Web
- Re: XML namespaces on the Web
- Re: XML namespaces on the Web
- Re: XML namespaces on the Web
- Re: Tree construction: Coalescing text nodes
- Re: Tree construction: Coalescing text nodes
- Re: XML and HTML differences (Re: XML namespaces on the Web)
- Re: XML and HTML differences (Re: XML namespaces on the Web)
- Re: XML namespaces on the Web
- Re: XML namespaces on the Web
- {agenda} HTML WG telcon 2009-11-19: issues, action items, calls for consensus/proposals, task force reports
- Re: Tree construction: Coalescing text nodes
- Re: XML namespaces on the Web
- Re: Santa Clara F2F session notes
Tuesday, 17 November 2009
- Santa Clara F2F session notes
- Re: X3D comments in Bug 8238.
- XML and HTML differences (Re: XML namespaces on the Web)
- Re: XML namespaces on the Web
- Re: XML namespaces on the Web
- Re: XML namespaces on the Web
- Re: XML namespaces on the Web
- Re: Thoughts on @profile
- Re: XML namespaces on the Web
- Re: XML namespaces on the Web
- Re: XML namespaces on the Web
- Re: XML namespaces on the Web
- Re: XML namespaces on the Web
- Re: XML namespaces on the Web
- Re: XML namespaces on the Web
- Re: XML namespaces on the Web
- Re: XML namespaces on the Web
- Re: XML namespaces on the Web
- Re: XML namespaces on the Web
- Re: XML namespaces on the Web
- Re: XML namespaces on the Web
- Re: XML namespaces on the Web
- Last Call for XML Entity Definitions for Characters
- Re: X3D comments in Bug 8238.
- Re: XML namespaces on the Web
- Re: XML namespaces on the Web
- Re: X3D comments in Bug 8238.
- Re: Tree construction: Coalescing text nodes
- ISSUE-55, was: Thoughts on @profile
- Re: XML namespaces on the Web
- Thoughts on @profile
- We now have Atom feeds for all Tracker issues [was: HTML Working Group Decision Policy - for discussion]
Monday, 16 November 2009
- Re: XML namespaces on the Web
- Re: XML namespaces on the Web
- Re: XML namespaces on the Web
- Re: XML namespaces on the Web
- Re: XML namespaces on the Web
- [XHR2] Redirects (was: Re: [whatwg] unexpected use of the CORS specification)
- XML namespaces on the Web
- [Bug 8309] semantics of footnotes : why not using <aside> elements as well?
- [Bug 8310] script block's source initialization: please honor the specified charset and type
- Re: "start", "first" and "last" in link relations draft, RDFa and (X)HTML
- "start", "first" and "last" in link relations draft, RDFa and (X)HTML
Sunday, 15 November 2009
- Re: Rel="first" and "index" breaks specs and implementations
- Re: <video> and <audio> (was RE: Implementor feedback on new elements in HTML5)
- Re: <video> and <audio> (was RE: Implementor feedback on new elements in HTML5)
Friday, 13 November 2009
- Re: XHTML character entity support
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 2)
- Re: <video> and <audio> (was RE: Implementor feedback on new elements in HTML5)
- Re: CfC: Adopt Proposed Decision Policy
- Re: Tree construction: Coalescing text nodes
- RE: <video> and <audio> (was RE: Implementor feedback on new elements in HTML5)
- Re: Tree construction: Coalescing text nodes
- Re: Tree construction: Coalescing text nodes
- Re: XHTML character entity support
- Re: XHTML character entity support
- Re: Tree construction: Coalescing text nodes
- Re: <video> and <audio> (was RE: Implementor feedback on new elements in HTML5)
- Re: <video> and <audio> (was RE: Implementor feedback on new elements in HTML5)
- Re: <video> and <audio> (was RE: Implementor feedback on new elements in HTML5)
- Re: <video> and <audio> (was RE: Implementor feedback on new elements in HTML5)
- Re: Tree construction: Coalescing text nodes
- Re: Tree construction: Coalescing text nodes
- Re: XHTML character entity support
Thursday, 12 November 2009
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 2)
- Setting selectedIndex before adding option with that index
- Re: XHTML character entity support
- Re: XHTML character entity support
- Re: XHTML character entity support
- Re: XHTML character entity support
- Re: XHTML character entity support
- Re: XHTML character entity support
- Re: XHTML character entity support
- Re: XHTML character entity support
- Re: XHTML character entity support
- Re: ARIA roles added to the a element should be conforming in HTML5.
- Re: XHTML character entity support
- [Bug 8264] Fix terminology for "resource", "representation", "retrieval"
- Re: Unobtrusive Namespaces, Imaginary Nmespaces
- Re: XHTML character entity support
- RE: ARIA roles added to the a element should be conforming in HTML5.
- [Bug 8264] Fix terminology for "resource", "representation", "retrieval"
- Unobtrusive Namespaces, Imaginary Nmespaces
- Re: ISSUE-83 ACTION-152 Change Proposal for the use of dt/dd in figure and details
- Re: ISSUE-83 ACTION-152 Change Proposal for the use of dt/dd in figure and details
Wednesday, 11 November 2009
- Re: ARIA roles added to the a element should be conforming in HTML5.
- RE: ISSUE-83 ACTION-152 Change Proposal for the use of dt/dd in figure and details
- Re: ARIA roles added to the a element should be conforming in HTML5.
- Re: XHTML character entity support
- Re: XHTML character entity support
- Re: ARIA roles added to the a element should be conforming in HTML5.
- Re: XHTML character entity support
- Re: XHTML character entity support
- Re: XHTML character entity support
- Re: XHTML character entity support
- Re: XHTML character entity support
- Re: XHTML character entity support
- Re: XHTML character entity support
- Re: XHTML character entity support
- Re: Tree construction: Coalescing text nodes
- Re: XHTML character entity support
- Re: ISSUE-83 ACTION-152 Change Proposal for the use of dt/dd in figure and details
- Re: XHTML character entity support
- Re: ISSUE-83 ACTION-152 Change Proposal for the use of dt/dd in figure and details
- Re: ISSUE-83 ACTION-152 Change Proposal for the use of dt/dd in figure and details
- Re: XHTML character entity support
- Re: XHTML character entity support
- Re: ISSUE-83 ACTION-152 Change Proposal for the use of dt/dd in figure and details
- Re: ISSUE-83 ACTION-152 Change Proposal for the use of dt/dd in figure and details
- Re: XHTML character entity support
- Re: ISSUE-83 ACTION-152 Change Proposal for the use of dt/dd in figure and details
- Re: XHTML character entity support
- Re: Tree construction: Coalescing text nodes
- Re: Tree construction: Coalescing text nodes
- [Bug 8241] Named properties on window
- [Bug 8252] HTTP caching rules are _ignored_? What the hell? What's wrong with extending Cache-Control to support user-agent caching instead of coming up with an entirely new mechanism?
- Re: ARIA roles added to the a element should be conforming in HTML5.
- Re: ISSUE-83 ACTION-152 Change Proposal for the use of dt/dd in figure and details
- RE: ARIA roles added to the a element should be conforming in HTML5.
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 2)
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 2)
- Re: ISSUE-83 ACTION-152 Change Proposal for the use of dt/dd in figure and details
- Re: Change Proposal Template
- Re: ISSUE-83 ACTION-152 Change Proposal for the use of dt/dd in figure and details
- Re: ISSUE-83 ACTION-152 Change Proposal for the use of dt/dd in figure and details
Tuesday, 10 November 2009
- Re: ISSUE-83 ACTION-152 Change Proposal for the use of dt/dd in figure and details
- ISSUE-83 ACTION-152 Change Proposal for the use of dt/dd in figure and details
- Re: ARIA roles added to the a element should be conforming in HTML5.
- Re: ARIA roles added to the a element should be conforming in HTML5.
- RE: ARIA roles added to the a element should be conforming in HTML5.
- Re: ARIA roles added to the a element should be conforming in HTML5.
- RE: ARIA roles added to the a element should be conforming in HTML5.
- Re: ARIA roles added to the a element should be conforming in HTML5.
- Re: [whatwg] unexpected use of the CORS specification
- Re: ARIA roles added to the a element should be conforming in HTML5.
- [Bug 8256] [gs] Is form.submit() async or sync? I don't see where this is defined. From my reading it should be sync, as it should just run the steps to completion.
- Re: ARIA roles added to the a element should be conforming in HTML5.
- Re: HTML Accessibility Task Force: Call for Participation
- Re: ARIA roles added to the a element should be conforming in HTML5.
- Re: HTML Accessibility Task Force: Call for Participation
- Re: ARIA roles added to the a element should be conforming in HTML5.
- Re: ARIA roles added to the a element should be conforming in HTML5.
- Re: unexpected use of the CORS specification
- RE: HTML Accessibility Task Force: Call for Participation
- Re: ARIA roles added to the a element should be conforming in HTML5.
- Re: HTML Accessibility Task Force: Call for Participation
- Re: HTML Accessibility Task Force: Call for Participation
- Re: ARIA roles added to the a element should be conforming in HTML5.
- thanks everyone for an excellent f2f meeting at tpac09
- Re: HTML Accessibility Task Force: Call for Participation
Monday, 9 November 2009
- Re: ARIA roles added to the a element should be conforming in HTML5.
- Re: ARIA roles added to the a element should be conforming in HTML5.
- Re: ARIA roles added to the a element should be conforming in HTML5.
- Re: ARIA roles added to the a element should be conforming in HTML5.
- Re: ARIA roles added to the a element should be conforming in HTML5.
- RE: ARIA roles added to the a element should be conforming in HTML5.
- Re: ARIA roles added to the a element should be conforming in HTML5.
- Re: ARIA roles added to the a element should be conforming in HTML5.
- Re: HTML Accessibility Task Force: Call for Participation
- Re: ARIA roles added to the a element should be conforming in HTML5.
- Re: ARIA roles added to the a element should be conforming in HTML5.
- RE: ARIA roles added to the a element should be conforming in HTML5.
- Re: ARIA roles added to the a element should be conforming in HTML5.
- Re: ARIA roles added to the a element should be conforming in HTML5.
- Re: ARIA roles added to the a element should be conforming in HTML5.
- X3D comments in Bug 8238.
- Re: Automatic XML namespaces
- Re: HTML Accessibility Task Force: Call for Participation
- Re: Automatic XML namespaces
- Re: ISSUE-30 (Longdesc) Change Proposal
- RE: ARIA roles added to the a element should be conforming in HTML5.
- Re: ARIA roles added to the a element should be conforming in HTML5.
- Re: ARIA roles added to the a element should be conforming in HTML5.
- Re: ARIA roles added to the a element should be conforming in HTML5.
- Re: Automatic XML namespaces
- Re: the MathML comments
- Re: the MathML comments
- Re: the MathML comments
- Re: the MathML comments
- Re: the MathML comments
- Re: the MathML comments
- Re: the MathML comments
- Re: the MathML comments
Sunday, 8 November 2009
Monday, 9 November 2009
- Re: X3D - a case study in centralized extensibility
- Re: [whatwg] unexpected use of the CORS specification
- Fw: Caching breakout session at TPAC
Sunday, 8 November 2009
- Re: X3D - a case study in centralized extensibility
- Re: the MathML comments
- Re: X3D - a case study in centralized extensibility
- Re: the MathML comments
- Re: the MathML comments
- Re: [whatwg] unexpected use of the CORS specification
- Re: ARIA roles added to the a element should be conforming in HTML5.
- Re: the MathML comments
- Re: the MathML comments
- unexpected use of the CORS specification
- Re: ARIA roles added to the a element should be conforming in HTML5.
- Re: HTML Accessibility Task Force: Call for Participation
- [Bug 8235] Given that Gecko and Webkit don't support them in XML, I think that named properties in HTMLDocument objects should be restricted to HTML documents, given that this feature is only included for backward compatibility and is horribly designed.
- [Bug 8238] Add support for X3D
- [Bug 8236] 1) why a query is stored in the `search' attribute and a URL fragment is stored in the `fragment' attribute? The naming is a bit confusing. 2) Why the is no restrictions for the `port' attribute: an integer in a range [0-65535]; 3) The getter condition fo
Saturday, 7 November 2009
Sunday, 8 November 2009
- Re: Automatic XML namespaces
- Re: ARIA roles added to the a element should be conforming in HTML5.
- Re: ARIA roles added to the a element should be conforming in HTML5.
- Re: the MathML comments
- Re: the MathML comments
- Re: the MathML comments
- Re: the MathML comments
- X3D - a case study in centralized extensibility
- Re: the MathML comments
Saturday, 7 November 2009
- Re: the MathML comments
- Re: the MathML comments
- Re: the MathML comments
- Re: the MathML comments
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 2)
- Re: ARIA roles added to the a element should be conforming in HTML5.
- RE: ARIA roles added to the a element should be conforming in HTML5.
- Re: the MathML comments
- Re: the MathML comments
- Re: the MathML comments
- Re: the MathML comments
- Re: the MathML comments
- Re: [MathML3-last-call] comments from HTML WG
- Re: the MathML comments
- Re: the MathML comments
- Re: ARIA roles added to the a element should be conforming in HTML5.
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 2)
- Re: the MathML comments
- Re: the MathML comments
- [Bug 8224] Mention that it's possible for the Atom section to generate invalid Atom if there's not enough data (e.g. missing authors).
- [Bug 8225] Make it clear that the Atom generation section is not the only such algorithm (e.g. hAtom is fine too).
- the MathML comments
- Re: Topics for "Video" Breakout Group
Friday, 6 November 2009
- Re: wondering what happened to Section 13 and X3D reference
- Re: Automatic XML namespaces
- Re: wondering what happened to Section 13 and X3D reference
- RE: ARIA roles added to the a element should be conforming in HTML5.
- Re: Caching breakout session at TPAC
- Re: X3D+HTML5 talk presented to HTML5 working group today
- [Bug 8220] Remove microdata
- X3D+HTML5 talk presented to HTML5 working group today
- wondering what happened to Section 13 and X3D reference
- Caching breakout session at TPAC
- Re: [MathML3-last-call] comments from HTML WG
- Re: Topics for "Video" Breakout Group
- [MathML3-last-call] comments from HTML WG
- Re: Automatic XML namespaces
- Re: Automatic XML namespaces
- [Bug 8210] Add drawFocusRing(x,y,w,h,element) which, if element is focused, draws a system focus ring at x,y,w,h.
- [Bug 8211] HTML 4 defined these as entities &name; where the ";" wasn't part of the entity name, and there wasn't a variation that some names don't have ";". If this is an example of error recovery, valid HTML should require the ;.
- Re: Topics for "Video" Breakout Group
- Topics for "Video" Breakout Group
Thursday, 5 November 2009
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 2)
- TAG and HTML WG joint meeting discussion topics
- Re: HTML CHANGE PROPOSAL; change definition of URL to normative reference to IRIBIS
- [Bug 8207] Change definition of URL to normative reference to IRIBIS
- Re: TPAC Meeting Minutes (was Re: those who attended the decentralized extensibility meetings at TPAC)
- TPAC Meeting Minutes (was Re: those who attended the decentralized extensibility meetings at TPAC)
- Re: Automatic XML namespaces
- Re: those who attended the decentralized extensibility meetings at TPAC
- those who attended the decentralized extensibility meetings at TPAC
- HTML CHANGE PROPOSAL; change definition of URL to normative reference to IRIBIS
- Re: Automatic XML namespaces
- Re: Automatic XML namespaces
- Re: request for comments HTML WG comments to MathML WG
- Re: Namespace-aware APIs do not need to suck
- Start of Thursday F2F may be a bit later than anticipated
- Re: request for comments HTML WG comments to MathML WG
- Re: Namespace-aware APIs do not need to suck
- Re: request for comments HTML WG comments to MathML WG
- Re: request for comments HTML WG comments to MathML WG
- Re: request for comments HTML WG comments to MathML WG
- Re: request for comments HTML WG comments to MathML WG
- Re: request for comments HTML WG comments to MathML WG
- Re: Automatic XML namespaces
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 2)
- Re: HTML5/IRI: "resolve a URL"
- Re: Automatic XML namespaces
- Re: Namespace-aware APIs do not need to suck
- Re: request for comments HTML WG comments to MathML WG
- Re: request for comments HTML WG comments to MathML WG
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 2)
- request for comments HTML WG comments to MathML WG
Wednesday, 4 November 2009
- Re: what's the language of a document ?
- Re: Namespace-aware APIs do not need to suck
- Namespace-aware APIs do not need to suck
- RE: ACTION-127: establish process for "official WG response" to other WG's RFC on LC drafts
- [Bug 8171] Implement the text alternatives proposal from WAI
- [Bug 8187] Section 4.8.7 on video makes no reference to audio description
- [Bug 8188] Has any thought been put into changing "Fetching an external script must delay the load event..." for async scripts? It seems reasonable to at least provide a way for scripts to not block window.onload.
- Re: Color correction in video, check
- Re: Automatic XML namespaces
- RE: ACTION-127: establish process for "official WG response" to other WG's RFC on LC drafts
- Automatic XML namespaces
- Re: request agenda time to present X3D summary at HTML5 TPAC meeting
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 2)
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 2)
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 2)
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 2)
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 2)
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 2)
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 2)
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 2)
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 2)
- Re: XHTML character entity support
- Re: XHTML character entity support
- Re: XHTML character entity support
- Re: ISSUE-55: Re-enable @profile in HTML5 (draft 2)
- Re: Color correction in video, check
- Re: XHTML character entity support
Tuesday, 3 November 2009
Wednesday, 4 November 2009
- ISSUE-55: Re-enable @profile in HTML5 (draft 2)
- Re: HTML5/IRI: "resolve a URL"
- Re: XHTML character entity support
- Re: XHTML character entity support
Tuesday, 3 November 2009
- Re: request agenda time to present X3D summary at HTML5 TPAC meeting
- HTML5/IRI: "resolve a URL"
- [Bug 7539] Since @summary is an official part of the table element, it is no longer obsolete. Suffienct warning language exists in it's definition that this entry should be removed
- [Bug 8000] ARIA roles added to the a element should be conforming in HTML5
- Re: XHTML character entity support
- [Bug 7633] The use of @summary should be encouraged when circumstances warrant
- [Bug 7721] Drag and Drop is not keyboard accessible
- [Bug 7011] [in off-bug discussion] canvas accessible fallback provision is under specified
- Re: Color correction in video, check
- RE: Color correction in video, check
- [Bug 5758] insufficient accessibility fallback for <audio> or <video>
- Re: XHTML character entity support
- [Bug 7721] Drag and Drop is not keyboard accessible
- Re: XHTML character entity support
- Re: XHTML character entity support
- Color correction in video, check
- Re: XHTML character entity support
- Re: XHTML character entity support
- Re: XHTML character entity support
- Re: XHTML character entity support
- Re: XHTML character entity support
- [Bug 8154] Make it clear that serving polyglot documents as text/html is OK
- Re: XHTML character entity support
- Re: XHTML character entity support
- Re: XHTML character entity support
- Re: XHTML character entity support
- Re: XHTML character entity support
- Re: Fwd: XHTML character entity support
- Re: Fwd: XHTML character entity support
- Re: Fwd: XHTML character entity support
- Re: Fwd: XHTML character entity support
- Re: XHTML character entity support
- Re: XHTML character entity support
- Re: Fwd: XHTML character entity support
- Re: Fwd: XHTML character entity support
- Re: Fwd: XHTML character entity support
- Re: XHTML character entity support
- Re: Fwd: XHTML character entity support
- [Bug 8152] Consider removing the <progress> and <meter> fallback magic
Monday, 2 November 2009
- Re: [Minutes] Accessibility of Media Elements in HTML5 Gathering
- Re: Short-term workarounds - - <source> in <video>
- Re: Fwd: XHTML character entity support
- Re: XHTML character entity support
- Re: ISSUE-30 (Longdesc): WebAIM 2009 survey
- [Bug 8095] link's "type" attribute could be used to advertise available representations if it were linked to the Accept: header per Mike Kelly's thread(s)
- [Bug 8096] <link>'s "type" attribute should be allowed to appear multiple times and/or should allow for a space separated list of advertised types, such that clients can request them via the Accept: header.
- [Bug 8097] Link relation types should use the IANA registry per draft-nottingham-http-link-header
- [Bug 8099] Update 9.5 (Parsing HTML Fragments) for "script data" tokenizer state
- [Bug 8143] [gsnedders] Need to add EOF here, as <xmp>foo</xmp behaviour changed when removing content model flags (also to similar RCDATA state).
- [Bug 8147] The suggested size limit is absurd considering the multi-GB space available on even the cheapest netbooks these days. We need a clear "I want this much, how much did the user and his agent allow me to have?" API. Otherwise, online media apps like photo al
- Re: ISSUE-30 (Longdesc) Change Proposal
- ISSUE-30 (Longdesc): WebAIM 2009 survey
- Re: CfC: Adopt Proposed Decision Policy
- Re: XHTML character entity support
- Re: Fwd: XHTML character entity support
- Re: Fwd: XHTML character entity support
- Re: CfC: Adopt Proposed Decision Policy
- Re: Fwd: XHTML character entity support
- Re: CfC: Adopt Proposed Decision Policy
- Re: XHTML character entity support
- Re: CfC: Adopt Proposed Decision Policy
- Re: XHTML character entity support
- Fwd: XHTML character entity support
- Re: request agenda time to present X3D summary at HTML5 TPAC meeting
- Re: request agenda time to present X3D summary at HTML5 TPAC meeting
- Re: XHTML character entity support
- Re: XHTML character entity support
- Re: CfC: Adopt Proposed Decision Policy
- Re: XHTML character entity support
- Re: CfC: Adopt Proposed Decision Policy
- HTML5 Accessibility Wiki page
- [Minutes] Accessibility of Media Elements in HTML5 Gathering
- Re: CfC: Adopt Proposed Decision Policy
- Re: CfC: Adopt Proposed Decision Policy
Sunday, 1 November 2009
- Re: XHTML character entity support
- Re: XHTML character entity support
- Re: XHTML character entity support
- Re: XHTML character entity support
- Re: XHTML character entity support
- Re: CfC: Adopt Proposed Decision Policy
- [Bug 8144] Is a 'visibility: hidden' element being rendered?
- Re: XHTML character entity support
- RE: what's the language of a document ?
- Re: XHTML character entity support
- Re: XHTML character entity support
- Re: XHTML character entity support
- Re: CfC: Adopt Proposed Decision Policy
- RE: discussion of IRI during W3C TPAC: TImes
- Re: XHTML character entity support
- Re: XHTML character entity support
- Re: XHTML character entity support
- Re: XHTML character entity support
- Re: XHTML character entity support
- Re: XHTML character entity support
- Re: XHTML character entity support
- Re: XHTML character entity support
- Re: XHTML character entity support
- RE: what's the language of a document ?
- Re: XHTML character entity support
- Re: XHTML character entity support