The spec (at least from what I know) wants to create a unified experience, we don't want users to have a different experience from browser to browser. Nor do developers want to implement hacks for every browser. If no common ground can be reached then maybe no common ground is better than common ground, who knows it may spark new ideas that we haven't thought of yet.
On Mon, Jul 6, 2009 at 1:18 PM, Aryeh Gregor <[email protected]<simetrical%[email protected]> > wrote: > On Mon, Jul 6, 2009 at 4:01 AM, David Gerard<[email protected]> wrote: > > A spec that makes an encumbered format a "SHOULD" is unlikely to be > > workable for those content providers, e.g. Wikimedia, who don't have > > the money, and won't under principle, to put up stuff in a format > > rendered radioactive by known enforced patents. > > That's why "should" is not the same as "must". Those who have a good > reason not to do it can decline to do it. > -- - Adam Shannon ( http://ashannon.us )
