WORK-725
ID:WORK-725Status:ready

The UI a behaviour builds carries data-name, and its CSS moves to it

SPEC-196 D6. Behaviours create their own UI (toolbars, buttons, indicators) with about 70 className = writes. Those classes are the behaviour's own, so nothing breaks while they stay. But the CSS styling them reads classes, so a page under classes: "none" would still depend on them. Each element also gets a data-name, and the CSS moves to it.

This is the lowest-priority item in the milestone. If it slips, it moves to the next one without holding anything up.

Priority:lowComplexity:moderateMilestone:v0.50.0Source:SPEC-196
claude/composition-usage-rune-pages-c87ar6 View source

Criteria completion

Criteria completion: 0 of 4 (0%) checked; tracking started on Nov 9, no incremental history yet0%25%50%75%100%Nov 9Nov 22

Tracking started Nov 9 — check back for trends.

Branches 2
claude/composition-usage-rune-pages-c87ar6 current ready
main readyclaude/rune-composition-layout-convention-hkqrzx ready
History 1
  1. aea7072
    Created (ready)by bjornolofandersson

Acceptance Criteria

  • Every element a behaviour creates and gives a class also gets a data-name (or data-state for a state class)
  • The Lumina rules styling behaviour-built UI select the attributes
  • The classes stay: this item adds attributes and moves CSS, and removes nothing
  • The behaviour tests that check created UI assert the attribute

Approach

  • WORK-723 already gives data-name to the elements its 13 self-injected selectors target. Start from the className = writes it left, behaviour by behaviour.
  • Name each element as its part of the rune: data-name="toolbar", data-name="sort-indicator". Reuse a name the rune's config already declares where the element plays that part.

Blocked by

  • WORK-723

References

  • SPEC-196 D6.