Skip to content

KSES: Allow CSS anchor positioning properties in safecss_filter_attr()#11419

Open
deepakpra wants to merge 1 commit intoWordPress:trunkfrom
deepakpra:add/kses-anchor-positioning
Open

KSES: Allow CSS anchor positioning properties in safecss_filter_attr()#11419
deepakpra wants to merge 1 commit intoWordPress:trunkfrom
deepakpra:add/kses-anchor-positioning

Conversation

@deepakpra
Copy link
Copy Markdown

Summary

This updates safecss_filter_attr() to allow CSS anchor positioning properties in the safe_style_css allowlist.

Added properties:

  • anchor-name
  • anchor-scope
  • position-anchor
  • position-area
  • position-try
  • position-try-fallbacks
  • position-try-order
  • position-visibility

A regression test was also added to cover the new properties.

Trac ticket: https://core.trac.wordpress.org/ticket/64972

Use of AI Tools

AI assistance: Yes
Tool(s): Codex
Model(s): GPT-5

@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 1, 2026

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props deepakprajapati.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 1, 2026

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant