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

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.