This may look cool, but it should not become part of the API. IE sucks when it comes to manipulating links/images that are within a "layer". They don't have a separate structure for each layer in the same fashion as NS. For this reason, adding such code would result in EVERY link on a page, regardless of location being manipulated with each call to setHTML.
This code is only intended to be used for correctly sending mouse events to the required location and not for "ease of coding". I know this may seem a bit harsh, but we need to draw a hard line in the sand on what is NEEDED and what is NOT. Sorry : ) >From: "Doug Melvin" <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >Subject: [Dynapi-Dev] links.lyobj >Date: Tue, 4 Dec 2001 15:50:34 -0500 > >See below code (start's line 281 of dynlayer.js) >Under NS we iterate through all links of a newly populated layer >assigning each link a lyobj property.. >but we don't do this under Ie.. why? >I've found that this works under IE >this.lyobj.setVisible(false) is WAY better than >"top.area1.DynAPI.document.getAll['mylayer'].setVisible(false)' _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp _______________________________________________ Dynapi-Dev mailing list [EMAIL PROTECTED] http://www.mail-archive.com/dynapi-dev@lists.sourceforge.net/
