Poll Results for Conditional Comments
17 Comments
How did people respond when asked if they wanted the power to serve content conditionally to any browser? The results are pretty interesting…
How did people respond when asked if they wanted the power to serve content conditionally to any browser? The results are pretty interesting…
We’ll cover how to blur text with CSS3 and do it safely by feature-detecting first. Then we’ll do a bunch of experiments with individual letter blurring and also some clever jQuery which gives us deeper access into specific values of a text-shadow.
These are different pseudo class selectors that do slightly different things. In my opinion, :nth-child is more common but :nth-of-type is more useful.
Using a couple of floated pseudo elements on the elements containing columns of text, we can knock out a part in the middle making it look like text is wrapping around an image both directions.
HTML5 range inputs, in supported browsers and by design, don’t show the user the actual value they are submitting. If you want to use the cool slider, but show the value, you’ll have to do that yourself. Here we use the output element and jQuery to show the current value in a bubble that hovers above the range input.
Trent Walton designs a website then codes it up two ways: new school CSS3, and old school image slicing with no CSS3. Going new school meant 1) he could do it faster 2) the page size was smaller 3) less HTTP requests needed and 4) it's easier to update. Not that you all need convincing around here.
Nicolas Gallagher challenges some old assumptions about what's needed to make the pseudo element style "clearfix" work.
Except it's the best reason of all: HOT CSS NERD ACTION.
HTML5 has an incredibly simple method for storing persisting data called localStorage. Natively, you just call a method with key/value pair and that is saved (pretty much) forever. Knowing the key, you can retrieve it at any time. This can be used with "progressive enhancement" in mind, doing things to enhance experiences but not be required. In this screencast we'll look at how to save the data on a form (before submission) so in case the browser window closed or the computer crashed or something, the data would not be lost.
Links from video: