Skip to content

Conversation

@andrewserong
Copy link
Contributor

This PR adds the following CSS properties to safe_style_css to support positioning:

  • position
  • top
  • right
  • bottom
  • left
  • z-index

This is a prerequisite for rolling out a feature from Gutenberg that allows container blocks (e.g. Group) to be set to a particular position (e.g. sticky or fixed). For more context, see the Gutenberg PR: WordPress/gutenberg#46142

The goal with adding these CSS properties is to be able to support (especially in the longer term) sticky/fixed/relative/absolute positioning of blocks, a position offset (top/right/bottom/left) and which block sits ontop of another block (so that sticky/fixed blocks can sit above site or post content).

To test, ensure the tests pass, or if you're using the Docker environment for wordpress-develop, run the following locally: npm run test:php /var/www/tests/phpunit/tests/kses.php

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


This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.

@mukeshpanchal27
Copy link
Member

@andrewserong Left one feedback

Copy link
Contributor

@hellofromtonya hellofromtonya left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • Confirmed this PR does cover the needed changes from the GB PR

Changes LGTM 👍 Marking for commit.

@hellofromtonya
Copy link
Contributor

Sorry the delay in reviewing this. It didn't have the things I'm tracking in Trac query for finding backports. Added the gutenberg-merge keyword.

@hellofromtonya
Copy link
Contributor

@andrewserong
Copy link
Contributor Author

Wonderful, thank you! Now that this has landed, I'll put together the follow up changes for the rest of the position block support 👍

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.

3 participants