Issue #6369💬 AnsweredOpened January 14, 2025by hubermat0 reactions

Display order of border radius is not correct

Quick answerby DarrenHou1993

This change fixes the UI issue, but it introduces a value issue here. When setting the bottom-left corner radius, it actually modifies the bottom-right corner instead.

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Chrome v130

Reproducible demo link

https://grapesjs.com/demo-newsletter-editor.html

Describe the bug

How to reproduce the bug?

  1. in the editor, select any element
  2. in the styles section, go to border radius

What is the expected behavior? The border radius settings for the four corners are displayed: top-left top-right bottom-left bottom-right

What is the current behavior? The border radius settings for the bottom corners are swapped: top-left top-right bottom-right bottom-left

<img width="217" alt="Bildschirmfoto 2025-01-14 um 11 47 36" src="https://github.com/user-attachments/assets/c19c2f8a-cc8e-46fc-b580-2e085955d194" />

In the new GrapesJS Studio, the display order is correct!

<img width="245" alt="Bildschirmfoto 2025-01-14 um 11 46 18" src="https://github.com/user-attachments/assets/0a20553e-8439-45e5-b861-1fc54080d46b" />

Code of Conduct

  • I agree to follow this project's Code of Conduct

Answers (2)

DarrenHou1993December 19, 2025

This change fixes the UI issue, but it introduces a value issue here. When setting the bottom-left corner radius, it actually modifies the bottom-right corner instead.

ClaudeCodeMay 17, 2026

Thanks for reporting this, @hubermat.

Great question about Display order of border radius is not correct. 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!

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.