https://www.w3.org/TR/pointerevents/ redirects to old spec...

[marcoscaceres]

Should https://www.w3.org/TR/pointerevents/ redirect to https://www.w3.org/TR/pointerevents3/ instead?

[patrickhlauke]

Level 3 isn't REC yet, https://www.w3.org/TR/pointerevents/ points to the latest REC version (Level 2)

[marcoscaceres]

Right, but generally you’d want the main one to point to what developers and implementers should be looking at, no?

I’m asking because I googled for the spec and then took me a while to figure out I was looking at something that’s not the latest.

[patrickhlauke]

deferring to @plehegar here, as I'm not 100% au-fait with the intricacies of what exactly should redirect to where

[smaug----]

I'm rather confused about this issue. TR/ points usually to the latest published spec, but everyone should look at the latest editor's draft. And https://www.w3.org/TR/pointerevents/ has a link to that.

[plehegar]

https://www.w3.org/TR/pointerevents3/ points to ... Level 4.

I need to spend time to untangling this... :-/

[patrickhlauke]

sorry, hope i'm not the one who made it worse with recent pushes

[plehegar]

For Level 4 to be properly reflected to /TR, I would need:
[[
We will need a Group decision to publish a first public Working Draft
for level 4 if we want to reflect the gh-pages branch to w3.org/TR .
]]
Minutes of 31st July

Did we get that?

[plehegar]

ok, I fixed https://www.w3.org/TR/pointerevents3/ to link it to pushes in the level3 branch.

I need a pointer to the group decision to publish level4.

And, if we really want everyone should look at the editor's draft, we should change https://www.w3.org/TR/pointerevents/ to point to https://www.w3.org/TR/pointerevents/upcoming/ instead of https://www.w3.org/TR/pointerevents/latest/ .