Style manager does not accurately reflect inherited color

Hi Barry, yeah currently this is the expected behavior (check also this discussion) but I hope one day to add proper support for inherited properties.

okay, thank you for letting me know

On Mon, Jul 18, 2022 at 9:29 AM Artur Arseniev @.***> wrote:

Hi Barry, yeah currently this is the expected behavior (check also this discussion https://github.com/artf/grapesjs/discussions/4245) but I hope one day to add proper support for inherited properties.

— Reply to this email directly, view it on GitHub https://github.com/artf/grapesjs/issues/4447#issuecomment-1187431826, or unsubscribe https://github.com/notifications/unsubscribe-auth/AARNBQYPWWWGE4ZNALD2EFDVUVL27ANCNFSM53O6VWTA . You are receiving this because you authored the thread.Message ID: @.***>

--

Barry Ross

Software Engineer

T:

M:

https://bit.ly/2PZOloH

https://www.eventfarm.com/safety?utm_source=email&utm_medium=signature&utm_campaign=clear https://www.eventfarm.com/safety?utm_source=email&utm_medium=signature&utm_campaign=clear

Thanks for reporting this, @barryross.

Great question about Style manager does not accurately reflect inherited color. The recommended approach with StyleManager is to use the event-driven API.

Start here:

1. Check the GrapesJS documentation for your specific module
2. Look for the on() event listener method
3. 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!