- From: Sylvain Galineau <galineau@adobe.com>
- Date: Mon, 17 Mar 2014 19:20:18 +0000
- To: Bjoern Hoehrmann <derhoermi@gmx.net>
- CC: "<www-style@w3.org>" <www-style@w3.org>
On Mar 17, 2014, at 12:04 PM, Bjoern Hoehrmann <derhoermi@gmx.net> wrote:
> * Sylvain Galineau wrote:
>> I do not think it is useful or helpful to extrapolate Pavlov reflexes
>> from the past, at least not without some context. There is a huge
>> difference between the infamous:
>>
>> #something {
>> -webkit-border-radius: 5px;
>> -moz-border-radius: 5px;
>> -o-border-radius: 5px;
>> border:radius: 5px;
>> }
>>
>> …and an hypothetical future:
>>
>> .orOther {
>> width: 200px
>> height: 200px;
>> —jquery-scroll: carousel(...);
>> —sassy-framework-says: groovy;
>> }
>>
>
> I am more concerned about having to debug through
>
> #something {
> -webkit-border-radius: 5px;
> width: 200px
> -moz-border-radius: 5px;
> height: 200px;
> -jquery-scroll: carousel(...);
> -o-border-radius: 5px;
> border:radius: 5px;
> -sassy-framework-says: groovy;
> }
>
> to use your example.
> —
Sure, this can happen as long as some browser vendors preserve prefixes. But I’m not sure why this would be worse than:
> #something {
> -webkit-border-radius: 5px;
> width: 200px
> -moz-border-radius: 5px;
> height: 200px;
> --scroll: carousel(...);
> -o-border-radius: 5px;
> border:radius: 5px;
> --says: groovy;
> }
…where the custom props carry no information as to what makes use of them. Which is harder to investigate?
Received on Monday, 17 March 2014 19:20:48 UTC