Skip to main content

Issue #2 Supporting Article Rewrite Pack (Draft)

Paste-ready rewrite blocks for supporting variant/swatch articles to prevent Fin duplication.

This draft contains four supporting-article rewrites for Issue #2. Each section is formatted for Intercom so you can copy it directly into the target article.

Rewrite 1 - Article 13768426

Target: Why is my size chart disappearing when variants change?

Proposed title: Why does my size chart disappear when variants change?

Proposed description: Learn why this happens and when enabling Reinject fixes it.

This article explains why charts may disappear after variant changes and how Reinject works. For the full troubleshooting workflow, use Fix Size Chart Disappearing After Variant or Swatch Selection.

When variants change, some themes rebuild parts of the product page. If the chart is injected inside a rebuilt container, it can disappear.

Quick fix to try first

  1. Enable Reinject in Kiwi (Styles & Settings -> Enable reinject -> Save).

  2. Retest on a live product page while switching variants.

If the issue continues, follow the complete troubleshooting article linked above.

Rewrite 2 - Article 13256403

Target: Fixing Size Chart Issues with Variant Apps (Swatch King & Similar Apps)

Proposed title: Advanced: Variant App DOM Behavior (Swatch King & Similar Apps)

Proposed description: Technical guide for DOM re-render behavior and stable placement strategy with variant apps.

This is an advanced guide for variant-app behavior (Swatch King and similar apps). For the standard end-to-end troubleshooting flow, start with Fix Size Chart Disappearing After Variant or Swatch Selection.

Variant apps may re-render product blocks, replacing DOM nodes after selection. This can remove previously injected chart elements if placement is inside dynamic containers.

This article is most useful for

  • How DOM re-rendering breaks fragile placements

  • How to identify dynamic vs stable containers

  • Why selector stability matters with variant apps

  • App-specific caveats and edge-case behavior

Keep the complete troubleshooting flow in the main article and use this one for advanced context.

Rewrite 3 - Article 10291020

Target: Swatch King and Kiwi Size Chart Compatibility

Proposed title: Swatch King-Specific Compatibility Notes for Kiwi Size Chart

Proposed description: Swatch King-only constraints, expected behavior, and safe placement guidance.

This article is specific to Swatch King compatibility behavior. For general variant/swatch disappearance troubleshooting, use Fix Size Chart Disappearing After Variant or Swatch Selection.

Swatch King can rebuild variant containers after selection. If Kiwi is placed inside those containers, charts may disappear, move, or duplicate.

Use this article to cover

  • Swatch King-specific limitations

  • Where not to inject Kiwi when Swatch King is active

  • Safer placement zones with Swatch King

For the full troubleshooting and escalation path, use the main troubleshooting article.

Rewrite 4 - Article 13256240

Target: Kiwi Size Chart Placement & Injection Troubleshooting

Proposed title: Placement & Injection Selector Reference (Advanced)

Proposed description: Reference for building stable Kiwi selectors (class, pseudo-class, parent-child strategy).

This article focuses on placement and injection selector mechanics. For the full variant/swatch disappearance troubleshooting flow, use Fix Size Chart Disappearing After Variant or Swatch Selection.

Use this article as a selector reference

  • When to use class selectors

  • Why IDs are unstable across products

  • How to use :last-of-type / :nth-of-type safely

  • How to target stable parent containers

Remove broad troubleshooting statements like "chart disappears after variant changes" unless tied directly to selector mechanics.


Rewrite 2 (Full Updated Non-Conflicting Version) - Article 13256403

Target article: Fixing Size Chart Issues with Variant Apps (Swatch King & Similar Apps)

Use this complete rewrite if you want one final version that stays advanced-only and does not conflict with the canonical troubleshooting article.

Proposed title

Advanced: Variant App DOM Behavior (Swatch King & Similar Apps)

Proposed description

Technical guide for DOM re-render behavior and stable placement strategy with variant apps.

Final rewrite

This is an advanced guide for variant-app behavior (Swatch King and similar apps). For the standard end-to-end troubleshooting flow, start with Fix Size Chart Disappearing After Variant or Swatch Selection.

Variant apps like Swatch King, Bold Options, and custom scripts can dynamically rebuild variant sections. When this happens, elements are removed and recreated, which can affect where Kiwi is rendered.

Why variant apps cause placement instability

  • Variant blocks are re-rendered after selection changes.

  • DOM nodes can be destroyed and replaced with new nodes.

  • Previously injected content can disappear if placed inside dynamic containers.

If Kiwi is injected into one of those dynamic zones, the chart may disappear, duplicate, jump position, or trigger script conflicts.

Important: These are usually theme/app DOM lifecycle issues, not basic selector syntax mistakes.

