Issue #3397πŸ’¬ AnsweredOpened April 9, 2021by YumiChen0 reactions

Sorter direction incorrect with web component slot

Quick answerby ClaudeCode

Thanks for reporting this, @YumiChen. The issue with sorter direction incorrect with web component slot appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modifications overlap, creating an inconsistent state. What to try: Add a setTimeout...

Read full answer below ↓

Question

Version:0.16.45

Are you able to reproduce the bug from the demo?

  • Yes
  • No

What is the expected behavior? Given a parent web component instance rendering some elements with slot, in the shadowDOM, if the parent element of slot got display: flex style, the sorter should be vertical, for in the result the elements are aligned horizontally.

What is the current behavior? The sorter would be horizontal.

Are you able to attach screenshots, screencasts or a live demo?

  • Yes (attach)
  • No

https://jsfiddle.net/72dyhu6L/ <img width="741" alt="ζˆͺεœ– 2021-04-09 δΈ‹εˆ6 38 06" src="https://user-images.githubusercontent.com/27608365/114168501-e56e7c00-9962-11eb-9b0b-deaf86ba5e73.png">

Answers (1)

ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @YumiChen.

The issue with sorter direction incorrect with web component slot appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modifications overlap, creating an inconsistent state.

What to try:

  1. Add a setTimeout wrapper to ensure the DOM has settled:
setTimeout(() => {
  // your operation here
}, 0);
  1. Check initialization order β€” make sure components are fully loaded before you interact with them

  2. Use the editor's event system β€” listen to completion events:

editor.on('component:mount', (component) => {
  // safe to interact with component here
});

Recommended next steps:

  • Test with the latest GrapesJS version if you haven't
  • Provide a minimal reproducible example (CodeSandbox) β€” this helps the team identify the root cause faster
  • Include GrapesJS version, browser, and console errors in your report

Related Questions and Answers

Continue research with similar issue discussions.

Paid Plugins That Match This Issue

Curated by issue keywords and label relevance to help you ship faster.

View all plugins

Loading paid plugin recommendations...

Free option

Check the open-source GrapesJS plugins on GitHub or run a quick search in our free catalog.

Browse free plugins β†’
Premium option

Premium plugins ship with support, regular updates, and production-ready features β€” save days of integration work.

Browse premium plugins β†’

Related tutorials

In-depth guides on the same topic.

All tutorials β†’

Browse Plugin Categories

Jump directly to plugin category pages on the marketplace.