public-html@w3.org from September 2008 by subject

2 new posts: Research Assistant/ Research Fellow in Semantic Web/Ontology and Recommender Systems for Live Sciences: Closing Date: 12 September 2008

4.3 Source fallback

<style scoped> and semi-transparent content models

@headers issue resolved - allowing a td to be referenced by a header to be in the HTMl5 spec.

@headers Wiki page

@longdesc - starting over (was RE: Acessibility of <audio> and <video>)

[Bug 6032] New: Serializing a doctype with invalid public id

[Bug 6033] New: Forms section

[Bug 6034] New: Process <video> feedback

[Bug 6035] New: Process appcache feedback

[Bug 6036] New: HTMLCollection.namedItem() should look for non-HTML elements

[Bug 6037] New: Elaborate on Web compat characteristics of task queue interaction

[Bug 6038] New: "noframes", "script", "style", "title" in 'after head' mode pop prematurely

[Bug 6052] New: Should propagate uncaught exceptions from workers to their owner

[Bug 6057] New: 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'

[Bug 6097] New: <body background> is a URL attribute?

[Bug 6098] New: input type=foo as an element-level section

[Bug 6099] New: Process notification feedback

[Bug 6100] New: Process MessagePort feedback

[Bug 6101] New: media elements - ready states - events should be async

[Bug 6102] New: Please do not break applet element in HTML 5

[Bug 6103] New: video section editorial issues

[Bug 6104] New: <video> and <audio> should prevent cross-origin media loads

[Bug 6127] New: Deal with origin details in WebSocket and postMessage feedback

[forms] control_element.value getter/setter newline normalization

[forms] Detailed review of the DOMControlValueChanged and 'input' events

About video & audio elements

acceptable fallbacks [was: Re: Is longdesc a good solution? ...]

Accessibility for the Media Elements in HTML5[1][2]

Accessibility of <audio> and <video>

Acessibility of <audio> and <video>

align justify? Re: Comparing conformance requirements against real-world docs

Are new void elements really a good idea?

Buffered bytes for media elements

Citing multiple <blockquote> elements in HTML5

Comparing conformance requirements against real-world docs

conformance checker for HTML+ARIA?

contrived data table example

dir=rtl and table header algorithm (was: Re: function and impacts)

Dirac 1.0.0 released. Comments?

Do we need axis or headers='a-TD-cell' ?

Draft agenda, Oct. 23-24 face-to-face meeting

Editor skills and funding (was: Looking for more editors and Editors)

For information : Google to release web browser

Formal Request for Re-Instation of @longdesc into the HTML 5 specification (was RE: How to add/reinstate dropped accessibly features in HTML5 (was Re: longdesc="" in HTML5))

fragid navigation and pct-encoded

function and impacts

function and impacts (was: @scope and @headers reform)

Fwd: @headers issue resolved - allowing a td to be referenced by a header to be in the HTMl5 spec.

FYI PFWG F2F topics of potential interest

How to add/reinstate dropped accessibly features in HTML5 (was Re: longdesc="" in HTML5)

HTML 5 draft copyright?

HTML5 non-accessibility?

HTMLOptionElement constructor

Is "breaking the Web" with HTML 5 a non issue?

Is CHOICE a good solution? (was RE: Is longdesc a good solution? (was: Acessibility of <audio> and <video>))

Is longdesc a good solution?

Is longdesc a good solution? (was: Acessibility of <audio> and <video>)

ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec]

Limitations of IE8 type-sniffing opt-out

Long fallback. A problem description.

longdesc in the wild [was: Re: Is longdesc a good solution? ...]

longdesc="" in HTML5

Looking for more editors

Minor clarrification : Is CHOICE a good solution? (was RE: Is longdesc a good solution? (was: Acessibility of <audio> and <video>))

minor tweak to FYI PFWG F2F topics of potential interest

Multimedia Accessibility <Audio> <Video> Wiki Page

new XSLT output methods, was: several messages

No tabbed browsing in HTML 5?

Overemphasis on screen readers?

Pause on exit from Cue Ranges

Privacy implications of automatic alternative selection (Re: Acessibility of <audio> and <video>)

profile attribute and conformance (copy-and-paste details)

profile attribute and conformance [was: Comparing conformance requirements against real-world docs]

Question about origin serialization

Quirks mode vs. standards mode

Quirks mode vs. standards mode (was: Re: ISSUE-54 (html5-doctype-vs-xslt): ...)

Regarding Transcriptions/Captions (was RE: acceptable fallbacks [was: Re: Is longdesc a good solution? ...])

Request for PFWG WAI review of multimedia accessibility requirements <audio> <video>

several messages

State transitions for media elements

Status of Link header

SVG Semantics Re: SVG and MathML in text/html

table headers - clear description of problem

the "special" doctype (ISSUE-54), was: several messages

Unsupported transport-layer encodings

W3C Workshop on Security for Access to Device APIs - London, December 10-11

What namespace features popular SVG tools really emit (ISSUE-37)

Why the curly braces are not solving a real problem [was: Re: Mandatory and Important]

willValidate and image controls

Last message date: Tuesday, 30 September 2008 23:58:34 UTC