palantir/blueprint

EditableText does not measure contents correctly when alwaysRenderInput=true

Open

#4,423 建立於 2020年11月17日

在 GitHub 查看
 (1 留言) (3 反應) (0 負責人)TypeScript (20,263 star) (2,167 fork)batch import
P2Package: coreType: bughelp wanted

描述

Environment

  • Package version(s): core 3.36.0
  • Operating System: macOS
  • Browser name and version: Chrome 86

Code Sandbox

https://codesandbox.io/s/editabletext-alwaysrenderinput-bug-5x99u?file=/src/index.tsx (forked from https://github.com/palantir/blueprint/issues/3870#issue-530056037)

Steps to reproduce

  1. open the sandbox

Actual behavior

First EditableText is clipped, second one is full width of contents

Expected behavior

Both should display full width of contents

Possible solution

...

貢獻者指南

技術棧
typescriptreact
領域
frontend
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Basic knowledge of ReactFamiliarity with Blueprint's EditableText component
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
60
研究方向
Investigate the EditableText component in Blueprint's source, specifically the handling of the alwaysRenderInput prop. Look at how content width is measured when alwaysRenderInput is true, comparing the behavior when it's false. Focus on the CSS and the component's logic for setting input width. The issue likely involves a missing or incorrect measurement of the input's content width, possibly related to the component's state or refs. Check the forked sandbox for a live reproduction and test a fix by ensuring the input width is calculated correctly for both modes.
EditableText does not measure contents correctly when alwaysRenderInput=true · palantir/blueprint#4423 | Good First Issue