CSS properties default values
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 π₯²
Read full answer below βQuestion
GrapesJS version
- I confirm to use the latest version of GrapesJS
What browser are you using?
N/A
Reproducible demo link
https://grapesjs.com/demo.html
Describe the bug
Hi everyone !!! <3
How to reproduce the bug?
- open grapesjs official webpage demo
- click on a container, e.g. the hero section container
- apply a
font-weight: bold;style to the container => all the texts inside become bold - select one of the texts inside, check the property
font-weight, it is set tonormal
What is the expected behavior?
font-weight should be on '' empty string or unset so that i can select normal to un-apply the font-weight: bold;
What is the current behavior?
the property font-weight is set to normal already, making it impossible for me to really apply "normal" (i need to select something else then normal again)
I work on this issue in silex (for other css properties defined in silex) with @oliviermgx, maybe we can make a PR if everyone agrees that this is a bug and the default value should be an empty string?
Code of Conduct
- I agree to follow this project's Code of Conduct
Answers (3)
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
editor.StyleManager.getProperty('typography', 'font-weight').set({ default: ' ' });
So I guess this is not a core bug but an "unexpectedly expected" behavior π₯²
Oh ok, I thought you would want the default default value to be the expected expected behaviour π
Thank you for the answer
Thanks for reporting this, @lexoyo.
Great question about CSS properties default values. The recommended approach with StyleManager is to use the event-driven API.
Start here:
- Check the GrapesJS documentation for your specific module
- Look for the
on()event listener method - Most operations can be achieved by listening to editor and component events
Common patterns:
// Listen for changes
editor.on('change', () => console.log('something changed'));
// Component lifecycle
editor.on('component:mount', (c) => console.log('component ready', c));
editor.on('component:update', (c) => console.log('component updated', c));
If you're still stuck:
- Share a minimal CodeSandbox reproduction
- Include what you've already tried
- Mention your GrapesJS version
- The community is here to help!
Related Questions and Answers
Continue research with similar issue discussions.
Issue #6152
CSS added via custom code persists after custom code component is removed
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? any Reproducible demo link https://grapesj...
Issue #5583
Can't set background:none in mobile version using styles panel
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Edge last version Reproducible demo link h...
Issue #4859
Editing CSS property sets a style to a common class instead of element
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome v108Reproducible demo link https://gr...
Issue #4448
Error on resize image.
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Brave Browser Last version Reproducible de...
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
Find the Right GrapesJS Plugin in Seconds: Smarter Discovery Is Live
We're shipping a set of discovery upgrades. New label filters, a proper compatibility switch for GrapesJS vs Studio, one-click and a smarter sort bar.
Tutorial
GrapesJS vs Webflow vs Tilda: What to Choose for Your Business in 2026
Choosing the right website platform in 2026 is no longer just about building a site
Tutorial
GJS Market 2.0 - Donations, Tracking, Labels and Better Product Discovery
Weβve rolled out a new set of GrapesJS marketplace updates across GJS Market, focused on improving how creators distribute products
Browse Plugin Categories
Jump directly to plugin category pages on the marketplace.