Remove the papercuts for frontend rendering (PropertyValueConverters and beyond)

[nul800sebastiaan]

Umbraco version

v9

Description

Over the years we've not been really good at paying attention to make frontend rendering a consistent experience leading to a few papercuts over time. Anything can easily be worked around of course but wouldn't it be great if everything "just" worked like you would expect it to.

It's always painful to have to close these issues and patiently explain that we're stuck with this wonky behavior. 😓

We have an opportunity now with the upcoming v9 to do something about it. Why not in v8? Well, all of these changes will introduce breaking changes for people relying on the current behavior. So each of the things listed below would be a breaking change to a significant amount of people.

With v9, people will have to rewrite their views anyway, so why not take the opportunity to make it more consistent!

This work doesn't really fit into the HQ roadmap, so we are seeking assistance from contributors in 2 areas:

1. Listing the things that are not behaving as expected, and getting to a conclusion as to how they should behave
2. Implementing the correct behavior

To get us started, I've been looking into all the issues we had to close because fixing them would mean a behavioral breaking change.

• StripHtmlTags does not remove HTML tags (if first tag is a block level element) StripHtmlTags does not remove HTML tags (if first tag is a block level element) #8789
• Default-value of a Checkbox-property is not used in YesNoValueConverter Default-value of a Checkbox-property is not used in YesNoValueConverter #7409
  / Existing instances are not updated if property (True/false) with default true is added to existing documenttype Existing instances are not updated if property (True/false) with default true is added to existing documenttype #9649
• V8 .GetCropUrl("CropAlias") generates invalid ImageProcessor URL V8 .GetCropUrl("CropAlias") generates invalid ImageProcessor URL #8116
• Numeric properties cannot be nullable Numeric properties cannot be nullable #10369
• Property value converter for Eye Dropper Color Picker Property value converter for Eye Dropper Color Picker #10323
• V8 - Model.Value() default value doesn't show if string is empty V8 - Model.Value() default value doesn't show if string is empty #6680
• Umbraco Multi Url Picker - Recursive not working in RTE Umbraco Multi Url Picker - Recursive not working in RTE #6111

I am not too sure about this one, haven't investigated yet: Textarea Macro Parameter Not Rendering HTML Markup #6286

Then there's also the package `SuperValueConverters by @callumbwhyte: https://our.umbraco.com/packages/developer-tools/supervalueconverters/. That package works with:

• Multi-Node Tree Picker
• Nested Content

So what else is missing from this list?
For each item, can we agree what the correct behavior should be, so we can work on it for the upcoming v9?

How can you help?

No response