Honestly, I think that this is a bug and the Chrome team is just being lazy about it.
If the type wasn’t provided, I’d expect this behavior, but Chrome shouldn’t be allowing you to embed the wrong type w/ the same URL that the right type was hosted on before. That’s the issue here in my opinion.
The chromium devs have commented on their bug now, as the spec bug has been raised they’re probably going to look at fixing it once the spec has been finalised.
In both Firefox and Chrome they handle it differently, Safari seems to be the only one (from what I’ve tested, I didn’t test Edge or Opera!) that is very opinionated.
I hope from the conclusion you can see that my line of thinking shifted this way, but at the time I became so wrapped up in the excitement of it all that I thought I’d hit something!
Honestly, I think that this is a bug and the Chrome team is just being lazy about it.
If the
typewasn’t provided, I’d expect this behavior, but Chrome shouldn’t be allowing you to embed the wrong type w/ the same URL that the right type was hosted on before. That’s the issue here in my opinion.The chromium devs have commented on their bug now, as the spec bug has been raised they’re probably going to look at fixing it once the spec has been finalised.
In both Firefox and Chrome they handle it differently, Safari seems to be the only one (from what I’ve tested, I didn’t test Edge or Opera!) that is very opinionated.
Well that’s good news :)
I would assume Safari is more strict w embed anyway? I hope so anyway
Not sure whether I’d call it a security bug, but it’s definitely a bug. Thank you for filing it!
I hope from the conclusion you can see that my line of thinking shifted this way, but at the time I became so wrapped up in the excitement of it all that I thought I’d hit something!
Yeah, I can relate. Been there way too often :-)