@loadbare/widgets 0.11.0 → 0.11.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/docs/lb-checkbox.md +4 -8
  2. package/package.json +1 -1
  3. package/skills/loadbare-widgets/references/lb-checkbox.md +4 -8
package/docs/lb-checkbox.md CHANGED
@@ -33,20 +33,16 @@ so they are expansion attributes here rather than `lb-column` and
33
33
  ## Why it is not like `lb-input`
34
34
 
35
35
  `lb-input` has a script that makes the tag itself the control, so the page
36
- writes `lb-column` on the tag. `lb-checkbox` cannot do the same. A value
37
- that lands before a widget's script has loaded reaches it only as the
38
- `lb-column-value` stamp, a string, and a checkbox's state is a boolean. A
39
- script `lb-checkbox` would read the stamp `"false"` as checked, since no
40
- string is read. The native checkbox has no such gap: the hub sets `checked`
41
- on it directly.
36
+ writes `lb-column` on the tag. `lb-checkbox` is markup alone, and the hub
37
+ sets `checked` on the native checkbox inside it directly.
42
38
 
43
39
  `lb-input` could equally be markup alone; its script is a convention, kept
44
40
  for now.
45
41
 
46
42
  ## The control
47
43
 
48
- The checkbox is checked when its column is anything but `false` or null, and
49
- sends `"true"` or `"false"`. See "Checkboxes" in the data-binding reference
44
+ The checkbox is checked when its column is anything but `false`, null,
45
+ `"false"` or `""`, and sends `"true"` or `"false"`. See "Checkboxes" in the data-binding reference
50
46
  of the loadbare-app skill.
51
47
 
52
48
  ## Styling
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@loadbare/widgets",
3
3
  "description": "The basic widget set for @loadbare/app: input, select, options, picker, table, unknown-page, confirm, form, insert-dialog, master, checkbox, number, date, tel, mailto",
4
- "version": "0.11.0",
4
+ "version": "0.11.1",
5
5
  "type": "module",
6
6
  "files": [
7
7
  "dist",
package/skills/loadbare-widgets/references/lb-checkbox.md CHANGED
@@ -33,20 +33,16 @@ so they are expansion attributes here rather than `lb-column` and
33
33
  ## Why it is not like `lb-input`
34
34
 
35
35
  `lb-input` has a script that makes the tag itself the control, so the page
36
- writes `lb-column` on the tag. `lb-checkbox` cannot do the same. A value
37
- that lands before a widget's script has loaded reaches it only as the
38
- `lb-column-value` stamp, a string, and a checkbox's state is a boolean. A
39
- script `lb-checkbox` would read the stamp `"false"` as checked, since no
40
- string is read. The native checkbox has no such gap: the hub sets `checked`
41
- on it directly.
36
+ writes `lb-column` on the tag. `lb-checkbox` is markup alone, and the hub
37
+ sets `checked` on the native checkbox inside it directly.
42
38
 
43
39
  `lb-input` could equally be markup alone; its script is a convention, kept
44
40
  for now.
45
41
 
46
42
  ## The control
47
43
 
48
- The checkbox is checked when its column is anything but `false` or null, and
49
- sends `"true"` or `"false"`. See "Checkboxes" in the data-binding reference
44
+ The checkbox is checked when its column is anything but `false`, null,
45
+ `"false"` or `""`, and sends `"true"` or `"false"`. See "Checkboxes" in the data-binding reference
50
46
  of the loadbare-app skill.
51
47
 
52
48
  ## Styling