palantir/blueprint

DateInput2 weird timezone UX when typing incomplete date

開放

#5,443 建立於 2022年7月19日

 (1 則留言) (0 個反應) (0 位負責人)TypeScript (2,167 個分叉)batch import
P1Package: datetimeType: bughelp wanted

倉庫指標

星標
 (20,263 顆星)
PR 合併指標
 (PR 指標待抓取)

描述

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

??

貢獻者指南