Skip to content

Commit 967431c

Browse files
chore(elements.d.ts): add "Accept-CH" as valid value for http-equiv (#16671)
* chore(elements.d.ts): add "Accept-CH" as valid value for `http-equiv` It seems like this is a valid value and it has been working for me, however I did find conflicting information on whether it is supported or not. Supporting Evidence: - https://github.com/WICG/client-hints-infrastructure?tab=readme-ov-file#opt-in-mechanism - https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/Client_hints#overview - https://developer.chrome.com/docs/privacy-security/user-agent-client-hints#introducing_the_new_user-agent_client_hints - httpwg/http-extensions#189 Conflicting Evidence: - https://html.spec.whatwg.org/multipage/semantics.html#attr-meta-http-equiv * changeset --------- Co-authored-by: Rich Harris <[email protected]>
1 parent 0348b4a commit 967431c

File tree

2 files changed

+6
-0
lines changed

2 files changed

+6
-0
lines changed

.changeset/thick-books-fail.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
---
2+
"svelte": patch
3+
---
4+
5+
fix: add "Accept-CH" as valid value for `http-equiv`

packages/svelte/elements.d.ts

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1268,6 +1268,7 @@ export interface HTMLMetaAttributes extends HTMLAttributes<HTMLMetaElement> {
12681268
charset?: string | undefined | null;
12691269
content?: string | undefined | null;
12701270
'http-equiv'?:
1271+
| 'accept-ch'
12711272
| 'content-security-policy'
12721273
| 'content-type'
12731274
| 'default-style'

0 commit comments

Comments
 (0)