Search parsed GitHub issues, see highlighted answers, and open the original discussion when needed.
1180 issues found
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...
The color picker in grapesjs does not work the same between Chrome and Firefox. When you open the picker on a selected component that has never had it's background color set before (for instance...) the color picker opens with opacity set to 100% in Chrome and 0% in Firefox. The issue is that the user may hot even loo...
mhowey
@artf Another difference to note between Firefox and Chrome is what is displayed in the palette. Firefox shows a transparent box while Chrome shows a gray one.
artf
Seems to be solved on the latest Firefox version
Version: 0.16.27 Are you able to reproduce the bug from the demo? [ ] Yes [ ] No [X] Video but no demo What is the expected behavior? Add as many nested span elements as necessary and preserve their style/ID. What is the current behavior? From two nested span elements, style/ID of parent span elements disappear. Are y...
artf
Hi Benjamin, the bug was already fixed (when you report a bug, ensure to have the latest version)
Hello, I've hit weird bug when I tried to get block category. block.get('category') returns object in Chrome, but in Firefox the same code returns string: Left - Chrome, rIght - Firefox Also with enabled adblock or selenium extensions this code also returns string. Some other extensions might cause this problem too, s...
xinnai
@kuhelbeher I got same issue, did you resolve your problem?
artf
This seems to be solved with the latest version of GrapesJS
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...
kumarabhishek008
Issue has been resolved
Hi, We are encountering an issue - color of property name such as "Width" is blue when dragging a new component to canvas, but we don't modify its value. Grapesjs is powerful, and very helpful to us. However, we are new to grapesjs, and have spent much time on this issue with no progress. Would you please tell us the...
artf
Hi @luziye9 for sure you're using a block/component with a custom style property on it... Anyway, if you're opening a BUG issue, you have to follow the template (grapesjs version, reproducible demo, etc.). So, for now, I'm closing this as...
Hi @artf - what you've built is magnificent. It's been a gentle struggle as I'm far from being a JS wizard. However, I've got just about everything fully configured - except for this! I want to set traits that display when an image is selected (alt, src, id). I am sure it can be done once at initialisation, but I'm bu...
artf
Hi Freddy, you can simply extend the image component in this case
Version: 0.16.27 to latest Are you able to reproduce the bug from the demo? Yes [ X] Yes [ ] No What is the expected behavior? insert text block inside another text block Describe the bug detailed when adding new block, or even when creating a new custom type, the "textable attribute is not working as expected and as...
artf
Duplicate of #2771
Version: 0.16.34 What is the expected behavior? When the editor is initialized, no element is selected, so the style manager should say "Select an element before using Style Manager" like it does when not using "appendTo" in the editor configuration. What is the current behavior? When using "appendTo" in the editor co...
mosh-tudor
I used this code to solve it:
Nielsticot
This is not what I want, my issue is before any element is selected so before the event "component:selected" is trigerred. I temporarily fixed it by selecting an element on editor load but it is not what I really want
artf
If you're using the StyleManager in a custom element you have to handle that state on your own.
Way to Importing Html and CSS from demo to upgrade version, one shot import ?