JavaScript, the Elephant in the Room of Progressive Enhancement
Does JavaScript have a place in the world of progressive enhancement? Rob weighs the arguments.
49 Results
Does JavaScript have a place in the world of progressive enhancement? Rob weighs the arguments.
Rob Tarr shares about detecting postion:fixed in the browser—trying to find a solution that will work with iOS 4.
We needed a small, light-weight, cross-browser color picker. So we built one with canvas and a little JavaScript.
Modifying jQuery.trim to accept other characters besides just whitespace. By doing this in your code, your changes will persist, even when upgrading to a different jQuery version.
Our incredibly talented designer Ryan Clark has a tendency to create these really cool looking select box UIs. They’re awesome, except for the fact that they’re impossible to style. So we decided to create our own that fit the needs of both us and our clients.
In our review of websites for corporations across the US, we’ve seen a large number of navigation systems that are completely dependent on JavaScript to function. While it’s true that most people browsing the web have JavaScript enabled (about 98% of individuals), it’s also true that this dependence creates barriers for the disabled in using the site and for Google in indexing the site.
JavaScript should enhance the usability of a website, not make it unusable. This is why we build our JavaScript last.
My first-hand experience with progressive enhancement and history.pushstate for newer browsers. Sometimes the simplest solution is the best.
Testing the chaining of jQuery find/children methods vs. chaining the selector of one method.

Katie Jennings
Vice President of Business Development