palantir/blueprint

DateRangeInput shows wrong time in input field on mouseover

Open

#4,239 opened on 2020年7月23日

GitHub で見る
 (0 comments) (0 reactions) (0 assignees)TypeScript (20,263 stars) (2,167 forks)batch import
P2Package: datetimeType: bughelp wanted

説明

Environment

  • Package version(s): 3.18.4
  • Operating System: macOS 10.15
  • Browser name and version: Chrome 84

Code Sandbox

This is reproducible in the official documentation for the component.

Steps to reproduce

  1. Enable the time picker on a DateRangeInput (in the docs, toggle "Enable time picker")
  2. Change the date format to anything that shows the time (in the docs, select "YYYY-MM-DD HH:mm:ss (moment)")
  3. Focus one of the input fields
  4. Hover over any date

Actual behavior

Regardless of what is entered in the time picker, the input field shows 12:00 PM on hover. After you click, the entered time is applied to the input field, as expected.

image

Expected behavior

I would expect what is shown on hover to match what will be applied when you click. Specifically, I would expect the selected time to be respected.

コントリビューターガイド

技術スタック
typescriptreact
領域
frontend
Issue 種別
bug
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-3 hours
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
fresh
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
React basicsBlueprint UI understanding
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
40
調査方針
Investigate the DateRangeInput component in the Blueprint repository, focusing on the time picker logic. Look at how the hover preview time is generated versus the actual selected time. Relevant files likely include the DateRangeInput component and related time formatting utilities. Check if there is a discrepancy in the state used for display during hover vs after click.