Will the mobile version be opt-in for mobile users, or will it (at least) work correctly in Opera Mini? Either is fine with me so long as I no longer have to use my Android 'desktop' to 'upload' new stories!
These changes only affect the visual arrangement of the header and footer, not the actual body sections of the site. The overall Archive code is remaining the same - the only difference between the mobile and desktop interface is the visual CSS.
I should note that testing related to an impending upgrade to our JavaScript library has revealed a wide number of issues with how Opera Mini on Android renders the Archive. Due to these issues, we recommend using a different mobile browser if your phone supports it.
"I should note that testing related to an impending upgrade to our JavaScript library has revealed a wide number of issues with how Opera Mini on Android renders the Archive."
Issues which Opera Mobile had and which were fixed on your end.
"Due to these issues, we recommend using a different mobile browser if your phone supports it."
My phone does support Opera Mobile, but it's too large for me to want to use, given the fact it functions exactly the same as Opera Mini where sites have optimised for the non-bloated version of this browser.
It may be that Opera Mobile changed how it handles JavaScript, as it currently seems to be functional on an Android 4.x phone. But we simply don't have the resources to optimize the site for Opera Mini. Because of how it handles Javascript, we would basically be required to create and maintain a separate version of the site that would only run for Opera Mini. More so, if Opera Mini let a user shut JS off, the site would be more functional. Also, certain tools, such as the character counter and rich text editor would not function at all.
Due to how much our base code is changing while we're in Beta, the extent of our support for any mobile browser is unfortunately limited to visual modification. Once our code stabilizes after version 1.0, we plan to address mobile access more fully, be it through a modified site or through an app. Right now, though, we simply don't have the time or coder resources to maintain multiple versions of the code to support a specific browser.
Comment on Sneak Peek: Our Shiny New Header!
Sheogorath Thu 14 Feb 2013 03:34AM UTC
Last Edited Fri 15 Feb 2013 02:40AM UTC
Comment Actions
Sam of Support (AO3_Support) (Official) Fri 15 Feb 2013 04:55AM UTC
Comment Actions
Sheogorath Fri 15 Feb 2013 11:41PM UTC
Last Edited Fri 15 Feb 2013 11:43PM UTC
Comment Actions
AO3_Support (Official) Mon 18 Feb 2013 02:16AM UTC
Comment Actions
Sheogorath Mon 18 Feb 2013 03:29PM UTC
Comment Actions