"Content tab" missing modified state indicator dot

Feature Requests / Improvements
1

Browser: Chrome 146.0.7680.178 (Official Build) (64-bit).
OS: Windows 11.
Bricks Builder: 2.3.1 / 2.3.2

Hi,

There is a visual inconsistency between the Content and Style tabs when default settings are modified (this applies to both Element ID and Global Classes).

  1. Style Tab: Whenever a property is changed, an indicator dot appears on the tab header. The HTML structure correctly reflects this by adding a <span class="indicator"> element.

    image
    image909Ă—1391 118 KB

  2. Content Tab: When modifying settings such as HTML Tag, Flex configurations (Direction, Align), Grid settings, or any other functional controls, the Content tab fails to show the indicator dot. The span.indicator element is completely missing from the DOM for this tab.

    image
    image1023Ă—1377 124 KB

  3. Context: I agree that purely content-based changes (such as typing text into a Heading element) may not require an indicator dot on the tab itself.

    However, the Content tab now includes numerous structural and visual settings such as: HTML Tag, Type, Style, Width, Height, Align, Color, Background, Spacing… (as shown in the attached screenshot). These are functional configurations, not just “content”.

    When these properties are modified, the Content tab does not display an indicator dot, and the span.indicator element is not generated in the DOM. This makes it difficult to track which elements have active customizations compared to the behavior of the Style tab.

    image
    image700Ă—1404 91.9 KB

This lack of visual feedback makes it difficult to identify which tabs contain active customizations without clicking through each one. The Content tab should trigger the modified state indicator just like the Style tab does when any of its controls are changed from their default values.

Thanks

:bear:

2

Hi Gau,
I moved your bug report to the improvements category, as it’s not a bug (it has been like this forever).

It might be technically inconsistent, but from a UI perspective, we’ve always preferred it that way, since there’s always a content-tab setting populated. So the indicator adds no value basically.

Let’s see if we get more feedback on this, since you’re the first user to bring it up, as far as I can see :v:

1 Like