-
Notifications
You must be signed in to change notification settings - Fork 4k
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
RichText: Remove 'Footnotes' when interactive formatting is disabled #53474
Merged
Mamaduka
merged 3 commits into
trunk
from
fix/rich-text-footnotes-interactive-formatting
Aug 10, 2023
Merged
Changes from 2 commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -71,16 +71,18 @@ export function useFormatTypes( { | |
return false; | ||
} | ||
|
||
// The "Footnote" format requires special handling due to its nested interactive content tag. | ||
if ( | ||
withoutInteractiveFormatting && | ||
interactiveContentTags.has( tagName ) | ||
( name === 'core/footnote' || | ||
interactiveContentTags.has( tagName ) ) | ||
) { | ||
return false; | ||
} | ||
|
||
return true; | ||
} ); | ||
}, [ allFormatTypes, allowedFormats, interactiveContentTags ] ); | ||
}, [ allFormatTypes, allowedFormats, withoutInteractiveFormatting ] ); | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Fixes the
|
||
const keyedSelected = useSelect( | ||
( select ) => | ||
formatTypes.reduce( ( accumulator, type ) => { | ||
|
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Maybe we should add a property to the format registration object to let formats declare themselves as interactive (in addition to checking the tag of course).
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.
Yes. I was also thinking about that after I pushed this PR. There could be other cases like this and we don’t want to maintain a separate list of format types.
I’ll update the code 👍
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.
Updated in 638bac2.
Sidenote: It would be nice to document some "recent" additions to format-type settings like
object
,contentEditable
andattributes
. I know @fabiankaegy has requested this before - #40051.