pedro-cf opened a new issue, #67852: URL: https://github.com/apache/airflow/issues/67852
### Description In the AF3 Trigger DAG form, each param is rendered on a single row: the field label and the control sit inline. For boolean params, the toggle appears immediately after the label text. When labels differ in length, toggles and other controls do not share a common right edge, so the form is harder to scan than a classic label/control grid. In Airflow 2.x, the FAB trigger form used a two-column layout: label on the left, control on the right, with controls aligned in a dedicated column. That right-aligned control column made boolean toggles easy to compare at a glance, especially for DAGs with many params. **Airflow2:** <img width="1113" height="437" alt="Image" src="https://github.com/user-attachments/assets/1e161c39-784d-4e9a-9dee-f1994cae0c8f"; /> **Airflow 3:** <img width="953" height="646" alt="Image" src="https://github.com/user-attachments/assets/3dffea6c-7a9d-4110-b085-ec01a9a61f3d"; /> ### Use case/motivation We trigger DAGs from the UI with many boolean params (e.g. selecting which integration tests to run). Operators need to flip several toggles quickly without hunting for each switch along an uneven line. A consistent label column + right-aligned control column would match how the AF2 trigger UI behaved and would improve daily use for any DAG with more than a handful of params, not only test runners. ### Related issues - Bug (long param names overflow the modal): link after filing — apache/airflow#XXXX - AF3 FlexibleForm introduction: https://github.com/apache/airflow/pull/45270 - Trigger form wire-up: https://github.com/apache/airflow/pull/45790 - AIP-50 (FAB trigger UI): https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-50+Trigger+DAG+UI+Extension+with+Flexible+User+Form+Concept ### Are you willing to submit a PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
