Cavemanon/piratepoet
7
Fork 0
Code Pull Requests Actions Releases 16 Activity

Get rid of useFlashEditableBlocks

Browse Source 
It is a private API which is not critical for our application.
It shortly highlights blocks that are editable after a click in the parent.
As it is not critical and is private, it is a risk, and we should rather not use it.
[MAILPOET-6319]
This commit is contained in:
Rostislav Wolny
2024-11-22 10:56:46 +01:00
committed by Oluwaseun Olorunsola
parent 5bbdc41679
commit c72b0b6f79
1 changed files with 1 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
packages/js/email-editor/src/components/block-editor/visual-editor/visual-editor.tsx
View File

@ -30,7 +30,7 @@ export const TEMPLATE_PART_POST_TYPE = 'wp_template_part';
export const PATTERN_POST_TYPE = 'wp_block';
export const NAVIGATION_POST_TYPE = 'wp_navigation';
const { ExperimentalBlockCanvas: BlockCanvas, useFlashEditableBlocks } = unlock(
const { ExperimentalBlockCanvas: BlockCanvas } = unlock(
blockEditorPrivateApis
);
@ -129,9 +129,6 @@ export function VisualEditor( {
localRef,
contentRef,
renderingMode === 'post-only' ? typewriterRef : null,
useFlashEditableBlocks( {
isEnabled: renderingMode === 'template-locked',
} ),
useSelectNearestEditableBlock( {
isEnabled: renderingMode === 'template-locked',
} ),