@keyframes not adding even after i pass the the keyframes object
Question
Hi @artf,
I have added the
`let cc = editor.CssComposer;
cc.setRule('.fadetop-animate',
{ opacity: 0, 'animation-name': 'fadeTop' },
{
atRuleType: 'keyframes',
atRuleParams: 'fadeTop',
selector: 'to',
style:{
opacity: 1
}
});`
as per the Document [](https://grapesjs.com/docs/api/css_composer.html#setrule)
however rule for keyframes is not getting added to the component.
how to add keyframes to the component style?Answers (2)
Use this one
editor. CssComposer.getAll().add(`@keyframes fadeTop { ... }`) // Your CSS string
Thanks for reporting this, @niranjank151.
Great question about @keyframes not adding even after i pass the the keyframes object. 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 #3222
How to refresh/re-render after new node added?
I manually add a new node into a rendered component. The visual result is OK, but impossible to save, because my style isn't with the auto-...
Issue #5316
Editor not subscribing to selector:remove
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome v115.0.5790.170 Reproducible demo lin...
Issue #4765
The documented way to parse @keyframes does not work
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome v107Describe the bug How to reproduce...
Issue #3703
custom ids have a \3 injected into the css and a space after the following letter after the \3 when added to the canvas
WARNING READ and FOLLOW next 3 steps, then REMOVE them before posting the issueFollow CONTRIBUTING Guidelines https://github.com/artf/grape...
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 →Browse Plugin Categories
Jump directly to plugin category pages on the marketplace.