Pull Request for Issue #34903.

PR #34391 that was merged in 3.9.28 was a wrong PR. The render_class was already output for the field parent element. That PR added it to the span of the value itself, which causes problems because now the same class is in two nested elements.

It's not good to apply the global render_class to the value. So we got two solutions:

• Either UNDO PR #34391 and call it a day
• Or, if you want a class for just the value, it should be a separate class.

Summary of Changes

So here's what I did:

• Revert back the wrong changed made in #34391
• Create a separate class input for just the value
• Make the value use this value class instead of the parent render class
• As a bonus, as suggested by @pepperstreet, I added the field name/alias to the class of the parent element of the field

Testing Instructions

Actual result BEFORE applying this Pull Request

The render_class of a custom field is also applied to the span of the field-value

Expected result AFTER applying this Pull Request

• The "Render Class" of a custom field is reverted back to only appear in the parent element of the field
• The parent element of the field now also gets the fieldname as additional class
• You can now use the new "Value Class" setting to give a class to the span of the field-value