Tag Info

Hot answers tagged

4

Double clicking to edit something that looks like an <H1> tag is a really unconventional behaviour to use in a browser environment, and to my experience double clicks as a whole are very rarely seen. I could imagine a scenario where a user hysterically double clicks a range of labels just to be annoyed that they don't understand which ones are editable ...


3

For a cleaner look, avoid having a reset button. Hovering (although complicated) is visually more appealing. For a "null" vote, you can have a 'o' (preceding the stars) which can turn red when selected -- meaning the user has dropped his vote. o * * * * * (Many current systems do not have the provision to remove a vote; if a user doesn't like the ...


3

The one thing to be careful about when mixing onMouseDown behaviors is that user may want to drag and select the text (to copy the text for instance). So I think a better solution for you would be to keep the box interaction as just click to edit and have a drag icon on left/right which will allow the user to drag them. You could also do so that each of ...


2

The first interaction pattern that you show is very close to the way that apple handle it in their built-in apps. The difference being that they don't have an "add new row" item. They use a clear + button in the navbar to achieve that - which is the right way to go. If you use an item at the end of the list to add new items, you are not only breaking user ...


2

Inline not Modal Inline edit is to be preferred at all times. The user keeps context, have the ability to use information related and narrow to the edit and the user don’t have to focus on a new UI. It is the same, simple, easy and straightforward process where the flow of work can be kept. Modal dialogue breaks the users’ context and it takes time for the ...


1

Editable elements are simple and has pre-defined formatting. Trying to implement complex rules you will probably end up with advanced inline editor. The better way is to to use multiline editor with very simple syntax rules and immediate preview mode. The same we have here, at UX SE. The rules could be as follows: Line without a * mark is a title Line, ...


1

Working with a few assumptions ... The number of fields you want to display is few (city/state/country). The user already knows what city/state/country they want, they are using the search to locate the record for it. Therefore they will be able to add more characters to the search box until the item they are looking for appears in the list. I would ...


1

You would use the popover for smaller, more transient tasks. If there are multiple views that the user can find under this view, you would use a modal view. For example, if the user is simply viewing the details (with the option to edit) of an entry in your table, then you would want to use a popover. This is what you mentioned in your question, so in ...


1

Why not fully embrace the navigation model of iOS? Selecting and item would open the item in a new screen that would slide from the right (giving the impression of diving deeper towards the right hand side). From there, a back button would show on the header, with which a user can return to the list of items.



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