Having worked on browser engines, I don't think this is a straightforward example of poor code. There are many optimizations that the complexity of the web platform means you have to disable in more complex conditions. (1/?)
I think I disagree, the party with the bug should fix it - in this case Edge failed to handle valid and reasonable markup correctly, but rather than fix it asked for other people to workaround the bug. The website *did* change to accommodate them, and you still see a problem. 
-
-
Edge handled the markup correctly, they just didn't optimizer it well. Here's a browser engineer saying why edge's optimization makes sense https://news.ycombinator.com/item?id=18703568 …
-
The original post seems to indicate that YouTube ignored them and gave no feedback. If this is false then it's fine. Of course it was eventually fixed, Google properties get redesigned every few months.
- 9 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.