Define / constrainNav block orientation via block supports #32596
Conversation
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
|
Size Change: -686 B (0%) Total Size: 1.03 MB
ℹ️ View Unchanged
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
A PoC PR which works as part of #30007 (comment).
The aim is to be able to restrict the orientation of the Nav Block via block supports.
How has this been tested?
block.jsonfor thecore/navigationblock change the following to only include one or other of the orientations:__experimentalAllowedOrientations.Unfortunately the variations still show up but this is a PoC and we can explore that later.
Screenshots
Types of changes
Checklist:
*.native.jsfiles for terms that need renaming or removal).