label not triggering form control elements events

[Klemen2]

In html, some events on form control elements can be triggered by interacting with the label itself, while in blitz they do not trigger them.

Examples

<label onclick="console.log('label 1')">Label 1<input onclick="console.log('input 1')"></label>
<label for="input" onclick="console.log('label 2')">Label 2</label><input id="input" onclick="console.log('input 2')">

rsx! {
      label {
          onclick: move |_| {dbg!("label 1");},
          "Label 1",
          input {
              onclick: move |_| {dbg!("input 1");}
          }
      }
      label {
          for: "input",
          onclick: move |_| {dbg!("label 2");},
          "Label 2"
      }
      input {
          id: "input",
          onclick: move |_| {dbg!("input 2");}
      }
  }

[nicoburns]

Hmm... we definitely have some support for this, but I think perhaps it only generates default actions and not actual script-observable events.

[yinnho]

Data point from a taffy-lineage renderer on our side (aginxbrowser): forwarding through the control's own .click() is what makes label activation fully script-observable (15b5470).

When a click lands on a label (or a non-interactive descendant of one), we resolve the labeled control — the for attribute's target when present and non-empty, else the first labelable descendant — and call control.click() on it. That runs the control's real listeners plus its own activation behavior, so frameworks binding on the input's click/change see the same sequence a mouse user produces. Checkbox toggling, input+change events, all of it.

Two edge cases worth pinning if you grow the default-action path into this: a click landing directly on an interactive descendant of the label must not forward (or checkboxes toggle twice per click), and a disabled control has no activation behavior — including disabled through an ancestor <fieldset>.