If you haven't encountered this browser before, I find it fascinating. It's meant for devices that aren't necessarily computers. For example, someone making a digital "sign" can use HTML and CSS, or dynamic HTML motion graphics, to create their content, and run it in Flow. It doesn't have to be able to run, say, Google Docs. However, the developer wrote a blog post about getting Google Docs to run, by fixing the necessary bugs and adding the necessary features: https://www.ekioh.com/devblog/google-docs-in-a-clean-room-br... For example, Google Docs keeps the focus in a hidden iframe, apparently, and Flow wasn't firing the right series of events when the focus traveled between frames.
The way I look at it, for a custom "browser engine" whose goal is to let you use an independent implementation of the DOM to create graphics and UIs that render on the GPU of an embedded device, it's delightfully over-engineered.