Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change button when configuring property is not visible when focused #17451

Closed
MMasey opened this issue Nov 7, 2024 · 4 comments
Closed

Change button when configuring property is not visible when focused #17451

MMasey opened this issue Nov 7, 2024 · 4 comments

Comments

@MMasey
Copy link
Contributor

MMasey commented Nov 7, 2024

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

15.0.0

Bug summary

When using the keyboard whilst configuring a property on a document type, if you want to change the property type, focusing on the "Change" button does not make it visible

Specifics

No response

Steps to reproduce

  1. Navigate to Settings -> Document Types
  2. Create a new document type if one doesn't exist
  3. Add a new property, or select an existing property
  4. Use the keyboard and tab through the different fields used to configure the proeperty. When you get to the Change button, it does not become visibe

Expected result / actual result

How it currently looks when focusing on the Change button (blue circle indicates where we should be seeing the button).
image

What it it should look like
image

@MMasey MMasey added the type/bug label Nov 7, 2024
Copy link

github-actions bot commented Nov 7, 2024

Hi there @MMasey!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

  • We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
  • If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
  • We'll replicate the issue to ensure that the problem is as described.
  • We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

@MMasey
Copy link
Contributor Author

MMasey commented Nov 7, 2024

This issue was actually related to the UUI library. I have greated a PR for it at umbraco/Umbraco.UI#949

I'm not sure what steps need to be taken, once the PR has been merged into the UI library

@nielslyngsoe
Copy link
Member

Hi @MMasey currently we do not have a process, or in other words, the process is that when we see value in UI Library, value that is not yet released, then we make it happen and it gets into the next CMS release.

Ideally this would happen once for each minor.

In other words this will take part of 15.1

@nielslyngsoe
Copy link
Member

I'm closing this as the PR have taken part in latest UI Library release, which takes part of v.15.1 — In other words, fixed in 15.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants