FIREFOX SUCKS ROCK-SCUM!

[MrLeN]

Man, I've just about had it with FireFox. I mean, what's the big thing? Why does everyone like FireFox so much? It's a piece of JUNK!

Sure it understands all the W3C simple standard stuff, but every time I want to get a bit complicated, it just looks at me with a blank face and says.. "huh??".

I don't care what anyone says. IE Rocks. Ok, so it's owned by a ruthless company. So? I don't care. That doesn't concern me. It works! It always did.

All those idiosyncrasies that everyone complains about. All the things that make people say IE is not valid. ALL the code that it renders CORRECTLY even when it's WAY OFF course. Did you know that someone spent a LOT OF TIME and effort to get all those so called "mistakes" to render? It's no mistake. It's called INSIGHT.

Now, I have a website that I am building at http://www.promoterhost.com I decided that I would ad a "More Info" link, which would open a new <TR>. So I asked around and finally worked out how to do it.

The result is at my test site here:

http://www.aesap.com

Now click "More Info" on the right (in FireFox). Look what happens. IE seems to understand my code - Yet again (of course). But pretty, prim and proper (good for nothing) FireFox "doooesn't geeet iiiit" (yet again).

Keep opening and closing the More Info link. What is FireFox thinking?

Can anyone help me to solve this, before I damage something?

FireFox sucks. It always did, always will. My code is "W3Ceee Vaaaalid" *rollseyes*.

What more does it want? Doesn't understand JavaScript now?

There's always something!

Stuff the W3C standards. IE wrote the standards 10 years ago. Maybe everyone should have just ran along with it, instead of trying to be stubborn, saying:

"Umm.. just a sec, as soon as I get my hand out of the back of my pants, to stop scratching my rear, I'll see if I can get a browser working from these so called "standards". Just give me ten years, and we'll go through things like Nutscrape and Mozilla and Firefox and drive all the webmasters totally insane for the next decade. Yeah that's a good idea."

Can everyone just go download the latest version of IE and be done with it? FFS!

MrLeN

[speed]

JavaScript (swap.js):

function HideandUNhideObj(ThisObj){
    if((nav = document.getElementById(ThisObj)).className == 'myHide')
        nav.className = 'myShow';
    else
        nav.className = 'myHide';
}

Remove the following from the style sheet:

#a100webspacecom,
#atspacecom,
#geocitiescom,
#hostravecom {
 display: none;
}

Add the following to the style sheet:

.myShow {
    visibility: visible;
}

.myHide {
    display: none;
}

For each of the <tr>s you want hidden add class="myHide" e.g.

<tr id="hostravecom" class="myHide">

That gets it working for me in both Firefox and IE6, I've not tried any other browsers, I'll leave that to you.

If you find it doesn't work then I might have forgotten to paste something here, so let me know.

Also this will not allow visitors to access the additional information if they have JS off, which might be something you need to think about.

Edit: I just tried Opera 8 and it seems to work in that as well.

[MrLeN]

THANK YOU!

You da man!

You da maaaan!

http://www.aesap.com/index2.html

MrLeN

[speed]

Glad to help, I like the odd interesting problem.

[MrLeN]

Well, just stick with me.

I middle name is OddInterestingProblem :)

Thanks again. Very much appreciated.

Now I can get on with the site.

MrLeN

[Evic]

In Firefox if you click the More Info link twice, it will show/hide the tr. Then if you click it again it loads the tr with a blank tr underneath it.

On a side note, what you are blaming on FF for not working isn't FF's problem. Your code is wrong, IE is just putting it's "mistake filter" in place and doing the right thing.

More often than not, I find IE's mistake filter messes my stuff up - which is why you should always do it correctly and not rely on that mistake filter.

Also, I use FF because it doesn't trust anyone. Even the newest update of IE has the CSS glow overflow bug, and Microsoft has said that buffer overflow will remain until the new IE is released. So, you have fun w/ that gaping hole into your system. I'll stick with FF. :)

And extensions are awesome too.

[MrLeN]

Ok genius, please point out exactly where my W3C compliant XHTML is wrong?

MrLeN

[wsmeyer]

Just because code is W3C compliant doesn't mean it isn't poorly written.

The way you originally had it you neglected the colspan in the <td> that appeared. IE assumed you wanted it there where FF will display it as you had presented it.

