Topic awaiting preservation: NN4/Mac Resize Bug : How and Where To Include Fix?

If you still support Navigator 4.x for the Mac, then you probably know what I'm talking about -- it's the bug that destroys your CSS layouts on resizing a window.

Basically what I'm asking here is what kind of pages need the fix inserted in them?

I've already got a script to fix it, and I'd assume that if you put it on a frameset page, then you don't need to insert it into the frame pages as well, is that right?

My other questions are, if a popup window isn't opened as resizable, does it still need the script?

And are there any other pages you can ignore?

Last question: I made a JavaScript include file to include in my pages, both to cut file size and complexity (even thought it's only about .3K), and also to simplify updates in case I ever wanted to remove or change the actual code in it. Is this a good way to go (using an include file)?

[This message has been edited by viz (edited 10-18-2002).]

The poster has demanded we remove all his contributions, less he takes legal action.
We have done so.
Now Tyberius Prime expects him to start complaining that we removed his 'free speech' since this message will replace all of his posts, past and future.
Don't follow his example - seek real life help first.

Just out of curiousity, what kind of script have you found, then? I have been told the only way to fix this is to reload the whole page...

Thanks, InI -- I've actually posted this on several boards, and gotten lots of conflicting advice about it. One fellow for example, who sounded pretty knowledgable about DHTML, said the frameset thing was a matter of choice: either the frameset or all of the frames. That seems to make some sense, as reloading the frameset would reload the frames as well, wouldn't it? Anyway, if you know reasons contradicting or going beyond that, I'd be interested to hear more.

Nevel, I've actually collected about half a dozen bugs related to resizing in NN4. There's three that I discovered on my own, but haven't had time to test or work with very much, so wouldn't want to say too much about them yet. Two others I found out about by posting about the first one above, which is not too hard to find info about on the Web.

The best way to find out more about it would probably be to search for articles on it. It's really a lot moe involved than just reloading the page via JavaScript, as doing that can easily lead to an endless reloading cycle. I think you'll find that many sites have code embedded in them to thwart this bug. Here's some code from http://libraries.mit.edu/ :

function MM_reloadPage(init) {  //reloads the window if Nav4 resized

  if (init==true) with (navigator) {

    if ((appName=="Netscape")&&(parseInt(appVersion)==4)) {

      document.MM_pgW=innerWidth; document.MM_pgH=innerHeight; onresize=MM_reloadPage; 

    }

  }

  else if (innerWidth!=document.MM_pgW | | innerHeight!=document.MM_pgH) location.reload();

}



MM_reloadPage(true);

The poster has demanded we remove all his contributions, less he takes legal action.
We have done so.
Now Tyberius Prime expects him to start complaining that we removed his 'free speech' since this message will replace all of his posts, past and future.
Don't follow his example - seek real life help first.