3

It looks like a release today changed the default font to New Times Roman:

Looking deeper, it looks like this CSS variable is to blame, at least in Firefox &#39 appears to invalidate the font-family rule, defaulting to the browser default of serif (aka, New Times Roman).

:root {
  --font-main: system-ui, sans-serif, 'Apple Color Emoji', 'Segoe UI Emoji', 'Segoe UI Symbol', 'Noto Color Emoji';
  --search-result-gap: 24px;
}

    Hi,

    What version of Firefox are you using & what operating system?
    We do not have that character sequence in our files, so I am not sure where it is coming from and it does not happen for me.

    Does it happen in other browsers too?

      Do you have custom css enabled?
      That is the only thing I can think of, since we just recently in the latest deploy allowed custom css to be used on assistant.

      I believe we found an escaping issue with this, so we will take a look at that and get that fixed.

        pixel Yes, that's it!

        I didn't even think about disabling custom CSS.

          For completeness, this is my custom CSS:

          /* Remove bottom border from links */
          .__sri_title_link._0_sri_title_link._0_URL {
            border-bottom-color: transparent;
          }
          
          /* Remove underline with nested links */
          .__srgi-title a {
          border-bottom: none; var(--result-item-title-border);
          }
          
          /* Remove underline with News module */
          .newsResultItem .newsResultHeader .newsResultTitle a._0_TITLE {
            border-bottom: none; var(--result-item-title-border);
          }
          
          /* Remove underline from links in Wikipedia module */
          .wikipediaResult a {
            border-bottom: none; var(--result-item-title-border);
          }
          
          :root {
            --font-main: system-ui, sans-serif, 'Apple Color Emoji', 'Segoe UI Emoji', 'Segoe UI Symbol', 'Noto Color Emoji';
            --search-result-gap: 24px;
          }
          
          @media (prefers-color-scheme: light) {
            :root {
              --search-result-title: #1a0dab;
              --search-result-content-text: #000000;
              --header-bg: #fff;
              --color-primary_hover: #595959;
            }
          }
          
          /* Remove Dogo */
          .doggo_sit_a {
            display: none;
          }
          
          /* Remove Shadow */
          .search-form .search-input-container {
            box-shadow: none;
          }
          
          /* Restore Underlining of title links */
          .__sri_title_link._0_sri_title_link._0_URL:hover {
            border-bottom-color: var(--result-item-title-border_hover);
          }
          
          /* Improve styling of search corrections */
          .correctedQuery {
              margin-top: 0.8rem;
          }
          .correctedQuery>.original {
              margin-top: 0.2rem;
          }
          .correctedQuery>.original>a {
              text-decoration: underline;
          }

            @silvenga Thanks for confirming! We've queued a fix for this; I don't have an exact timeframe but should go out sometime before EOD tomorrow, if not sooner.

            15 days later
            No one is typing