CanvasView.getPosition returns strange values in designer mode with a narrow device

Yeah I'd say it's definitely confusing (width and height refer to the canvas, top and left to the frame) but any direct change to those functions breaks some functionality in other points as those were built around this confusing logic 😞 (eg. the sorter of blocks in the standard mode). So I guess before doing any kind of change here we should probably refactor the logic in other points. I'll probably close this issue as the method itself is not really public/documented.

Thanks for reporting this, @contentfree.

The issue with CanvasView.getPosition returns strange values in designer mode with a narrow device 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);

2. Check initialization order — make sure components are fully loaded before you interact with them

3. 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