inset-area renamed to position-area

[chrisdavidmills]

DO NOT MERGE THIS UNTIL THE ASSOCIATED DOCS UPDATES ARE DONE: see mdn/content#35390

Summary

The CSS Anchor Positioning inset-area property has been renamed to positioned-area. See the change discussion, and the position-area spec definition.

I have been told by Chrome engineering that position-area is being added alongside inset-area as of Chrome 129, and they are removing it around Chrome 132-ish (I'll make changes related to that in a subsequent PR).

Test results and supporting details

Related issues

[chrisdavidmills]

@Elchi3 ack. I just noticed that you've already submitted a PR for this; sorry about that. Before closing, you might want to check mine to see if there is anything else you should include in yours.

[Elchi3]

Thanks Chris, my PR is more minimal as it doesn't record any data about Chrome 129 yet. (there is no beta for 129 just yet and we can't yet verify if the rename really ships in 129).

The fact that you had to add new entries to the browser/ folder is a good warning sign that compat data is being added prematurely. So, my recommendation would be to merge my PR and wait until we're in the 129 beta cycle for any other changes. Does that make sense?

[chrisdavidmills]

Thanks Chris, my PR is more minimal as it doesn't record any data about Chrome 129 yet. (there is no beta for 129 just yet and we can't yet verify if the rename really ships in 129).

The fact that you had to add new entries to the browser/ folder is a good warning sign that compat data is being added prematurely. So, my recommendation would be to merge my PR and wait until we're in the 129 beta cycle for any other changes. Does that make sense?

@Elchi3 that works for me. Get yours merged, and let me know when that happens, then I'll merge the corresponding content PR. Then let's revisit this once the 129 beta cycle starts.

[github-actions]

This pull request has merge conflicts that must be resolved before it can be merged.

[Elchi3]

@chrisdavidmills can you review #23993? That could land and then I can see about Chrome 129 next week with a collector run.

[chrisdavidmills]

@chrisdavidmills can you review #23993? That could land and then I can see about Chrome 129 next week with a collector run.

Done!

[github-actions]

This pull request has merge conflicts that must be resolved before it can be merged.

[Elchi3]

Closing in favor of #24210