Skip to content
New issue

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

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

Already on GitHub? # to your account

V15: Make it more clear that a tree node is disabled #18545

Open
bjarnef opened this issue Mar 3, 2025 · 2 comments
Open

V15: Make it more clear that a tree node is disabled #18545

bjarnef opened this issue Mar 3, 2025 · 2 comments
Assignees
Labels
affected/v15 area/frontend state/reproduced state/sprint-candidate We're trying to get this in a sprint at HQ in the next few weeks type/bug

Comments

@bjarnef
Copy link
Contributor

bjarnef commented Mar 3, 2025

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

15.3.0-rc

Bug summary

Currently when a tree node is disabled (or isn't selectable), I don't think it is clear enough.

Image

In the old backoffice (v13) these were dimmed + not-allowed cursor style.

Image

Specifics

No response

Steps to reproduce

Notice when selecting a master template for a template, there is no visual difference from a selectable and non-selectable tree node besides cursor style and the current template is highlighted.

Expected result / actual result

No response


This item has been added to our backlog AB#50244

Copy link

github-actions bot commented Mar 3, 2025

Hi there @bjarnef!

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 🤖 🙂

@NguyenThuyLan
Copy link
Contributor

umbraco/Umbraco.UI#1034

@iOvergaard iOvergaard added the state/sprint-candidate We're trying to get this in a sprint at HQ in the next few weeks label Mar 8, 2025
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
affected/v15 area/frontend state/reproduced state/sprint-candidate We're trying to get this in a sprint at HQ in the next few weeks type/bug
Projects
None yet
Development

No branches or pull requests

3 participants