[Dynapi-Dev] [Bug #128155] Overriding setHTML method in sub class of DynLayer problem

[<no...@so...>]

Bug #128155, was updated on 2001-Jan-09 03:49
Here is a current snapshot of the bug.

Project: DynAPI 2
Category: Core API
Status: Closed
Resolution: Wont Fix
Bug Group: None
Priority: 5
Submitted by: camhart
Assigned to : dcpascal
Summary: Overriding setHTML method in sub class of DynLayer problem

Details: I've made a widget that is a sub class of DynLayer. This widget
overrides the behaviour of setHTML so that a call to setHTML changes the
HTML of a child layer of the widget, rather than the widget itself. This is
causing the Layer creation to break in IE5 and Mozilla (but not NS4)
presumably because when DynLayer calls setHTML during layer creation in
createElement, it been replaced with my method. NS4 is not using setHTML in
createElement.

This is only a bug if you think people should be allowed to override the
setHTML method when creating sub classes of dynlayer.

However this did used to work in earlier versions of the API.

The line that causes this to break is line 91 in dynlayer.js:

dlyr.setHTML(dlyr.getInnerHTML(),false);

Follow-Ups:

Date: 2001-Jan-12 11:15
By: dcpascal

Comment:
Not a real bug, it's upto the widget developer to do a check for the 
this.created  flag.. if it's not set, then call the original DynLayer's
setHTML()


-------------------------------------------------------

For detailed info, follow this link:
http://sourceforge.net/bugs/?func=detailbug&bug_id=128155&group_id=5757