Supported HTML and SVG vocabulary

The current tag names, attribute names, value categories, and rejected React spellings for zudo-react.

What the renderer accepts

The renderer uses the finite names below for standard HTML and SVG elements. Attribute acceptance is per name across the namespace, not per element: for example, loading is accepted on iframe, img, video, and div. The HTML and SVG attribute sets are separate; common attributes and the listed open-ended families apply in both namespaces. These counts and tables come from the current vocabulary.ts source, including rb.

The svg tag starts the SVG namespace. A foreignObject switches its children to HTML; a nested svg switches back to SVG. An unsupported tag in the active namespace reports ZR_TAG.

Element names

HTML tags (118)

An HTML custom element name matching ^[a-z][a-z0-9]*(?:-[a-z0-9]+)+$ (for example, x-card) is also accepted. Custom element attributes follow their separate string-only rule below. Custom elements also support on:<event> listeners and reserved runtime props.

SVG tags (26)

Attribute names

The lists below are flat name sets, not per-tag HTML tables. A name in the HTML set is accepted on any supported HTML tag; a name in the SVG set is accepted on any supported SVG tag. Some names occur in more than one set.

These families are accepted on standard HTML and SVG elements:

The attribute name must match ^[A-Za-z_:][A-Za-z0-9_:.-]*$. Null and undefined values are omitted. For standard attributes not listed in a special value category, strings and finite numbers are accepted.

Attribute value categories

The following value rules apply to the names shown whenever those names are accepted in the active namespace. The sets can overlap with the common, HTML, and SVG name groups.

style is common to both namespaces but has a dedicated handler: CSS strings pass through, while plain object styles are validated. It is not a string-only standard attribute. Custom element attributes take precedence over these standard categories and must be strings; reactive string values are supported, and null and undefined are omitted.

Rejected React spellings and suggestions (35)

These are diagnostic suggestions, not accepted aliases: the authored React spelling fails and is neither rewritten nor emitted. The suggestion is available only when its target spelling is valid in the current namespace. dangerouslySetInnerHTML suggests the special renderer prop rawHtml, which is not an HTML attribute. on[A-Z] event props are handled separately: for example, onClick suggests on:click, and onDoubleClick suggests on:dblclick.

Ordinary aliases are not checked specially on custom elements, which accept otherwise valid attribute names as strings. The legacy spellings listed here remain rejected on custom elements, as do React-style on[A-Z] props. A legacy spelling is also rejected in other namespaces, but has no suggestion there when its target is invalid. Other mappings produce ZR_PROP_DIALECT only in the listed namespace; in other namespaces they fail with ZR_ATTRIBUTE as unsupported attribute names.

Runtime props are not attributes

• key belongs to the description, and children supplies child content; neither is emitted as an attribute.

• ref is a client runtime object prop. Native listeners use on:<event> as described above.

• modelValue, modelChecked, defaultValue, and defaultChecked are form runtime props, not HTML attributes. See the forms guide.

• rawHtml supplies trusted renderer-owned markup, is mutually exclusive with children, and is unsupported in SVG. See Components and JSX.

• style uses a dedicated handler: CSS strings pass through, while plain object styles are validated.

Read a vocabulary error

An unsupported attribute name or value reports ZR_ATTRIBUTE; an unsupported tag reports ZR_TAG. For static rendering, the message includes the tag or attribute, element path, and phase:

ZR_TAG: madeuptag at root in static render
ZR_ATTRIBUTE: input.enterkeyhint at root in static render

See server rendering for the full diagnostic format.