Clearly state what they're missing. Chances are there's some good reason ...
I've taken the time to draw some wireframed examples that might help you decide on how to design your time-picker control. Below you can see 3 screenshots which show (IMAGE 1) a time-picker control for all units, an increment button, decrement button, numeric input field and unit picker dropdown (if needed.)
IMAGE 2: The idea is that you set it up so that ...
While JoJo's comment is valid there's always a trade off between the extra effort required to implement full graceful degradation and the rewards that it brings.
If Yahoo!'s figures are correct then the question you have to answer becomes "is this 2% of the on-line population valuable to me?"
If their sample is representative of your user base then the ...
Another option is a logarithmic slider, like this:
download bmml source – Wireframes created with Balsamiq Mockups
This is appropriate when the value can span multiple orders of magnitude, but the number of significant figures is low. It will not allow the user to select between, say, 500 ms and 501 ms, so I suspect it might not be what you need. It ...
Keep it simple:
As the user types into the first textfield, have a strength indicator near by telling the user if their password is strong that updates as they type. Don't enable the confirm field until they have entered a password that meets your requirements.
When they tab into the second field to confirm, have a label next to it that updates as they ...
I'd just use the noscript tag.
<div class="error message">
You may find in your own analytics that the percent is smaller (or possibly ...
Pragmatically it's when the cost of doing the graceful degradation outweighs the benefit.
Look at how times are shown in other stopwatch applications as an indication, as they have been refined over years. The typical way that it is shown is simply as HH:MM:SS.
If you're only looking for time to an accuracy of seconds and you want more than just numbers, then something like 2h 23m 12s seems clear enough without taking up lots of space. You ...
I would use there 24 Colors found in 24-pack Crayola Crayons.
red, yellow, blue, brown, orange, green, violet, black, carnation pink, yellow orange, blue green, red violet, red orange, yellow green, blue violet, white, violet red, dandelion, cerulean, apricot, scarlet, green yellow, indigo and gray
I'm sure some sort of research went into getting the ...
Short answer: do not select any radio button. Leave them all unselected.
This is a misuse of radio button control where (by convention) there always should be one (and only one) selected item.
Unselecting all items is not noisy (IMO) and recall same pattern used in other controls (for example combo boxes) where no selection means multiple ...
In a marketing and publisher point of view what Tynt is providing seems very beneficial for their needs. On a UX point of view it's a double edged sword in my meaning.
You could argue that the user experience benefits from the auto generated addition to copied content since it seamlessly enables the receiver or "copier" of the content to keep track of its ...
Regarding sliders/carousels I say most definitely yes.
Sliders are Lists of Information
A slider (e.g., like slidejs) is really a list, or array, of information elements. In this case the elements usually consist of a full-bleed background image possibly containing a title, some descriptive copy, and possibly a link/call-to-action. The idea is you can ...
You are asking what 24 colors to use, but I think the bigger question is 'is there an ideal number of colors to even offer in the first place?'
Looking at a couple of the sketching apps on the iPad, you will notice they they use very limited palettes.
Paper, for example, has palettes of 7 colors:
Granted, Paper comes with a bunch of different palettes to ...
One of the golden rules of UX is to never do anything unexpected.
Adding a bit of text to copied text is very much unexpected behaviour, and will definitely lead to frustrated users.
The users will either paste it and hit enter without removing the added text first, which will frustrate them and make them look like an idiot, possibly driving them to ...
I usually draw the line at sanity. At a certain point, the amount of time/effort spent on an ...
From my perspective, there is not much difference between flipping card or pop-over window showing more details. So, yes it is a good idea as long as it's just transition effect and does not negatively affect usability.
Pros you get:
You can pack more cards in one view (of course: avoid excess), and funnel user actions from selecting artist to going to the ...
They can do it, therefore they WILL do it. Count on it, if you want to write software that works.
I resize my browser windows (desktop PC) quite frequently for a variety of reasons.
Your webapp isn't necessarily the focus of the user's entire world.
Using many input controls with different measurments is rather not optimal, because user will spend time to decide, which one fits to him.
You may trim and move x100ns outside edit:
download bmml source – Wireframes created with Balsamiq Mockups
If odd value is entered, after leaving focus it is corrected to odd (lesser or bigger).
Also in similar ...
Often times you need both.
The pop up sign in (or a drop in panel) is the smoothest experience for most use cases. It allows users to sign in without leaving their current path.
But you will also run into cases where you need to land users on a sign in page. In my experience, this should be the exception, not the standard.
One example of the exception ...
I think the user needs to know where he is and what is not working.
So for two main reason I would push a state:
User might want to come back to check if it was fixed
Having a dead address visible in the browser gives the user the certainty that the page is not working. The user might want to copy the address and come back later to see if ...
No! There are no good cases for ruining standard scrolling.
Standard scrolling of web pages is the page turning of web viewing.
Any changes to standard scrolling are no longer standard scrolling, and need their own interface.
There's plenty of options for fancy scrolling mechanisms and interfaces:
Little highlights in the scroll bars for jump points
I always get into arguments with designers over this, because I think that JS is a part of the web, and it should be expected if you want to browse cool, modern up to date websites. However, I also accept that sites should probably be browsable without JS, at least at a basic level. So for those who insist on not having JS, the core parts of the site should ...
I would say this is a perfectly reasonable action in terms of UX - Provided you make it clear to the user that a drop-down is available, of course.
If you fail to make it obvious then a quick hover with the mouse will provide the user with no visual feedback due to the delay, and as such the user will miss the drop-down entirely.
Whilst instant drop-downs ...