4 ms·
Pages from the very origin of the internet back in 1992 still work perfectly fine today Yeah, but none of my <marquee> tags work. Which is funny, because that
by jballanc 15y ago
Pages from the very origin of the internet back in 1992 still work perfectly fine today
Yeah, but none of my <marquee> tags work. Which is funny, because that was also a non-standard, browser-specific feature. If that element had been standardized, but as <marquis>, then those pages would still break.
How about doing things correctly to start with?
I thought that's what we were advocating? Using vendor specific prefixes is the same as using a non-standard tag: it will likely break, and will almost definitely not work on multiple platforms. That doesn't seem to me, though, to be an argument against them.
If you want to complain that the standardization process is too slow, and thus people are used to continue using vendor-prefixed tags longer than they should, I'll be right beside you yelling about it. But the solution, it seems to me, isn't to "break" or abolish vendor prefixes. If you want to speed up the standardization process, do what the WHATWG did.