Re:shows up in IE but not Netscape

From: Date: Sat, 10 Feb 2001 15:17:12 +0000
Subject: Re:shows up in IE but not Netscape
Groups: php.general 
Request: Send a blank email to php-general+get-39079@lists.php.net to get a copy of this message
"Erik Boles" <erik@rmwt.net> wrote: > > We are running a webform, that asks for user ID and pass, then passes it on > to a .php3 file that shows them a page to continue (not a security thing, > just a tracking thing). > > This .php3 file, called login.php3 works just fine in IE but when viewed in > netscape it simply shows a white screen. We did a "view source" and all of > the php file is there, and it doesn't show any errors (HTML errors blink in > the 'view source' with Netscape). > > Any ideas why the code below is not working right in Netscape?? Well, I ran your code through weblint which (and this is pretty normal behaviour for that old fusspot) spewed out an A4 page of errors! But the trick with weblint is to work from the last error backwards (the exact opposite of what you'd do with a C compiler). (I called it login.php -- I may want to pinch some of the code sometime!) <output snipped, only last few lines shown> login.php(0): no closing </HTML> seen for <HTML> on line 1. login.php(0): no closing </BODY> seen for <BODY> on line 1. login.php(0): no closing </HTML> seen for <HTML> on line 27. login.php(0): no closing </BODY> seen for <BODY> on line 27. login.php(0): no closing </CENTER> seen for <CENTER> on line 28. login.php(0): no closing </TABLE> seen for <TABLE> on line 29. login.php(0): no closing </TABLE> seen for <TABLE> on line 63. login.php(0): no closing </HTML> seen for <HTML> on line 69. login.php(0): no closing </BODY> seen for <BODY> on line 69. <end of weblint output> And here we see the dreaded missing </TABLE>. Someone made the point that it's best to develop on Netscape, and I think this is true for HTML. It's also true, to a point, for Javascript, while the Java applet issue is pretty much that the only way to get many Java applets to run is to use Netscape: if they'll run (by some miracle) in IE, they'll run in Netscape, so develop on IE. What a mess. Weblint is -- I think -- available for Windows. It's a fussy old tool, but really usefull for spotting those mistakes which the code blinded coder can't spot in an editor with colour syntax highlighting. It's saved me from throwing the monitor out of the (X)window on several occasions. -- ****************************************************************************** Marx: "Why do Anarchists only drink herbal tea?" Proudhon: "Because all proper tea is theft." ******************************************************************************

« previous php.general (#39079) next »