Skip to content

Backport of UI: Move keyboard help text above code editor on ACL policy creation page into release/1.20.x#30896

Merged
drivera258 merged 1 commit into
release/1.20.xfrom
backport/ui/VAULT-32374/fix-keyboard-trap/partially-open-sole
Jun 6, 2025
Merged

Backport of UI: Move keyboard help text above code editor on ACL policy creation page into release/1.20.x#30896
drivera258 merged 1 commit into
release/1.20.xfrom
backport/ui/VAULT-32374/fix-keyboard-trap/partially-open-sole

Conversation

@hc-github-team-secure-vault-core
Copy link
Copy Markdown
Collaborator

Backport

This PR is auto-generated from #30865 to be assessed for backporting due to the inclusion of the label backport/1.20.x.

The below text is copied from the body of the original PR.


Description

What does this PR do?

  • Moves helper text from the bottom of the json editor on ACL policy page to the top so a keyboard-only user knows how to exit out it before entering into it and isn't trapped unknowingly

Solves a11y defect regarding keyboard trap when creating an ACL policy

before (below editor) after (above policy section header)
image image

TODO only if you're a HashiCorp employee

  • Backport Labels: If this fix needs to be backported, use the appropriate backport/ label that matches the desired release branch. Note that in the CE repo, the latest release branch will look like backport/x.x.x, but older release branches will be backport/ent/x.x.x+ent.
    • LTS: If this fixes a critical security vulnerability or severity 1 bug, it will also need to be backported to the current LTS versions of Vault. To ensure this, use all available enterprise labels.
  • ENT Breakage: If this PR either 1) removes a public function OR 2) changes the signature
    of a public function, even if that change is in a CE file, double check that
    applying the patch for this PR to the ENT repo and running tests doesn't
    break any tests. Sometimes ENT only tests rely on public functions in CE
    files.
  • Jira: If this change has an associated Jira, it's referenced either
    in the PR description, commit message, or branch name.
  • RFC: If this change has an associated RFC, please link it in the description.
  • ENT PR: If this change has an associated ENT PR, please link it in the
    description. Also, make sure the changelog is in this PR, not in your ENT PR.

Overview of commits

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jun 6, 2025

Build Results:
All builds succeeded! ✅

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jun 6, 2025

CI Results:
All Go tests succeeded! ✅

@drivera258 drivera258 merged commit be21046 into release/1.20.x Jun 6, 2025
36 of 38 checks passed
@drivera258 drivera258 deleted the backport/ui/VAULT-32374/fix-keyboard-trap/partially-open-sole branch June 6, 2025 18:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed pr/no-changelog pr/no-milestone ui

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants