Skip to content

[Components ] Enable Style Settings in Conditions and Filters #17544

@NDCallahan

Description

@NDCallahan

🧩 Feature: Enable Style Settings in Conditions and Filters

📝 Description

Currently, when applying conditions or filters to form inputs in Budibase, style settings (such as margin, padding, or size) cannot be updated. This limitation becomes especially problematic when designing for mobile, where responsive adjustments are critical.

For example, if a condition hides or shows a field, developers may also want to adjust its spacing or sizing dynamically. Without the ability to modify styles in conditions/filters, the form can look misaligned or inconsistent on smaller screens. Specifically for size, we are unable to change that by just choosing custom css.

This feature request proposes allowing style settings to be updated within conditions and filters when certain criteria are met.

💡 Use Case

As a Budibase user, I want to update style settings (margin, padding, size, etc.) through conditions and filters so that:

  • Forms remain visually consistent across desktop and mobile.
  • Dynamic changes (e.g., showing/hiding inputs) don’t break layout or spacing.
  • I can fine‑tune responsive design without manual workarounds.

✅ Expected Behavior

  • Style settings (margin, padding, size, alignment, etc.) are available as configurable options in conditions/filters.
  • When a condition is met, the selected style changes are applied immediately.
  • Works consistently across all form inputs and components.
  • Provides clear UI feedback when style rules are active.

🚀 Why It Matters

  • Enhances responsive design capabilities, especially for mobile layouts.
  • Eliminates the need for clunky workarounds or duplicate components.
  • Improves overall form cleanliness, efficiency, and user experience.
  • Aligns Budibase with modern form builders that support conditional styling.

🖼️ Screenshot

Current

Image Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestneeds-triageNeeds more investigation, and not ready to progress until that happens.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions