iamlost - 12:18 am on Jul 23, 2005 (gmt 0)

I have been frustrated for years trying to fathom the IE backend thought processes. Thanks, once again, SuzyUK for a nice tidy explanation. hasLayout is certainly in the running for least mentioned/documented/understood Microsoft process.

My conclusion is that MSFT, being a software application company, always wanted an (interactive) application that browses. If not the only such application then the preferred one. Simple document request and display just wouldn't do.

The w3c works on consensus and consensus takes time. The w3c is open and open is level. Rather than wait and start even with everyone else IE jumped out first and fast. It is possible that they thought it would also allow them to set the rules by implemention. Also Microsoft applications are expected to be proprietary and that required their own DOM. Whatever, IE 4.0 implemented their Dynamic HTML (DHTML) Document Object Model rather than wait on the w3c Document Object Model (DOM).

If the w3c had caved, Opera not set a quality example, and Mozilla not been created this discussion would be moot. IE's way would be the only way. But. And so we have recommended standard behaviours and two (plus) browsers that largely meet them.

Attempts at reconciliating DHTML and DOM are, I think, behind hasLayout appearing in 5.5. IE 6 "standards mode" meant further changes to hasLayout. And that IE hoped would be enough. It hasn't been and isn't and the market is slipping away.

The big questions are:
* can IE truly reconcile the two DOMs?
* do they want reconciliation?
* if not, what will they do?

So far all I expect are improved security and tabbed browsing. I have heard nothing to expect DOM changes. It is very difficult to render the same exterior from differing skeletons. Sadly - from a designers perspective. Happily - from that of IE's competitors.