Re: [csswg-drafts] Versioning policy and backwards incompatible changes (#5114)

For maintained specs, yes, we try to make sure that lower levels are compatible with future work. This generally isn't too much work, since higher levels refine behavior or add features, they don't usually *change* things that were defined in earlier levels. In the rare cases where there's a change from what was specced previously, we go back and make sure the older spec is compatible with the future spec.

For unmaintaned specs, like CSS1, we mark the specs as obsolete and define that level as being, essentially, the set of features defined therein as defined by the higher level maintained specs.

So essentially, we're doing a combination of 1 and 2 from the OP, depending on whether we've obsoleted the spec or not.

GitHub Notification of comment by fantasai
Please view or discuss this issue at using your GitHub account

Received on Tuesday, 26 May 2020 23:50:23 UTC