@alciregi, I would if I knew that this were a bug, but I want to ensure that it’s not a common misconfiguration, etcetera.
Additionally, I’ve no particular reason to believe that it’s a downstream problem: I realise that, technically, for most packages, the report process is downstream, then upstream. However, RHBZ isn’t utilised like that in practice.
I intend to report it if I’ve no response here, though.
I looked at your GitHub report, but I don’t quite understand where you expect something different. Do you expect some of the texts of different size to be the same (pixel) size? Which ones?
You need hard arguments to convince upstream, and even then … Just saying “config move bug” …
@mjg, you reckon they didn’t have the heart to say that they couldn’t see what I was talking about? That would be as sad as it would be funny. Anyway, I think what you’re seeing is GitHub’s lossy bitmap compression, although it’s also difficult to see when it’s not 1:1 with the pixel grid, due to standard image viewers’ interpolators.
The context menu’s text is antialiased how I’ve defined in kcm_fonts, which all else adheres to (including NC’s configuration window), whereas flyout’s text is AA’d differently, such that it’s significantly more blurry than all else’s.
If you mean that I should convince them that it exists, hopefully, the undermentioned screenshot demonstrates that the pixel grid differs:
