-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Button block border: fix block validation issue for numeric border radius #33100
Conversation
CC: @aaronrobertshaw — I wasn't sure if it was best for us to add a deprecation or ensure we can handle both cases from within the edit and save functions. Because we aren't changing the markup of the saved post content, I was leaning toward handling both cases, but happy to look into deprecations if you think that's a better approach to resolving this. |
Size Change: +77 B (0%) Total Size: 1.05 MB
ℹ️ View Unchanged
|
I see there's a separate PR that looks at using the deprecation approach in #33117 — that one might be better to land than this one? |
Thanks for working on a fix for this @andrewserong, I'm wondering if the oversight I made actually occurred in #31483 rather than #33017. Fixing up the deprecations appears to be the best option so I'd vote we close this one in favour of #33117. |
Good call, thanks @aaronrobertshaw, I'll close this one out. |
Following on from #33017, it looks like we might have missed a particular case of the button block where the radius is set numerically. This resulted in the following block pattern throwing a block validation error:
Description
Following on from #33017, add back in a condition to use the numeric border radius attribute if present, otherwise use the border props styles.
How has this been tested?
Screenshots
After this change, the above should render correctly, e.g.
Types of changes
Bug fix
Checklist:
*.native.js
files for terms that need renaming or removal).