Open madhusudhand opened 7 months ago
Going to add this to the 6.5.1 section for consideration since this impacts a feature coming to 6.5 but is minor in the grand scheme of things.
My guess is that it's because we're directly overriding the hook's props here.
~I would like to submit a PR soon.~
Update: It seems that the above is not the cause. I'll continue researching, but I'd be happy if anyone can find a solution to this problem.
@t-hamano
As I understand the function useBorderPanelLabel uses const settings = useBlockSettings( blockName );
to get block settings and then returns the right label.
But, the settings object is being returned differently from different instances.
for comparison
from global styles returns settings.border.radius: true
,
where as
from block inspector-controls returns settings.border.radius: false
.
I don't understand the reason behind this.
But, the settings object is being returned differently from different instances.
Yes, I'm also wondering why this happens 🤔
@annezazu since we reverted a change in #60204, shadows in classic themes aren't enabled/supported yet and it's no longer a bug in 6.5 This will be address in WordPress 6.6 along with support for classic themes.
shadows in classic themes aren't enabled/supported yet and it's no longer a bug in 6.5
Given this, I'm going to remove this issue from the 6.5.x board, since we no longer plan to address it in a minor release.
This is issue when the support is enabled in classic themes in #60373
This is not a regression, must be punted to 6.7
Description
When
defaultPresets
is set to true in classic themesvia functions.php
Issue: Label is set to
Shadow
even though there exists radius control. Expectation: When Border and shadow controls both present label should be set toBorder & Shadow
Step-by-step reproduction instructions
Enable defaultPresets by adding following code to
functions.php
Screenshots, screen recording, code snippet
No response
Environment info
Please confirm that you have searched existing issues in the repo.
Yes
Please confirm that you have tested with all plugins deactivated except Gutenberg.
Yes