This is a per-snap feature, snapd doesn't specifically modify any font
features, and we are working towards having as many snaps as possible
use snapcraft's configure hook which sets up a private font cache that
is per-snap and not shared. So if you find this is happening for a snap
which uses that configure hook, then we can add a snapcraft task here to
look into updating the configure hook there to support your config.
An example snap that uses that configure hook would be the chromium snap
on the stable channel, can you try installing that snap with
snap install chromium --stable
and then check if your fonts are configured the way you expect?
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916342
Title:
Sub-pixel anti-aliasing is not being applied to snaps
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1916342/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
