??????????????
<br />
<b>Warning</b>:  Cannot modify header information - headers already sent by (output started at /home/mybf1/public_html/class.bf1.my/wp-includes/js/dist/index.php:4) in <b>/home/mybf1/public_html/class.bf1.my/wp-includes/js/dist/index.php</b> on line <b>173</b><br />
<br />
<b>Warning</b>:  Cannot modify header information - headers already sent by (output started at /home/mybf1/public_html/class.bf1.my/wp-includes/js/dist/index.php:4) in <b>/home/mybf1/public_html/class.bf1.my/wp-includes/js/dist/index.php</b> on line <b>174</b><br />
<br />
<b>Warning</b>:  Cannot modify header information - headers already sent by (output started at /home/mybf1/public_html/class.bf1.my/wp-includes/js/dist/index.php:4) in <b>/home/mybf1/public_html/class.bf1.my/wp-includes/js/dist/index.php</b> on line <b>175</b><br />
<br />
<b>Warning</b>:  Cannot modify header information - headers already sent by (output started at /home/mybf1/public_html/class.bf1.my/wp-includes/js/dist/index.php:4) in <b>/home/mybf1/public_html/class.bf1.my/wp-includes/js/dist/index.php</b> on line <b>176</b><br />
<br />
<b>Warning</b>:  Cannot modify header information - headers already sent by (output started at /home/mybf1/public_html/class.bf1.my/wp-includes/js/dist/index.php:4) in <b>/home/mybf1/public_html/class.bf1.my/wp-includes/js/dist/index.php</b> on line <b>177</b><br />
<br />
<b>Warning</b>:  Cannot modify header information - headers already sent by (output started at /home/mybf1/public_html/class.bf1.my/wp-includes/js/dist/index.php:4) in <b>/home/mybf1/public_html/class.bf1.my/wp-includes/js/dist/index.php</b> on line <b>178</b><br />
TODO
 - Check how we compare to the HTML5 parsing rules
 - limit the length of markup elements that never end.   Perhaps by
   configurable limits on the length that markup can have and still
   be recognized.  Report stuff as 'text' when this happens?
 - remove 255 char limit on literal argspec strings
 - implement backslash escapes in literal argspec string
 - <![%app1;[...]]> (parameter entities)
 - make literal tags configurable.  The current list is hardcoded
   to be "script", "style", "title", "iframe", "textarea", "xmp",
   and "plaintext".


SGML FEATURES WE WILL PROBABLY IGNORE FOREVER
 - Empty tags: <> </>  (repeat previous start tag)
 - <foo<bar>  (same as <foo><bar>)
 - NET tags <name/.../
 

MINOR "BUGS" (alias FEATURES)
 - no way to clear "boolean_attribute_value".
 - <style> and <script> do not end with the first "</".


MSIE bug compatibility
 - recognize server side includes as comments; <% ... %>
   if no matching %> found tread "<% ..." as text
 - skip quoted strings when looking for PIC