Recently I watched a video on building for touch screens that discusses the challenges when building for touch and keyboard interactions —something that is on the mind of many, many, many, many, many people and something I’ve written about before. So what’s the best way to deal with touch at the moment? Modernizr? Well, detecting for touch primarily using something like
Modernizr.touch can sometimes lead to false positive results plus it can be dangerous to make that assumption when a device also includes a keyboard.
Why on earth authors post blog entries and helpful articles using third party services is beyond me. One may argue to drive traffic and they would be totally legit in saying so, but you see there’s still a problem that lurks about -What if that super cool service goes down? Guess where your content goes? You got it! It sinks with the ship! See ya later super awesome, helpful article on a well researched topic…nice to know you…tah tah.
I had the pleasure of joining my pal Chris Van Patten on his Podcast The Wrapp Up discussing one of my favorite color pickers Frank DeLoupe. I really enjoyed talking with Chris about this time saving tool that I use on a daily basis and the best part of it all? It costs less than a dollar! Boom goes the dynamite.
Web forms are bottom-line the bread and butter of the Web. They allow us to send and input information pertaining to a number of factors revolving around our interests/needs/wants. When it comes to styling inputs (and in particular styling custom select menus) some have argued that styling custom select menus are obnoxious and distract a user from what they’re normally accustomed to. I would disagree with that last statement and think it really involves customizing a select menu in a way that can be distinguished and understood logically. Lets take a look at customizing a select menu and then examine a possibility I’d like to see readily available to authors.
Media queries are a gigantic pain in the ass especially when they’re scattered throughout your code base. This Sass
@mixin attempts in a half-ass way to resolve that problem (for me personally) by keeping it DRY and defining once. There’s also a RubyGem called “Breakpoint” http://breakpoint-sass.com, however I desire a custom
@mixin without the reliance of a dependency like a Gem to manage this for me.