3 ms·
I don't believe it's a quirk. Browsers are supposed treat tags they don't recognize basically the same as a <div> (or some other reasonable default presentation
by lolinder 6y ago
I don't believe it's a quirk. Browsers are supposed treat tags they don't recognize basically the same as a <div> (or some other reasonable default presentation). It's intentionally designed that way for forward compatibility. We rely on this behavior when we provide some content inside an <object> tag for browsers that don't support it.
- e111077 6y agoHTMLUnknownElement https://developer.mozilla.org/en-US/docs/Web/API/HTMLUnknownElement https://developer.mozilla.org/en-US/docs/Web/API/HTMLUnknown...
- runarberg 6y agoFun fact: <blink> is an HTMLUnknownElement. What GGGP did is essentially the same as: blink { animation: blink 1s steps(2, jump-none) infinite; } @keyframes blink { to { opacity: 0; } } Now when you write <blink> in your HTML you will essentially get an HTMLUnknownElement with the specific style of blinking every ½ second.
- dqv 6y agoI guess the other browsers caught up because I remember trying it in a few different browsers after doing it in Firefox and it only worked in Firefox.