Quantcast
Channel: Posts/rss
Browsing latest articles
Browse All 20 View Live

Comment from Web Axe

If designers weren't so silly we wouldn't have this problem to start with...

View Article



Comment from xulai

good!you NB!

View Article

Comment from Lu Nelson

Ach. Bummer

View Article

Comment from Daniel

Hey Lu, the ~ selector is siblings after the element, not before it - would have been great!

View Article

Comment from Gregor

sorry, my fault, :empty is to select empty HTML nodes, not to select empty input tags. They way Jonathan did it seems the only way to do it in CSS-only

View Article


Comment from Lu Nelson

Couldn't you use the sibling selector '~' instead of '+', and thus be able to put the label before the input? You'd have to wrap each label and input in a span or div. Browser support is less good for...

View Article

Comment from Adam

@GREGOR: CSS only recognizes the initial value of the input and doesn't update when the value changes.

View Article

Comment from Patrick H. Lauke

I like the general hacky approach. Of course, a few caveats on top of your own: - from an accessibility point of view, you should explicitly associate your label with the relevant input. Although...

View Article


Comment from Gregor

why not using input:empty / input:not(:empty) instead?

View Article


Comment from Scott Gilbertson

Very cool. Problem one will be solved by the subject select in CSS level 4. At least I think that's what this is talking about:CSS Selectors4 Subject As I understand that, it would let you put the...

View Article
Browsing latest articles
Browse All 20 View Live


Latest Images