Bug 502206

SUMMARY
The default when setting font settings from the system settings app will generate a .fonts.conf file with many MATCH tags for each condition. Since all of them are assigned to match target=font I thought I would clean up the file a bit and get rid of all the match tags except for one to make it easier to read/edit. What I have noticed is that the system does NOT like that. I was noticing colour-fringing in right-click menus and buttons, etc. that should have been greyscale.

STEPS TO REPRODUCE
1. Have a .fonts.conf file with many match tags (default) and one with only 1 match tag and all the conditions in it.

OBSERVED RESULT
With many match tags it will produce more or less the expected output. With one match tag it starts ignoring things and using subpixel with no lcd filter, etc. when the file is set to use greyscale. Basically it expects to receive only 1 condition so an assignment has to be done over and over.

EXPECTED RESULT
Output should look the same, whether it is many match tags in .fonts.conf or a single tag.

SOFTWARE/OS VERSIONS
Operating System: SteamOS 3.6.22 Build: 20250224.1
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.12


ADDITIONAL INFORMATION
To give an example of the formatting I am talking about, shouldn't the system interpret both of these layouts exactly the same because "font" is the same target?

 <match target="font">
  <edit name="lcdfilter" mode="assign">
   <const>lcdnone</const>
  </edit>
 </match>
 <match target="font">
  <edit name="rgba" mode="assign">
   <const>none</const>
  </edit>
 </match>

vs

 <match target="font">
  <edit name="lcdfilter" mode="assign">
   <const>lcdnone</const>
  </edit>
  <edit name="rgba" mode="assign">
   <const>none</const>
  </edit>
 </match>