Go to https://grapesjs.com/demo.htmlClear canvasClick on body, add class, apply background colorBackground color now appearsClick Export -> Export to ZipOpen the Zip file and look at the index.html file. While the class was created in style.css, the class name was never applied to <body></body> in the html.
florinr1
I'm experiencing the same problem. The wrapper class attribute is set but the editor.getHtml() returns "<body></body>". I'm initalizing GrapesJS using: { fromElement: true, autorender: 0, // Size of the editor height: '100%', width: '100%'...
Hello GrapesJs team After updating the grapesjs version form 14.0.59 i noticed the gradient plugin stopped to work, i also checked the gradient demo page and i noticed the same behavior here https://codepen.io/artf/pen/bYwdQG Thanks in advance
ssabrewolf
hi @artf i noticed you added the help wanted tag, i could try but could you give some tips or hypothesis about what could be the reason to not start from zero wondering in the dark, of course im asking because you seem to be the author of...
artf
@ssabrewolf yeah I'm the author of the gradient plugin but to be honest I've no idea what is happened, definitely a regression after some update in the Style Manager module. What I can say, is working fine with the v0.14.50
alikabeer32
It's absurd but I find that if you type 'decoration' instead of Decoration, the plugin works! In the demo and in my code as well.
For some predefined commands, has a new name and old name. It tells the user to use the new one as preferred. If choosing the new command name to extend, will not works, that because of old names in the internal. The reason is: In commands/index.js, the added or extended commands are the newly created views (extends f...
Did the procedure to start the local server using dev branch as described on README, it worked on the console, but fails on chrome and the grapesjs don't load due to the following error
artf
I made a quick check and the reason seems to be the latest [email protected] I don't have time to investigate so I'll just freeze the currently used version
artf
Weird, never seen that before. It might be some dev dependency change in some minor release. Try to reinstall node_modules with exact dependency versions
verdverm
I'm having issues following the dev setup: Maybe a bundler issue? I am able to drop the min from grapes.min.js in the index.html file and it works. However, if I build the grapes.js output, then this error returns.
Hello, I am running into an issue when selecting or unselecting a class on an element in the StyleManager through the UI. This happens on both my own project and the newletter demo from the GrapesJS page. It happens on version 0.14.61 which should be the current version. Reproduction:Open the newletter demo from the G...
Hi, I have an error on your demo :( 1- In the style, on the "Build your templates without coding" text, set TOP to 5px 2- In the same element, set Dimension > Margin > Top to 10px 3- In the "Hover me" button, set TOP to 1% and Margin > Top to 2% 4- Select "Build your templates ..." The TOP value change top 5px -> OK T...
WebEtSolutions
For fix this issue, you must change PropertyView.targetUpdated() and change this line let targetValue = this.getTargetValue({ ignoreDefault: 1 }); by this one let targetValue = this.getTargetValue({ ignoreDefault: 1, ignoreCustomValue: 1 }...
artf
Thanks @WebEtSolutions I'm not totally sure about the solution but the bug is confirmed
Hi, since the latest version, I noticed that when I use the droppable query selector using [data-gjs-type="my-component-type"] no longer seems to work. I have added two codesandbox demos to show you the issue. I am not able to figure out what changed. Hope it helps, thanks!You're submitting a BUGAre you using the late...
artf
Ok seems like the regression was introduced by this change: https://github.com/artf/grapesjs/commit/702ba828b13bae4b64bfd7bc79f23d8909d757f4#diff-6aa74cf54855daa6ca63a5d1e8b77c44R358 I'll fix it in the next release. Thanks for the report
OS: Windows 10 Browser: Chrome 73 GrapesJS version: 0.14.57 I have remote storage configured using this call to grapesjs.init(): While I see the request to /load fire in the Network tab of Chrome's dev tools, I don't see any requests to /store, no matter how many changes I make in the editor. Is there a configuration...
DylanSp
Updating to the next release fixed this, I now see requests to to the /store endpoint. Thanks for the prompt fix!
DylanSp
I should also note that manually saving with editor.store() does send a request that I can see in the Network tab.
artf
Thanks for the report @DylanSp actually there is an issue with the listener. If the first load call fails (and I guess your /load endpoint is fake just like mine) it never starts tracking the editor changes so autosave doesn't work. It wil...
The Toolbar of the RTE Editor is not visible vor Text field higher than the Browserwindow. While scrolling to the middle the RTE Toolbar is not visible. The Toolbar is on top or on the bottom. It should be sticking somewhere it keeps visible. Perhaps it is better to stick it to the top / top frame border. This is also...
artf
Yeah, we should replicate the behavior of the component toolbar
lock[bot]
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
If the default device is smaller than fullscreen, it will still load as fullscreen. Once you change devices the sizes will then be recognized. https://jsfiddle.net/benvmatheson/7b4gq1kx/1/
benvmatheson
Looks like a workaround is setting the device manually, instead of assuming the first selection will be chosen. editor.setDevice('Device 1')