Search parsed GitHub issues, see highlighted answers, and open the original discussion when needed.
3464 issues found
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Firefox Reproducible demo link dist/index.d.ts Describe the bug Typping error ?proeperty instead of property don't know if it's serious lines 8053/8054 : addBuiltIn(prop: string, definition: Omit<PropertyProps, "property">...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? chrome v9 Reproducible demo link Describe the bug How to reproduce the bug?...... What is the expected behavior? ... What is the current behavior? ... If is necessary to execute some code in order to reproduce the bug, pas...
artf
@gitpugal please use the Discussions if you have any questions
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? N/AReproducible demo link https://grapesjs.com/demo.htmlDescribe the bug Hi everyone !!! <3 How to reproduce the bug?open grapesjs official webpage democlick on a container, e.g. the hero section containerapply a font-weight...
artf
i need to select something else then normal again Yeah in case there are no values, the default UI preselects the default value, but that can be easily updated So I guess this is not a core bug but an "unexpectedly expected" behavior 🥲
lexoyo
Oh ok, I thought you would want the default default value to be the expected expected behaviour 😃 Thank you for the answer
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome v122 Reproducible demo link https://grapesjs.com/demo.html Describe the bug This may be by design, but it seems odd given the intent. How to reproduce the bug?Click preview (eye) What is the expected behavior? The p...
bernesto
Awesome @artf you are a rockstar!
artf
Thanks @bernesto there is actually an update to do on the demo side. I prepared the change and will fix it on the next release.
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Arc Version 1.35.0 / Chromium Engine 123.0 Reproducible demo link https://grapesjs.com/demo.html Describe the bug How to reproduce the bug?Open dev toolsSelect a componentRun in console: What is the expected behavior? Shou...
artf
If you need to make a copy of traits I'd suggest simply doing this JSON.parse(JSON.stringify(editor.getSelected().getTraits())). I don't remember ever mentioning cloning traits in docs, so I'd avoid using non-public APIs.
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome v122 Reproducible demo link not applicable Describe the bug The GrapeJs Docs indicate that it is possible to add mixed content to the "content" property of a block (see https://grapesjs.com/docs/modules/Blocks.html#...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome v122, Safari 17 Reproducible demo link https://grapesjs.com/demo.html Describe the bug How to reproduce the bug?Add link component, try editing the link text What is the expected behavior? The link text should be ed...
artf
Thanks for the report, will be fixed in the next release.
Mauzer93
I have the same issue recently.
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome v122 Reproducible demo link https://grapesjs.com/docs/getting-started.html#style-manager Describe the bug How to reproduce the bug?Go to the "StyleManager" section of the "Getting Started" doc from GrapeJSTry to use...
bernesto
Hi @artf, The root issue is that we are trying to place a popover palette absolutely positioned over another element at an arbitrary location on the page. And we need to do this even when the origin element is outside of the editor contain...
artf
@bernesto can you check this one as it seems to be related to your changes
bernesto
Yes, I see the issue. The logic needs to account for when the parent is outside of the container. Let me see what I can do there.
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Edge v122 Reproducible demo link https://jsfiddle.net/bwreyq29/1/ Describe the bug How to reproduce the bug? open this link https://jsfiddle.net/bwreyq29/1/ and javascript code attached to src attribute will be executed au...
bernesto
I think the pre-parser option is a really good idea. It sticks to the 'plug-in' per feature concept. How about updating fromElement to accept a string element ID or boolean. If bool == true, works as it does now, parsing the container HTML...
artf
Totally agree with @bernesto indeed no matter how hard we try to make it safe, it will never be enough and I don't want to give the impression that the library is "so safe" to justify a missing server-side validation. The current options (...
bernesto
This is unavoidable when using fromElement to load from an active DOM element. The element of the page loads and executes synchronously. GrapesJS would never have a chance to process and disarm the XSS html. This would need to be addressed...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome v122 Reproducible demo link N/A Describe the bug How to reproduce the bug?Checkout git onto a Windows 10+ machineBuild using provided procedure. What is the expected behavior? It should build the same as in a *inx s...
bernesto
Yeah, I did all the usual stuff. Lock files, updates, various ways of imports ({}, require, *, full path, etc.) Not sure why, but when I break stuff, I break it good. Always tier 2 or 3 support LMAO. I do believe the issue resides in CLI,...
bernesto
Good points. I have not tried the other versions of Node. I will give that a shot.
artf
Yeah build/serve are managed by the CLI (let's move the issue there) but I'm not sure what might be the problem (no Windows to test 🥲)