Text selection usability degradation
See original GitHub issueBug reports
Version
2.0.2
Steps to reproduce
- To type any text in first input here http://ericgio.github.io/react-bootstrap-typeahead/
- Try to select this text by pressing out inside of typehead component but outside of typed text (inner input) and then dragging across the text.
Expected Behavior
- text in typeahead should be selectable from any part of the component
Actual Behavior
- you won’t able to select text this way, only by starting dragging from typed text.
Additional
The previous version (1.3.0
) of this component is used here http://web.archive.org/web/*/github. So you could select text by dragging cursor cross the component. but in new version here https://web-beta.archive.org/web/*/github (where is used the last version of the component) it won’t able to achieve.
Possible solution: increase side of inner input which was fit to the side of typeahead component in 1.3.0 version, but now just fit a typed text.
Issue Analytics
- State:
- Created 6 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
The degradation of UX - UX Collective
This involves the design of the entire process of acquiring and integrating the product, including aspects of branding, design, usability and ...
Read more >Poor Text Readability Is Killing Your UX
“Users won't read web content unless the text is clear, the words and sentences are simple, and the information is easy to understand.”...
Read more >Low-Contrast Text Is Not the Answer - Nielsen Norman Group
Before using low-contrast colors on a website, especially for text, take a moment to remember all the reasons why they degrade usability.
Read more >Is "user-select: none" bad UX? - UX Stack Exchange
If the text-highlighting doesn't harm the usability (e.g. horizontal dragging), then I wouldn't disable it, especially as desktop users are used ...
Read more >Age-related differences in the legibility of degraded text - PMC
Accounting for these differences when designing interfaces will improve usability and the user experience for older and younger users alike.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks for the report. This is expected, though I admit it’s not ideal. For context, I rewrote the input in v2.0 to render the same way in both the single- and multi-select cases. This was done to simplify the code paths and hopefully reduce bugs in the process. The tradeoff is that it introduces some subtle behaviors like what you’re describing. I haven’t spent much time trying to solve this particular issue because it feels relatively minor and doesn’t prevent any functionality.
Are you reporting the issue mainly just to bring it to my attention or did you feel like it was a significant behavioral problem?
@alasdairhurst: That issue should be fixed as of v2.3.1