<p>As a contributor to multiple browsers, I think it's important to note the distinctions between cases like Acid3 (where IIRC all tests were supposed to test specs that had been published with no dispute for 5 years), much of HTML5 (where items not yet implemented generally have agreement-on-principle from various vendors) and this issue, where vendors have publicly refused to implement particular cases. Particular specs in the first two cases represent vendor consensus, and when vendors discover problems during implementation the specs are changed. This is not a case where vendor consensus is currently possible (despite the apparently naive beliefs on the part of some who think the vendors are merely ignorant and need education on the benefits of codec x or y), and "just put it in the spec to apply pressure" is not a reasonable response.</p>
<p>PK</p>
<p><blockquote type="cite">On Jun 30, 2009 2:17 AM, "Sam Kuper" <<a href="mailto:sam.kuper@uclmail.net">sam.kuper@uclmail.net</a>> wrote:<br><br><div class="gmail_quote">2009/6/30 Silvia Pfeiffer <span dir="ltr"><<a href="mailto:silviapfeiffer1@gmail.com" target="_blank">silviapfeiffer1@gmail.com</a>></span><p>
<font color="#500050">
>
> On Tue, Jun 30, 2009 at 2:50 PM, Ian Hickson<<a href="mailto:ian@hixie.ch">ian@hixie.ch</a>> wrote:
> > I considered requiring Og...</font></p><div><br>Right. Waiting for all vendors to support the specified codec would be like waiting for them all to be <span>Acid</span>3 compliant. Better to specify how browsers should behave (especially if it's how most of them will behave), and let the stragglers pick up the slack in their own time under consumer pressure.<br>
<br>Sam<br></div></div>
</blockquote></p>