A regression bug was identified in Neo.filter.BooleanContainer. The issue arises from the shift to domApiRenderer as the default in DefaultConfig.mjs. Some setters update vdom.text (mapping to element.textContent) instead of vdom.html. This causes escaped strings (e.g., <i>) to render as text instead of HTML elements.
Specifically, Neo.form.field.CheckBox uses valueLabelText and afterSetValueLabelText, which sets vdom.text.
Proposed Solution:
- Refactor
Neo.form.field.CheckBox:
- Rename
valueLabelText_ to valueLabel_ (breaking change).
- Accept either a string or a VDOM object/array.
- If it's a string, treat it as
text.
- Update
Neo.filter.BooleanContainer to use the new config.
- Find and update all usages of
valueLabelText across the codebase (src, apps, examples, docs/app).
Affected Files:
src/form/field/CheckBox.mjssrc/filter/BooleanContainer.mjs- All files using
valueLabelText config on CheckBox.
A regression bug was identified in
Neo.filter.BooleanContainer. The issue arises from the shift todomApiRendereras the default inDefaultConfig.mjs. Some setters updatevdom.text(mapping toelement.textContent) instead ofvdom.html. This causes escaped strings (e.g.,<i>) to render as text instead of HTML elements.Specifically,
Neo.form.field.CheckBoxusesvalueLabelTextandafterSetValueLabelText, which setsvdom.text.Proposed Solution:
Neo.form.field.CheckBox:valueLabelText_tovalueLabel_(breaking change).text.Neo.filter.BooleanContainerto use the new config.valueLabelTextacross the codebase (src,apps,examples,docs/app).Affected Files:
src/form/field/CheckBox.mjssrc/filter/BooleanContainer.mjsvalueLabelTextconfig on CheckBox.