PUBLIC MARKS with search vendor

I think vendor prefixes are hurting the Web. They are hurting Web authors. They are hurting users of browsers. They are hurting competition in the Web browser space. I think we (people developing browsers and Web standards) should stop hurting the Web. It would also make sense for browsers to implement other browsers’ prefixed features to the extent existing content uses prefixed features.

As far as I can tell, the only WebKit is benefiting.

The common conception among Web designers is that a good style sheet is created by hand, each curly bracket meticulously placed, each vendor prefix typed in manually. But how does this tradition fit in a world where the websites and applications that we want to create are becoming increasingly complex?

If I had the choice, I would go an intermediate radical way (Yes It is strange). I would make the vendor prefixes usable only in the Developer mode of the browser. Most browsers have now a Developer mode. Once the developer mode is activated, the CSS vendor prefixes are shown, but for the vast majority of people, this never happens. Then the vendor prefixes are not usable for production with wide audiences. Web developers in Web agencies will not use them for business only for pleasure.

Speaking as a long-time Web Developer, I'm appalled by the dismissive

and insulting attitude taken by the constituency dictating HTML 5 as

pertains to the standards that myself and those like me are perfectly

capable of understanding, by declaring repeatedly that we're a bunch of

morons who can't understand resource/representation or anything else

the vendors are hell-bent on changing, as justification for said

changes ignoring those well-understood standards.

Which motivates me to participate in this thread, because I don't want

that vendor-centric approach to pollute HTTPbis, rendering the spec so

large and unwieldy that only browser vendors could ever hope to

understand its meaning, in terms of what they've implemented. A big,

emphatic -1 to the notion that HTTPbis should follow HTML 5 down the

road of standardizing error correction behavior for user agents, for

C-D or anything else.

How Vendor Relationship Management and the Federated Social Web align with each other, and why they can be implemented in a single architecture.

A publisher can't depend on anything being broadly implemented just because some spec says a browser MUST do something. A MUST in a specification isn't a law; it provides no push. The only role a MUST in standard actually has is to provide a check-box for implementations; if the vendor of the implementation says "I implement standard X", they mean, among other things, "I follow every MUST in the spec, and I also follow every SHOULD except when I have a good reason not to, which I can explain". That's it. That's all the standard really does, is give you something to measure against.