If devices in DeviceManager all have a width specificed an editor breaking error occurs
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.
Read full answer below βQuestion
If all devices specified for the DeviceManager have a width set, an editor breaking error occurs: "TypeError: contRules is null". I'm seeing this in my local project with v0.14.52.
jsfiddle: https://jsfiddle.net/5ycmoftj/1/
I think what is happening is that CssRulesView.js render() is creating div fragments as containers for different media targets, based on the widths of the devices in the device manager. If you don't have a device set up with a undefined width, there is no place for css rules that don't specify a media width to go. It doesn't create a container for them.
Answers (1)
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.
Related Questions and Answers
Continue research with similar issue discussions.
Issue #1830
[Bug]: StyleManager properties without "property" defined cause an error on component selection
When using a StyleManager property where "property" is not defined, and defaults to '', I'm seeing an error on component selection: "TypeEr...
Issue #2044
Npm start to develop on local server didn't work
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...
Issue #727
Two devices with same width
Hi all, We have an scenario where we need to have two devices with same width. Almost everything works fine, but when we try to change betw...
Issue #1104
[Bug] Color trait can't setup property after 0.14.9
After v0.14.9 color trait can't setup component property when user press "OK" on colorpicker form. Live:v0.14.9 https://jsfiddle.net/Lqm7ou...
Paid Plugins That Match This Issue
Curated by issue keywords and label relevance to help you ship faster.
Loading paid plugin recommendations...
Check the open-source GrapesJS plugins on GitHub or run a quick search in our free catalog.
Browse free plugins βPremium plugins ship with support, regular updates, and production-ready features β save days of integration work.
Browse premium plugins βRelated tutorials
In-depth guides on the same topic.
Tutorial
How to Build a Production GrapesJS Editor: The Complete Walkthrough of Brief, Preset, Plugins, and Services
A complete walkthrough of building a production GrapesJS editor: how to choose a preset, pick plugins, and scope setup services without burning a sprint.
Tutorial
GrapesJS Inline RTE Plugins Update: CKEditor 5 v0.1.4 and Froala Inline Text Editor
CKEditor 5 Inline for GrapesJS v0.1.4 fixes Studio SDK toolbar clipping, iframe injection and link balloon bugs. Compare with Froala Inline β both $69.
Tutorial
Embed GrapesJS in Your SaaS: A Weekend Guide
Embed GrapesJS in your SaaS and ship a white-label page builder over a weekend. Honest tradeoffs, real code, and the plugins that close the UX gap.
Browse Plugin Categories
Jump directly to plugin category pages on the marketplace.