3 ms·
thx @trunalb, good find, will check out the video later (man, it is an hour long). I pretty much understand all LinkedIn techniques. Just lack the time to impl
by datadiver 13y ago
thx @trunalb, good find, will check out the video later (man, it is an hour long).
I pretty much understand all LinkedIn techniques. Just lack the time to implement them and support this code for various environments. Ideally this is what JQM team should have provided as a replacement for their barebones and very tricky to use listview widget. Good scrolling/swiping performance is impossible on mobile without managing a sliding window in DOM, like good old editors used to do with files that did not fit into memory.
- trunalb 13y agocool @datadiver. LMK if you need any help. FWIW, I implemented the infinite scrolling when I was at LinkedIn ;)
- datadiver 13y agoomg, you did? I see that you used the sliding window with 3 parts. The closest pages are left as is. Then next set use the technique #1 unloading images. Then the next set of pages use technique #2 hiding pages, while the rest of the pages use technique #3 removing pages. Why not just use #3? Is there a speed advantage to still having around the pages with the fake image and the pages with visibility hidden?
- trunalb 13y agoYup there is. It also takes care of the use cases if the user swipes forwards and then back again quickly.