Skip to main content

Module reset

Module reset 

Source
Expand description

What an HTML element brings uninvited, and how a primitive gives it back.

The renderer picks an element from the description (a link that writes is a <button>, a described set of values is a <ul>) and the element arrives carrying a user-agent look nobody asked for. Withdrawing that look is a recurring ask rather than an edge case, and left to each arm it gets written by hand once per arm with no arm aware of the others.

§Why this is a withdrawal and not a depth

makeover_layout::Depth was the obvious home and is the wrong one. A depth states what a region is, a fill and a bevel, and every variant answers None for a stroke, so an added border axis would have covered one of the seven properties in play and left .link untouched. What these arms share is not a shape. It is the absence of one the browser supplied.

§Renderer-local by construction

A terminal has no element chrome to withdraw and an immediate-mode painter draws from nothing, so this concept cannot rise into the description layer. Nothing in makeover-layout knows the word, and there is no cascade.

Structs§

Reset
A set of Chrome a primitive opts into giving back.

Enums§

Chrome
One thing an element brings that a description never asked for.