playcanvas / playcanvas/pcui

The value dragger can get in the way when dealing with long/large numbers

Open
#86 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
793
Forks
97
PR merge metrics
No merged PRs in 30d

Description

There are two main issues here:

  1. The value dragger icon overlaps with the text. The users intention is to try to select or place the cursor at a point on the right hand side of the text field but on hover, the drag icon appears on top of text that the user wanted to select.

https://user-images.githubusercontent.com/16639049/109308254-ab756a80-7839-11eb-8433-9879cf3740fd.mp4

  1. The value dragger 'hit' area seems to be too wide. In the video below, I have to go a fair bit to the left before I can select the text.

https://user-images.githubusercontent.com/16639049/109308337-c9db6600-7839-11eb-9e83-484a66198963.mp4

Not sure what the best solution here as if we separate the label, the editable text field is smaller. ie Making it so that the placeholder X never disappears and give the background a different colour.
image

Another possibility is if the field is already selected, not to show the dragger on hover? Not too keen on this idea though 🤔

Maybe the dragger could only appear below the text field if it's selected?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the value dragger component and reproduce the two cases with long or large numbers shown in the issue videos. Check the dragger’s hover and hit-area behavior around the editable text; done means users can place or select text on the right side without the icon obscuring it or intercepting clicks.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.