Twitter Account(s)
18 Comments
The point: on Twitter I’m @chriscoyier. If you prefer a stream of links from CSS-Tricks only, you can follow @real_css_tricks.
The point: on Twitter I’m @chriscoyier. If you prefer a stream of links from CSS-Tricks only, you can follow @real_css_tricks.
Tables of data can only squish horizontally so far, so they can be a pain to browse on small screens (like mobile devices) where you may need to scroll both horizontally and vertically to browse the information at readable text sizes. We’ll explore a CSS-based possible-solution to this issue.
The new poll (in the sidebar) asks:
In what environment do you primarily work?
I’ve worked from home for a lot of years but that will soon be changing. I’m interested to know the environment readers of this site work in.
If you don’t work at the moment, there is an option for that. If you are a student, there are options for that. If you are a student that works, vote based on the working part.
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.
Nicole Sullivan thinks "wouldn't it be a nice if there was a tool to convert an image of a gradient into CSS code?" The community responds with some newly-created tools to do just that. I couldn't get either of the non-command-line tools to do a multi-stop gradient, but they are only a few days old.
Bookmarklet from Andy Edinborough which analyzes your page by removing class names one by one from all elements and testing the pages scroll performance. In other words, if you are having trouble scrolling a page and suspect it's fancy CSS3 stuff slowing down the party, this bookmarklet may help you track down exactly what it is.
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.
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: