Do you think it is possible to still use this engine on another modern browser?
I think it wasn't bad at all, at least for this navigation function on Facebook...

@tao102 said in Static pages modality until Opera Mini 13:

@hybris2

Hmm, Opera Mini 13 was quite a long time ago!

I was going to say that around the time of Opera 13, the layout engine shifted from Opera's proprietary "Presto" engine to Google's "Blink" engine. And the layout engine in Mini likely shifted as well.

https://en.wikipedia.org/wiki/History_of_the_Opera_web_browser

A number of years ago I noticed a remarkable difference when changing from Mini on my Symbian phone to Mini on Android. But according to

https://en.wikipedia.org/wiki/Opera_Mini

if it can be believed, Mini has continued on with Presto.

Being unable to go back and look at that Facebook code, I'd guess that whatever issues you were having, I don't think it was anything as blunt as a major missing feature, but something more akin to Mini's poor Javascript support, a server Javascript timeout, etc. that Opera (or Facebook...there is a Mini developer's guide) fixed over time.

Hi. What is the name of the protocol used by the Opera Mini browser up to version 13 in which the pages are static and do not automatically update in real time? for example, the Facebook home is made up of a series of static pages connected to each other by links to click or any already loaded page must be manually updated in order to be reloaded. In later versions this disappeared.
Thank you!

Hi!
For many years I used your old version of Opera Mini 7 which had the characteristic that when viewing the Facebook home there was no infinite scroll but the home was divided into several static pages.
(From version 8 the structure has completely changed and the classic "infinite scrolling" has appeared).
Can this same function also be activated or used for the new version?
Thank you!