Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Anchor attribute is at risk, should it be prominently documented? #38233

Open
lukewarlow opened this issue Feb 19, 2025 · 6 comments · May be fixed by #37990
Open

Anchor attribute is at risk, should it be prominently documented? #38233

lukewarlow opened this issue Feb 19, 2025 · 6 comments · May be fixed by #37990
Labels
Content:HTML Hypertext Markup Language docs needs decision The task needs consensus through discussion

Comments

@lukewarlow
Copy link
Contributor

MDN URL

https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/anchor

What specific section or headline is this issue about?

No response

What information was incorrect, unhelpful, or incomplete?

The feature this page (and other pages) refers to is only implemented behind a flag in one browser and is at risk from a standardisation point of view. The spec PR can be found here: whatwg/html#9144 overall the sentiment seems mixed. This lead to the recent implicit anchoring feature of showPopover({source}) and popovertarget.

What did you expect to see?

This is to discuss whether this feature should be documented at all, or at least as widely as it is?

Do you have any supporting links, references, or citations?

No response

Do you have anything more you want to share?

No response

@lukewarlow lukewarlow added the needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened. label Feb 19, 2025
@github-actions github-actions bot added the Content:HTML Hypertext Markup Language docs label Feb 19, 2025
@lukewarlow lukewarlow linked a pull request Feb 19, 2025 that will close this issue
@Josh-Cena
Copy link
Member

By "as widely as it is" what are you referring to? I think a single page is about the right amount of attention that each feature deserves, but if it has its own mention in a guide page, we are happy to point to alternatives instead. Our policy is anything that's available in browsers should be documented, so even if Chrome unships it, we need to wait two years to remove its documentation.

@lukewarlow
Copy link
Contributor Author

Chrome never did ship it fwiw. It's in Chrome behind a flag which I don't believe has the same requirements but could be wrong.

It's also mentioned on the main Using CSS Anchor Positioning page https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_anchor_positioning/Using#html_method possiblye elsewhere too.

@lukewarlow
Copy link
Contributor Author

This issue comes from #37990 (comment)

@Josh-Cena
Copy link
Member

I think we should remove its mention in the guide, but keep its reference, unless Chrome actually unships it, in which case it may be not subject to the 2-year rule if we think Canary means unstable anyway.

@Josh-Cena Josh-Cena added needs decision The task needs consensus through discussion and removed needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened. labels Feb 19, 2025
@hamishwillee
Copy link
Collaborator

hamishwillee commented Feb 21, 2025

I agree 100 % with Josh. FYI @chrisdavidmills - this is tangentially related to the popover stuff. Is it something you could clean?

@chrisdavidmills
Copy link
Contributor

I agree 100 % with Josh. FYI @chrisdavidmills - this is tangentially related to the popover stuff. Is it something you could clean?

Done in b9c9e03

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Content:HTML Hypertext Markup Language docs needs decision The task needs consensus through discussion
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants