2 replies to this topic

[Randy]

A quickie in case anybody falls victim to this new bug that's not really a bug, just a change.

Make sure you close all of your HTML Comments from here on out. Especially don't forget to close 'em when you start and end your Javascript or CSS.

The new IE Security Update will totally bungle your site if you have an opening comment that is never closed. I just got to discover that when a friend called me in a panic because "My site is totally gone!"

She hadn't closed a comment in the CSS styles at the head of her page, so every page on her site displayed totally blank, even though the source code was there. Should have always been this way probably, but even Netscape overlooks that one these days.

Now you know where to look first if someone with the new XP/IE security update (I got it yesterday, others got it today apparently) can't see your site. Or if you don't use IE, you might want to fire it up at least long enough to make sure your sites are still showing as intended.

It's an easy one to miss!

[linux_lover]

Hmmm y'd think it should be the case if you didnt close a comment all following code would be commented.... its like leaving /* with no */ and wondering why ur php code doesnt work

If browsers (*cough* yes you bill) had not been so lax to errors in the first place no one would be in this position

CODE

$num = infinity;
for ($i=0;$i<$num;$i++) {
echo ('curse you IE and all your evil');
}

[torka]

On a mailing list to which I subscribe, recently somebody there mentioned she'd had an error in her site code which she didn't discover until she fired up the page in Safari. Apparently, testing it by viewing in IE hadn't been sufficient to catch the problem. (I know you're all shocked -- SHOCKED -- to learn this... )

And her only comment was about what an overly sensitive browser Safari is...

--Torka