The reason we process input events off the main thread is because our rendering engines are required to render content designed for desktop on mobile. These sites are not engineered for the requirements of mobile devices and therefore do not have sufficiently low latency to process input events on the main thread. To create highly interactive, bespoke visual effects, apps that run on other platforms (e.g., Cocoa and the Android framework) process input events on the main thread. In order to create the breadth and quality of visual effects, we anticipate needing to let web developers also process input events on the main thread. Introducing a JS worker to process input events off the main thread might help web apps that aren't engineered for mobile produce better visual effects, but it's not a path that leads to a web platform that competes on an equal footing with apps written to the Cocoa and Android frameworks. Adam On Sat Sep 20 2014 at 7:59:23 AM Robert O'Callahan <robert@ocallahan.org> wrote: > BTW, a while back the Blink team produced a proto-proposal which involved > using a JS worker to process input off the main thread. Why did you end up > not pursuing that path? > > > Rob > -- > oIo otoeololo oyooouo otohoaoto oaonoyooonoeo owohooo oioso oaonogoroyo > owoiotoho oao oboroootohoeoro oooro osoiosotoeoro owoiololo oboeo > osouobojoeocoto otooo ojouodogomoeonoto.o oAogoaoiono,o oaonoyooonoeo > owohooo > osoaoyoso otooo oao oboroootohoeoro oooro osoiosotoeoro,o o‘oRoaocoao,o’o > oioso > oaonosowoeoroaoboloeo otooo otohoeo ocooouoroto.o oAonodo oaonoyooonoeo > owohooo > osoaoyoso,o o‘oYooouo ofooooolo!o’o owoiololo oboeo oiono odoaonogoeoro > ooofo > otohoeo ofoioroeo ooofo ohoeololo. >
Received on Wednesday, 24 September 2014 14:30:28 UTC