Known behaviors in Swatch-style variant apps

  • Full replacement of variant HTML blocks

  • Variant inputs generated dynamically

  • Event-driven DOM destruction and recreation

  • Multiple variant blocks sharing similar classes

Because of this, inline placement inside variant controls is fragile.

Required placement rules for variant-app stores

Do

  • Place the size chart outside variant-rendering containers.

  • Use Kiwi App Block when possible.

  • Prefer placement below the full variant section or above Add to Cart.

  • Use modal display fallback when inline placement is unstable.

Do not

  • Inject inside swatch/radio markup that reloads on variant change.

  • Inject directly into app-generated variant nodes.

  • Rely on highly dynamic IDs/classes as primary anchors.

Selector strategy (advanced)

  • Target a static parent container that exists on initial load.

  • Avoid nodes created only after variant events fire.

  • Use stable classes first, then positional pseudo-classes only when needed.

  • Re-test after variant switching to confirm persistence.

If the chart disappears after variant changes, placement is still targeting a dynamic container.

Use this article for

  • DOM and architecture-level debugging

  • Variant-app compatibility edge cases

  • Advanced selector placement decisions

For full troubleshooting workflow, use the main article.


Rewrite 1 (Full Updated Non-Conflicting Version) - Article 13768426

Target article: Why is my size chart disappearing when variants change?

Proposed title: Why does my size chart disappear when variants change?

Proposed description: Learn why this happens and when enabling Reinject fixes it.

This article explains why charts may disappear after variant changes and how Reinject works. For the complete troubleshooting workflow, see Fix Size Chart Disappearing After Variant or Swatch Selection.

Why this happens

Some themes and variant apps rebuild parts of the product page when a shopper changes color, size, or style. If Kiwi was injected inside a rebuilt container, the chart can disappear.

First fix to try: Enable Reinject

  1. Open Kiwi admin.

  2. Go to Styles & Settings.

  3. Find Enable reinject.

  4. Turn it ON and click Save.

  5. Retest on a live product page while switching variants.

What Reinject does

  • Watches for product-page content changes.

  • Re-adds chart/recommender if a theme removes it.

  • Improves stability on dynamic variant updates.

When to move to full troubleshooting

If the chart still disappears after Reinject is enabled, continue with the main article for placement checks, verification, and escalation steps.


Rewrite 3 (Full Updated Non-Conflicting Version) - Article 10291020

Target article: Swatch King and Kiwi Size Chart Compatibility

Proposed title: Swatch King-Specific Compatibility Notes for Kiwi Size Chart

Proposed description: Swatch King-only constraints, expected behavior, and safe placement guidance.

This article is specific to Swatch King compatibility behavior. For general variant/swatch disappearance troubleshooting, use Fix Size Chart Disappearing After Variant or Swatch Selection.

Known Swatch King behavior

  • Variant blocks may be rebuilt after selection.

  • IDs/classes can change after interaction.

  • Previously injected elements can disappear or move.

Swatch King-safe placement guidance

  • Do not inject inside Swatch King-managed option wrappers.

  • Prefer Kiwi App Block where possible.

  • If using selector injection, target stable parent containers outside dynamic swatch markup.

  • Use modal display fallback when inline placement remains unstable.

What this article does not cover

This article does not replace the full end-to-end troubleshooting workflow. Use the main article when you need diagnosis, verification, and escalation flow.

Escalate with Swatch context

  • Product URL + exact variant actions that cause disappearance

  • Theme name/version

  • Swatch King app/version if available

  • Placement selector screenshot and app embed state


Rewrite 4 (Full Updated Non-Conflicting Version) - Article 13256240

Target article: Kiwi Size Chart Placement & Injection Troubleshooting

Proposed title: Placement & Injection Selector Reference (Advanced)

Proposed description: Reference for building stable Kiwi selectors (class, pseudo-class, parent-child strategy).

This article focuses on placement and injection selector mechanics. For full variant/swatch disappearance troubleshooting, use Fix Size Chart Disappearing After Variant or Swatch Selection.

Use this article for selector mechanics only

  • Choosing stable parent selectors

  • Class vs ID reliability on Shopify themes

  • Using :last-of-type and :nth-of-type() safely

  • Avoiding dynamic nodes that are recreated after interactions

Recommended selector strategy

  1. Start with stable classes that exist on initial page load.

  2. Use parent -> child structure for precise placement.

  3. Add pseudo-class only when multiple similar variant blocks exist.

  4. Validate selector on multiple products/templates before finalizing.

Common selector anti-patterns

  • Product-specific dynamic IDs

  • Generic utility classes with many matches

  • Selectors that only exist after variant JS runs

Scope

Keep this article technical and selector-focused. For end-to-end troubleshooting, use the main article.

Did this answer your question?