Version:0.16.30 Are you able to reproduce the bug from the demo? [1 ] Yes What is the expected behavior?* SelectorManager.getState() is supposed to return a string according to https://grapesjs.com/docs/api/selector_manager.html#getstate Describe the bug detailed What is the current behavior? SelectorManager.getState(...
congweibai
Could you have a look at https://github.com/artf/grapesjs/pull/3182 is this fix this issue? Thanks
GJSBlock
Thanks for reporting this, @congweibai. The issue with SelectorManager not return a String but an Object appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modi...
Is there a way through the api to change the selected component tooltip or is that something that can only be done by editing the source? If so with the api please exlain as I am not bright enough to be able to effectively change the source and every time i try to make other changes I end up with errors when using the...
artf
Hi, when you define a new component, you can customize its toolbar You can also update the toolbar at runtime in this way: but won't be stored (eg. on a refresh of the page), so I always suggest to think more in a component-oriented way.
anatoli-dp
Thanks, that is a big help to some of the things i want to add for my own use. On Tue, Dec 29, 2020 at 1:01 PM Artur Arseniev <[email protected]> wrote: Closed #3177 <https://github.com/artf/grapesjs/issues/3177>. β You are receivin...
GJSBlock
Thanks for reporting this, @anatoli-dp. The issue with QUESTION/FEATURE REQUEST: Changing Selected Component Tooltip appears to be a race condition or state management timing problem. This typically happens when component lifecycle events...
Version: 0.16.30 Are you able to reproduce the bug from the demo? [x] Yes [ ] No Steps to reproduce:Open the consoleExecute editor.setComponents('', {avoidStore: true});Execute editor.setStyle('', {avoidStore: true});The "Stored ..." log still appears (see attached screenshot) What is the expected behavior? The option...
artf
Thanks @mcottret the fix is ready for the next release
artf
Unfortunately, due to the bad initial naming, avoidStore is intended to skip the UndoManager and not the Storage π The good news, I had to introduce the new noCount option, in order to fix #3189, this will skip triggering the editor chang...
mcottret
Hello @artf ! I'm sorry to reopen this issue but the setStyle issue still seems to be present. Redoing the steps above, the "Stored ..." log still appears while calling setStyle with the noCount option. I'm seeing the fixed handleChanges h...
Version: 0.16.30 Are you able to reproduce the bug from the demo? [x] Yes [ ] No Steps to reproduce:Select a text component in the demo's canvasThe selection box & RTE appearOpen the consoleExecute editor.setComponents('');The component is removed, but the selection box & RTE are still present (see attached screenshot...
artf
Thanks @mcottret for the report. I've handled this on my side, so it should be fixed in the next release, but as always, thanks for your willingness to help :)
GJSBlock
Thanks for reporting this, @mcottret. The issue with Selection & active RTE not cleared when component is removed programatically appears to be a race condition or state management timing problem. This typically happens when component life...
*Version:0.16.27 Are you able to reproduce the bug from the demo? [ ] Yes [ ] No What is the expected behavior? In the right panel and canvas, the pasted node should be after the copied node. What is the current behavior? I copy a node. In the views-container(right panel), the pasted node is after the copied node. But...
artf
I've tried locally but the node is placed correctly. Are you able to create a live demo, please?
nanaya1
Sorry, I did not elaborate on the scenario where this error occurred. The components that come with grapesjs do not produce this error, because they donβt have spacesοΌcarriage returns or tabs. I found this problem while customizing compone...
The collection of the selected component before Undo The collection of the selected component after Undo Code to replace the component with new component Uncaught TypeError: n.getEl is not a function and Uncaught TypeError: t.getSelectors is not function are the errors reported on save. Iβm unable to replace the selec...
artf
Sorry, but without a reproducible demo, this issue doesn't make sense to me
ssmanoj-grapes
Hi artf, Please find the demo video of the issue grapejs-issue.zip.
artf
Ok, as you're not able to create a reproducible demo, I have to close this...
I am using the latest GrapesJS (v0.16.27). As per the fix for the issue, (#2029) the exception has been caught and logged into the console. Is there any way where we can get to know about the errors other than from console log? Something similar to asset:upload:error, if we have parse:error, it would be helpful to han...
artf
Usually, the error doesn't come from the parser but from the creation of the DOM (eg. the editor creates the element by using setAttribute). You can catch the editor's errors by listening to the log event Here, for example, you can put you...
GJSBlock
Thanks for reporting this, @sathyanarayananaCES. The issue with [Question] Is there any way to get the parser errors other than from console log appears to be a race condition or state management timing problem. This typically happens when...
Version: 16.27 Are you able to reproduce the bug from the demo? [x ] Yes [ ] No Describe the bug: I discovered an issue with gjs-hovered, the class that handles the mouse-hover outline for elements. Sometimes the blue outline will move relative to its parent during scrolling . Check out this JsFiddle (and scroll with...
lofcz
Would be nice to have this fixed, not the end of the world, but mildly annoying.
matteocollina
any news?
artf
I'm closing this one as it was actually already fixed, indeed the old demo is working now properly. You might still face the issue if your editor is placed in a scrollable container, in that case, use this option please: https://github.com...
Version: Last In the demo the bug does not appear, I believe that for using localstorage for storage. Grapesjs works normally, with background, but when I insert the background layers, except, everything is displayed correctly. The problem is that when I reload the editor, it does not show the layers that were created...
artf
In the demo the bug does not appear, I believe that for using localstorage for storage. No, using local storage or remote one has no difference as the JSON structure to use is the same. Indeed, I guess you're loading back the HTML instead...
GJSBlock
Thanks for reporting this, @MarksEliel. The issue with Background layers empty in reload editor appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modifications...
Not getting styles of the selected element Here is my code, const model = editor.StyleManager.getModelToStyle(component); let styleObject = model.getStyle(); console.log("styles", styleObject) Version: 0.14.49 Are you able to reproduce the bug from the demo? [X] Yes [ ] No What is the expected behavior? When an elemen...
artf
First of all, you need to upgrade your grapesjs version (you're using a 2 years old one), then you have to provide a live demo of the issue.
no-response[bot]
This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take ac...
GJSBlock
Thanks for reporting this, @Asha1597. The issue with When I select an particular element I'm not getting its styles. This issue happens only with some elements. appears to be a race condition or state management timing problem. This typica...