fix(ui): Image scaling tweaks for sharper pixels#339
Open
Conversation
saves 50kb of js
portal webkit can't upscale cleanly, so introduce "big" versions of images that are point upscaled for clean pixels. also tweak layout to always display at native rather than up/downscaling.
48 and 96 are actually used pretty extensively in the portal interface
they really are quite poor sometimes
Contributor
But I like putting |
suprstarrd
approved these changes
Feb 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resolves #XXX
Changes:
General improvements to image scaling and handling.
image-renderingand thus always uses blurry filtering. For most of our images - especially paintings - this is terrible. Instead, 2x them serverside (so paintings become 640px) and tweak the portal layout to display them 1:1 at that size.We've stacked up a few changes to image rendering, but the frontend still has to support all the legacy options. If these quality settings sit well with the users, we may want to consider doing a bulk migration of the historical post attachments and replacing them on the CDN. Then we can assume all the formats we want are there and don't need to worry about fallbacks.
Filed as a draft against a work branch for early review and to get the right diff, can change base to
devonce #332 lands.