A dash inside a checkbox can indicate a mixed selection, but the mark alone does not identify the selected items. It does not mean that every item is selected. To interpret the screen correctly, inspect the individual child checkboxes rather than treating the parent’s appearance as a count.
What the dash represents
In a native HTML checkbox, a horizontal line can represent an indeterminate visual state. This state is separate from the checkbox’s checked state. The appearance alone therefore cannot tell you that all children are selected, and it cannot by itself tell you what a form will submit. For the native-control distinction, see MDN’s checkbox reference.
Worked hypothetical example
Hypothetical example: imagine a reading list with four item checkboxes:
| Item | Child state |
|---|---|
| A | Checked |
| B | Unchecked |
| C | Checked |
| D | Unchecked |
In this fictional interface, the parent is deliberately given a dash to summarise the mixed child states. The calculation is 2 selected out of 4: A and C are checked, while B and D are unchecked. The correct conclusion is “two of four selected,” not “four selected.” The parent’s dash summarises the mixture; it does not replace the child states.
Suppose the parent keeps its dash while a separate record says its checked property is false. That is not a contradiction: the visual marker and checked property are separate pieces of information. Do not add a fifth selected item merely because the parent appears above the four children. Count the actual items in the stated selection scope.
What you still cannot infer
A dash does not prove that the selection has been saved, sent, or submitted. It also does not identify which children are selected unless you inspect them individually. In this hypothetical example, the observations establish only the visible checkbox states and the resulting count. They do not establish any server action or later screen outcome.