So for @Moneycito and @blake, here are some bugs that have come to light. From @Vimala:
One think I donât like so much is in the sidebar under Navigation tab, the next and previous suttas appear under each other (at least on the screen Iâm looking at now: 1280x1024 on Chrome in W8). I would prefer them next to each other, taking up less space - I think it should be possible. But just my preference. They used to be next to each other (on the same screen) so you probably had a good reason to change this.
This isnât a change, itâs a bug. I see the same thing on my screen. The added âDiscuss & Discoverâ tab must do something that creates this.
On Galaxy Mini: looks much better but cannot find the sidebar menu at all. search does not work and the top menu gets printed over the bottom bar so becomes unworkable (at least for âsuttaâ and âabhidhammaâ but not for âvinayaâ???). So still some work to do there if you want the mobile version to work. But I must say this is a very old android 2.2.1 phone.
On my Galaxy Nexus, it works well. The animations are jerky, but this is par for the course on a somewhat older phone (even the Google apps are kind of jerky). But they work just as theyâre supposed to.
Iâm seeing the same bug in the sidebar prev/next links. In addition, Iâm seeing a similar bug with the script selector buttons under the âControlâ tab; the last button is pushed on to the next line. This is not the case on my laptop.
Then thereâs a weird bug with the prev/next links at the bottom of the page (not the sidebar ones). They are oddly inflated, and the round background is distorted. (see screenshot)
In addition to all these, there is an old bug, one that I had secretly hoped would be fixed by redoing the header, but alas not. And that is that the width of the text column in the text pages is too narrow, squashing into about the left 70% of the screen, which also means the text is too small. Screenshots are attached.
This one shows that the horizontal spacing issue also affects the footer. It also shows the previously mentioned bug with the text prev/next links.
I also had a brief chance to test the site on an iPhone, not sure of the model, but anyway not the latest.
There was a very serious bug, the header aggressively disappeared behind the browser header. It was next to impossible to use it at all. As a general rule, I prefer to keep our code simple, clean, and standards-compliant. So in edge cases like this, rather than resorting to complicated hacks to get it working, sometimes its better to just disable the header animations completely for that model. But itâs your call.
A more minor bug on the same phone, the Notification arrow broke, I guess the relevant CSS properties were not supported. Use an image instead, or donât worry about it?