|February 22nd, 2013|
|html, tech [html]|
HTML parsing is not possible with regular expressions, since it depends on matching the opening and the closing tag. Regular expressions can only match regular languages but HTML is a context-free language.This is true, but only in a sense so narrow it's useless. When someone asks about "regular expressions" they don't mean the restricted computer science kind but the implementations available in various programming languages. Those are much more powerful, capable of parsing HTML.
Here again we're using dangerously precise words. When someone says "HTML" they don't mean HTML as defined by the spec but HTML that they are likely to encounter in the real world. Which means you might need to handle monstrosities like "<i>italic <b>bold-italic</i> bold</b>" which have no parse tree but your browser still renders as italic bold-italic bold. 
But again with the precision! For typical tasks you don't need to 'parse' HTML, just extract some information from it. Regular expressions and other ad-hoc techniques can do that well and are likely to be less trouble in practice  than trying to use a parser.
(Because mod_pagespeed needs to make context-dependent changes to arbitrary web pages, regular expressions are not a good fit. You might think using the parsing code from a web browser would work well, but it turns out that browsers mix HTML-parsing with HTML-cleanup . So pagespeed instead goes token-by-token, triggering callbacks for start and end tags.)
 Webkit turns <i>italic <b>bold-italic</i> bold</b> into <i>italic <b>bold-italic</b></i> <b>bold</b> at an early stage of interpreting the page.
 The advice to use an XML parser is just bad, as funny as the author is. XML parsers get to assume they're only going to be given valid XML and just reject anything that isn't. Extremely few pages are (or even try to be) XML, so your XML parser isn't going to be helpful.