[CSSWG][css-cascade-4] CR of CSS Cascade L4

[fantasai]

The CSS WG has published a Candidate Recommendation and invites implementations
of the CSS Cascading and Inheritance Module Level 4

https://www.w3.org/TR/css-cascade-4/

This CSS module describes how to collate style rules and assign values to all
properties on all elements by way of cascading (choosing a winning declaration
among many) and inheritance (propagating values from parent to child).

Additions to Level 4 include:

  * introduced the 'revert' keyword, which rolls back the cascade
to the previous origin
  http://www.w3.org/TR/css-cascade-4/#default

e.g. * { all: revert; } /* wipe out the entire set of author-level styles */

  * introduced supports() syntax for conditional @import rules
  http://www.w3.org/TR/css-cascade-4/#at-import

There have been no changes since the September LCWD.

Please send comments, if any, to the www-style mailing list, ,
and  please, prefix the subject line with

[css-cascade-4]

(as I did on this message).

For the CSS WG,
~fantasai

Re: Web Push API intended scope

[Martin Thomson]

On 16 January 2016 at 08:06, Ben Last  wrote:
> I don't recall this being stated as a design goal or implicit requirement,
> though I may have missed it. What counts as infrequent in this context?

Maybe it wasn't express, but implied.

There are a few simple drivers for this:

1. Push messaging is intermediated and relatively slow and expensive;
direct communication is always cheaper and faster
2. ...but only when you already have a connection; maintaining a long
term connection from multiple clients is very expensive.

Therefore, push is best used when you don't have a direct
communication channel open to your site.  Use direct connections when
available, but let them close and use push when you aren't actively
using them.