4 ms·

That button is there and has always existed there. For Wordpress, that might be a great idea of making it a global opt-out. I'm actually going to suggest that

• tednaleid 15y ago
  Thanks, I think that'll release a lot of the pressure that it sounds like you're getting from your other comments here. I think that trying new things is good, and I support that, but without an escape hatch some people are going to feel trapped.
• mikeklaas 15y ago
  We have a native app that is similar in that it makes extensive use of css transforms to animate content on the iPad (Zite, btw. I believe it is smoother and less crashy than the OnSwipe pages I have seen). The biggest issue we've come across is limiting the total screen area (in pixels) of elements having "-webkit-transform: translate3d(0,0,0);" (this is the declaration you use to force the browser to use 3d acceleration to animate this element). Once it goes beyond a certain size, there isn't enough memory on the iPad to handle it and you get jerky animation and crashes. This will help: http://mir.aculo.us/2011/02/08/visualizing-webkits-hardware-acceleration/ http://mir.aculo.us/2011/02/08/visualizing-webkits-hardware-...
• rix0r 15y ago
  For another thing, on WordPress.com the "View Standard Site" button hardly ever works for me. I keep on trying it, hoping for the better, and cursing every time I'm forced to deal with the OnSwipe theme. And on Mike Taylor's blog (http://reprog.wordpress.com/ http://reprog.wordpress.com/), the scroll used to be broken in OnSwipe (it kept scrolling me back to the top). Not sure if it's still the case, these days I just keep to my feed reader instead of visiting his site because I don't want to deal with OnSwipe.