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
Encountering red squiggles on fetchpriority, even though it's a valid attribute
It's annoying in this context because there's no way to suppress the error without applying // @ts-nocheck to the whole file (please correct me if I'm wrong)
<svelte:head>
<scriptsrc="https://challenges.cloudflare.com/turnstile/v0/api.js?render=explicit"asyncon:load={() => {
script_loaded=true;
}}
fetchpriority="low"></script>
<!-- ^^^^^^^^^^^^^^ Object literal may only specify known properties, and '"fetchpriority"' does not exist in type 'HTMLProps<"script", HTMLAttributes<any>>'.js(2353) -->
</svelte:head>
Describe the proposed solution
Add type support for the fetchpriority attribute on HTMLScriptElement. May as well add it for HTMLLinkElement while we are in the space too.
(Support for HTMLImageElement was already added here)
Describe the problem
Encountering red squiggles on fetchpriority, even though it's a valid attribute
It's annoying in this context because there's no way to suppress the error without applying
// @ts-nocheck
to the whole file (please correct me if I'm wrong)Describe the proposed solution
Add type support for the
fetchpriority
attribute onHTMLScriptElement
. May as well add it forHTMLLinkElement
while we are in the space too.(Support for
HTMLImageElement
was already added here)Browser support is solid, except for FireFox 🙂
Importance
nice to have
The text was updated successfully, but these errors were encountered: