2 ms·
Do I understand it correctly, to cause a problem, a page needs to: 1) Add a touch handler to the window.document element 2) Do computations even when there is
by TekMol 9y ago
Do I understand it correctly, to cause a problem, a page needs to:
1) Add a touch handler to the window.document element
2) Do computations even when there is no user interaction
So when the user wants to scroll, the touch handler cannot be run because some other javascript is already running. So the browser waits until the other javascript is finished, executes the touch handler and only then scrolls.
Is that correct?
If so, I am not in much danger. Because I usually do not do a lot of computation without user interaction. And I also do not put a touch handler on the document element.
- ensiferum 9y agoThe problem is that the client side browser side implementation which has it's own display thread (It displays prerasterized tiles) must post the scroll event to the rendering thread which runs the JavaScript engine and then wait for the response before it can show the result of the scroll. With this flag the client side can respond to the scroll request immediately and display already rasterized tiles without waiting for the js thread.