Fix datetime pickers unusable on Firefox and Safari - #71627
Merged
Conversation
boring-cyborg
Bot
added
area:translations
area:UI
pierrejeambrun
force-pushed
the
fix-backfill-firefox-datetime
branch
from
August 17, 2026 09:36
e2225c9 to
50a141e
Compare
pierrejeambrun
marked this pull request as ready for review
August 18, 2026 09:29
pierrejeambrun
requested review from
bbovenzi,
choo121600,
guan404ming,
ryanahamilton,
shubhamraj-git and
vatsrahul1001
as code owners
August 18, 2026 09:29
Member
Author
|
Similarly for task state store: |
Native `datetime-local` inputs report no value until both a date and a time are entered, and Firefox and Safari do not auto-fill the time when a date is picked from their calendar. Picking a date without a time therefore left the field empty, which disabled the backfill form (and every other datetime field). Rebuild the picker on text date and time inputs — the same building blocks the date-range filter already uses — so a date-only entry defaults the time and produces a usable value consistently across browsers.
pierrejeambrun
force-pushed
the
fix-backfill-firefox-datetime
branch
from
August 18, 2026 09:48
50a141e to
de4d241
Compare
bbovenzi
approved these changes
Aug 18, 2026
Contributor
Backport successfully created: v3-3-testNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
|
pierrejeambrun
added a commit
that referenced
this pull request
Aug 19, 2026
…) (#71788) Native `datetime-local` inputs report no value until both a date and a time are entered, and Firefox and Safari do not auto-fill the time when a date is picked from their calendar. Picking a date without a time therefore left the field empty, which disabled the backfill form (and every other datetime field). Rebuild the picker on text date and time inputs — the same building blocks the date-range filter already uses — so a date-only entry defaults the time and produces a usable value consistently across browsers. (cherry picked from commit 9ef2b27) Co-authored-by: Pierre Jeambrun <pierrejbrun@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Native
datetime-localinputs report no value until both a date and a time are entered, and Firefox and Safari do not auto-fill the time when a date is picked from their calendar. Picking a date without a time therefore left the field empty and disabled the backfill form.The picker is now built on text date + time inputs — the same building blocks the date-range filter already uses — so a date-only entry defaults the time (start of day, or end of day for a range's upper bound) and produces a usable value consistently across browsers. It shows the selected timezone and offers a calendar popover, matching the date-range picker.
This affects every place the shared
DateTimeInputis used: the backfill dialog, the trigger form (logical date + manual data interval), and dynamic / flexible-form datetime params.closes: #54429
Before / After
Backfill — date range
Trigger — logical date
Trigger — manual data interval
Dynamic form — date-time param
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 4.8) following the guidelines