UI designer/developer here. One who works on features that facilitate reading.
Based on their writing style and the text highlighting habit, this person is likely dyslexic. I’ve helped create functions that facilitate this behavior, which is better suited as a mode that can be enabled manually. There are browser extensions that can do this sort of thing for you. I’ve worked on a lot of assistive reading features.
If this was set as a default behavior, most users would fucking riot. Most of them are using text highlighting for what this person doesn’t want to do.
Edit - I think I need to emphasize that this is based on real data. A shit ton of it. These decisions aren’t made based on vibes. If the user base is performing a specific action repeatedly, we’re going to facilitate it. We can see what you all are doing. UI’s aren’t built around a bunch of conflicting edge cases based on anecdotes. If something performs a certain way, at least major applications, it’s usually because a lot of direct observations and metrics have strongly indicated that this is the preferred approach.
Admittedly, sometimes business goals get in the way of that. But if those business goals we have to push get in the way of conversions, they get abandoned pretty quickly.
(Apologies for my tone below, but this affects me also, and I dislike the notion that messing with how you normally select text is a niche desire)
We don’t need any new functionality or a custom mode, we just want unexpected popups to not get in the way of expected behaviour when selecting text.
As long as your options appear well above the text, and doesn’t cancel the highlighting, I can’t accept whatever you want to do. But as the OP writes, if it’s easy to misclick, this is bad UI design because it does not conform to the expectation that nothing will pop up. (Google Docs is the first example that comes to mind as implementing popup options totally fine, from recollection)
If it’s too close to the selected text and causes misclicks, then I’m gonna be annoyed about this since the vast, vast majority (luckily) of text on the internet you can highlight to your heart’s content and nothing pops up.
Just keep options decently above the highlighted text (I dunno what the right number is, 2 lines above the start of your selection? hey I’m not a UI designer)
In conclusion, change is okay, but intuition is important.
Tantacrul makes some great UI videos if you haven’t seen them before (not that I’m telling you how to suck eggs about your own profession, he’s just genuinely funny and interesting to watch)
The mode for options is called the right mouse button and the mode for just highlighting is the left mouse button. One of the great pillars of UI design is conforming to expectations.
lots of people do it, not just people with dyslexia. it helps keep track of where you are when there are large blocks of text. also it usually raises contrast so I’m sure that helps some people even more.
If you’re selecting merely to read, there’s a good chance the text is too small, the lines too long without enough space, the contrast too low, and that would all be addressed by following common web accessibility standards.
Good accessibility is good UI.
16px is commonly considered a good minimum text size for accessibility.
When I outgrew thinking tiny text was cool, I standardized interfaces to render at least that size & found a vast improvement.
A good rule of thumb for interfaces is “one action, one function.” Highlighting text and opening a context menu are two separate functions that should require separate actions (at least as default behavior, user configurability is also a good thing). If I highlight text, the only thing that should indicate is that I want the text highlighted. If I subsequently want a context menu, I will do the context menu action (right click, long press, etc). A UI should never be trying to predict what I want and it absolutely should not be doing things that I didn’t explicitly direct.
You need sane defaults and having what is effectively a predefined macro is not a sane default.
I think I agree with you. I usually select the text to do an action and the choices are useful. I don’t select for the better reading, if anything it’s just to highlight the text.
UI designer/developer here. One who works on features that facilitate reading.
Based on their writing style and the text highlighting habit, this person is likely dyslexic. I’ve helped create functions that facilitate this behavior, which is better suited as a mode that can be enabled manually. There are browser extensions that can do this sort of thing for you. I’ve worked on a lot of assistive reading features.
If this was set as a default behavior, most users would fucking riot. Most of them are using text highlighting for what this person doesn’t want to do.
Edit - I think I need to emphasize that this is based on real data. A shit ton of it. These decisions aren’t made based on vibes. If the user base is performing a specific action repeatedly, we’re going to facilitate it. We can see what you all are doing. UI’s aren’t built around a bunch of conflicting edge cases based on anecdotes. If something performs a certain way, at least major applications, it’s usually because a lot of direct observations and metrics have strongly indicated that this is the preferred approach.
Admittedly, sometimes business goals get in the way of that. But if those business goals we have to push get in the way of conversions, they get abandoned pretty quickly.
(Apologies for my tone below, but this affects me also, and I dislike the notion that messing with how you normally select text is a niche desire)
We don’t need any new functionality or a custom mode, we just want unexpected popups to not get in the way of expected behaviour when selecting text.
As long as your options appear well above the text, and doesn’t cancel the highlighting, I can’t accept whatever you want to do. But as the OP writes, if it’s easy to misclick, this is bad UI design because it does not conform to the expectation that nothing will pop up. (Google Docs is the first example that comes to mind as implementing popup options totally fine, from recollection)
If it’s too close to the selected text and causes misclicks, then I’m gonna be annoyed about this since the vast, vast majority (luckily) of text on the internet you can highlight to your heart’s content and nothing pops up.
Just keep options decently above the highlighted text (I dunno what the right number is, 2 lines above the start of your selection? hey I’m not a UI designer)
In conclusion, change is okay, but intuition is important.
Tantacrul makes some great UI videos if you haven’t seen them before (not that I’m telling you how to suck eggs about your own profession, he’s just genuinely funny and interesting to watch)
I disagree.
The mode for options is called the right mouse button and the mode for just highlighting is the left mouse button. One of the great pillars of UI design is conforming to expectations.
lots of people do it, not just people with dyslexia. it helps keep track of where you are when there are large blocks of text. also it usually raises contrast so I’m sure that helps some people even more.
So does the edge of the window & mouse pointer.
If the contrast sucks, then the UI is already broken. There are accessibility standards for
If you’re selecting merely to read, there’s a good chance the text is too small, the lines too long without enough space, the contrast too low, and that would all be addressed by following common web accessibility standards. Good accessibility is good UI.
16px is commonly considered a good minimum text size for accessibility. When I outgrew thinking tiny text was cool, I standardized interfaces to render at least that size & found a vast improvement.
UI user here.
A good rule of thumb for interfaces is “one action, one function.” Highlighting text and opening a context menu are two separate functions that should require separate actions (at least as default behavior, user configurability is also a good thing). If I highlight text, the only thing that should indicate is that I want the text highlighted. If I subsequently want a context menu, I will do the context menu action (right click, long press, etc). A UI should never be trying to predict what I want and it absolutely should not be doing things that I didn’t explicitly direct.
You need sane defaults and having what is effectively a predefined macro is not a sane default.
No, you are seeing what the people too clueless to install tracking protection are doing.
I think I agree with you. I usually select the text to do an action and the choices are useful. I don’t select for the better reading, if anything it’s just to highlight the text.
I can confirm the dyslexia thing and highlighting