Idea
Add a compatibility toggle (e.g. under the existing Bricks settings/enhancements admin page) that lets users opt to use Bricks' own native button styling controls instead of having the framework's button classes/tokens take over button appearance.
Why
Some users prefer builder-native controls for specific elements rather than framework-driven styling. There's currently no such escape hatch anywhere in the Bricks integration — it's all-or-nothing. A simple on/off switch scoped to buttons would resolve that without a broader architecture change.
Scope
- New option in
includes/class-bricks-settings-page.php alongside the existing reBEMer / Color System / class-hints toggles.
- When enabled, framework button classes/tokens should not apply competing styles to elements using Bricks' native button controls.
- Keep default behavior (framework controls buttons) unchanged — this is opt-in.
Idea
Add a compatibility toggle (e.g. under the existing Bricks settings/enhancements admin page) that lets users opt to use Bricks' own native button styling controls instead of having the framework's button classes/tokens take over button appearance.
Why
Some users prefer builder-native controls for specific elements rather than framework-driven styling. There's currently no such escape hatch anywhere in the Bricks integration — it's all-or-nothing. A simple on/off switch scoped to buttons would resolve that without a broader architecture change.
Scope
includes/class-bricks-settings-page.phpalongside the existing reBEMer / Color System / class-hints toggles.