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

Slider property editor no longer supports decimal values #17546

Closed
matthewcare opened this issue Nov 15, 2024 · 2 comments
Closed

Slider property editor no longer supports decimal values #17546

matthewcare opened this issue Nov 15, 2024 · 2 comments
Labels
state/sprint-candidate We're trying to get this in a sprint at HQ in the next few weeks type/bug

Comments

@matthewcare
Copy link
Contributor

matthewcare commented Nov 15, 2024

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

15

Bug summary

I've upgraded to v15, and am finding that my "slider" editor isn't working correctly, whereby I cannot save my document if I change the slider value as now it doesn't seem to support decimals.

Specifics

Previously I was using this to set the sitemap XML priority value, which needs to be between 0 and 1.
image

Although the validation / tooltip says that the value should be a whole value, it doesn't actually prevent you from saving the data type. (In my case the data type already existed).

image
image

When viewing the data type on a page, it partially shows decimal values (values above the track are decimal, values below the track are rounded to the nearest whole)

Attempting to save the page results in this error
image

Steps to reproduce

Create a slider data type with a decimal initial value and step (as shown in previous picture)
Add the data type to your document type, and try to save a page.

Expected result / actual result

No response


This item has been added to our backlog AB#46062

Copy link

Hi there @matthewcare!

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

@bergmania bergmania added the state/sprint-candidate We're trying to get this in a sprint at HQ in the next few weeks label Nov 16, 2024
@nikolajlauridsen
Copy link
Contributor

This turned out to be two issues 😄 The backend is fixed in #17568 and the frontend in UUI umbraco/Umbraco.UI#959

Thanks for reporting 🐛🕵️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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