| 12:02 pm on Jul 10, 2012 (gmt 0)|
something like this might work:
| 12:12 pm on Jul 10, 2012 (gmt 0)|
HTML5 allows the id attribute to be set on the <html> element, HTML4 didn't (but this rule doesn't affect parsing in browsers). So this is valid HTML5 code:
| 1:17 pm on Jul 10, 2012 (gmt 0)|
|HTML5 allows the id attribute to be set on the <html> element |
But with JS, because it actions in the client browser, and because it runs between the head tags, wouldn't the opportunity to modify the html tag already have gone?
| 1:48 pm on Jul 10, 2012 (gmt 0)|
| 1:12 am on Jul 11, 2012 (gmt 0)|
| 5:15 am on Jul 11, 2012 (gmt 0)|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
without the usual "http://www.w3.org/TR/html4/loose.dtd" included.
| 1:34 pm on Jul 11, 2012 (gmt 0)|
What kind of plugin is this?
| 4:16 pm on Jul 11, 2012 (gmt 0)|
I imagine you know that half-doctype puts the document into Quirks mode. Be ready for other oddities in various browsers. :-)
| 5:53 pm on Jul 11, 2012 (gmt 0)|
Right, what rocknbil said. You're just asking for even worse problems by running in Quirks mode.
| 11:46 pm on Jul 11, 2012 (gmt 0)|
After further testing I now find that whereas the success of our handshake was dependent on doctype, the problem gets worse... browsers have become too unreliable. Before you could compensate for irregularities and those updates would be good for a couple of years. Now there is a danger of losing support within a month.
IE version is unlikely to change, but with Fool and Clown one could run a pool on guessing their version number available at the end of the year and there will not be many winners.
| 11:58 pm on Jul 11, 2012 (gmt 0)|
| 4:32 pm on Jul 12, 2012 (gmt 0)|
No. It's a proprietary plugin that is needed to demonstrate the issue, and demonstration requires licensing. Anyway, we are dropping that support feature as it won't be needed by the time our team releases an alternative product.