SitePoint Sponsor

User Tag List

Results 1 to 3 of 3
  1. #1
    What? Maelstrom's Avatar
    Join Date
    Oct 2001
    Whistler BC originally from Guelph Ontario
    0 Post(s)
    0 Thread(s)

    Problem with Netscape 6.0

    I am having a problem I hadn't encountered with IE and didn't even realize it was a problem till I upgraded.

    If in the head I have something like this

    function display(){

    and somewhere in the body I call this function


    in IE it works fine and inserts it into the body and does no new screen. With Netscape it clears the screen and only outputs what I ordered.

    Now I realize that that is what document.write but I thought that calling from within the body nullified that. This is a very cut down version as what I have done is actually an object I created to dynamically create a resume and then print it.

    Does anyone knw of a fix or am I screwed with the document.write command.

    Oh and I have though of using

    document.getElementById('idname').innerHTML += "add every piece of the code like so"

    Maelstrom Personal - Apparition Visions
    Development - PhP || Mysql || Zend || Devshed
    Unix - FreeBSD || FreeBsdForums || Man Pages
    They made me a sitepoint Mentor - Feel free to PM me or Email me and I will see if I can help.

  2. #2
    SitePoint Member
    Join Date
    Nov 2001
    Lexington, KY U.S.A.
    0 Post(s)
    0 Thread(s)
    This is from the js reference:

    Event handlers execute after the original document closes, so the write method implicitly opens a new document of mimeType text/html if you do not explicitly issue a method in the event handler.
    I couldn't even get IE to do this on my box.

    I did something similar to your dynamically created resume, but I used tons of layers---that doesn't work in NN 4.x either. What about multiple calls to the server and use PHP?


  3. #3
    JavaScript Guru (Big Ego) Arielladog's Avatar
    Join Date
    Jul 1999
    SC, USA
    0 Post(s)
    0 Thread(s)
    If the script executes while the <body> is loading, it should work fine. However, if it's after (or before), it won't work. The discrepency might be that Mozilla runs the code after <body> has loaded and IE does it while <body> is loading.

    Or, all of what I said could be BS It's just a hunch, though



Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts