The modern web is always changing, and this article is more than two years old.
Lots of goodness this week and some “badness,” sort of, in the form of posts warning us of the dangers of stopping event propagation and using async scripts. Still, important even if not awesome.
Fans of this site may notice that I also stopped the Monday article dump. From a planning standpoint, this was easier, but it certainly didn’t help traffic (which would drop off on other days) and was arguably not great for readers, who had several articles dumped on them at the same time. Anyway, I hope you find it better.
An excellent article by Philip Walton on why stopping event propagation is a bad idea and ways in which you might be doing so without even knowing it.
The Dangers of Stopping Event Propagation
Ilya Grigorik explains some complications when loading async scripts, when they are appropriate and how to overcome some of the issues of out-of-order execution.
Script-injected “async scripts” considered harmful
Addy Osmani explains Object.observe() which is landing in Chrome 36 beta.
Data-binding Revolutions with Object.observe()
Morphing Menu Button
Ryan Morr explains a technique he uses to capture user interactions before the page has fully initialized.
Maintain Responsiveness by Capturing Unbound Action Events
Recreating the “Design Samsung” Grid Loading Effect
Libraries and Frameworks
An overview of CoffeeScript basics from Azat Mardanov.
Hugo Giraudel discusses several options for managing your responsive breakpoints within Sass, and the benefits and drawbacks of each.
Managing Responsive Breakpoints with Sass
Adam Tuttle looks at a simple but common problem when building Android apps from the Cordova CLI.
Creating Cordova (PhoneGap) Android Prod/Dist Builds on the CLI
Krasimir Tsonev explains a number of features built into Chrome that can make it the must-have tool for testing responsive sites.