You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Windows 8.1
Chrome Version 84.0.4147.125 (Official Build) (64-bit)
Webhint online scanner running Webhint version 6.0.7
Website scanned; https://thomasbrodhead.com
Preload elements referencing locally hosted resources that make use of the <base> path element are not recognized. For example:
hint #1: Could not be fetched.
https://thomasbrodhead … Cabin-Bold-700.woff2
<link rel="preload" href="fonts/Cabin-Bold-700.woff2" as="font" type="font/woff2" crossorigin="anonymous">
10 hints are triggered for locally hosted font resources. The common denominator is that they make use of the element in the <head>:
<base href="https://thomasbrodhead.com/">
The text was updated successfully, but these errors were encountered:
tmb-github
changed the title
[Bug] Bug description
[Bug] Preload LINK elements to locally hosted resources making use of BASE element not recognized by scanner
Aug 13, 2020
Looks like this is only affecting @hint/hint-http-compression so it should repro on the webhint CLI as well (but not the browser extension which excludes this hint due to API limitations). Unlike most hints this one tries to manually re-request resources using a variety of different headers to test server configuration. I haven't had a chance to dig deeper yet so I'm not sure if it's specifically a problem with the <base> element (which seems likely), but will share once I know more.
Windows 8.1
Chrome Version 84.0.4147.125 (Official Build) (64-bit)
Webhint online scanner running Webhint version 6.0.7
Website scanned; https://thomasbrodhead.com
Preload elements referencing locally hosted resources that make use of the
<base>
path element are not recognized. For example:10 hints are triggered for locally hosted font resources. The common denominator is that they make use of the element in the
<head>
:<base href="https://thomasbrodhead.com/">
The text was updated successfully, but these errors were encountered: