W3C home > Mailing lists > Public > www-style@w3.org > February 2012

Re: Vendor Prefix solutions

From: Markus Ernst <derernst@gmx.ch>
Date: Fri, 10 Feb 2012 10:52:11 +0100
Message-ID: <4F34E8CB.4060205@gmx.ch>
To: Anselm Hannemann - Novolo Designagentur <anselm@novolo.de>
CC: "Style www-style@w3.org" <www-style@w3.org>
Am 10.02.2012 10:03 schrieb Anselm Hannemann - Novolo Designagentur:
> Am 10.02.2012 um 09:48 schrieb Markus Ernst:
>>
>> Just as myself, many developers have not enough knowledge about the
>> state of the art in every aspect of the evolution of web technologies
>> to know exactly which property is at which state, and which syntax can
>> be safely used in order to make their sites look as expected in as
>> many UAs as possible. Trying to do it right, we google around and
>> follow recommendations we find at Stackoverflow and such places. Thus,
>> in order to reduce the amount of abuse, I'd suggest to create a kind
>> of "official" collection of recommended syntaxes for the most common
>> tasks.
>>
>> I assume that most (ab)use of vendor prefixes (and fancy script-based
>> solutions) is about:
>> - rounded corners
>> - box shadow
>> - text shadow
>> - transparency
>>
>> Maybe I miss some, but I am sure there are not too many different
>> topics here. A quasi-official page from browser vendors or the W3C on
>> how to best do these would be highly appreciated, very helpful, and a
>> way to reduce bad syntaxes out in the web.
>>
>
> No, you're totally right here. It's about us, the ones who teach such
> stuff and write blog articles etc. who should more mention that this is
> "beta" stuff we're talking about and you either should know what you do
> when using it or either not use it.
> And I like the idea of creating a knowledge base. An initial version is
> already here: http://html5please.us/. You can get advise here if it's
> safe to use or highly unrecommended.

This is a great resource indeed, specially the "View browser share" 
linked overviews. What would make it the killer resource would be an 
addition like "What do you need, if you must support the feature in a 
corporate website" - including prefixes or even MS filters or jQuery 
stuff if necessary.

Usually, there is a designer who has a Mac and an Iphone, and a client 
who has Windows XP with IE 7 and some smartphone which may be some 2 or 
3 years old. I am not always in the position to tell the client that the 
designer's design will not work in his/her environment. I can tell the 
client (and the designer) that text shadows won't work reliably, but I 
can't tell the same about rounded corners or box shadows, because they 
see them "working" on their screens all the time.
Received on Friday, 10 February 2012 09:52:41 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:50 GMT