Issue #4529Opened August 24, 2022by FaisalShaikhHA6 reactions

BUG: When we resize an image with a class 'xyz', all the elements on the page with same class also gets resized because editor adds css to those classes.

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Version 104.0.5112.101 (Official Build) (arm64)

Video demo link

https://d.pr/i/27EgH2

Describe the bug

  • When we resize an image with a class 'xyz', all the elements on the page with the same class also get resized because the editor adds height width CSS to those classes.
  • But when I remove all the classes from the image, the editor uses the id to set height width CSS.
  • I am loading a bootstrap template in the editor. Recording link: https://d.pr/i/27EgH2

Steps to reproduce:

  • Load bootstrap template for editing.
  • Add multiple divs with shadow class ex.(<div class='shadow'></div>)
  • Place an image in one of the div which has shadow class and then try to resize the image.
  • Notice all the divs moving/resized along with the image.
  • Expected behavior only image should be resized.
  • Using grapesjs-parser-postcss as well and added it in initialization code.
  • Passing the CSS & javascript URLs using canvas option.

init method:

grapesjs.init({
            container: "#gjs",
             .....,
            canvas: {
                scripts: scriptUrls,
                styles: styleUrls,
            },
            parser: {
                parserPostCSS,
            },
        });

Code of Conduct

  • I agree to follow this project's Code of Conduct

Answers (3)

DevMetwalyAugust 25, 20224 reactions

https://grapesjs.com/docs/modules/Components.html#components-css

Component-first styling By default, when you select a component in the canvas and apply styles on it, changes will be applied on its existent classes. This will result on changing of all the components with those applied classes. If you need the style to be applied only on the specific selected component you have to select componentFirst strategy in this way.

grapesjs.init({
 ...
 selectorManager: {
   componentFirst: true,
 },
})
FaisalShaikhHAAugust 25, 20222 reactions

Thanks, @DevMetwaly it worked, my bad I missed this.

FaisalShaikhHAAugust 24, 20220 reactions

Hi @artf, first of all, amazing framework, and thanks for making it open source. As described in the above comment I am facing this weird issue, please let me know if I am doing something wrong or a way to fix this thanks.

Related Questions and Answers

Continue research with similar issue discussions.

Paid Plugins That Match This Issue

Curated by issue keywords and label relevance to help you ship faster.

View all plugins

Loading paid plugin recommendations...

Browse Plugin Categories

Jump directly to plugin category pages on the marketplace.