Got Subform layout solver working with custom React rendered on top of Pixi.js (WebGL)
CSS is dead, DOM is dead 
Yeah, if you run into anything while using the WASM engine just open an issue on github or topic on the forum.
-
-
Hope you don’t mind if I ask here. WASM engine doesn’t seem to recognize “hug” unit. Is it a recent addition?
-
Not implemented yet because I'm not sure what the API should be so that you can interop w/ text or other children that aren't sized by the engine itself. (In the app, Subform measures font metrics based on the exact string --- can't do that in WASM.)
-
And measuring font metrics cross-browser is a bit of a nightmare. Eg: you have to make sure all fonts have loaded — which, IIRC, is sometimes impossible — or your measurements might suddenly become invalid and your code won't know.

-
In my case Pixi is taking care of everything. Using bounding box of the text node should work fine. Gonna try it.
-
Yeah, totally. 99.99% of the time it won't happen, and when it does.. nobody will notice. A probably harmless Heisenbug, but a Heisenbug all the same (sigh, thanks browsers).
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
I like it so far. Also, it would be super helpful to have all layout props documented 