HI,
actually this happened even before my recent install of Leap 15.3 (that is, in previous Leap 15.2 that I used before on the same computer).
Anyway, here’s my little problem:
when I visit last.fm pages there are parts of the pages where small caps i is displayed as high caps I (I expect it can’t simply be small caps L, right ?)
Hopefully, this is more clear, and visible in this capture:
https://imgur.com/0aDjyfi
As seen, it happens only on parts where entities are bold (namely, song titles as seen in the capture); artist names where font is not bold, seems to be displayed properly.
Since some time (November 2020, to be more precise) last.fm decided to switch their main fond from Open Sans to Barlow.
And after some time it started to behave like this for me.
Usually I’m working with Chrome browser, but I tried this and it happens with every other browser I tried (Firefox, Opera, and Chromium).
On the other hand, it does not behave like this on other computers (Windows or Linux) where I’ve tried to compare.
Even on my computer where I have this issue, if I try to boot the DVD with Knoppix for instance, it does display OK.
So I believe there is something related only to this combination: from Opensuse Leap 15.3 (and previously from Leap 15.2).
There is even something more strange about this: for a very very short time (split of a second, really) when trying to display a page at last.fm site, it appears taht the i is displayed OK, but immediately is “turned” into this I instead. Sorry, I’m not able to capture this on some video to be more clear about it.
It bother me mostly on my user page on last.fm, but this happens also on just about any page, for instance on that artist\s page: https://www.last.fm/music/Thea+Gilmore
Anyway, does this happen to anyone else trying to display anything on last.fm ?
Is there anything I can investigate/change on my system in order to overcome this problem ? That is, besides installing some addon on Chrome, like Font Changer, and pick some other font (I tried this when I ws on Leap 15.2, and indeed issue is avoided in this way, but frankly I don’t like this sort of solving of this problem, I prefer to not have that addon on my browser).
Thanks.