“The parser accepts a type” and “the type works on this device” are different statements. This reference first gives the current type taxonomy, then leaves the final support decision to actual DeviceCaps, the target renderer, and local acceptance.
The 18 cross-device primitives
| Group | Current types |
|---|---|
| Basic interface | view, text, media, input, action, overlay |
| Structure and time | table, time, chart, map, calendar |
| Interactive surface | chat, rtc, explorer, editor, canvas, surface, afs-list |
Those 18 names form the cross-device primitive table and are the subject of the capability map. Open AUP primitives for one contract page per name. For each type, a device reports native, webview, partial, or unsupported; do not substitute the table for a real target report.
The 42 Web-only widgets
The current type table also contains 42 Web widgets. They include presentation/site-oriented types such as frame, terminal, breadcrumb, pagination, tooltip, comments-surface, blocklet-embed, webgl-hero, and wm-surface. They can have a renderer in the Web runtime, but they are not cross-device primitives and do not enter the guaranteed DeviceCaps.primitives scope.
To avoid writing “60 types” as “60 cross-device capabilities,” use these rules for documentation and examples:
| Claim | Required evidence |
|---|---|
| A primitive works on one target | That target's capability report plus real presentation acceptance |
| A primitive has a fallback | A currently listed degradation chain, verified on the target |
| A Web widget works | Web runtime/browser acceptance |
| A custom type works | Target registration/renderer plus real acceptance |
When an unknown/custom type has no shared chain, the current degradation implementation passes it through unchanged rather than automatically turning it into safe text. Before taking a custom type to a second renderer, design both its presentation and failure boundary.
Nearby references
- For device reports, the nine explicit degradation chains, and their failure shape: Device capabilities and degradation.
- For node, props, data binding, and children semantics: Semantic tree.
- For static HTML boundaries in Web Device: AUP on Web Device.
- For a document-surface walk of the 18 primitives, Markdown host, and deck media demos: AUP capability tour.
This page is the 2.0.0-beta.25 type taxonomy, not a cross-version, cross-device compatibility promise.