Category: Code

Ryan McCue has started a discussion around plugin dependencies in WordPress, Gary Pendergast has responded. Ryan thinks it needs to be solved, Gary doesn’t – but if he did, would solve it a different way. As a user, I don’t want to be exposed to security issues in orphaned code. Each of them go into some technical details, […]

I made a dumb bookmarklet on April 1 and forgot to publish it. drag this to your bookmarks Better late than never, he lied.

Complaining about WordPress 4.2’s inline Emoji script is to complain about the biggest front end performance gain of the feature. You see, that tiny script does two things: check if your visitors browser supports Emoji, and, asynchronously load the JavaScript to polyfill Emoji if the visitor’s browser requires it.

I like a much reduced set of body classes when coding up a WordPress theme. Two template types, two main classes. Oh, and I put it on the HTML element too. To call my coding opinionated is somewhat of an understatement.

As I work on patterns for my site redesign, I generated two templates without consideration for microformats. The two templates I created were for a WordPress archive template and an article/page template. Microformats add structured data to a web site. Using microformats allow machines reading a site to know find information such as the: page […]

The Filament Group continues to do great work: Font Loading Revisited with Font Events

calc isn’t a new feature, but at the time of writing MDN describes it as experimental: this technology’s specification has not stabilized, check the compatibility table for the proper prefixes to use in various browsers. Also note that the syntax and behavior of an experimental technology is subject to change in future versions of browsers […]

Internet Explorer makes me sad every time I open it to cross-browser test during development and it crashes on console.log. A simple check OR define option can kill console in the IE developer toolbar, so I decided to write a more robust cross-browser compatible console.log.

Jeremy Keith’s recent post Polyfills and products asked an interesting question about handing polyfilled code to clients: [Short term client projects] makes it very tricky to include a polyfill in our deliverables. We’d need to figure out a way of also including a timeline for revisiting that polyfill and evaluating when it’s time to drop […]

There are a few Sass media query mixins going around for dealing with old versions of IE. Often they include predefined break points, whereas I like the simplicity of passing a numeric value. Capable browsers wrap the content in a media query, incapable browsers get the unwrapped content.