44 karma · joined January 25, 2012
"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.
"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...
Polyfill for supporting IE < 8: https://github.com/Schepp/box-sizing-polyfill
> 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]
[1][2] http://daringfireball.net/2011/03/nitro_ios_43
AFAIK all that is still true today aside from webapps saved to the home screen (which now does use the Nitro engine)
I personally don't mind the scrolling effect (there are much worse examples out there).
http://responsive.is/ animates the iframe resize meaning the event will be repeatedly fired.
Up until recently I had a similar issue with position fixed on mobile devices.