Renders what it holds until a component inside it fails while rendering, updating or running an effect, then shows
the fallback in its place and raises the failure on the board enclosing the
guard, so a reader learns what went wrong while the screen around the guard keeps working. Guards nest: the innermost
one around the failing component takes the failure up, and a guard further out keeps rendering what it holds, the
inner guard showing its fallback among the rest, so a failure is confined as narrowly as guards are placed.
The failure is raised as a defect of the interface, or as a failure where the component threw problem details,
and logged to the console as caught, so whoever fixes the defect finds the stack the post leaves out.
A failure in an event handler or in asynchronous work happens outside rendering and never reaches a guard: the board
takes it up among the issues the page raises on its own account. A fallback failing in turn is taken up by the guard
enclosing this one, or left to the board where no other guard encloses it, so no failure goes unseen.
The guard keeps to its fallback for as long as it stays mounted. It takes no box of its own, so what it holds and
the fallback alike sit in the row, the grid or the flow around it as they would without the wrapper, and it carries
no semantics: a fallback telling assistive technology what went missing states it itself.
Creates a guarded area.
Renders what it holds until a component inside it fails while rendering, updating or running an effect, then shows the fallback in its place and raises the failure on the board enclosing the guard, so a reader learns what went wrong while the screen around the guard keeps working. Guards nest: the innermost one around the failing component takes the failure up, and a guard further out keeps rendering what it holds, the inner guard showing its fallback among the rest, so a failure is confined as narrowly as guards are placed.
The failure is raised as a
defectof the interface, or as afailurewhere the component threw problem details, and logged to the console as caught, so whoever fixes the defect finds the stack the post leaves out.A failure in an event handler or in asynchronous work happens outside rendering and never reaches a guard: the board takes it up among the issues the page raises on its own account. A fallback failing in turn is taken up by the guard enclosing this one, or left to the board where no other guard encloses it, so no failure goes unseen.
The guard keeps to its fallback for as long as it stays mounted. It takes no box of its own, so what it holds and the fallback alike sit in the row, the grid or the flow around it as they would without the wrapper, and it carries no semantics: a fallback telling assistive technology what went missing states it itself.