Repository navigation
[css-contain-1] Allow new features, in future? #5808
Description
The pubrules checker has a suggestion:
If it is the intention to incorporate new features in future updates of the Recommendation,
please make sure to identify the document as intending to allow new features.
If it is the intention to incorporate new features in future updates of the Recommendation,
please make sure to identify the document as intending to allow new features.
Recommended text is:
Future updates to this Recommendation may incorporate new features.
Include one of this source code:
<p>Future updates to this Recommendation may incorporate
<a href="https://www.w3.org/2020/Process-20200915/#allow-new-features">new features<a>.</p>
@frivoal @tabatkins Do we want to do that? If so, now (before Monday) would be the time :)
Activity
svgeesus commentedon Dec 18, 2020
Since if doesn't commit us to anything, but allows adding new features, should we add this to the CSSWG Proposed Rec boilerplate?
tabatkins commentedon Dec 18, 2020
Yes and yes.
fantasai commentedon Dec 19, 2020
I don't think we'll be adding features to the REC of css-contain-1, we'd be adding it to css-contain-2, which already exists.
frivoal commentedon Dec 20, 2020
We cannot. As 6.2.9 of the Process says:
css-contain-1 has already been a REC before, and didn't carry this text, so it cannot be added now.
(this is intentional: RECs that predate Process 2020 could not gain new features, and may be normatively referenced by things that count on this property to be maintained. So as not to change the existing meaning of REC, only things that declare the intention of gaining new features prior to becoming a REC can do so)
We don't need to, since css-contain has a level 2, which deals with the new features.