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

Incorrect link for CSS Anchor Positioning on the Experiment Features page #36170

Closed
cjpearson opened this issue Oct 2, 2024 · 0 comments · Fixed by #36173
Closed

Incorrect link for CSS Anchor Positioning on the Experiment Features page #36170

cjpearson opened this issue Oct 2, 2024 · 0 comments · Fixed by #36173
Labels
Content:Firefox Content in the Mozilla/Firefox subtree

Comments

@cjpearson
Copy link
Contributor

MDN URL

https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Experimental_features

What specific section or headline is this issue about?

CSS Anchor Positioning

What information was incorrect, unhelpful, or incomplete?

https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Experimental_features#css_anchor_positioning

The linked ticket in bugzilla relates to colors in calc() rather than anchor positioning.

What did you expect to see?

A link to the ticket for anchor positioning.

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

No response

Do you have anything more you want to share?

No response

MDN metadata

Page report details
@cjpearson cjpearson added the needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened. label Oct 2, 2024
@github-actions github-actions bot added the Content:Firefox Content in the Mozilla/Firefox subtree label Oct 2, 2024
@Josh-Cena Josh-Cena removed the needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened. label Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Content:Firefox Content in the Mozilla/Firefox subtree
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants