Vixen
feb85697

Core · guide

Generated content

::before and ::after with a string content — a box the sheet adds as an element's first or last child box, laid out, painted and hit as part of that element, and never an element of its own.

Edit this page on GitHub

Documents

Next

  • Cascade layers — Vixen's base / components / utilities ladder — why every theme sheet opens with the same @layer statement, what a game's or a plugin's own sheet should do, and why the whole ladder has to live inside one origin.
  • Stylesheet diagnostics — What happens to CSS Vixen cannot read — the at-rules, selectors and @apply names it drops, the build step's two refusal channels, where each refusal is now reported, why a rule that does nothing used to be indistinguishable from a rule that was never written, and the three rules that apply and still warn.
  • Inline layout — Line boxes over Vixen's layout store — inline-block and inline-flex, shrink-to-fit sizing, baseline alignment and vertical-align, and the one invariant an inline formatting context asks the store to give up.
  • The accessibility tree — A role, a name, a value, a state and a set of relations on every element, computed from what a control already holds rather than mirrored into it — plus one coalesced per-frame event, so a screen-reader bridge can cache a tree and diff it instead of asking a node at a time.