HtmlRenderDiagnosticCodes

All stable renderer diagnostic codes.

CSS background-image layers beyond the configured per-element limit were omitted.

A CSS background-repeat value used a single-image fallback.

A CSS background image value used a deterministic supported fallback or was omitted.

A CSS foreground or background color value used its property fallback.

Repeated CSS background images exceeded the configured operation-wide tile limit.

CSS gradients exceeded the configured color-stop limit.

Layout exceeded the configured nesting-depth limit.

Layout exceeded the configured operation limit.

A paged running-string value exceeded its configured character limit.

The source HTML string exceeded the configured character limit.

The parsed HTML document exceeded the configured DOM node limit.

A table contained no renderable rows or cells.

A table exceeded the configured row or column limit.

Collapsed table border resolution exceeded the configured segment limit.

An external image requires asynchronous resource resolution.

An external stylesheet requires asynchronous resource resolution.

A font data URI could not be decoded.

An @font-face rule had no usable family descriptor.

No source from an @font-face rule was available to the renderer.

A font source was not a supported TrueType glyf-outline font.

A CSS font-variant used a documented managed-rendering approximation.

Legacy diagnostic retained for source compatibility; bounded bidi positioning is active.

A complex-script run requires provider-owned shaping that no configured provider accepted.

Legacy diagnostic retained for source compatibility; inline paint effects are rendered by the shared effect model.

Flex layout used the documented normal-flow fallback.

A flex property value used a documented deterministic fallback.

A float or clear property value used a documented deterministic fallback.

Multi-column generation exceeded the configured safety limit.

A multi-column property value used a documented deterministic fallback.

Content without a safe page break was force-fragmented.

Grid layout used the documented normal-flow fallback.

A grid property value used a documented deterministic fallback.

Grid track expansion exceeded the configured safety limit.

A generated-content expression was omitted because it could not be represented.

A CSS counter declaration was ignored because it could not be represented.

A generated counter representation exceeded its bounded output budget and used a safe fallback.

A replaced-element sizing or object-placement value used a deterministic fallback.

A positioned inset could not be resolved by the current length model.

A positioned layout mode used the documented normal-flow fallback.

An automatic positioned inset could not use its hypothetical normal-flow anchor.

A scrollable overflow box was captured at its initial static scroll position.

An overflow property value used a documented visible fallback.

An overflow-clip-margin value used its initial padding-box zero fallback.

A CSS transform or transform-origin value used the identity fallback.

A CSS clip-path value used no clipping because it could not be represented.

A PDF semantic tag override was invalid and automatic HTML semantics were used.

A CSS bookmark value was invalid and automatic heading navigation was used.

A form control inside a transformed, translucent, or clipped paint group used static rendering because an interactive PDF widget cannot preserve the authored appearance.

A text control with a zero maximum length used static rendering because PDF /MaxLen must be positive.

A text control whose authored value exceeds maxlength used static rendering because PDF /MaxLen cannot preserve that initial state.

A multiple-file input used static rendering because PDF file-select fields cannot preserve multiple-file selection.

A form control with a whitespace-only name used static rendering because PDF field names must contain a non-whitespace character.

A checkbox or radio control with a blank submitted value used static rendering because PDF button export values must contain a non-whitespace character.

A radio group with duplicate submitted values used static rendering because PDF appearance states must be unique.

A multi-select with duplicate selected submitted values used static rendering because value-only PDF choice selections cannot preserve both option identities.

A radio group mixing enabled and disabled options used static rendering because PDF radio widgets cannot preserve disabled state per option.

A select containing disabled options used static rendering because PDF choice fields cannot preserve disabled state per option.

Multiple HTML controls sharing one submitted name used static rendering because distinct PDF fields cannot preserve repeated form-data entries under one field name.

A select containing a blank option label used static rendering because PDF choice fields require non-empty display labels.

An empty select used static rendering because interactive PDF choice fields require at least one option.

A form control with non-uniform or elliptical corner radii used truthful static rendering.

A form control with translucent widget paint used truthful static rendering.

A form control with background-image paint used truthful static rendering.

A form control with an unsupported interactive border style used truthful static rendering.

A text or choice control with typography unavailable to generated PDF widgets used truthful static rendering.

A textarea with wrap=off used truthful static rendering because PDF multiline widgets cannot preserve no-wrap appearance semantics.

A CSS opacity value used the opaque fallback.

A CSS border radius contained invalid or unsupported syntax and used square-corner fallback.

A CSS box shadow contained invalid or unsupported syntax.

CSS box-shadow layers beyond the configured per-element limit were omitted.

A CSS border paint declaration used invalid or unsupported syntax.

A CSS outline paint declaration could not be represented by the current outline model.

A sticky-positioned element was captured at its stable static document position.

A z-index declaration used auto because its value was neither auto nor an integer.

A complex page selector could not be applied per page.

A pseudo-page geometry declaration requires page-by-page content reflow.

A page-margin generated-content expression was unsupported.

A page-margin position was unsupported by the current visual model.

An @page size declaration was unsupported.

SVG content could not be represented by the bounded shared vector scene.

MathML content could not be represented by the bounded shared mathematical expression model.

A caller codec rasterized SVG features outside the bounded vector scene.

A resource exceeded the configured per-resource byte limit.

Resolved resources exceeded the operation-wide count limit.

Resolver invocations exceeded the operation-wide request limit.

A resolver returned an incompatible media type.

The configured resource resolver failed.

Resource resolution exceeded its configured timeout.

The configured resource resolver returned no resource.

A resource reference could not be represented as an absolute URI.

A resolved stylesheet could not be decoded as supported CSS text.

A recursive stylesheet import cycle was suppressed.

Stylesheet imports exceeded the configured recursion depth.

Legacy diagnostic retained for source compatibility; stylesheet URL resources are active.

A repeated table header was suppressed because it left no safe body-row break.

A repeated table footer was suppressed because it left no safe body-row break.

A table formatting property used its documented fallback.

Resolved resources exceeded the operation-wide byte budget.

A visual could not cross a forced page boundary safely.