palantir/blueprint

DateInput2 weird timezone UX when typing incomplete date

Open

#5,443 opened on Jul 19, 2022

View on GitHub
 (1 comment) (0 reactions) (0 assignees)TypeScript (2,167 forks)batch import
P1Package: datetimeType: bughelp wanted

Repository metrics

Stars
 (20,263 stars)
PR merge metrics
 (Avg merge 43d 10h) (27 merged PRs in 30d)

Description

Environment

  • Package version(s): @blueprintjs/datetime2 as of #5440

Steps to reproduce

  1. visit docs preview from #5440, or build the repo at https://github.com/palantir/blueprint/commit/fbe3c9e3662f0d0dc4096e082c4f3f014e0ab01f
  2. type "7/19/202" into DateInput2

Actual behavior

Incomplete date results in a very unexpected timezone shown in the TimezoneSelect

Expected behavior

Don't parse strange/invalid timezones like this

Possible solution

??

Contributor guide

Research direction
Investigate the DateInput2 component's date parsing logic and timezone handling. Look for where incomplete dates cause unexpected timezone selections.
Tech stack
typescriptreact
Domain
frontend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitReact
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70