.NET changing crossorigin/> to crossorigin=""/>

Question

I'm trying to preconnect to resources on my .aspx page.

My code:

<link rel="preconnect" href="https://vars.hotjar.com" crossorigin/>

Which .NET turns into

<link rel="preconnect" href="https://vars.hotjar.com" crossorigin=""/>

I've upgraded to VS2019, I'm pretty sure on past projects I've never had this problem so it may be a VS issue. Does anyone know how to bypass this change?

Thanks

The two expressions [are identical](https://developer.mozilla.org/en-US/docs/Web/HTML/CORS_settings_attributes). There's no problem — Panagiotis Kanavos, May 20 '19 at 12:52

Erik Šťastný · Answer 1 · 2019-05-20T12:53:18.643

2

Why do you want to bypass it? VS2019 is just correcting your typo to correct syntax

From term of functionality there is no difference.

edited May 20 '19 at 12:53

answered May 20 '19 at 12:49

Erik Šťastný

1,487
1
15
41

Because crossorigin="" isn't correct syntax, I don't think? No browser recommends crossorigin="". – MattHodson May 20 '19 at 12:50
If you do not use that key, why you want to specify it? – Erik Šťastný May 20 '19 at 12:51
@GerryHodson on the contrary, [crossorigin needs a value](https://developer.mozilla.org/en-US/docs/Web/HTML/CORS_settings_attributes). Omitting the value is the same as passing `""` – Panagiotis Kanavos May 20 '19 at 12:52
I've never added a value, check here: https://www.w3.org/TR/resource-hints/ – MattHodson May 20 '19 at 12:53

.NET changing crossorigin/> to crossorigin=""/>

1 Answers1