New answers tagged css
"All" option to the left of the "#" would be an easy fix. If you're thinking about adding more advanced functionallity in the future - namely multiple selection, consider doing it this way: download bmml source – Wireframes created with Balsamiq Mockups I really like this option for complex filters.
You could chunk the complexity into a lower limit and an upper limit, and optionally a difference between the two if this is useful. Increasing the lower limit above the upper limit automatically shunts the upper limit along, while decreasing the upper limit below the lower limit automatically shunts the lower limit down. If the user has manually entered a ...
You can keep hidden the two input controls, and show them only when the user taps one of the extremes: User should be able to drag extremes, which may also contain the current values.
Well formatted markup will not necessarily present information in the order that a person would expect it. For years I've placed the navigation at the bottom and the primary text at the top (within the HTML) and used CSS to place the nav where I wanted to. SEO people I talk to still consider that to be a good practice. I think that looking at your page w/o ...
The W3C answer to this is a strong "yes". They consistently advocate separation of semantic and presentation concerns, and if that is done rigorously, then unstyled HTML should make visual sense, because the default behaviors for paragraphs, definition lists, captions etc. are designed to make visual sense. The point is not so much that people will have ...
Generally speaking if you are coding semantically your unstyled page will be clear. Browsers apply default properties to elements like h1, p, legend etc. Pseudo elements (:before and :after content) is usually not desirable for accessibility - think screen readers. Unless you have a specific use case for unstyled content then you can safely ignore it along ...
Top 50 recent answers are included