WARNING READ and FOLLOW next 3 steps, then REMOVE them before posting the issueFollow CONTRIBUTING Guidelines https://github.com/artf/grapesjs/blob/master/CONTRIBUTING.mdDo a quick SEARCH first, to see if someone else didn't open the same issueAll relative statements/questions have to be filled/answered, otherwise, th...
anatoli-dp
please note this issue is bad . . . now that i see it i feel stupid . . . ids cant start with a number and i didnt take that into account when making this
GJSBlock
Thanks for reporting this, @anatoli-dp. The issue with custom ids have a \3 injected into the css and a space after the following letter after the \3 when added to the canvas appears to be a race condition or state management timing proble...
WARNING READ and FOLLOW next 3 steps, then REMOVE them before posting the issueFollow CONTRIBUTING Guidelines https://github.com/artf/grapesjs/blob/master/CONTRIBUTING.mdDo a quick SEARCH first, to see if someone else didn't open the same issueAll relative statements/questions have to be filled/answered, otherwise, th...
artf
The string here is supposed to be a query string so it tries to query a wrapper tag, which obviously doesn't exist. The editor attaches data-gjs-type attribute to all components in the frame, so the query you can use is draggable: '[data-g...
anatoli-dp
ah that makes a lot more sense now . . . thanks, that solved the issue
GJSBlock
Thanks for reporting this, @anatoli-dp. The issue with setting draggable: 'wrapper' does not drop in wrapper appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM...
Hi! I'm using grapesJs for e-mail editing in a project in my company, with Newsletter plugin. Everithing works very well, except for this bug i can't solve: Sometimes, when I drag blocks inside the canvas, the cell hover gets scrambled. The biggest problem is that this behavior is completely random, it can happen or n...
artf
Are you using the latest version?
diegoSenra
Using minified 0.10.7
artf
Sorry mate, it's a 4-year-old release, can't help you here. Did you try to update?
Version: You can get the version by typing grapesjs.version into the console 0.17.22 Are you able to reproduce the bug from the demo?[x] Yes[ ] No What is the expected behavior? Should be able to see the web component in similar fashion as it is outside the grapesJS container Describe the bug detailed Grapesjs not abl...
artf
This issue is due to how AdoptStylesheet works and it's similar to this one from lit-element. Basically, you can't share the same CSSStyleSheet across multiple documents, so you have to recreate it manually, here below is a code for custom...
vasicvuk
Is there any solution for using lit-element components 3.X with grapesJS?
GJSBlock
Thanks for reporting this, @GaikwadShubham. The issue with AdoptStylesheet not supported in grapesJS appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modifica...
Version: 0.17.22 Are you able to reproduce the bug from the demo?[ ] Yes[X] No I can't reproduce it in a demo however you can see it for yourself if log into Documint using the following credentials:Email: [email protected]: demo then make a change to the template and try using ctrl+z What is the expected behavior? S...
Joshmamroud
You were right, it wasn't React or GrapesJS. Event propagation was being stopped by the rc-drawer component I was using. @artf thanks for your help, this has been an issue from day one.
artf
Hey @Joshmamroud we have this code that propagates keydown keyup keypress events to the parent document, this allows keymaps to work, ensure to not contain any code/component which prevents the propagation of those events.
Joshmamroud
Hey @artf, I believe it may be blocked by React. Any suggestions on how to re-bind these event listeners? Not even sure if that is the right solution or path.
Version: 0.17.22 Are you able to reproduce the bug from the demo?[X] Yes[ ] No What is the expected behavior? Should be able to drop a textable element into a custom component that extends the text component What is the current behavior? Can't drop a textable component into a custom component that extends a text compo...
artf
Hey @Joshmamroud there is actually a general issue about textable components here #2771
Joshmamroud
Thanks, @artf. I think my problem here is more so the custom component that extends the Text component. Textable works as expected with the original Text component but when I try to create my own, custom text component that's where I run i...
artf
From your demo, I don't see issues with the extended text component, but only those related to textable
Thanks for #3673 I have a new bug feedback. Version:. 0.17.22 Are you able to reproduce the bug from the demo?[ ] Yes[ ] No What is the expected behavior? I want the default to be the width of the mobile device, so I configured min-width priority, but only the mobile width is displayed by default on the select box, an...
artf
Yeah, you're right, actually, there is no option to select the default device... For now, as a workaround, do it manually after init: And as you're using the mobile-first approach, you would need to fix your Desktop device: In the next rel...
GJSBlock
Thanks for reporting this, @imouou. The issue with Device width is invalid by default appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modifications overlap,...
Version: 0.17.23 Are you able to reproduce the bug from the demo?[x] Yes[ ] No Its possible for the badge to obscure the content of the element if the element is placed at the top of the canvas. What is the expected behavior? If there is room, the label should be placed below the element. Are you able to attach screen...
GJSBlock
Thanks for reporting this, @rywilson28. The issue with Badges can obscure elements content even when there is room below the element appears to be a race condition or state management timing problem. This typically happens when component l...
Version: 0.17.19 What is the current behavior? That the added webcomponent is visible: When adding web components inside grapesjs container, the component is empty/blank, if the component has elements in the shadow DOM. (If not using shadow dom to create components there is no issue.) It is visible in layer manager, b...
artf
Posted a workaround here https://github.com/artf/grapesjs/issues/3693
artf
Hey @sriya-srinivasan can you create a reproducible demo, please?
WARNING READ and FOLLOW next 3 steps, then REMOVE them before posting the issueFollow CONTRIBUTING Guidelines https://github.com/artf/grapesjs/blob/master/CONTRIBUTING.mdDo a quick SEARCH first, to see if someone else didn't open the same issueAll relative statements/questions have to be filled/answered, otherwise, th...
artf
Use component first styling
GJSBlock
Thanks for reporting this, @imouou. The issue with option resizable:true will change all the same components in canvas. appears to be a race condition or state management timing problem. This typically happens when component lifecycle even...