Another fine example of “off-canvas” navigation.
I think we all know to not use :hover on mobile, but Thomas does a nice job of adding the why, which might be useful for discussions with clients, as well as a few methods for allowing :hover in your CSS, but blocking it on certain devices.
Anyone see any reason to argue with this? Not me… ;-)
Having never had any need or desire to do this myself, I initially flippantly skipped past the article notifying the world that unlocking their mobile phone can now get them arrested. Then it kind of irked me, as I started thinking I paid for the phone, why can’t I do with it what I want? But then I read down to the line about the phone being a “subsidized phone”… So, what, they gave me a discount (with my signature on the 2-year contract, of course), so now they partially own my phone?
The lessons to be learned from Google’s way of doing business seem never-ending, and the way they approach employee morale is yet another…
Could the end of CAPTCHA finally be nigh??
A nice collection of CSS generator sites. (The initial link is in Russian, but each destination site is English.)
I haven’t had to think about IE in a while (well, until recently, with the arrival of IE on mobile devices, anyhow!), but for those that do deal with older IEs more regularly, modern.IE seems like a wet dream! I did a couple quick sites and was impressed with what it found for me.
Ever need to work with canvas? Me neither, but I know if I did, I would definitely take a hard look at Canvas Query: “a wrapper library for HTML5 Canvas element which allows it to be used with jQuery like syntax”. Nice!
I’ve written previously about part 1 and part 2 of this series on “getting to know Chrome Dev Tools,” and now part 3 is here, this time dealing with JavaScript performance tracking!
And speaking of Chrome Dev Tools, wow, Google Chrome Workspaces look great (assuming your site doesn’t need to reside on an external host)!
Two new remote debugging tools: Remote Preview, “a tiny JavaScript based tool [that] allows you to preview any URL on large number of mobile devices simultaneously”, and the WebDriver API, a just-published W3C Draft which “will enable browser and platform agnostic control over browsers for automated testing” including “a fairly nice way to write scripts to control browser behavior, DOM manipulation and inspection, and more from a separate controlling process.”
Haven’t had time to play with this, and unfortunately the only demo is a pretty basic example of a responsive site, but the Responsive Boilerplate is certainly worth looking into!
A lot of front-end performance posts are just re-hashes of Steve Souders’ information, and while this post does reference some of Steve’s rules, it also adds a few new tidbits; worth the read.
Mozilla’s Dev Derby is a fantastic event, giving fresh, young developers a chance to show their abilities and grab a little well-deserved spotlight. It’s always great to see what they come up with, and this year’s participants are no different. Congrats to all who involved!
Offering translated versions of a site is often, sadly, like adding accessibility: it is often an afterthought, if ever a thought. But this A List Apart article is right on the button: Translation is UX. If being able to read your content is part of the user experience, I don’t know what is…
And finally, (I know, this is an awful lot of Google wrapped into a single post!) while some think Google’s self-driving car will bring a very happy future, there is still a fear that the opposite will be true… :-)
Happy reading,
Atg