mirror of
https://github.com/OrcaSlicer/OrcaSlicer.git
synced 2026-07-29 13:52:07 +00:00
cleanup
This commit is contained in:
@@ -153,15 +153,12 @@
|
||||
autocomplete="off" autocapitalize="off" aria-label="Capability configuration (JSON)"></textarea>
|
||||
</div>
|
||||
<!-- Custom capability UI. Sandboxed without allow-same-origin, so the plugin's HTML
|
||||
runs in an opaque origin: it cannot touch this page, and the only host surface
|
||||
it gets is the window.orca getConfig/saveConfig bridge injected into srcdoc. -->
|
||||
runs in an opaque origin and reaches the host only through the injected
|
||||
window.orca bridge. -->
|
||||
<iframe id="configCustom" class="config-custom" title="Plugin configuration"
|
||||
sandbox="allow-scripts" referrerpolicy="no-referrer" hidden></iframe>
|
||||
<!-- Host chrome for both editors, not just the JSON one: a capability with a custom
|
||||
UI needs Restore just as much, and keeping it here leaves it out of the plugin's
|
||||
HTML and off the JS bridge. Save and the validation message belong to the JSON
|
||||
editor alone (a custom UI saves through its own controls), so they are hidden
|
||||
when a custom UI is showing. -->
|
||||
<!-- Host chrome for both editors: a custom UI needs Restore too, and keeping it here
|
||||
leaves it off the JS bridge. Save and validation are JSON-editor only. -->
|
||||
<div id="configFooter" class="config-view-footer" hidden>
|
||||
<span id="configValidation" class="config-validation" role="status" aria-live="polite"></span>
|
||||
<div class="config-actions">
|
||||
|
||||
Reference in New Issue
Block a user