There was an error while loading. Please reload this page.
📝 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: pt-BR pages link to pt-BR pages
📝 docs: Components speaks pt-BR