Thursday, October 8, 2020
1 change · master
Resolved issues and error corrections
Website menu buttons now use the configured button font consistently, even when it matches the main text font. This makes header and mega menu styling more predictable for users customizing their website design, with a small possible change to plain text font styling inside navigation areas.
Original PR description
Since 13.0, the website menu can contain text and buttons through mega menus, which created inconsistencies on the way the "navbar font" configuration works. Indeed, when setting the "button font", navbar buttons were updated too... except if that "button font" was equal to the "text font", in that case those buttons used the "navbar font", so not logical at all. This commit solves the problem by only using the navbar font to style bootstrap nav links, which is the common content of mega menu snippets anyway but this has a side-effect: text-in-navbar font may change from navbar font to text font which is acceptable as the 14.0 was released very recently. Sorry for the inconvenience if any, but it felt important to fix the problem that way for the new static content of header templates. X-original-commit: 31bfb5075063070d24a607ed47da6bdd8207aa5a