Hi
I'd like to report some fundamental internal architecture problems with Opera Mini.
This is NOT related to the rendering, and NOT related to the proxy/rendering servers.
This is about how it actually behaves as a web browser application.
It seems that the handling of HREF links and the loading of pages is quite broken. This has been going on for years (I've submitted bug reports) but hasn't been fixed yet. At the moment I would say that it is affecting 50% or more of the links I click on and pages I want to load. If it doesn't affect you as badly as it affects me, please don't say "it's ok for me". I just want to hear how badly it affects other people so we can get an idea of how pervasive this is and encourage the developers to actually fix it. And also please note I am not reporting anything to do with page serving or page rendering.
For reference I'm using opera mini on Android (Z3C) and use the extreme savings mode.
-
Pressing on a link takes me to the wrong page! Yes, it renders something completely different. Often seen with facebook, I press on a link and it takes me to one of the other links on that page.
-
Links stop responding completely. Pressing on a link does absolutely nothing. However holding down on the link and opening in a new tab does work. But once it has got into this state the only solution is to close all tabs, quit browser, and start again, because it never recovers.
-
Pressing on a link goes to a new blank page and the spinner shows it is loading but then loading stops and the page remains blank. This happens to ANY link, it's not a page rendering problem or a particular website problem, ANY page may end up blank. As proof, if I hold down on the link and open it in a new tab then it works fine.
-
Following a link sometimes throws away history. Pressing Back takes you back to where you were two clicks ago and it's impossible to get back the immediately preceding page. Back/Forward actions show that the page has been completely removed from the history.
-
Pressing on a link shows all the indications that it's going to load the page (spinner, etc), but when finished the page has not changed. Sometimes simply pressing the link again will cause it to work (proof that it's not the destination which is the problem). Sometimes twice is not sufficient, sometimes three times, sometimes even four times I have to click the link before it works. (I've never had to click more than four times to get a link to work).
Are there any developers reading who can comment on the fundamental internal architecture issues?