{%- endcapture %}
{% raw %} {% endraw %}
@@ -436,13 +436,13 @@ The following example demonstrates the full technique:
{% raw %} {% endraw %}
{% capture faq_animations_html -%}
-
-
-
-
-
-
-
+
+
+
+
+
+
+
{%- endcapture %}
{% raw %} {% endraw %}
@@ -1036,7 +1036,7 @@ of the named component without requiring an extra wrapper:
{% raw %} {% endraw %}
{% capture faq_mixin_labeled_input_html -%}
-
+
diff --git a/docs/_about/showcase.md b/docs/_about/showcase.md
index 3663ba15..52371c70 100644
--- a/docs/_about/showcase.md
+++ b/docs/_about/showcase.md
@@ -522,20 +522,20 @@ in the following example:
{% capture simple_list_singleton -%}
█
-█
-█
-█ Phones:
-█
-█
(None)
-█
-█
-█
-█
-█
-█
-█
+█
+█
+█Phones:
+█
+█
(None)
+█
+█
+█
+█
+█
+█
+█
{%- endcapture %}
{% raw %} {% endraw %}
@@ -844,19 +844,19 @@ list like the following example:
{% raw %} {% endraw %}
{% capture schedule_list -%}
-
-
-
- Schedule:
-
-
- to
+
+
+
+ Schedule:
+
+
+ to
+
+ (Closed)
+ ,
+ and
- (Closed)
- ,
- and
-
-
+
{%- endcapture %}
{% raw %} {% endraw %}
@@ -2052,16 +2052,16 @@ In the *JS* tab there is a simple JavaScript code that:
{% capture nested_forms_with_load_save -%}
{%- endcapture %}
{% raw %} {% endraw %}
@@ -3236,84 +3236,84 @@ button. Then a very simple JavaScript code makes the rest...
{% raw %} {% endraw %}
{% capture calculator -%}
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
-
{%- endcapture %}
{% raw %} {% endraw %}
@@ -3500,84 +3500,84 @@ reach a perfect UX.
{% raw %} {% endraw %}
{% capture supercalculator -%}
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
-
{%- endcapture %}
{% raw %} {% endraw %}
diff --git a/docs/_advanced_concepts/data_import_and_export.md b/docs/_advanced_concepts/data_import_and_export.md
index 0de862be..a0154666 100644
--- a/docs/_advanced_concepts/data_import_and_export.md
+++ b/docs/_advanced_concepts/data_import_and_export.md
@@ -93,25 +93,25 @@ The structure of the exported value mirrors the nesting of the form:
{% raw %} {% endraw %}
{% capture export_structure_html -%}
-
{%
endcapture %}
{% raw %} {% endraw %}
@@ -229,18 +229,18 @@ The `import` action accepts:
{% raw %} {% endraw %}
{% capture import_example_html -%}
-
+
-
-
+
+
-
-
+
+
-
+
{%
endcapture %}
{% raw %} {% endraw %}
@@ -370,18 +370,18 @@ a "New record" button.
{% raw %} {% endraw %}
{% capture clear_vs_reset_html -%}
-
+
-
-
+
+
-
-
+
+
-
-
+
+
{%
@@ -464,43 +464,43 @@ directly into its target (the shipping address) subform:
{% raw %} {% endraw %}
{% capture pipe_example_html -%}
-
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
+
{%
endcapture %}
{% raw %} {% endraw %}
diff --git a/docs/_advanced_concepts/events.md b/docs/_advanced_concepts/events.md
index 18d6795c..f54b2fab 100644
--- a/docs/_advanced_concepts/events.md
+++ b/docs/_advanced_concepts/events.md
@@ -274,10 +274,10 @@ The recommended pattern is to use an `export` trigger and intercept the
{% raw %} {% endraw %}
{% capture events_submit_example_html -%}
-
-
-
-
+
+
+
+
{%- endcapture %}
{% raw %} {% endraw %}
diff --git a/docs/_advanced_concepts/form_traversing.md b/docs/_advanced_concepts/form_traversing.md
index ebd3c436..4bda31eb 100644
--- a/docs/_advanced_concepts/form_traversing.md
+++ b/docs/_advanced_concepts/form_traversing.md
@@ -378,16 +378,16 @@ while (currentItem) {
{% raw %} {% endraw %}
{% capture form_trav_copy_adjacent_html -%}
-
+
-
-
-
-
-
+
+
+
+
+
-
-
+
+
{%- endcapture %}
{% raw %} {% endraw %}
@@ -424,14 +424,14 @@ async function validateSequentially(list) {
{% raw %} {% endraw %}
{% capture form_trav_navigation_ui_html -%}
-
+
-
-
-
-
-
-
+
+
+
+
+
+
@@ -494,25 +494,25 @@ This example demonstrates a practical implementation of sibling navigation for d
{% raw %} {% endraw %}
{% capture form_trav_practical_copy_html -%}
-
+
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/docs/_advanced_concepts/hotkeys.md b/docs/_advanced_concepts/hotkeys.md
index 77c37e40..71aecf6e 100644
--- a/docs/_advanced_concepts/hotkeys.md
+++ b/docs/_advanced_concepts/hotkeys.md
@@ -110,22 +110,22 @@ re-used in different parts of the form without conflict:
{% raw %} {% endraw %}
{% capture hotkeys_context_sensitivity_html -%}
-
+
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
-
-
+
+
{%- endcapture %}
{% raw %} {% endraw %}
diff --git a/docs/_advanced_concepts/mixin_types.md b/docs/_advanced_concepts/mixin_types.md
index 059c99a3..f3d459a3 100644
--- a/docs/_advanced_concepts/mixin_types.md
+++ b/docs/_advanced_concepts/mixin_types.md
@@ -598,14 +598,14 @@ data path in the exported value.
{% raw %} {% endraw %}
{% capture mixin_contact_block_html -%}
-
-
+
+
Primary
Emergency
-
+
@@ -691,7 +691,7 @@ template's default of three.
{% raw %} {% endraw %}
{% capture mixin_option_override_html -%}
-
+
Priority tags (3 slots by default)
@@ -702,7 +702,7 @@ template's default of three.
-
+
@@ -760,10 +760,10 @@ uses `id="nameLabel"` to mark the slot, and each placeholder supplies its own
{% raw %} {% endraw %}
{% capture mixin_snippet_params_html -%}
-
+
- Author name
+ Author name
Reviewer name
diff --git a/docs/_component_types/type_color.md b/docs/_component_types/type_color.md
index 762be117..763a7bb0 100644
--- a/docs/_component_types/type_color.md
+++ b/docs/_component_types/type_color.md
@@ -78,7 +78,7 @@ Alternatively, you can also use the shorthand notation inferring the type from t
{% raw %} {% endraw %}
{% capture simple_color -%}
-
+
{%
endcapture %}
{% raw %} {% endraw %}
@@ -129,10 +129,10 @@ would have to specify the context in the button action, like this:
{% raw %} {% endraw %}
{% capture singleton_color -%}
-
+
-
+
{%
endcapture %}
{% raw %} {% endraw %}
@@ -161,10 +161,10 @@ INPUT element or its type is explicitly defined and different to "color".
{% raw %} {% endraw %}
{% capture singleton_color_error -%}
-
+
-
+
{%
endcapture %}
{% raw %} {% endraw %}
diff --git a/docs/_component_types/type_date.md b/docs/_component_types/type_date.md
index 158da894..c6d384e1 100644
--- a/docs/_component_types/type_date.md
+++ b/docs/_component_types/type_date.md
@@ -68,7 +68,7 @@ Alternatively, you can also use the shorthand notation inferring the type from t
{% raw %} {% endraw %}
{% capture simple_color -%}
-
+
{%
endcapture %}
{% raw %} {% endraw %}
@@ -111,7 +111,7 @@ throwing an error.
{% raw %} {% endraw %}
{% capture date_error -%}
-
+
{%
endcapture %}
{% raw %} {% endraw %}
diff --git a/docs/_component_types/type_datetime-local.md b/docs/_component_types/type_datetime-local.md
index 906b25a7..2149ceb8 100644
--- a/docs/_component_types/type_datetime-local.md
+++ b/docs/_component_types/type_datetime-local.md
@@ -68,7 +68,7 @@ Alternatively, you can also use the shorthand notation inferring the type from t
{% raw %} {% endraw %}
{% capture simple_datetime_local -%}
-
+
{%
endcapture %}
{% raw %} {% endraw %}
@@ -115,7 +115,7 @@ throwing an error.
{% raw %} {% endraw %}
{% capture datetime_local_error -%}
-
+
{%
endcapture %}
{% raw %} {% endraw %}
diff --git a/docs/_component_types/type_form.md b/docs/_component_types/type_form.md
index f64a66c1..3935fbf6 100644
--- a/docs/_component_types/type_form.md
+++ b/docs/_component_types/type_form.md
@@ -63,36 +63,36 @@ Following example shows a simple *SmarkForm* form with two nested forms:
{% raw %} {% endraw %}
{% capture simple_form_example -%}
-
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
+
{%
endcapture %}
{% raw %} {% endraw %}
@@ -145,26 +145,26 @@ The following example demonstrates the distinction between `clear` and `reset` a
{% raw %} {% endraw %}
{% capture clear_reset_example -%}
-
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
-
+
+
+
-
+
{%
endcapture %}
{% raw %} {% endraw %}
diff --git a/docs/_component_types/type_input.md b/docs/_component_types/type_input.md
index 6fa049c8..ca0d995e 100644
--- a/docs/_component_types/type_input.md
+++ b/docs/_component_types/type_input.md
@@ -54,7 +54,7 @@ To use the `input` component type, simply add the `data-smark` attribute to your
{% raw %} {% endraw %}
{% capture input_basic_usage_html -%}
-
+
{%- endcapture %}
{% raw %} {% endraw %}
diff --git a/docs/_component_types/type_label.md b/docs/_component_types/type_label.md
index d41f8245..ef86ef57 100644
--- a/docs/_component_types/type_label.md
+++ b/docs/_component_types/type_label.md
@@ -50,24 +50,24 @@ Enhanced SmarkForm `label` elements work similarly to standard HTML labels but o
{% raw %} {% endraw %}
{% capture basic_examples -%}
-
Explicit association
-
-
-
-
-
📌 Label propperly guesses the more appropriate target, even though the intermediate <span>.
-
-
Explicit target specification
-
-
-
-
📌 Explicit target specified by relative path.
-
-
Implicit pairing
-
-
📌 Wrapping the field inside still works likewise standard HTML.
+
Explicit association
+
+
+
+
+
📌 Label propperly guesses the more appropriate target, even though the intermediate <span>.
+
+
Explicit target specification
+
+
+
+
📌 Explicit target specified by relative path.
+
+
Implicit pairing
+
+
📌 Wrapping the field inside still works likewise standard HTML.
{%- endcapture %}
{% raw %} {% endraw %}
@@ -211,43 +211,43 @@ You can use any other element in place, like ``, `` or even `
{%
endcapture %}
{% raw %} {% endraw %}
diff --git a/docs/_getting_started/quick_start.md b/docs/_getting_started/quick_start.md
index 1fac7a22..d69e7faf 100644
--- a/docs/_getting_started/quick_start.md
+++ b/docs/_getting_started/quick_start.md
@@ -859,12 +859,12 @@ additional capabilities of the library:
➖➕
+
-
-
- ❌ Clear
- 💾 Submit
-
+
+ ❌ Clear
+ 💾 Submit
+
{%
endcapture %}
{% raw %} {% endraw %}
From 902b644cd25a2a0dd27c289f697b698b69d65fb7 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Tue, 31 Mar 2026 11:52:26 +0000
Subject: [PATCH 5/5] Fix Ace editor indentation: preserve spaces through HTML
compressor
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Root cause: Just-The-Docs theme uses vendor/compress.html (HTML compressor)
which applies `split: " " | join: " "` to ALL content outside