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

V14-RC2: Colour Picker Datatype - Tab and return behavior when adding colours to is incorrect #16158

Closed
KevinJump opened this issue Apr 26, 2024 · 2 comments · Fixed by umbraco/Umbraco.CMS.Backoffice#2305

Comments

@KevinJump
Copy link
Contributor

KevinJump commented Apr 26, 2024

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

v14-rc2

Bug summary

  1. When entering colours on a Colour picker datatype the tab order between the rgb value and the label is wrong, meaning you can't tab between the two (easily)

  2. After entering a lable, hitting return doesn't open a new color value (as per v13)

Specifics

when you enter a value in the rgb box. you have to tab 4 times to move from that box to the label box. (when include lables is checked).

Also when you hit enter after you have added a label value should open a new row , so you don't have to click add.

Steps to reproduce

  • create a new colour picker datatype
  • toggle 'include lables'
  • add rgb value
  • tab

you should only have to tab once.

  • then enter a label and hit return

return should open a new row.

Expected result / actual result

No response


This item has been added to our backlog AB#42514

Copy link

Hi there @KevinJump!

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

@Zeegaan
Copy link
Member

Zeegaan commented Apr 29, 2024

I can certainly reproduce this, if I don't write a value, it works just as expected, but as soon as I write something in there, it doesn't 🤔 Thanks for reporting 🐛

@Zeegaan Zeegaan removed their assignment Apr 29, 2024
@iOvergaard iOvergaard added the state/sprint-candidate We're trying to get this in a sprint at HQ in the next few weeks label Jul 24, 2024
@iOvergaard iOvergaard added release/14.3.0 and removed state/sprint-candidate We're trying to get this in a sprint at HQ in the next few weeks state/reproduced labels Sep 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants