You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I built the example program example_emscripten_wgpu without any issue.
When I load it in my browser (Chrome), I noticed that as the window gets resized the ratio is not preserved, thus leading to a situation like this screenshot
Obviously this is an extreme scenario, but the reason why I am reporting it is because the first time I opened it in my browser, my browser was not 1280x720 and as a result, the text/font looked really bad. So it seems that something was broken with the build or rendering. Also, it is not really easy to make the browser window exactly 1280x720 to have no artifacts due to stretching.
Note that I cannot copy/paste the build info because "Copy to clipboard" does not seem to work in this environment.
It is the latest commit on the docking branch 83c433682883aaa6f9583a4a84d1ae4bd8d1e977 built on macOS (13.5.2) with emscripten
I built the example program
example_emscripten_wgpu
without any issue.When I load it in my browser (Chrome), I noticed that as the window gets resized the ratio is not preserved, thus leading to a situation like this screenshot
Obviously this is an extreme scenario, but the reason why I am reporting it is because the first time I opened it in my browser, my browser was not 1280x720 and as a result, the text/font looked really bad. So it seems that something was broken with the build or rendering. Also, it is not really easy to make the browser window exactly 1280x720 to have no artifacts due to stretching.
Note that I cannot copy/paste the build info because "Copy to clipboard" does not seem to work in this environment.
It is the latest commit on the docking branch
83c433682883aaa6f9583a4a84d1ae4bd8d1e977
built on macOS (13.5.2) with emscriptenThis is the "about" window, with a more "normal" size, yet the font rendering does not look very good.
The text was updated successfully, but these errors were encountered: