On Sat, Apr 11, 2015 at 7:12 AM, Greg Weng <[email protected]> wrote: > Hi all, > > Recently I've seen some projects (ex: [1][2]) want to render DOM generated by > JavaScript in WebGL or canvas, and they all claim that they can reach the > performance goal that current DOM system couldn't[3][4]. Suppose their claim > includes all modern browsers like Firefox, I don't really know what's the > issue with DOM system (since I'm unfortunately not a Gecko guy). So I wonder > if there are some advantages these project could provide we may use in Gaia, > and if so does it mean the current DOM system has some issues that we, the > Gaia developers, need to avoid them in application layer? > > And from graphic team I've heard that we're planing to render DOM to GL in > the underlying layer (that is, from my very poor Gecko knowledge, to get rid > of 2D engine like Cario). I don't know if this means we're doing the similar > thing but in different layer, or they're totally different approaches? > > [1]: https://github.com/PixelsCommander/HTML-GL > [2]: https://github.com/Flipboard/react-canvas > [3]: "No DOM + WebGL rendering = highest FPS possible for Web platform" - > README.md of HTML-GL > [4]: "The DOM is too slow. It's not just slow, it's really slow. If you touch > the DOM in any way during an animation you've already blown through your 16ms > frame budget." - "60fps on the mobile web" by Michael Johnston > _______________________________________________ > dev-b2g mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-b2g
Ultimately our goal is to build an operating system on the web platform, and that includes the DOM. If the DOM is too slow to ever achieve 60 fps we need to fix that. - Kyle _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
