4 ms·
The hardest part is actually layout managers, i.e. what happens if you want to support more than one pixel width. With all its clunkiness, CSS & DOM actually so
by Nitramp 12y ago
The hardest part is actually layout managers, i.e. what happens if you want to support more than one pixel width. With all its clunkiness, CSS & DOM actually solve that.
edit: they actually have their own layout implementation(s). I wonder how those compare to the built in browser versions (performance, correctness, ...)?
https://github.com/Flipboard/react-canvas/blob/master/lib/Layout.js https://github.com/Flipboard/react-canvas/blob/master/lib/La...
- jlongster 12y agoIt's css-layout: https://github.com/facebook/css-layout https://github.com/facebook/css-layout. The same engine used in React Native. It turns out that you only need a portion of CSS for apps. It's very performant.
- mortenjorck 12y agoHuh. Using a reimplemented, minimal CSS engine would mean more or less baked-in cross-browser compatibility, right?
- jlongster 12y agoYes, but it's hard to do your own layout on the web because in times that want to width of an element that has text with `flex: 0`, you can't do that. It's mainly useful for things like this where you control everything.