Re: [css-cascade] unwinding all: property

On Tue, Feb 17, 2015 at 10:36 AM, Brian Kardell <bkardell@gmail.com> wrote:
> Somehow it would appear that I was absent or asleep during earlier
> discussions on this, so apologies for that, but I have an issue with our
> current incarnation of the all property values.
>
> Essentially it boils down to this:  I would be willing to wager my last
> dollar that the vast majority of authors do not understand how the browser
> arrives at how an HTML page is rendered with no author stylesheets.
> Currently many friends and people that I talk to are dismayed or surprised
> by the behavior having expected it to do something more "default" like:
>
> all: user-agent;
>
> and reset back to -that- behavior.  If suddenly the contents of script or
> style tags is displayed, or blockquotes just look like regular inline text,
> that seems to be upside down on the priority of constituencies.  Currently
> it's up to them to recreate and define what would have been an initially
> sane group of styles and that seems just wrong.

Yes, we intend to add this back.  That's why the "default" keyword is
still reserved as a global keyword.

~TJ

Received on Wednesday, 18 February 2015 18:01:24 UTC