You could generate a stylesheet with a stupid amount of generated breakpoints, or you could assume the user isn't going to resize the browser after loading the page. (Most won't, and if they do, the only consequence is non-ideal text wrapping).
You could generate a stylesheet with a stupid amount of generated breakpoints, or you could assume the user isn't going to resize the browser after loading the page. (Most won't, and if they do, the only consequence is non-ideal text wrapping).
The second problem is solvable though I think, by loading the JS text balancer asynchronously.
It can, yes. The response header `Accept-CH: Viewport-Width` suggest to the client that future request should transmit a `Viewport-Width: 320` header. Chrome only as the other browsers consider it harmful.
It doesn’t solve the problem, though. Font availability and subpixel rendering varies from OS to OS and browser to browser.
...oh, uh, no, that was dumb of me.
I do still wonder though if auto-generating a css file with lots of media queries would be feasible.