palantir/blueprint

DateInput2 weird timezone UX when typing incomplete date

Open

#5443 opened on Jul 19, 2022

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

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

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.
3
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.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
React experienceDate/time handling basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Examine the DateInput2 component's date parsing logic, particularly how incomplete dates are handled and how the timezone is displayed. Refer to the linked PR #5440 and commit fbe3c9e3662f0d0dc4096e082c4f3f014e0ab01f. Look in the @blueprintjs/datetime2 package for the parsing function and the TimezoneSelect component to understand how the timezone string is generated.