Re: [css3-ui] directional nav error handling

> 
> On 15 Apr 2015, at 18:42, Tab Atkins Jr. <jackalmage@gmail.com> wrote:
> 
> On Wed, Apr 15, 2015 at 7:24 AM, Florian Rivoal <florian@rivoal.net> wrote:
>> The downside is that E is not what either of the existing implementations
>> I am aware of do. I don't have easy access to the corpus of existing
>> content to assess if we'd have a compat problem to do that. These properties
>> are heavily used on TV sites, so there is legacy content to consider.
> 
> Hm, true.  We'd have to check.

Anybody has easy access to a big corpus of TV oriented web page? Someone at
Opera (CCing Simon)?

>> Less interesting, but still worth thinking about is the question of spec advancement.
>> To get to level 3 past CR quickly, it may make things easier to do the
>> more lenient option C in level 3, and only tighten it up in level 4.
> 
> That's backwards from how we generally do that.  Outlawing more things
> in the future is generally page-hostile.

I am not saying to allow it now and forbid later. I am saying to disallow now
as an author requirement, but don't define behavior in case of violation of
this requirement. Later in level 4 (in a time frame where implementations can
adapt) define to be parse error. We could recommend (should) a parse error now,
just in case someone working on an implementation is wondering what to do.

Of course, an author level requirement means little if UAs don't enforce it, but
currently they don't. I would like to define it, but I am doubtful we
can expect implementations of these properties to change much in the short
term, so requiring things they don't do would just hold up the spec.

 - Florian

Received on Wednesday, 15 April 2015 22:48:58 UTC