Wednesday, 31 December 2008
- Re: Void elements in HTML (Was: ZIP-based packages and URI references into them ODF proposal)
- [Bug 6339] New: Define how to deal with onload, ononline, and other document/window-level events
- Re: Void elements in HTML (Was: ZIP-based packages and URI references into them ODF proposal)
- Re: Void elements in HTML (Was: ZIP-based packages and URI references into them ODF proposal)
- RE: online/offline events and bubbling
- Re: Void elements in HTML
- Re: Void elements in HTML
- Re: Void elements in HTML
- Re: Void elements in HTML
- Re: Void elements in HTML
- Re: Void elements in HTML
- Re: Void elements in HTML
- Re: Comments on HTML WG face to face meetings in France Oct 08
- Re: Void elements in HTML
- Re: Void elements in HTML
- Re: Void elements in HTML
- Re: Void elements in HTML (Was: ZIP-based packages and URI references into them ODF proposal)
- Re: Void elements in HTML (Was: ZIP-based packages and URI references into them ODF proposal)
- Re: Void elements in HTML (Was: ZIP-based packages and URI references into them ODF proposal)
- Re: Void elements in HTML (Was: ZIP-based packages and URI references into them ODF proposal)
- Re: Void elements in HTML (Was: ZIP-based packages and URI references into them ODF proposal)
- Re: Void elements in HTML (Was: ZIP-based packages and URI references into them ODF proposal)
- Re: Void elements in HTML (Was: ZIP-based packages and URI references into them ODF proposal)
- Re: Drop foster-parented stuff on the floor if parent gone
- Re: Void elements in HTML (Was: ZIP-based packages and URI references into them ODF proposal)
- Re: online/offline events and bubbling
- Re: Void elements in HTML (Was: ZIP-based packages and URI references into them ODF proposal)
- Re: Void elements in HTML (Was: ZIP-based packages and URI references into them ODF proposal)
- Re: Void elements in HTML (Was: ZIP-based packages and URI references into them ODF proposal)
Tuesday, 30 December 2008
- Re: Void elements in HTML (Was: ZIP-based packages and URI references into them ODF proposal)
- Re: Void elements in HTML (Was: ZIP-based packages and URI references into them ODF proposal)
- Re: Void elements in HTML (Was: ZIP-based packages and URI references into them ODF proposal)
- RE: online/offline events and bubbling
- Re: Void elements in HTML (Was: ZIP-based packages and URI references into them ODF proposal)
- [Bug 6336] New: XSLT-compat doctype only allowed for use by XSLT
- Re: Void elements in HTML (Was: ZIP-based packages and URI references into them ODF proposal)
- Re: Void elements in HTML (Was: ZIP-based packages and URI references into them ODF proposal)
- Re: Void elements in HTML (Was: ZIP-based packages and URI references into them ODF proposal)
- Re: Void elements in HTML (Was: ZIP-based packages and URI references into them ODF proposal)
- Void elements in HTML (Was: ZIP-based packages and URI references into them ODF proposal)
- Ruby feedback
- Re: Attribute syntax feedback
Monday, 29 December 2008
Saturday, 27 December 2008
Friday, 26 December 2008
Thursday, 25 December 2008
- Re: Typos in tokenizing character references
- Re: Speculative tokenization and foreign content
- Re: Speculative tokenization and foreign content
- Re: Drop foster-parented stuff on the floor if parent gone
- Re: Conditional branch in tree builder based on DOM state
- Re: Trying out SVG and MathML parsing
- Re: metadata content
- Re: Table feedback
- Re: metadata content
- Re: metadata content
- Re: metadata content
Wednesday, 24 December 2008
- Re: metadata content
- Re: metadata content
- Re: metadata content
- Re: metadata content
- Re: Comparing conformance requirements against real-world docs
- Re: Comparing conformance requirements against real-world docs
- Re: Comments on localStorage
- RE: DOM Storage feedback
- Re: Comparing conformance requirements against real-world docs
- Re: metadata content
- Re: DOM Storage feedback
- Re: metadata content
- Re: metadata content
- Re: metadata content
- Re: img issue: should we restrict the URI
- Re: metadata content
- Re: Comparing conformance requirements against real-world docs
- Re: media attribute and nested media restrictions
- Re: metadata content
Tuesday, 23 December 2008
- Re: dataset case issue
- Re: dataset case issue
- Re: dataset case issue
- Re: http-equiv
- Re: http-equiv
- Re: http-equiv
Sunday, 21 December 2008
Saturday, 20 December 2008
- Re: Table feedback
- Re: Table feedback
- http-equiv
- Table feedback
- Re: Comparison of Smart Headers and HTML5 (ACTION-85)
Friday, 19 December 2008
Thursday, 18 December 2008
- Setting document.domain
- Re: Authoring Guide
- Re: less than normal importance/emphasis
- Re: less than normal importance/emphasis
- Re: less than normal importance/emphasis
- Re: less than normal importance/emphasis
- Re: less than normal importance/emphasis
Wednesday, 17 December 2008
- Re: less than normal importance/emphasis
- Re: less than normal importance/emphasis
- Re: HTMLMediaElement defaultPlaybackRate and playbackRate
- RE: Button Element in IE8
- Re: Button Element in IE8
- Re: Button Element in IE8
- Re: Button Element in IE8
- Re: Button Element in IE8
- Re: Button Element in IE8
- Re: Button Element in IE8
- Button Element in IE8
Tuesday, 16 December 2008
- Re: OK to postpone ISSUE-13 handling-http-401-status (form authentication...)?
- OK to postpone ISSUE-13 handling-http-401-status (form authentication...)?
- Re: <q> omnibus
- Re: <q> omnibus
- Re: Sam Ruby appointed co-chair for HTML Working Group, effective January 5
- Re: Sam Ruby appointed co-chair for HTML Working Group, effective January 5
- Re: Sam Ruby appointed co-chair for HTML Working Group, effective January 5
- Re: <q> omnibus
Monday, 15 December 2008
- thanks and tweaks Re: request for input on organizing (ARIA, HTML)-to-API work
- Sam Ruby appointed co-chair for HTML Working Group, effective January 5
Thursday, 11 December 2008
- Re: Speculative tokenization and foreign content
- Re: Speculative tokenization and foreign content
- Re: Speculative tokenization and foreign content
- Re: Speculative tokenization and foreign content
- Re: Origin computation
- Re: Origin computation
- Re: Origin computation
- Origin computation
- Re: Speculative tokenization and foreign content
- Re: Speculative tokenization and foreign content
- Re: Speculative tokenization and foreign content
- [Bug 6300] New: reference RFC 5322 instead of RFC 2822
- Re: link relationship registration
Wednesday, 10 December 2008
- Re: Speculative tokenization and foreign content
- Re: Speculative tokenization and foreign content
- RE: Speculative tokenization and foreign content
- Speculative tokenization and foreign content
- Re: link relationship registration
- Re: link relationship registration
- Re: link relationship registration
- Re: link relationship registration
- Re: link relationship registration
- Re: link relationship registration
- Re: link relationship registration
- Re: link relationship registration
- Re: link relationship registration
- Re: link relationship registration [was: New Version Notification for draft-nottingham-http-link-header-03]
- Re: link relationship registration [was: New Version Notification for draft-nottingham-http-link-header-03]
- Re: link relationship registration
- Re: link relationship registration [was: New Version Notification for draft-nottingham-http-link-header-03]
- Re: link relationship registration
- Re: link relationship registration [was: New Version Notification for draft-nottingham-http-link-header-03]
- Re: link relationship registration [was: New Version Notification for draft-nottingham-http-link-header-03]
- Re: link relationship registration [was: New Version Notification for draft-nottingham-http-link-header-03]
- [Bug 6294] New: Date microsyntax defines incorrect range for month and day fields
- [Bug 6293] New: specify that the value attribute on <input type=url> must be an absolute URL
- Re: link relationship registration [was: New Version Notification for draft-nottingham-http-link-header-03]
- Drop foster-parented stuff on the floor if parent gone
- Conditional branch in tree builder based on DOM state
Tuesday, 9 December 2008
- Re: Comparison of Smart Headers and HTML5 (ACTION-85)
- Re: Comparison of Smart Headers and HTML5 (ACTION-85)
- Re: Comparison of Smart Headers and HTML5 (ACTION-85)
- Re: Comparison of Smart Headers and HTML5 (ACTION-85)
Monday, 8 December 2008
- Re: Comparison of Smart Headers and HTML5 (ACTION-85)
- Re: Comparison of Smart Headers and HTML5 (ACTION-85)
- Re: Comparison of Smart Headers and HTML5 (ACTION-85)
- Re: proposed change to dialog example in HTML5 section 4.6.26
- Re: proposed change to dialog example in HTML5 section 4.6.26
- Re: proposed change to dialog example in HTML5 section 4.6.26
- Re: Comparison of Smart Headers and HTML5 (ACTION-85)
- Re: proposed change to dialog example in HTML5 section 4.6.26
- Re: Comparison of Smart Headers and HTML5 (ACTION-85)
- Re: Comparison of Smart Headers and HTML5 (ACTION-85)
Sunday, 7 December 2008
Saturday, 6 December 2008
- Re: Comments on HTML WG face to face meetings in France Oct 08
- Re: Comments on HTML WG face to face meetings in France Oct 08
- Re:Comparison of Smart Headers and HTML5 (ACTION-85)
- Re: Comparison of Smart Headers and HTML5 (ACTION-85)
- Re: online/offline events and bubbling
- Re: Comments on HTML WG face to face meetings in France Oct 08
Friday, 5 December 2008
- Re: Comparison of Smart Headers and HTML5 (ACTION-85)
- Re: Comments on HTML WG face to face meetings in France Oct 08
- Re: Comments on HTML WG face to face meetings in France Oct 08
- online/offline events and bubbling
Thursday, 4 December 2008
- Re: Microsyntax parsing rules for numbers
- Re: Microsyntax parsing rules for numbers
- Re: Microsyntax parsing rules for numbers
- Re: Microsyntax parsing rules for numbers
- Microsyntax parsing rules for numbers
- Re: Media element events
- Re: Black-box equivalence of parsing fragments directly into context node
- Re: proposed change to dialog example in HTML5 section 4.6.26
- Re: Black-box equivalence of parsing fragments directly into context node
- Re: Black-box equivalence of parsing fragments directly into context node
Wednesday, 3 December 2008
- proposed change to dialog example in HTML5 section 4.6.26
- [Bug 6263] New: document.onreadystatechange
- Re: video: various width/height attributes
- Re: Black-box equivalence of parsing fragments directly into context node
- Re: Black-box equivalence of parsing fragments directly into context node
- Re: Form-associated elements in the parsing algorithm
Tuesday, 2 December 2008
- Re: Form-associated elements in the parsing algorithm
- Re: Black-box equivalence of parsing fragments directly into context node
- Re: Black-box equivalence of parsing fragments directly into context node
- Re: Form-associated elements in the parsing algorithm
- Re: Form-associated elements in the parsing algorithm
- Re: Translation control in HTML5
- Re: Media element events
- Re: Media element events
- Re: Black-box equivalence of parsing fragments directly into context node
- Re: img issue: should we restrict the URI
- Re: Black-box equivalence of parsing fragments directly into context node
- Re: img issue: should we restrict the URI
- Re: Form-associated elements in the parsing algorithm
- Re: Black-box equivalence of parsing fragments directly into context node
- Re: Form-associated elements in the parsing algorithm
- Re: Form-associated elements in the parsing algorithm
- Re: Translation control in HTML5
- Re: [WF2] new attributes that often conflict with actual pages
- Media element events
- Re: Translation control in HTML5
- Re: [forms] Detailed review of the DOMControlValueChanged and 'input' events
- Re: Form-associated elements in the parsing algorithm
- Re: Line breaks in the placeholder attribute
- Re: Minor form enctype errors
- Re: [forms] Detailed review of the DOMControlValueChanged and 'input' events
- Re: [WF2] new attributes that often conflict with actual pages
- Re: Black-box equivalence of parsing fragments directly into context node
- Re: document.cookie and HTTPOnly
- Re: Black-box equivalence of parsing fragments directly into context node
- document.cookie and HTTPOnly
- Re: Escaping text span and character references
- Re: New Version Notification for draft-nottingham-http-link-header-03
- <meta http-equiv="Content-Language">
- Re: Mutation events and document.open()
- Re: document.close() in document.write()
- Re: Point at which script blocks the parser
- Re: Re-entrant invocation of the tree builder
- Re: Black-box equivalence of parsing fragments directly into context node
- Re: Escaping text span and character references
- Re: Parsing problem with misnested tags
- Re: Case folding (lack thereof) in the doctype name state
- Re: HTMLMediaElement defaultPlaybackRate and playbackRate
- Re: Don't make <h1><h1> nest
- Re: HTMLMediaElement defaultPlaybackRate and playbackRate
- Re: HTMLMediaElement defaultPlaybackRate and playbackRate
- Re: HTMLMediaElement defaultPlaybackRate and playbackRate
- Re: HTMLMediaElement defaultPlaybackRate and playbackRate
- Re: HTMLMediaElement defaultPlaybackRate and playbackRate
- Re: New Version Notification for draft-nottingham-http-link-header-03
- Re: HTMLMediaElement defaultPlaybackRate and playbackRate
Monday, 1 December 2008
- Re: link relationship registration [was: New Version Notification for draft-nottingham-http-link-header-03]
- Re: Fwd: New Version Notification for draft-nottingham-http-link-header-03
- Feedback on draft-nottingham-http-link-header-03, was: Fwd: New Version Notification for draft-nottingham-http-link-header-03
- Fwd: Comparison of Smart Headers and HTML5 (ACTION-85)
- Re: HTMLMediaElement - detecting startup hysterisis
- Re: setting HTMLMediaElement volume and playbackRate attributes
- Re: Form-associated elements in the parsing algorithm
- Re: video: various width/height attributes
- Re: HTMLMediaElement defaultPlaybackRate and playbackRate
- Re: HTMLMediaElement readyState
- Comparison of Smart Headers and HTML5 (ACTION-85)
- Re: New Version Notification for draft-nottingham-http-link-header-03
- Re: New Version Notification for draft-nottingham-http-link-header-03
- Re: New Version Notification for draft-nottingham-http-link-header-03
- Fwd: New Version Notification for draft-nottingham-http-link-header-03