What Netscape Needs to Succeed
Monday October 26th, 1998
This week's editorial touches on four possible strategies Netscape could use to recover lost ground. I believe it is possible, but it won't happen without some serious introspection. Click Full Article to read more.
Update: Some of my opinion has come to fruition today, as you will see when you read the article...
#12 Re:What Netscape Needs to Succeed
by MozillaZine Admin <mozineAdmin@mozillazine.org>
Wednesday October 28th, 1998 12:30 PM
You are replying to this message
That functionality is currently in Mozilla and NGLayout. Remember, at the time of the release of Communicator 4 and IE4, there was no standard DOM spec. Microsoft already had in place technology that allowed the reflow of a page as new info came in (that's what allowed them to display a page's content early when images on the page lacked "height" and "width" attributes). They were able to leverage this technology to claim a lead in standards implementation (even though no DOM spec had been ratified).
If you were coding in DHTML for 4.0 browsers before the beginning of October of this year (when the DOM Level 1 spec was ratified), you should not fault Netscape for it's lack of incremental reflow. If you wanted compatibility based on standards, you should not have used DOM to accomplish it. Now that DOM has been recommended as a standard, you can hold the next generation browsers accountable to the spec. NGLayout should be more than able to appease your DHTML needs when it is finished.