Problem
On the Google Flights mirror homepage, the swap button between the origin and destination fields is positioned relative to the whole search row. When the origin field has a value, the destination field and date fields can shift visually, making the swap button appear in the middle of the destination input rather than on the seam between origin and destination.
Expected
The swap button should stay centered on the seam between the origin and destination fields regardless of input contents, and it should not overlap the date fields. On mobile, where the fields stack vertically, the swap button should be hidden.
Proposed Fix
Group the origin/destination fields into a dedicated route-field container and position the swap button relative to that group instead of the whole row. Keep the date fields in a separate group.
Problem
On the Google Flights mirror homepage, the swap button between the origin and destination fields is positioned relative to the whole search row. When the origin field has a value, the destination field and date fields can shift visually, making the swap button appear in the middle of the destination input rather than on the seam between origin and destination.
Expected
The swap button should stay centered on the seam between the origin and destination fields regardless of input contents, and it should not overlap the date fields. On mobile, where the fields stack vertically, the swap button should be hidden.
Proposed Fix
Group the origin/destination fields into a dedicated route-field container and position the swap button relative to that group instead of the whole row. Keep the date fields in a separate group.