Tag Info

Hot answers tagged

70

There's an easy way to approach user-select: none, and that is to ask a single question: Would selecting the text be the primary/secondary interaction a user would intend if touching the screen there, or would it be a hindrance to the task they were trying to carry out? Image Carousels (love them or hate them) are a fantastic example of this. In a touch ...


61

In general, you shouldn't use it globally. Oftentimes, users select some text, maybe to highlight something to show a part of the text to a friend, to copy text or to mark the text just to be able to read it better (which I do when the text is pretty wide and it's hard to follow the text wrap in the sentence). However, there are really good examples where ...


25

There are such people as "selection readers". I am one of them. I (for some reason consciously unknown to me) have a tendency to select text while I'm reading it. Sites that stop me from doing so make me very sad and mess up my user experience. I also completely disagree with the point in what is currently the top answer. Those things that pop up whenever ...


12

Not being able to select text is the most annoying anti user-friendly css property there is right now in modern websites. Reasons: Lets not try to act as if our website is something it isn't. It's not a mobile app and the reason you cannot select text in an application is because it is not inside a text-box and therefor is not supposed to be selected for ...


8

There are many contexts in which it is good UX, and many where it is bad UX - there's no one-size-fits all answer. As you flag in your question a button or action that when clicked highlights the text isn't good UX, and there are likely to be very few circumstances when a user should need to highlight that text. However bodies of text shouldn't be disabled ...


4

Messing around with standard application features (eg selecting text in a browser) is a bad idea in almost every instance ... the user expects to perform whatever action they've done. They can't, because you've broken it - ergo you've failed to meet user expectations. Simple as that. Personal rule of thumb: In all cases, disabling highlighting of text is ...


2

The simplest solution I can think of is a numerical text input followed by a drop down for unit size - something like this: download bmml source – Wireframes created with Balsamiq Mockups


2

the question is IMO fairly broad, so my answer will probably reflect this First of all, separate applications per platform are not déclassé, they live side by side and the choice for one or the other really is about the purpose & needs of the application + the performance that you want to get, full native app vs. web app will have a huuugeee difference ...


1

How about one tab for each object you want to create?


1

The user may be completely missing the checkbox and text, since it fades into the footer of your modal. There is nothing calling attention to it. I would try two distinct buttons for saving: "Save and Add Another" and "Save and Close" (or just "Save").


1

There is just one context where I found this a useful feature, and that was in the context of a game. I had a playing area the player was interacting with using the mouse. On that playing area were objects with text labels. Sometimes the player meant to click an object, but marked the text in the label instead. This was bad because it was not what the user ...



Only top voted, non community-wiki answers of a minimum length are eligible