GrapesJS Issues

Search parsed GitHub issues, see highlighted answers, and open the original discussion when needed.

212 issues found

#1084May 4, 2018by dsgh2 answers
0 reactions

[Bug] Bind handleAdd so that implementors can get a reference

I've marked as a bug just because I think this reflects a minor inconsistency; but it could also be understood as a feature request. The scenario is:I'm providing my own methods for uploadFile and handleAdd, which is something that's possible today.I can see that uploadFile has been bound to its parent object, allowin...

artf

Totally agree about the consistency 👍

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.

#1041April 13, 2018by tommedema3 answers
4 reactions

[Feature suggestion] optionally insert styles from StyleManager with !important

I'd like to suggest a feature that can be enabled through config: styleAsImportant: true (defaults to false, i.e. non-breaking). I thought this was already possible by configuring the cssComposer, though I've now learned that this is not the case (see below for an explanation). I am working with templates that sometim...

tommedema

added PR at #1056

artf

It might be a good idea, but what about improving those events (eg. pass model/pr to callbacks) to allow such customizations

artf

@tommedema Components and CssRules implement Styleable, therefore you would get it in all case. do you mean that we'd have to then write plugins to listen to those events and add additional styling to the component? Not additional, you ove...

#1039April 12, 2018by dsgh1 answer
0 reactions

[BUG] Missing support for empty-name traits

version: 0.14.8 I marked this as a bug, but it could be understood as a missing feature as well. Basically, grapesjs-blocks-bootstrap4 has some traits with an empty name, given that those traits set the (bootstrap) classes of the elements. The problem is that, as I understand it, grapesjs did not expect traits to have...

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.

#1029April 11, 2018by cmcintosh2 answers
0 reactions

Feature Request: Add Grippies for Resizing elements

Add Grippies and utilize jquery_ui or another similar mechanism for resizing elements.

artf

We have already a Resizer utility which fits perfectly our needs

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.

#1013April 7, 2018by tommedema3 answers
5 reactions

[Feature] Allow editing text nodes

Issue: text nodes that do not have a parent are not editable. Text nodes that have a parent but also have a sibling (e.g. a span), are also not editable. Support for raw text nodes is necessary. Example that doesn't work: Expected behavior is that the text node Try to edit me can be edited. Actual behavior is that it...

mipierce

tommedema

@artf <gjs-text-node> seems like a good solution!

artf

Aware and agree, the question is just How?. Text nodes don't have contentEditable property, so probably we need to try to wrap them all inside <span>s (only in its View) and see how all is handled

#1011April 6, 2018by pg16712 answers
0 reactions

[Question] Does grapejs provide variable selection in the UI

I have just come across grapejs and it looks amazing but I cannot find good information on how to manage variables. Is there are a way to give grapejs a list of allowed variables so the user can insert them easily through the UI when creating a template (editing text) or do they have to just type in the variable synta...

artf

There is no such a built-in feature but you can easily extend grapesjs for it. If you're looking for the usage of variables during the text editing this snippet might help you. You can also make use of Blocks to create draggable variables,...

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.

#1009April 5, 2018by krunal0393 answers
0 reactions

[Question] Richtext editor for trait

Is there way to have richtext box for trait. We want to user to insert rich text for trait and not sure how can we do it. We have below use case. There would be mutliple picture on page and once user mouse hover it will display some rich text and we want create component so admin can easily create page with above feat...

Piterden

But traits actually, are attributes of an element. For what purpose you need to use RTE there.

krunal039

We need user to add rich text with image and rich text is only visible when image mouse hover and user can drag and drop multiple image with rich text. On 6 April 2018 at 05:32, Denis Efremov <[email protected]> wrote: But traits ac...

Piterden

You don't need a RTE-trait. Why user can't use RTE in inline mode?

#1006April 4, 2018by parth-raj3 answers
1 reactions

Using grapejs in sas app.

WARNING READ and FOLLOW next 5 steps, then REMOVE them before posting the issueFollow CONTRIBUTING Guidelines https://github.com/artf/grapesjs/blob/master/CONTRIBUTING.mdUse the GitHub Issues EXCLUSIVELY for BUGS, FEATURE REQUESTS or QUESTIONS. Prefix the title of the issue with its context, eg. [Bug]: ....Do a quick...

KonradMil

https://opensource.org/licenses/BSD-3-Clause

parth-raj

Hi, i am using grapejs in sas app. Are there any restrictions regarding the usage of grapejs in sas app?

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.

#1005April 4, 2018by parth-raj1 answer
0 reactions

Using grapejs in sas app.

WARNING READ and FOLLOW next 5 steps, then REMOVE them before posting the issueFollow CONTRIBUTING Guidelines https://github.com/artf/grapesjs/blob/master/CONTRIBUTING.mdUse the GitHub Issues EXCLUSIVELY for BUGS, FEATURE REQUESTS or QUESTIONS. Prefix the title of the issue with its context, eg. [Bug]: ....Do a quick...

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.

#1004April 4, 2018by gabrigcl3 answers
0 reactions

[FEATURE REQUEST] Enhance "draggable" attribute of components in order to allow excluding certain components when wildcard "*" is set for draggable components

Hi. I wish to enhance "draggable" attribute of components in order to allow excluding certain components when wildcard "*" is set for draggable components. For example, according to my case: I need the "video" and "image" component to be draggable on every component, except the "mycustomcomponent". My suggestion is to...

artf

You mean something like draggable: "*:not(your-component)"?

gabrigcl

Yes, I liked your thinking!

artf

Inside draggable and droppable properties you can pass any CSS-like query string so it's already possible