-
Notifications
You must be signed in to change notification settings - Fork 47.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: support fetchPriority
in camel-case on DOM nodes.
#27233
Labels
Status: Unconfirmed
A potential issue that we haven't yet confirmed as a bug
Comments
fmacherey
added
the
Status: Unconfirmed
A potential issue that we haven't yet confirmed as a bug
label
Aug 15, 2023
4 tasks
Still an issue... |
Fixed in #25927 which is part of the Canary and Experimental release channel. Types were already added. |
Is the fix planned for React 18.x.x? |
No. It will be part of React 19 and is already available in the React 19 RC ( |
2 tasks
There are no plans for any backports at the moment. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At the moment, the HTML fetchPriority is only supported written as
fetchpriority
, see #26810But as per DefinitelyTyped/DefinitelyTyped#65972 it is required in
@types/react
to be written asfetchPriority
as it is also for other props e.g.imageSrcSet
.With spelling it as camel-case, react ejects a warning:
Relevant versions:
Steps To Reproduce
Example component:
The text was updated successfully, but these errors were encountered: