Unfortunately, this is not a newsgroup for Netscape Communicator. It is a newsgroup for Mozilla, an open source browser which will be embedded in the next version of Netscape. Mozilla is a totally different browser from Netscape Communicator.
> I realize I didn't give a URL--it's a brand new Human Resource job > application system, and I have been explicitly directed by my supervisor to > not release the URL anywhere until it's completely ready. Sorry :( Sure > makes it harder for me to get help, tho <sigh> > > elaine > > "EPPack" <[EMAIL PROTECTED]> wrote in message > a6t2jo$gpec9$[EMAIL PROTECTED]">news:a6t2jo$gpec9$[EMAIL PROTECTED]... > > I am developing a complex set of web pages using a LOT of server-side ASP > > coding (no Javascript or VBScript). I'm well aware that IE is a lot > sloppier > > than NS as far as handling the code, so I've spent a LOT of time cleaning > up > > improperly nested tags, etc etc, to get it to work the same in NS as it > does > > in IE.. All of this works fine in IE, btw. > > > > The current problem is that I'm populating dropboxes from largish external > > files using ASP, but some of them will not show up in NS. The source code > > looks fine, as far as nested tags and other syntax, and I can even run the > > actual parsed out code thru the w3c validator and it will come out fine. > > What's REALLY weird, is that when I look at the page in NS, and don't see > > the dropbox, if I then immediately print that page (CtrlP), the missing > > dropbox is there! And this is random behavior, btw, sometimes the dropbox > > shows up fine :( Reloading the page does not correct the problem. > > > > And yet another one--some of the populated fields on the dropbox are > college > > names, so there's "Texas A&M University", for example. If I run the > (parsed > > out) source for this page thru the validator, it flags that line. If I > > change it to "Texas A & M University" (spaces around the amp) it doesn't > > flag. Clearly the ampersand must be being parsed by NS, and I won't bet my > > rent this isn't part of the reason I'm having problems. <sigh> > > > > I thought perhaps it was a script timeout, but I'm not getting an error, > and > > all the entries do show up in source. The script timeout is set to 90 > > seconds, which *should* be OK, but we did bump it to 120 secs. > > > > Does anyone have any suggestions? > > > > Thanks! > > > > ----- > > Elaine Pack, Web Analyst > > Charlottesville, VA > > [EMAIL PROTECTED] > > Any opinions are my own > > > > > >