If you don't like FF that's your opinion and I have no problem with it, but please come up with a better reason than it won't try and fix poorly written code.

William.

[MrLeN]

You're both mad.

My code was compliant and the colspan "was" in place. I've been writing code for 6 years. I'm not so stupid to leave out a colspan and say "duh??".

I can't work out why it wasn't working, but the only change I made was to change the javascript, with the help of speed. Maybe he knows why it caused a problem in FireFox.

You're just one of those FireFox activists. Fancy coming into this thread, telling me that I had errors which I didn't have, just so you could accuse me of writing poor code.

My code is perfect. It's Firefox that isn't.

See. Look what I have now:

http://www.promoterhost.com

Isn't it pretty? And the code is A1. So go suck a rock.

MrLeN

[wsmeyer]

It's is pretty, it suits you perfectly...




What version of IE are we all on? What, no new browser ideas for four years??? “R-I-I-I-G-H-T!” In case you forgot, Microsoft’s original online strategy for MSN was to copy that other crappy closed network, AOL. Apple is not much better. Apple has spent five years trying to put the Nextstep Operating System I was selling back in 1995 underneath their pretty Mac interface.

William.

[MrLeN]

ROFLMAO - Good one.

Maybe you should become a graphic artist?

MrLeN

[wsmeyer]

Yeah, too bad that when you are done rolling on the floor and realize that is a screen shot OF YOUR WEBSITE you'll probably just edit your post.

William.

[MrLeN]

I'm gonna take a screenshot of your website too.

Just so you don't feel left out :)

MrLeN

[wsmeyer]

Please do! I welcome input on my website by you or anyone else.

Any opinion that starts out something like:

"I think this could have been done better..."

or

"I don't like the way you did this because..."

or

"Maybe you should try/do this..."

Will be appreciated and fully considered.

Any opinions that start out "this sucks" will simply be ignored.

William.

[MrLeN]

ok, now I have a new problem.

When I open the links that say "More Info"..

The page jumps back up to the top. That's going to be pretty sad when I have 100 links.

I think I have to place some anchors somewhere - or something. I'll see how I go. If I can't work it out I'll come back for help.

..and to tell people off, who try to tell me my code has errors "when it doesn't", just so they can suck rocks with all the other FF "rock scumm'ers", and people who lie about errors that aren't there and make up errors and fake screenshots to prove their reduntant points; as if they ever had any.

MrLeN

[MrLeN]

It's all good.

I can sort this one out myself :)

..just have to give the <a link..'s some names.

I might call them ffsux1, ffsux2, ffsux3 etc :)

MrLeN

[Evic]

A W3C compliancy check doesn't make sure your javascript is correct. Genius.

[MrLeN]

No shit shirlock!

That's exactly my point..

ESPECIALLY when FireFox is involved in the equation.

MrLeN

[Evic]

First of all, I'm not sure if the berating makes you feel like more of a man, but you're really not helping your situation out here. We are here to help, and that's what we are attempting to do.

Now, I'm not sure what your reply had to do with my post, so we'll just ignore that part.

You say your website is W3C compliant. That's all fine and dandy. Whatever application you are using to check that compliancy (whether it be an online scanner, a stand-alone app, whatever) does not check to make sure the logic within your javascript is correct. There's nothing in the world that can tell you if your logic is correct.

Just because something works in IE doesn't mean it is correct, and the same is for FF or any other browser. Your job as a web designer is to provide the most suitable solution to your customers/visitors, and the most suitable solution is to develop you website based on standards and accurate logic so that it works in all browsers.

I have seen thousands of Hide/Unhides and they work perfectly fine in IE, FF, and any other browser I try. It's not a problem with FF, it's a problem in your code.

[MrLeN]

Take another look.

http://www.promoterhost.com

It works fine now.

It was the JS.

MrLeN

[Evic]

That's what I told you from the beginning.

[mike]

If you don't like FF, that's fine (I'm a fan). Don't like IE? That's fine too.

I'm all for debating the merits of everyone's preferred browsers however a little less vitriol is in order.

[MrLeN]

Ok, I just had to go look up vitriol.

..I understand now.

I didn't mean to be vitreolus.

I just couldn't take it when I was told my code was wrong when it wasn't, for the sake of defending FireFox.

But I am getting better with my vitrialism and I promise to keep improving.

MrLeN