[Bug 24812] Remove at risk features from CR HTML5 spec

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24812

--- Comment #7 from Robin Berjon <robin@w3.org> ---
(In reply to Sam Ruby from comment #6)
> (In reply to Robin Berjon from comment #5)
> > I see two different reasons behind the "two implementations" rule. One is
> > implementability, and the other is implementer interest.
> 
> The exit criteria we've adopted is explicit on this matter:
> 
> http://dev.w3.org/html5/decision-policy/public-permissive-exit-criteria.html

I am well aware. However, while the rule of thumb is fine, it is just a rule of
thumb and there are cases (such as this one) which I would argue are
acceptable. The rules are only a tool to get to interoperability; in the
hierarchy of norms the latter rates above the former.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Friday, 28 February 2014 11:04:59 UTC