Well it's a glaring omission then. The <title>O̴̡̾ͫ̈́̿̑ͤͣ̾͛́́̀͞͏̝̝̘̪̮̹̪͎͚̞̟̣̱̤̘̺͕̪H̅ͧ͛ͧ̾͒ͫ҉҉͉̳̘̭̫̯ͅÄ̵̸͙̩̱̝͙̱̫̜͙̰̻̝͕͉̭̮̖͖͇́̊ͮͩ̅̌̈́ͮͧ̀́͞I̡̞̗͈͙̠͓͉̯̝̮̲̮͕̣̭̪̾͛̅̉́ͅ </title> may not be ASCII so the encoding RFC:MUST be known before parsing any content including other meta tags which might have encoded attributes. You have to know the encoding, and you have have to know it first, not after mish-mashing things together and guessing and hoping and blaming the spec. :P
And the obvious rebuttal will be Content-Type. Yes, it is necessary to be there and correctly agree but after a file is downloaded or opened locally, there are no server headers. The <meta/> should be there and has to be first to be perfectly robust.
In reply to Re^4: Ordering meta tags with HTML::Element
by Your Mother
in thread Ordering meta tags with HTML::Element
by HeadScratcher
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |