Merge branch 'feat/a-layout-follows-its-box'
📝 docs: the auto-fill track's bounds and its narrow-grid CSS
📝 docs: every producer draws the same tree: a Text's own box, a scrolled header, a draggable's offset, the lift through wrappers and the served density, since 0.2.0-preview.61 (EN + pt-BR)
📝 docs: a layout follows its box
📝 docs: a Select, a Menu and the pickers hold their panel's keys around their tree (EN + pt-BR)
📝 docs: the inner of two nested shortcuts of one chord answers, on the web and on Photon (EN + pt-BR)
📝 docs: a shortcut that is not enabled binds nothing, and the find bar's Escape closes its own editor's bar, since 0.2.0-preview.60 (EN + pt-BR)
📝 docs: the code diff view, and a component's own keys, since 0.2.0-preview.59 (EN + pt-BR)
📝 docs: a component may be written over a base of your own (EN + pt-BR) The last item of the brief in #272. A base of your own now carries everything the subclass declares into the twin, so the page says so: constructors, fields, properties, instance and static methods, and server-action stubs. The two Build cases are the ones a reader meets immediately, so they are stated rather than implied — an overriding child carries its own build, a child that inherits carries none and the prototype chain answers. An abstract base with members and no Build is emitted with those members. And the one shape a base may not carry: a [ServerAction], refused by EQ2012, because the server registers an action under the CONCRETE component's name and a stub on the base would invoke an id nothing serves. No version mark: the feature has not shipped in a release yet, and a mark on unreleased work is a promise WikiVersionMarkTests exists to refuse. It goes on the Upgrading page when the version is cut.
📝 docs: what 0.2.0-preview.56 changes, and the live region that came with it (EN + pt-BR)
📝 docs: what 0.2.0-preview.55 changed, on the pages that describe it (EN + pt-BR)
📝 docs: 0.2.0-preview.48 — the deletion, and three renames the wiki was still teaching The release removes the pre-write-once component model and renames three things in the vocabulary. The Upgrading page gains its first entry with real substance: a table of what is gone and where to go instead, and a second one for the renames, which are the half that bites an ordinary write-once app. The rest is the wiki catching up with what stopped being true: - Icons told a reader to implement `IIconProvider` and register it in DI. The interface is gone; the section is replaced by how an icon actually reaches the screen (a value, not a service) and the two real ways to have your own. - Architecture's Server Actions example was written against `ComponentState<T>` with a separate state class. Rewritten as write-once, state and lifecycle on the component. - `Sticky` became `Pinned`, `ZIndex` became `Layer`, `Alt` became `Label`, across fourteen files. Read rather than find-replaced: lowercase "sticky" in prose is the idea and stays, and `Alt` in a keyboard table is the key.
📝 docs: the bar and the rail share a model, not their metrics Components states both sets of figures (B4 and C16) and why they differ, plus the trailing edge the rail now paints instead of leaving to its shells.
📝 docs: the B2 numbers, and the one fence the List still carries Components states the row heights (52/68/88) and the divider rule the handoff gives — 16 + leading + gap, derived from the slot — and names the selectable-list fence: aria-current rather than a listbox, because the roving tab stop belongs to a container that does not compose it yet.
📝 docs: the two-pane component, and the rail's alignment knob Components gains ListDetail (the call, the one field that answers both shapes, and the two honest fences about the compact pane swap) and the rail's Alignment, which waited on a transpiler slice rather than a design one. Two version marks named symbols older than the section they head — the repo's own guard caught both, which is what it is for.
📝 docs: starting from a shape, and a navigation that says where you are Getting Started gains the --shell tables for both templates and the reason it is a parameter and not a template per form factor. Components gains the destination-semantics section: the three spellings that could not express it, what each target emits, and why only the current entry carries the attribute.
docs: the rail and the mobile bridges ship in preview.29, not 28 Both marks named the version that was already tagged before either symbol existed. The guard compares a mark against the first tag reachable from the commit that introduced the symbol, so these two would have gone red the moment the new tag made them checkable.
docs: the rail, and a track for the form factors Components gains NavigationRail beside BottomNavigation, stated as what it is: the same destinations for two window widths, one NavItem list inside an AdaptiveNode, with the 3-5 / 3-7 counts and the Drawer past them. Both roadmaps gain Track F: tablet is shipped, ahead are the template shells, Wear OS and Android TV, and Car/AAOS is out of scope with the reason written down. Both languages, and without em-dashes, following the sweep already in the working tree.
docs: version marks in the canonical shape the guards read
docs: the interaction contract catches up with the a11y pass — both languages
📝 docs: Components speaks pt-BR
docs: the interaction contract, and the marks say which release in their own syntax Components gains the §10 contract as shipped: hover derived and pointer-only, composite selection controls as one Tab stop, modal surfaces owning the keyboard and giving it back, fields naming themselves to assistive tech, and the SDK's own strings behind one seam. Styling gains the hover derivation and why the media gate wraps the rule and never the hash. The version marks move to `eq:since <version> symbol="…" src="…"`, so the site can read the release out of the mark itself and drop a page or a section a chosen version never had.
docs: a hovered link arrives warm, and where a link leaves the reader ServerIntegration — the navigation payload does not draw, and pointing at a link warms both halves of the navigation it suggests (172ms → 28ms, no request on the click). Names the two things that were quietly false: nothing ever marked a link for the prefetch seam, and the warmed answer was stored under one key and looked up with another. Components — Link.KeepsPosition, and why chrome with its own scrolling never needed it.
docs: the coordinate space, the navigation payload, and two implicit defaults CodeEditor — one coordinate space (the viewport lives outside CodeSurface, and why), Standalone and ViewportWidth, and the caret coming back into view. Names what is still missing: the gutter is not pinned, and what pinning would cost. ServerIntegration — what a client navigation now asks the target route for, and why it goes to the route rather than a side endpoint. Compiler — the two things C# gives you for free and JavaScript does not: an unset value type is zero, and a primary-constructor parameter is instance state. Components — the two reasons InView reported nothing on the web. Capabilities — GetService<T> only worked on the web from preview.21. Styling — a vendor prefix shares its atomic class with the standard property.
docs: InView clips on both targets now
docs: the InView fence on Photon, and it as a roadmap item
docs: knowing when something is on screen
docs: every version mark says which release, and which symbol it means
docs: correct the InFlow version, and the behaviours preview.15 changed
docs: capabilities below the page, and the contract Positioned is