Skip to content

fix: use selector with direct descendant, tested old issue #3416

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.

Sign up for GitHub

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

Closed
Arukuen wants to merge 1 commit into from
Closed

fix: use selector with direct descendant, tested old issue #3416

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions src/block-components/columns/style.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -133,12 +133,14 @@ export const addStyles = ( blockStyleGenerator, props = {} ) => {
} )

addBlockCssFunc( {
// In the frontend, use the css custom property to specify the order.
// Old Issue: In the frontend, use the css custom property to specify the order.
// See style.scss We do this because we cannot use the direct descendent
// selector ">" in the saved CSS or else non-admin users in multisite
// will encounter block errors (this is a WP issue)
// Tested on Local with multisite (subdirectories) with non-admin account (editor).
renderIn: 'save',
styleRule: `--stk-col-order-${ i }`,
selector: `.%s-column > :nth-child(${ i })`,
styleRule: `order`,
responsive: 'all',
attrName: 'columnArrangement',
valueCallback: value => {
Expand Down
Loading