Thu, 12 Oct 2017 11:39:17 GMT
I got this app that is pretty much basically a kind of corporate Instagram. It deals with a timeline of posts (both images and videos) that appears on a infinite scroll div. If I scroll down too fast, it will show lots of posts, each post request it own content from the server as it should do; However, Chrome has a limit of 6 simultaneous active tcp connections, so say that we have 10 or so elements downloading from server at same time due the user actions of scroll down the list too fast, the app become irresponsive (i.e. no href internal link will work) until a tcp connection become available because framework7 request inner pages via Ajax (which requires a new tcp connection, in this case to a localhost). Is there a way to circunvent this and force framework7 to at least reserve a tcp connection for page navigation?
Thu, 12 Oct 2017 11:41:42 GMT
The problem is particularly severe on poor 3g/4g networks...
Fri, 13 Oct 2017 05:20:38 GMT
See doc/google about "lazy loading" content