palantir/blueprint

DateRangeInput shows wrong time in input field on mouseover

Open

#4,239 建立於 2020年7月23日

在 GitHub 查看
 (0 留言) (0 反應) (0 負責人)TypeScript (20,263 star) (2,167 fork)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
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
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.