Repository navigation
Conversation
Test Results 867 files 867 suites 50m 1s ⏱️ Results for commit 8510b6e. ♻️ This comment has been updated with latest results. |
32fce3f to
ac8a718
Compare
ac8a718 to
982286c
Compare
CSSSWTColorHelper skipped setting a color when the control already reported it, but getBackground() also reports colors inherited from the parent. After a theme switch reset a control that owned a color, the new color was skipped whenever the parent had the same one, so the control owned no color. Children of a Forms Section then painted the Section's title gradient image. The helper now remembers that a control lost its own color on reset, including a color set before styling such as by FormToolkit.adapt, and then applies the new color even if it equals the inherited one. A reset compares the control's color with the inherited one, so the engine resets ancestors first. Controls that never owned a color keep inheriting, so the Section title label still shows the title bar. Assisted-by: multiple AI agents and layers of automated tooling 🤖
982286c to
8510b6e
Compare
|
How to reproduce: Theme B, on top of the Dark theme CSS ( Theme A is the same with Steps: open a |
After a theme switch, CSSSWTColorHelper skipped setting a control's new background whenever the parent already had the same color, because getBackground() also reports inherited colors. The reset control then owned no color, and children of a Forms Section painted the Section's title gradient image instead, for example the white text fields in the PDE manifest editor after switching from Light to Dark. The helper now remembers the color it applied and only skips when the control really owns it, and the element resets clear colors through the helper. The existing optimization for unchanged colors stays in place for ordinary re-applies, and a regression test covers the reset case.