Issue #3425πŸ’¬ AnsweredOpened April 30, 2021by anlumo1 reactions

StaticRules for CssComposer Non-Functional

Quick answerby artf❀ 1

Thanks @anlumo you're right, that was an old option, I'll remove it. For the purpose of static CSS rules, we have these options

Read full answer below ↓

Question

The sample config file for the CssComposer references a staticRules property. This property name is not used anywhere else in the source code (verified using GitHub search) and also doesn't do anything. Version: 0.17.3 Are you able to reproduce the bug from the demo?[ ] Yes[X] No (not really applicable) What is the expected behavior? Add the css rules to the document. What is the current behavior? Nothing happens. Are you able to attach screenshots, screencasts or a live demo?[ ] Yes (attach)[X] No

Answers (2)

artfβ€’ May 6, 2021

Thanks @anlumo you're right, that was an old option, I'll remove it. For the purpose of static CSS rules, we have these options

GJSBlockβ€’ May 17, 2026

Thanks for reporting this, @anlumo. The issue with staticRules for CssComposer Non-Functional appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modifications overlap, creating an inconsistent state. What to try: Add a s...

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...

Free option

Check the open-source GrapesJS plugins on GitHub or run a quick search in our free catalog.

Browse free plugins β†’
Premium option

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.

All tutorials β†’

Browse Plugin Categories

Jump directly to plugin category pages on the marketplace.