231642 2021-10-12 16:02:38 -0700 imported/w3c/web-platform-tests/content-security-policy/unsafe-hashes/javascript_src_allowed-href_blank.html timing out 2022-05-16 08:50:33 -0700 1 1 1 Unclassified WebKit WebKit Misc. WebKit Nightly Build Unspecified Unspecified NEW InRadar P2 Normal --- 1 katherine_cheney webkit-unassigned justas543 webkit-bug-importer oldest_to_newest 1803514 0 katherine_cheney 2021-10-12 16:02:38 -0700 Timing out with the error: null is not an object (evaluating 'opener.t1') 1806389 1 webkit-bug-importer 2021-10-19 16:03:32 -0700 <rdar://problem/84437936> 1869084 2 justas543 2022-05-15 10:41:23 -0700 Without unsafe-hashes CSP option, loading fonts in non blocking way while keeping up with CSP is not possible. https://css-tricks.com/how-to-load-fonts-in-a-way-that-fights-fout-and-makes-lighthouse-happy/#aa-the-optimal-way-to-load-fonts <!-- We use the full link to the CSS file in the rest of the tags --> <link rel="preload" as="style" href="https://fonts.googleapis.com/css2?family=Merriweather&display=swap" /> <link rel="stylesheet" href="https://fonts.googleapis.com/css2?family=Merriweather&display=swap" media="print" onload="this.media='all'" /> 1869239 3 katherine_cheney 2022-05-16 08:50:33 -0700 (In reply to justas543 from comment #2) > Without unsafe-hashes CSP option, loading fonts in non blocking way while > keeping up with CSP is not possible. > > https://css-tricks.com/how-to-load-fonts-in-a-way-that-fights-fout-and-makes- > lighthouse-happy/#aa-the-optimal-way-to-load-fonts > > <!-- We use the full link to the CSS file in the rest of the tags --> > <link rel="preload" > as="style" > > href="https://fonts.googleapis.com/css2?family=Merriweather&display=swap" /> > > <link rel="stylesheet" > > href="https://fonts.googleapis.com/css2?family=Merriweather&display=swap" > media="print" onload="this.media='all'" /> Hi! We added support for unsafe-hashes in Safari 15.4 (https://developer.apple.com/documentation/safari-release-notes/safari-15_4-release-notes). If you're experiencing unexpected behavior, could you file a separate bug on bugs.webkit.org about it? This particular bug tracks a failing test and is not the best place to handle a different issue. Thanks!