You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 8, 2021. It is now read-only.
THIS IS JUST A HUNCH: that Opera Mini servers cut-off JavaScript processing after 1 or 2 seconds (citation needed) so blank pages on Opera Mini may be due to abrupt arbitrary termination of processing.
Assuming truth to this, here are areas where we could radically trim execution processing for Opera Mini by limiting what we do within the DOM in this context.
Transitions -- not supported by Opera Mini anyway -- in jquery.mobile.navigation.js and jquery.mobile.transition.js.
Much list, page, and control markup -- not supported by Opera Mini anyway -- in
jquery.mobile.page.js
jquery.mobile.list*.js
jquery.mobile.buttonMarkup.js
Others?
One way to look at this is: it might be good to have access to different markup strategies based on execution context. IOW, the Strategy, or a Strategy-like design; TL;DR: at runtime, pick from available interchangeable markup generating implementations.