A couple weeks ago in Mountain View, CA, the Chrome Dev Summit 2014 went down. They’ve very kindly made available online videos for all the sessions.
Or for the TL;DW crowd, here are Chris Coyier‘s notes from the conference.
Snap Tomato seems like a seriously cool way to get your code on any device for testing. But it does require that you be able to paste your HTML into their online editor. Would be super cool if you could also pass them a URL, but then again, this actually lets you paste code that doesn’t currently exist on a public URL…
Nome (pronounced know me) is a JavaScript library that leverages the power of HTML5 geolocation and location data.
While that may sound a little weak on first-read, scroll down their homepage to see all the data you can easily get from their API… Nome is impressive.
Have to admit, I had not heard of window.fetch before, but this polyfill from GitHub (and the browser support it helps provide) makes me want to get to know it better!
Ever want to watch your users use your page? K, maybe not, but you do want to know how they interact with your page, right? Well we can at least make a pretty good guess how their eyes scan your page…
How readable is your CSS? Ever go back and look at something that you wrote like a year ago? Yeah. Mark Rabey offers a few solutions to help make your CSS better.
Based on the incredibly-awesome Can I Use website’s data, I Want to Use is a very cool spin, allowing you to enter something that you want to use, and see what percent of the current browser market will be able to support it… I do wish the site had a better way of dealing with someone (like me) looking for something that isn’t available, like vmin…
Stop Writing Stateless HTML: The basic concept is that only non-user-oriented HTML should actually be in the mark-up initially delivered to the browser; any user-oriented (log-in forms, geolocation info, shopping cart, any type of status indicator, etc.) should be added via JS… The initial benefit is a single code base for all users, less initial HTML to download, and this stuff isn’t needed by bots for search indexing anyway. Of course, many of you will scream “But what about actual users that don’t have JS?”, which is always a good point, but there is plenty of research saying that the number of users worldwide is about 1%. Then again, if your audience is big enough, 1% could be a significant number of people…
Wow, thorough run-down of how various browsers, and versions, deal with rounding and truncating percentages and pixels.
Got Git? I do, and I know our team can pick-up a thing or two from this team workflow with Git article.
When we hear regression testing we usually think back-end code, or maybe JS, but pretty much never CSS. BackstopJS just might change your mind…
I’ve always felt like a rep from each part of the team should be involved in the design process, not only so everyone can chime-in on easy, not-so-easy, etc., but also just because different people have different ideas and preferences, that can only help to make the overall project better. Smashing Magazine agrees… :-)
Sticking with Smashing, How To Create Your Own Front-End Website Testing Plan. Some good ideas and resources. I for one did not know you could use Shift + Command + 4 on a Mac to create screenshots! I use Skitch, which I love on a PC, but hate on a Mac, because it tries to shove everything through Evernote, which I do not use! Nice to now know this alternative…
Okay, so Smashing Magazine was on a roll, what can I say… A nice walk through creating a polyfill for the HTML5 detail element.
And finally, I finally found the reason for the annoying Facebook bug where opening a photo and canceling out of it bumps you back to the top…
Happy reading,
Atg