However, nothing prevents them from innovating and following the standards process. Yes, sometimes browsers come up with good stuff that does get standardized eventually (XMLHttpRequest, Drag and Drop API, contentEditable, Web fonts, to mention a few). Believe it or not, those features were also welcomed with excitement back in the day. Their only difference is better PR, as we haven’t faced the consequences yet. Does this remind you of something? The proprietary features of today are no better than ActiveX and IE filters. As a result, browsers didn’t bother much with web standards. However, authors didn’t care, and were perfectly willing to embrace proprietary extensions. You might be surprised to hear that web standards did exist during the Browser Wars too. The reason we now have this convenience is web standards, hard won in the Browser Wars. If you have been in this field more than a few years, you surely remember that it wasn’t always like this. ![]() In our eagerness to use the new bling, we often forget how many people fought in the past decade to enable us to write code without forks and hacks and expect it to work interoperably. The shiny new toys dazzle us and we start promoting them too, contributing to the echo chamber. It’s important because it encourages certain vendors (*cough* Apple *cough*) to circumvent the standards process, implement whatever they come up with in WebKit, then evangelize it to developers as the best thing since sliced bread. The same issue has been reported on Macs running macOS Monterey.Brief books for people who make websites. The regular web page version should allow you to play the embedded video without any hiccups!
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |