Web export: Support rendering at the display resolution

[NathanLovato]

It's all in the title. Currently, especially in the HTML5 version, the resolution is limited and users cannot choose it, but it'd be nice to render at the display resolution by default, (and see if people experience any performance issues). I have a 4k display and the text is always a bit blurry here, the max resolution seems locked.

As part of this issue I'd like to understand how/why the resolution works in the browser, what controls it.

[Razoric480]

I might be missing something. Where are we limiting the resolution? The window is resizable and the stretch mode is 2d, so it grows with.

[NathanLovato]

On the web, is it not locked to 1080p?

[Razoric480]

Oh, it's a bit weird about it.

If I F11, it opens to 1440p. Then if I F11 back to windowed, then double click the window bar to maximize, then un-maximize and F11 again, then it's 1080p. But if I F11 out of it and then F11 again, then it scales up to 1440p again.

[NathanLovato]

Right, of course it does something like that! :)

Actually, we had trouble making full screen toggle work reliably back in the day. This area could use a review today probably. I remember we had to move the full screen toggle outside of the app on the web with some weird logic to account for firefox's multiple fullscreen modes!

I don't know if today there is a built-in mechanism that works more reliably across browsers.

Regarding the resolution, the limitation was that at the time, the hardware rendering did not work 100% reliably on all devices if I recall correctly. The resolution was capped for performance reasons, but actually it hindered the experience of most other users as the text is not as sharp as a result.

If I recall correctly, the problem was specifically e.g. devices with retina displays, things like these.