Many sources, such as OpenJS WebHint, encourage you to set <meta http-equiv="x-ua-compatible" content="ie=edge">, to in turn cause Microsoft Edge to use its "highest rendering mode." The standards would have you set <meta http-equiv="content-type" content="text/html; charset=utf-8"> instead.
Shaman, sit with me, and tell me the story of the long long ago, when bad programmers sought to manage every browser engine, and in the two thousand eleven times, when the moon hung low in the sky, how they battled the Beast of Many Equivalences, and had to forge a mighty browser which could be IE5 and IE6 and IE8 and Edge1 and Edge3 at the same time. Let us sing the blood tears of our ancestors.
"No!" shouts the mighty warrior. "Fuck that! I have better shit to do!"
And so, the three wisdoms of the True Gods were each born anew in him:
Take from your soul any tool which does not work in browsers a decade past, for lo, everything you needed was there, and those roads are all walked by the ancestors, and well known
Ignore the heathens who play at the edges of CSS, for grid performance is bullshit, and you will regret not just using absolute and fixed
Declare the thing standards mode already, for these rules are governed in stone, and Thou Shalt Not Be Concerned With Brave, Amen. If thou shalt actually give a shit, use resets instead, for they grow linearly, not cominatorically.
Wait until someone actually has that problem before solving that problem, because this causes more problems than it solves in practice
Yes. The devil will sit on your shoulder and tell you "it's just one tag, and you can ignore it afterwards."
Maintenance by thy devil's name. Kill it before it spreads.
StoneCypher
commented
10 months ago
Many sources, such as OpenJS WebHint, encourage you to set
<meta http-equiv="x-ua-compatible" content="ie=edge">, to in turn causeMicrosoft Edgeto use its "highest rendering mode." The standards would have you set<meta http-equiv="content-type" content="text/html; charset=utf-8">instead.Shaman, sit with me, and tell me the story of the long long ago, when bad programmers sought to manage every browser engine, and in the two thousand eleven times, when the moon hung low in the sky, how they battled the Beast of Many Equivalences, and had to forge a mighty browser which could be IE5 and IE6 and IE8 and Edge1 and Edge3 at the same time. Let us sing the blood tears of our ancestors.
"No!" shouts the mighty warrior. "Fuck that! I have better shit to do!"
And so, the three wisdoms of the True Gods were each born anew in him:
Wait until someone actually has that problem before solving that problem, because this causes more problems than it solves in practice
Yes. The devil will sit on your shoulder and tell you "it's just one tag, and you can ignore it afterwards."
Maintenance by thy devil's name. Kill it before it spreads.