Very Html

what happened when manufactures started to create their versions of DHTML object model?

Browser manufactures started to create their versions of DHTML object model, which lead to some sites to not work correctly because of these manufactures using their own implantations, what happened as a result?

Public Comments

1. This article is informative http://ie.technion.ac.il/CC/Comp_news/xbdhtml.html It seems the idea is to utilize something called cross browser DHTML * shared support for Cascading Style Sheets, level 1 (CSS1) * shared support for Cascading Style Sheets Positioning (CSSP) * shared JavaScript support * Document Object Model functionality which is common to the two browsers * event model functionality which is common to the two browsers * downloadable font resources (also known as Dynamic Fonts) * full screen mode Fire fox seems to be the same as IE found in the article above.
2. I take it this is a homework question :-) The issue was that back in the day Microsoft Internet Explorer and Netscape Navigator(Now Mozilla) had different implementations of the DOM. It was virtually a race to add features to their browser to outdo the competitor. This meant that a browser could only render a page correctly if the coder implementing the dhtml used the right DOM representation for that browser. To make the site appear correctly on all browsers hacks were needed that checked the user's browser agent. This is why standardised DOM makes a web developers job easier. But even now, good web developers will check their pages on many different browsers.