§
bgColor: In pages inserted in DFrames the bgColor
attribute of the BODY tag is not recognized. Use instead the setContentBgColor
method of DFrame in the onLoadDFrame
function:
<HTML>
<HEAD>
<script>
function onLoadDFrame()
{thisDFrame.setContentBgColor('yellow')}
</script>
</HEAD>
…
Note: As ilayers
of Netscape are transparent you MUST set a contentBgColor in the pages inserted
in DFrames, either by the code above or by a contentBgColor in DFrame's Styles.
§
Documentation:
The documentation pages have
been made with Microsoft Word 2000 (not so bad … ) and include features that
are not well recognized by Netscape 4.x. We recommend you read this
documentation with Internet Explorer or Netscape 6.
§
If you read a
file containing dFrameAPI from the disk the reload is very slow. The delay becomes
correct if you , open a menu of Netscape while it is reloading (!). That does
not happen if you reload a page from a server.
§
The Style checker
does not work with Netscape 4.x
§ In some very rare circumstances using complicated code it can happend Netscape crashes. In this case inserting a
status = ''
statement in the code causing the crash can prevent it.
We used this workaround one time, in the billing
sample.
§
Scroll bars: If you use DynAPI scroll bars it can happen
in 2 cases that dFrameAPI does not know the correct size of document inserted
in DFrames:
o
The document is
big or built with a complex Javascript procedure and the resizing of scroll
bars is over before the document is completely built.
o
Some event
resizes the document. For instance hidden layers become visible.
If
this happens you must 'manually' resize
the scroll bars with the refreshScrollSize
method of the DFrame object.