When valueField/textField are not explicitly set in opts, the auto-select logic (line 1140) and nullable empty-option creation (lines 1144-1145) used data[0][undefined] which returned undefined, causing: - Single-option selects to show blank (auto-select failed) - nullable empty options to have undefined keys Now extracts vf/tf local variables with ||'value'/||'text' fallback at the top of build_options(), used consistently throughout.
21 lines
589 B
Markdown
21 lines
589 B
Markdown
# Html
|
|
|
|
Control Function: Used to insert custom HTML content into a page.
|
|
Type: Ordinary control
|
|
Parent Control: `bricks.JsWidget`
|
|
|
|
## Initialization Parameters
|
|
|
|
- `html` (String)
|
|
The HTML string content to be inserted into the control. This content will be set as the `innerHTML` of the control's DOM element.
|
|
|
|
Example:
|
|
```js
|
|
new bricks.Html({
|
|
html: '<div style="color: red;">This is red text</div>'
|
|
});
|
|
```
|
|
|
|
## Main Events
|
|
|
|
No specific events (inherits general events from the parent class, such as `init`, `render`, etc., but this control does not define any specific events). |