applyXSLTransform is too eager

applyXSLTransform is too eager

There's nothing that stops ProcessingInstruction from applying XSL Transforms
to HTML documents or from applying incompletely loaded XSL Transforms. This CL
adds a couple checks to avoid these cases.

The XSL Transform system is a bundle of insanity. So much of the system makes
so little sense it's hard to know where to start fixing it. Eric Seidel's
opinion is that we shouldn't drive the XSL transform process from style
resolution. Instead, we should kick off the transform either from
DOMContentLoaded or from the XSL sheet's load event. We tried a couple
approaches along those lines, but we didn't finish them for this CL. Maybe
we'll get that working for a future CL.

R=eseidel
BUG=260105
Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=155043

[eseidel, 2013-07-26 23:11:34]

lgtm

Bleh.

[commit-bot: I haz the power, 2013-07-26 23:12:44]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/abarth@chromium.org/20856002/1

[commit-bot: I haz the power, 2013-07-27 02:45:47]

Change committed as 155043