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.
#46 Re: Re: Re: Because is not only a standard
Tuesday March 12th, 2002 5:30 PM
You are replying to this message
Here's another page on the Netscape site worth consulting on this issue: <http://developer.netscape…dhtml-web-pages/#codefork> . As far as I can tell from that, there are very few things that need to be done on the browser side for compatibility:
1. Interpret the old LAYER tag as meaning a positioned DIV. 2. When someone calls "new Layer", interpret that as document.createElement. 3. When someone accesses document.elementID or document.layers["elementID"], interpret that as meaning document.getElementById("elementID"). 4. Return a non-null, non-false value for document.layers if accessed by itself.
There are some sites that this might break on, but I submit that it would work on the vast majority of them. If there's any significant bustage then it could probably be fixed by returning a real document.layers collection, which wouldn't be too hard, but might start to create some of the data structure shadowing overhead. I don't think it's required.
Sorry for the message bombing but it seemed like a good time to take this issue down to specifics.....