From the Service Portal login page, use of custom fonts causes login button to attempt to download the custom font. - Known Error

From the Service Portal login page, use of custom fonts causes login button to attempt to download the custom font. Description Service Portal developers have been able to use custom fonts by either using CSS Include that links to hosted font or by using the @font-face CSS rule in a Style Sheet while hosting the fonts on the sys_attachment table. Both techniques are described in the following Community article: https://community.servicenow.com/community/develop/blog/2016/09/28/using-custom-fonts-in-service-portal Options 1 and 3 both work on all Service Portal pages except the login page. With option 1, the login button directs the user to the platform interface and shows the message below: The page you are looking for could not be found. %3Clink%20href="https:/fonts.googleapis.com/css?v=d86dcc954fbc0300cf005f388310c75a@99@family=Pacifico%22+rel%3D%22stylesheet%22%3E

With option 3, the login button downloads the font files hosted on the sys_attachments table.

Steps to Reproduce

In the Application navigator, navigate to Service Portal > CSS. Create a new Style Sheet called testBranding Paste in the following CSS rule and save the Style Sheet p, li, lo, dd, a, label, h3, h4, h5, h6, h1, h2{ font-family: "Pacifico", cursive; } Navigate to Service Portal > Portals. Take note of the theme being used for the OOB Service Portal. Open that theme. Create a new CSS Include. Name "testBranding", Source "Style Sheet", Style sheet "testBranding". Create another CSS Include. Name "PacificoFont", Source "URL", URL " https://fonts.googleapis.com/css?family=Pacifico " rel="stylesheet">" Browse to the Service Portal login page from a Chrome Incognito window. Enter login details and click the login button. Expected behavior: The custom font will render on the login page. The login button will login the user. Actual behavior: The custom font does render on the login page. The login button directs the user to the platform interface and shows the message below: The page you are looking for could not be found. %3Clink%20href="https:/fonts.googleapis.com/css?v=d86dcc954fbc0300cf005f388310c75a@99@family=Pacifico%22+rel%3D%22stylesheet%22%3E Workaround Community article - https://community.servicenow.com/community/develop/blog/2016/09/28/using-custom-fonts-in-service-portal

Option 1 has solution:

In step 7 mentioned in Steps to reproduce - Edit CSS Include which has Name "PacificoFont" Change Source "URL", from " https://fonts.googleapis.com/css?family=Pacifico " rel="stylesheet">" to " https://fonts.googleapis.com/css?family=Pacifico " This avoids the problem of redirect to "The page you are looking for could not be found" in platform Option 3 does not have any solution:

This is due to the nature of ServiceNow Platform it requires user to login to download attachment. As such, in SP Login page, since user has not yet log in, download of font attachment fails and it retires after user successfully log in. There is no workaround available.