-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Enable back dropCap for paragraph #24930
Conversation
Size Change: +22 B (0%) Total Size: 1.17 MB
ℹ️ View Unchanged
|
const blockSupportValue = getBlockSupport( blockName, path ); | ||
if ( blockSupportValue !== undefined ) { | ||
return blockSupportValue; | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we need to check block support here? I think we should remove that check entirely from here. the useEditorFeature should be just about theme.json and block-editor setting and the hook should check for block support. At least that's my reasoning for the change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, I think the issue is on Core's experimental-default-theme.json
. It should be "true" there and not disabled. This fil e corresponds to the default value for Core if I'm not wrong.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alternative at #24932
Super-seeded by #24932 |
This fixes a regression introduced at #24761 by which the paragraph block lost the dropCap control.