Bugfix: Use <uui-input-lock> for workspace aliases
#2175
Merged
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
leekelleher
force-pushed
the
v14/bugfix/uui-input-lock-for-aliases
branch
from
8a5f710
to
666c5fe
Compare
|
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
Makes use of the
<uui-input-lock>component for workspace name/alias combinations.Fixes umbraco/Umbraco-CMS#16246.
This PR separates out part of PR #2092, to focus on the
<uui-input-lock>component, so to fix the accessibility/tabbing issue (for v14.2.0-RC).Auto-generating the alias is not part of this PR.
Types of changes
How to test?
Test that the padlocked alias UI is accessible in the following areas: