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.