Re: [whatwg] Validator.nu: "Attribute role not allowed on element h2 at this point."

2012-03-12 Thread Simon Pieters
On Tue, 13 Mar 2012 02:16:29 +0100, Charles Pritchard wrote: Warnings are generally not useful. Either something is fine and we should support it, or it's wrong and we should alert the author. I think "must" is very much the appropriate requirement level here. From the implementation-sid

Re: [whatwg] Validator.nu: "Attribute role not allowed on element h2 at this point."

2012-03-12 Thread Charles Pritchard
On 3/12/2012 5:52 PM, Ian Hickson wrote: On Mon, 12 Mar 2012, Charles Pritchard wrote: > > Ignore the error, the HTML5 spec does not reflect implementations in > this section about ARIA. > > The warning is not helpful to authors nor does it accurately describe > the means in which ATs work w

Re: [whatwg] Validator.nu: "Attribute role not allowed on element h2 at this point."

2012-03-12 Thread Ian Hickson
On Mon, 12 Mar 2012, Hugh Guiney wrote: > > Why not? > > I have this in an otherwise-valid HTML5 + SVG 1.1 + MathML 2.0 + RDFa > Lite 1.1 document: > > > Company Name > Tagline > > > Spec says: > > > Authors must not set the ARIA�role�and�aria-*�attributes in a manner > > that conflicts

Re: [whatwg] Validator.nu: "Attribute role not allowed on element h2 at this point."

2012-03-12 Thread Charles Pritchard
To clarify: http://www.w3.org/TR/2011/WD-html5-20110405/author/content-models.html#annotations-for-assistive-technology-products-aria "the presentation role may always be used.". The validator should not have thrown an error for role=presentation. The section was made because: "exceptions are

Re: [whatwg] Validator.nu: "Attribute role not allowed on element h2 at this point."

2012-03-12 Thread Charles Pritchard
Ignore the error, the HTML5 spec does not reflect implementations in this section about ARIA. The warning is not helpful to authors nor does it accurately describe the means in which ATs work with ARIA. -Charles On 3/12/2012 4:27 PM, Hugh Guiney wrote: Why not? I have this in an otherwise-va

Re: [whatwg] UndoManager: Nested transactions and execCommand

2012-03-12 Thread Ehsan Akhgari
I agree that nested transactions are a bad idea, and we probably don't want them. Cheers, -- Ehsan On Mon, Mar 12, 2012 at 2:19 AM, Ryosuke Niwa wrote: > Hi, > > Consider the following scenario: > > > > ... > um1.undoManager.transact({ // transaction 1 > executeAu

[whatwg] Validator.nu: "Attribute role not allowed on element h2 at this point."

2012-03-12 Thread Hugh Guiney
Why not? I have this in an otherwise-valid HTML5 + SVG 1.1 + MathML 2.0 + RDFa Lite 1.1 document: Company Name Tagline Spec says: > Authors must not set the ARIA role and aria-* attributes in a manner that > conflicts with the > semantics described in the following table, except that the

Re: [whatwg] Support for RDFa in HTML5

2012-03-12 Thread Manu Sporny
On 03/12/12 15:00, Benjamin Hawkes-Lewis wrote: > On Mon, Mar 12, 2012 at 5:16 PM, Philipp Serafin > wrote: >> I admit, I haven't really followed this debate. But out of >> interest: Is it by now actually possible to write any kind of >> implementation that complies to both, the HTML5 *and* the RD

Re: [whatwg] Support for RDFa in HTML5

2012-03-12 Thread Benjamin Hawkes-Lewis
On Mon, Mar 12, 2012 at 5:16 PM, Philipp Serafin wrote: > I admit, I haven't really followed this debate. But out of interest: Is > it by now actually possible to write any kind of implementation that > complies to both, the HTML5 *and* the RDFa specification? As Ian said, the HTML5 spec allows e

Re: [whatwg] Support for RDFa in HTML5

2012-03-12 Thread Philipp Serafin
I admit, I haven't really followed this debate. But out of interest: Is it by now actually possible to write any kind of implementation that complies to both, the HTML5 *and* the RDFa specification? Regards, Philipp Serafin Am Dienstag, 2. August 2011 19:32:52 schrieb Ian Hickson: > On Tue, 2 A