BUG: Propagating component defaults can break layers when child comments are introduced

[bernesto]

GrapesJS version

• I confirm to use the latest version of GrapesJS

What browser are you using?

Chrome v122

Reproducible demo link

https://jsfiddle.net/n38vbktg/

Describe the bug

How to reproduce the bug?

1. Create a component that propagates defaults that include layerable = true.
2. Introduce a comment under the competent.

What is the expected behavior?
The comment either remains hidden, or does not cause an error.

What is the current behavior?
The editor treats the comment as an HTMLElement. This triggers several errors when the editor tries to read non-existent properties from the node, such as getComputedStyle or getClientRects. Both methods should perform a check first. Or - a new type should be introduced for comments that overrides the defaults propagated from the parent.

Errors occur here:

grapesjs/src/commands/view/ShowOffset.ts

Line 39 in ac554a3

var style = window.getComputedStyle(el);

and here:

grapesjs/src/utils/dom.ts

Line 40 in ac554a3

return el && !!(el.offsetWidth || el.offsetHeight || el.getClientRects().length);

Code of Conduct

• I agree to follow this project's Code of Conduct

[artf]

Good catch @bernesto