max / quasi

A screen can carry a stylesheet, and markup it did not write Two members for one shape: a document whose styling is data and whose middle is opaque. MNW's custom pages are the measured consumer, where a creator writes HTML and CSS, the server sanitises both and re-scopes every selector under a canvas element, and neither half had anywhere to go. Document::style is the head half. A shell's layer list is fixed for the process, so a per-request sheet could not reach the head at all. It is written last and unlayered, which is what makes "on top of" true without the screen naming a layer it cannot know. The renderer owes it one thing the app cannot owe: a <style> element is raw text and ends at the first </style, so that sequence is broken with the CSS escape for "<". HTML escaping is not available -- &gt; reaches the CSS parser as four characters and a child combinator stops working. Node::Canvas is the body half, and it is the one member a description does not describe: the app hands over markup and the renderer writes it out. What earns the concession is markup that is data, authored by somebody who is not the app. The scope is a class and an id in the markup's own words, because that is the sanitiser's contract rather than this crate's invention, and a name prefixed or renamed here would leave a re-scoped sheet matching nothing. Its own nodes draw inside the scope after the markup, which is what lets a creator's sheet reach the platform's blocks. Opaque containment for both reasons a bespoke region has it. Every host but a markup one draws nothing, which is honest here in a way it would not be for most members: these are public web pages and no terminal will serve one.