AOL Moving to Gecko

Monday March 11th, 2002

Newsforge, and others are reporting that the AOL client will use Gecko, starting with the next major release, 8.0. Along with that, the story talked about AOL's departure from any server platform that isn't linux, and AOL's plans to release a standalone linux client (there aren't any).

This has long been the rumor, and many felt until AOL started using Gecko, it would be hard to get sites to stop using proprietary IE code. This may be the kick in the pants that's needed to help get major sites to allow non-Microsoft browsers access to all of their content.

#44 Re: Re: Re: Because is not only a standard

by strauss

Tuesday March 12th, 2002 3:47 PM

You are replying to this message

Um, it's not a question of supporting layers. Those are supported, regardless. It's just a matter of the language and DOM construct used to access them. My twenty hour estimate is based on the legacy document.layers construct being a synonym for the new "standard" (i.e., endorsed by the MIT Computer Science Department, alias the W3C) construct. If that's not true then the estimate goes up. Certainly a shadowed implementation such as you suggest would be a burden, while a simple JavaScript/DOM synonym would be almost no problem at all. I haven't seen any specific argument as to why more than a synonym is needed and it's possible there are complicating factors that haven't been brought up here. The argument that's been made up until now isn't that it would be hard but that it would corrupt the purity of standards -- a pretty insubstantial argument given Mozilla support for non-standard constructs such as the horrifying innerHTML, and the pragmatic need to support the sites and applications that actually exist in the real world.