W3C home > Mailing lists > Public > www-style@w3.org > December 2017

Re: Shorthands resetting properties they cannot set

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Fri, 1 Dec 2017 15:44:08 -0800
Message-ID: <CAAWBYDApaDVmofEcU6udBmu6oic6tNSKYKqR0V4N9KxdGqBpsA@mail.gmail.com>
To: Daniel Glazman <daniel.glazman@disruptive-innovations.com>
Cc: www-style list <www-style@w3.org>
On Mon, Nov 27, 2017 at 10:04 PM, Daniel Glazman
<daniel.glazman@disruptive-innovations.com> wrote:
> Le 28/11/2017 à 00:01, Tab Atkins Jr. a écrit :
>> Really tho, I'm just confused by the behavior Daniel discovered. I'd
>> need to dig - is that actually required behavior? It seems weird to
>> tear apart the shorthand declaration just because you added a longhand
>> - that could just as easily have just been "border: thin solid red;
>> border-top-color: blue;".
> That would probably help but where do you stop? I mean when do you
> stop overriding 'border' through longhands instead of using longhands
> only? When more than half of longhands are overriden? From an
> implementation's point of view, that's going to be painful.
> People really expect
>   border-color: red; border-width: thin; border-style: solid;
> and
>   border: red thin solid;
> to be the same thing. Furthermore, there's a question of stylesheet
> readability and maintainability. We've changed a twenty years old
> behaviour that impacts the way people author borders.

We've got a number of properties that this applies to, and several of
them can't be changed at this point, so it's kinda a moot point, no?

Received on Friday, 1 December 2017 23:44:55 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:09:09 UTC