Validation not working (Umbraco.RadioButtonList, Toggle)

[croban]

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

15.3.2

Bug summary

Validation does not work with Umbraco.RadioButtonList or Toggle.
I could save the document type.

Umbraco version 15.3.2

Specifics

No response

Steps to reproduce

really?

Expected result / actual result

No response

---

This item has been added to our backlog AB#48880

[github-actions]

Hi there @croban!

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]

Thanks, @croban , I was able to reproduce it on v15.2.0 (15.3.0-rc.preview.79).
However, I don't think the Toggle property has an error on it since when it is not enabled, it will have a false value

[croban]

@NguyenThuyLan thx,

Yes, this is more of a philosophical question 😊. In my view, a radio button list essentially has three possible states:

• true (selected),
• false (not selected), and
• undefined/null (no selection made by the user).

Similarly, in the case of a toggle switch, the "initial state" is unchecked.

In some scenarios, you may want to ensure that users consciously make a selection (required) rather than leaving it undefined.
This is how I believe it should work—but of course, I could be wrong.

br

[nielslyngsoe]

Hi @croban intersting thoughts on the Mandatory aspect.

I would say that a Mandatory Property would require the Toggle to be set to true.

Cause the alternative would be a undefined state (as you describe), which we should represent in the UI, so it does not become a secret state that developers understand — in other words we would need to make it clear to the user that they haven't made a choice. But this then changes how it has worked previously, so to avoid moving any cheese(breaking things) it should only hold false or true value.

But if you bring a good case for the three state approach we could make it possible. Maybe a new Property Editor, technically the name could be NullableToggle? Also notice how such toggle should be able to be unset to go back to the undefined/null state — such could properly be okay to only achieve via a Property Action.

:-)