Matt Kane

Hi. Can you confirm whether this issue is still present?

Both should work correctly, with no warnings. `fetchpriority` works in 18.2.0. Adding support for `fetchPriority` shouldn't have broken the previously-supported casing, but seems to have done so.

I mean the warning. It warns when previously it didn't complain. I think this would count as a breaking change. It renders fine in both cases, so the warning isn't...

_Are_ you planning to remove support? I'm not clear on the policy there: is the plan to only support DOM properties and not HTML attributes?

Is there any reason to not treat them as extra variants that are both supported (like Preact does), and not warn about either? One is the HTML attribute and the...

I wish there was a way to feature-detect for it though. A warning is fine for end users, but those of us building libraries will need to support both. Granted,...

I think this will be fixed by #473

@AustinLeeGordon your fix should be fine. Yes, it's a good idea to try to filter them like that. I will open an issue. The trouble is that Gatsby doesn't provide...

Great! Could you also try it with `netlify serve`?

Great! I'd say let's go ahead an update the package.json and [plugins.json](https://github.com/netlify/plugins/blob/main/site/plugins.json#L651)