1267064 - Update all CSS2 links to CSS 2.2

Status: RESOLVED INACTIVE

(Developer Documentation Graveyard :: CSS, defect)

Description

[Mats Palmgren (inactive)]

For example, on the page for the CSS z-index property:
https://developer.mozilla.org/en/docs/Web/CSS/z-index
there is a link to "CSS Level 2 (Revision 1)".

That spec is obsolete and have been replaced by CSS 2.2:
https://www.w3.org/TR/CSS22/

We should update all links to old CSS2 spec versions to point
to CSS 2.2 instead.  I'm pretty sure any paths & fragment IDs
should be the same, in this case:
https://www.w3.org/TR/CSS22/visuren.html#z-index

Comment 1

[Florian Scholz (Open Web Docs)]

I think we can either a) update the spec macros so that the key "CSS2.1" points to "CSS2.2" or b) we would need to update all the relevant pages to add a new key "CSS2.2".

Maybe Sebastian has thoughts here.

Comment 2

[Sebastian Zartner [:sebo]]

(In reply to Florian Scholz [:fscholz] (MDN) from comment #1)
> I think we can either a) update the spec macros so that the key "CSS2.1"
> points to "CSS2.2" or b) we would need to update all the relevant pages to
> add a new key "CSS2.2".

As I know that you guys are busy with other things, I'd rather vote for option a) as the quick solution and replace them step by step by "CSS2.2" afterwards.
Is there even a way to search for all relevant pages, i.e. all pages that have {{SpecName("CSS2.1",...}} or {{Spec2("CSS2.1",...}}?

Sebastian

Comment 3

[Jean-Yves Perrier [:teoli]]

I vote for a) too as it isn't really a new spec, but a new version of the same spec incorporating errata.

Comment 4

[Sebastian Zartner [:sebo]]

I picked this up now, but one more issue came up to my mind right now.
CSS 2.2 currently has the status of a working draft, while CSS 2.1 is already a recommendation.
So, it may be a bit confusing if we link to CSS 2.2 but show 'Recommendation' as its status.
Jean-Yves, what do you think about that?

Sebastian

Comment 5

[Jean-Yves Perrier [:teoli]]

I propose we wait a bit, I expect CSS 2.2 to become a recommendation very quickly. Once it is, we can change the link.

That has no fundamental influence on the readers, though I would like to avoid confusion for them.

Comment 6

[Sebastian Zartner [:sebo]]

Fine for me.

Sebastian

Comment 7

[Sebastian Zartner [:sebo]]

I'm removing myself as owner for now, because CSS 2.2 seems to take longer than expected and I am busy with other things.

Sebastian

Comment 8

[Sebastian Zartner [:sebo]]

(In reply to Jean-Yves Perrier [:teoli] from comment #5)
> I propose we wait a bit, I expect CSS 2.2 to become a recommendation very
> quickly.

Jean-Yves wrote that two and a half years ago and CSS 2.2 is still a FPWD...
So, it's fine you closed this, Janet. Once it becomes a recommendation, we can create a new issue for that.

Sebastian