Skip to content

Multi-select DAG parameter input gets truncated when inside a section making options painful to read #50322

@fredthomsen

Description

@fredthomsen

Apache Airflow version

2.10.5

If "Other Airflow 2 version" selected, which one?

No response

What happened?

When using a multi-select field for DAG parameters within a section, the element's width gets truncated and options become unreadable:

Simple example of what occurs below demonstrating the difference of within vs outside a section:

Image

What you think should happen instead?

The multi-select DAG parameter widget should fill the parent element ie it should behave like it does outside a parameter section.

How to reproduce

@dag(
    params=ParamsDict(dict(
        multiselect_in_section=Param(
            title="Multiselect in section",
            description="Multiselect form field changes size based on inputs.",
            default=["one"],
            examples=["one", "two", "three"],
            type=["array"],
            minItems=1,
            items={"type": "string"},
            section="SomeSection",
        ),
        multiselect_not_in_section=Param(
            title="Multiselect NOT in section",
            description="Multiselect form field has a static width filling up entire parent element.",
            default=["one"],
            examples=["one", "two", "three"],
            type=["array"],
            minItems=1,
            items={"type": "string"},
        )
    )),
    schedule=None,
    tags=["test", "bug"],
)
def reproduce_multi_select_dropdown_bug():
    """
    Multi-select DAG parameter field width gets truncated when within a section thus becoming unusable when no selections are present. Appears
    to work just fine outside of a parameter section.
    """

reproduce_multi_select_dropdown_bug()

Operating System

MacOS Sequoia 15.4.1

Versions of Apache Airflow Providers

No response

Deployment

Virtualenv installation

Deployment details

No response

Anything else?

No response

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:UIRelated to UI/UX. For Frontend Developers.area:corekind:bugThis is a clearly a bugneeds-triagelabel for new issues that we didn't triage yet

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions