NO BUG: Pinned CSS control group shows empty field despite bi-directional CSS Sync being active

Bugs
1

Browser: Aside 1.0.922.1
OS: macOS 27
Video: Zight Recording 2026-09-23 ...

Hi,

When the “CSS” control group is pinned (via Pin control groups), the pinned CSS textbox renders empty, even though the element has CSS generated by the bi-directional CSS Sync feature. Unpinning the group immediately shows the correct, up-to-date CSS again.

Steps to reproduce:

  1. Select any element.
  2. Open the Style panel → CSS tab.
  3. Pin the CSS control group (pin icon in the group header).
  4. Change any style via the GUI (e.g. Typography → Color) that should sync into the CSS field.
  5. Look at the pinned CSS section (bottom panel) → the field is empty, only showing the “Write your CSS here.” placeholder.
  6. Unpin the CSS group → the CSS field immediately displays the correct generated code (e.g. %root% { color: #ff0000; }).

Expected behavior:
The pinned CSS field should stay in sync with the GUI-driven styles just like the regular (unpinned) CSS tab does.

Actual behavior:
The pinned CSS field appears empty while pinned, hiding the actual CSS that is being generated/applied to the element. The underlying styles are not lost — only the pinned field’s display is broken. Toggling the pin off and on again “fixes” the display, suggesting the pinned instance of the CSS editor isn’t receiving sync updates while pinned.

3

Hi @danielvigh,

thank you for the report. However, I’m not able to replicate the issue. Please check the gif that I recorded when typing inside the typography controls, while having the CSS control pinned:
CleanShot 2026-09-23 at 11.36.07

So, what am I doing differently than you?

Matej

4

Hi @Matej ,

Found it — it’s not a native Bricks bug, sorry for the noise. It’s caused by Advanced Themer’s Builder Tweaks setting “Superpower the Custom CSS control.” When that toggle is enabled, the pinned CSS field goes empty; disabling it fixes the pinned CSS sync completely.

Since you couldn’t reproduce it, that’s the missing piece — you probably don’t have Advanced Themer active (or that specific tweak off) on your test site. I’ll flag it to Advanced Themer’s support instead. Thanks for checking it out!

Daniel

Screenshot: Zight 2026-09-23 at 12.11.31

6

Hey @danielvigh,

thank you for responding. I’m glad you figured it out, and yeah, it’s exactly that, I don’t have AT, so I couldn’t replicate it. :slight_smile:

I’m marking this topic as NO BUG, as it’s bug on our side.

Thank you,
Matej