Bonjour à tous, Suite au passage récent de notre instance sur la version v2026.6 de Discourse, nous rencontrons un problème inattendu avec le template Foundation que nous utilisons. Nous avons procédé à plusieurs vérifications de notre côté (tests de base, inspection des logs, désactivation d’autres composants, vérification des palettes de couleurs), mais à ce stade, nous n’avons pas réussi à identifier l’origine exacte du problème ni à trouver une solution pour le corriger. Est-ce que certains d’entre vous ont rencontré des soucis similaires avec ce template depuis cette mise à jour ? Auriez-vous des pistes d’investigation, des changements spécifiques dans le core de la v2026.6 à pointer du doigt, ou des suggestions à nous proposer ? Toute aide ou idée sera la bienvenue. Merci d’avance pour vos retours ! Avant la mise à jour : [Capture d’écran 2026-07-30 à 09.24.10] Après : [Capture d’écran 2026-07-30 à 09.25.44]

There is an upcoming change Modernizing the Foundation theme which is probably enabled by default now. I think right now you can still revert the changes by navigating to /admin/config/upcoming-changes and selecting “no one” for this change. [Screenshot_20260827_090343_Firefox] But once the change becomes permanent that won’t work anymore. Then you would need a custom theme component that overrides the new default.

Bonjour à vous deux, Je vous remercie pour ces premiers retours. @NateDhaliwal 1 - Un espace s’est ajouté au dessus et en dessous de la barre de recherche 2 - La police d’écriture qui est en bold est passée en semi bold 3 - Le texte dispose de moins de constraste, avec un léger flou qui est apparût. [Capture d’écran 2026-08-27 à 10.38.31]

[image] FabienL: 3 - The text has less contrast, with a slight blur that has appeared. This can be changed by adding this to your theme’s CSS: body { --webkit-font-smoothing: auto; } There’s some detail about what this does here: A Modern CSS Reset • Josh W. Comeau… In macOS Mojave, released in 2018, Apple disabled subpixel antialiasing across the operating system. I’m guessing they realized that it was doing more harm than good on modern hardware. Confusingly, macOS browsers like Chrome and Safari still use subpixel antialiasing by default. We need to explicitly turn it off, by setting -webkit-font-smoothing to antialiased. To demonstrate the difference… --webkit-font-smoothing: auto; on the left, and --webkit-font-smoothing: antialiased; on the right [image] [image] macOS renders text heavier by default, but only in browsers and not the rest of the OS… antialiased gets it closer in appearance to how text is rendered in other operating systems… in Chrome on Windows the CSS doesn’t apply and the text looks like this by default: [image] It’s debatable whether or not it’s worth adding as a reset like we are with this change… it technically makes fonts lighter on macOS which looks closer to other operating systems, but the mechanism is different because they’re different text rendering engines. Windows, while similarly light after applying this change for macOS, will still render fonts slightly sharper because of the engine differences (Windows does subpixel antialiasing, which is what gets turned off by this CSS on macOS).

Compatibility issue with the Foundation template (v2026.6)

Product Support

NateDhaliwal (Nate Dhaliwal) August 27, 2026, 7:39am 3

What are some problems or differences that you are having trouble with?

Topic		Replies	Views
Probleme d'affiche dans le topic depuis la derniere mise a jour UX fixed	8	313	June 23, 2026
Modernizing the Foundation theme Announcements	96	5990	August 6, 2026
Theme font size gets smaller due to hosted instance updates? UX	2	202	May 2, 2026
Why did our home page topic links font shrink? Product Support	7	284	June 1, 2026
刚才rebuild更新后，首页字体变的很小 UX foundation-theme	19	782	June 9, 2026

Compatibility issue with the Foundation template (v2026.6)

Related topics