feat(editor): a clear final state once the engine spent its three recoveries (canvas and action alerts)
This commit is contained in:
1 parent
f0580922b5
commit
0279953e9e
19 files changed
+101
-16
No files matched your search
@@ -809,7 +809,11 @@ imports it and restyles `data-state` in place as before.
|
||||
7. When the canvas cannot be drawn, it says why, inside the canvas (owner
|
||||
decision 2026-10-15): the engine did not run (`core_unavailable`,
|
||||
`internal`: the existing `sheet.core_unavailable` notice with "Réessayer",
|
||||
the retry builds again) or the view itself cannot be drawn (`svg_rejected`,
|
||||
the retry builds again on a fresh instance), the engine stopped after its
|
||||
three recoveries (`CoreRuntime.stopped`: the `core.stopped` notice, "reload
|
||||
the page, your report is kept in this tab", no retry; the editor's action
|
||||
alerts say the same instead of "try again") or the view itself cannot be
|
||||
drawn (`svg_rejected`,
|
||||
`no_asset`, `unknown_view`, `invalid_character`, a parse failure: the
|
||||
`canvas.view_unavailable` notice, no retry since nothing would change). The
|
||||
technical kind and detail stay in the core's outcome and the DEV console;
|
||||
|
||||
Reference in new issue
Block a user