Perhaps even more ironic is that they allow their page to be indexed by google. Much like Alanis Morisette song about the same subject, there isn't much irony in the page.
The author fails to take into consideration tablets, e-readers, smart TVs and every other device, currently available or in the distant future, that will have a web browser.
"It Defeats User Expectation"
So let's keep everything exactly the same?
Responsive design to me is progress, eventually we'll either come up with good practices for working with it or maybe something else will take it's place. The way we access the internet is in constant flux and the 960 magazine layout has many pit falls in terms of usability outside of desktop sized screens.
The odds of coming up positive on a DNA test are a lot higher than I would have originally believed:
"DNA matching for criminal cases looks at only a few specific loci and the alleles associated with them, so the chances of two separate people matching come in somewhere around 1 in 7,000"
http://www.fluther.com/145318/is-there-a-possibility-that-th...
Title is a bit misleading, it's a valid CSS property, not a hack. And the width of block elements has always been predictable, albeit slightly confusing (width + padding + border = element width, etc.)
If the alarm is armed shouldn't it be triggered if something connects to the OBD port? Not actually prevent the port functioning just trigger the alarm.
The lack of the faster Nitro javascript engine in webviews on iOS is probably a major reason for this.
> The Nitro JavaScript engine is only available within Mobile Safari. Outside Mobile Safari — whether in App Store apps using the UIWebView control, or in true web apps that have been saved to the home screen — apps get iOS’s older JavaScript engine. [1]
> “Apple is basically using subtle defects to make web apps appear to be low quality — even when they claim HTML5 is a fully supported platform,” says one mobile web app developer, who asked that his name not be used.[2]
> I personally don't mind the scrolling effect (there are much worse examples out there).
What I find really off-putting is that I scrolled and the page did not go down, not until letters completely flew away. I had the uncanny feeling I was required to work against the page.
The 3 month expiry is what led to my company paying for licenses. Having to potentially pause development and spend time doing the same setup process 4 times a year is painful (and wasteful since there's no real reason apart from trivial licensing issues - the resulting install is the same).
I think the jump is more realistic, it means the resize event will only be fired once. Which is what the orientation change on a mobile device would do.
http://responsive.is/ animates the iframe resize meaning the event will be repeatedly fired.
