You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It will be placed after all core panels, i.e. just before the Advanced panel in wordpress 5.8.3
However, for some reason, it is placed between the core panels, i.e. in front of the Typography panel in WordPress 5.9 (RC-1).
I have read the documentation and source for InspectorControls, but I could not understand why this behavior occurs.
Is there any way to place my own InspectorControls after all the core panels?
Step-by-step reproduction instructions
Please look at the code in the description.
Screenshots, screen recording, code snippet
Environment info
WordPress 5.8.3 and 5.9 RC-1
Gutenberg 12.3.0(I tested both with the gutenberg plugin enabled and disabled.)
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
The text was updated successfully, but these errors were encountered:
I have checked this issue again and the block sidebar is now split by tabs, e.g. #45005. Also, in #47105, the styles slot has been added, so this problem should not occur. I would therefore like to close this issue.
Description
I hooked up the
editor.BlockEdit
and added my ownInspectorControls
as follows.It will be placed after all core panels, i.e. just before the Advanced panel in wordpress 5.8.3
However, for some reason, it is placed between the core panels, i.e. in front of the Typography panel in WordPress 5.9 (RC-1).
I have read the documentation and source for
InspectorControls
, but I could not understand why this behavior occurs.Is there any way to place my own
InspectorControls
after all the core panels?Step-by-step reproduction instructions
Please look at the code in the description.
Screenshots, screen recording, code snippet
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
The text was updated successfully, but these errors were encountered: