Little problem with FireFox

[pgp2003]

John, you can check it out at http://www.nostreetracing.org if you wanna see if you can figure out the problem

[bondjetta]

PJ i'm gonna register over there and we're going to work on those templates...they're a MESS.

anyone who seriously feels like contributing to this thread feel free. but if all you're going to do is battle over ie vs ff take it somewhere else.

[TwinsX2Dad]

Originally Posted by Natch

O ... M ... F ... G ...

A very childish reaction.

Originally Posted by Natch

What if those companies that designed baby seats for cars thought as you did with regards standards? Dead children... (over the top? nah not really...)

Now that is absurd, on top of a very childish reaction. You might wish to come up with a more intelligent exclamation than 'Oh My Fattening Grease', unless you're trying to illustrate what is between your ears.

If we were to use the same analogy for baby seats, Firefox would protect the baby, while MSIE protected the baby AND helped the driver avoid the accident.

MSIE can view standardized code AND the stuff that is a little out of whack. Firefox throws a fit if the code isn't standardized.

Yes, there is good reason for standards - but we have an Internet where millions don't care, don't know or simply just want to push the envelope.

Of course, there are also quite a few who insist the world should narrow their tools and their online experience, just to accomodate standards which really aren't standards outside of one group.

[tubedogg]

Originally Posted by TwinsX2Dad

If we were to use the same analogy for baby seats, Firefox would protect the baby, while MSIE protected the baby AND helped the driver avoid the accident.

The only problem is, MSIE would probably have a leak in the gas tank causing the car to explode upon impact when it (inevitably) crashed.

MSIE can view standardized code AND the stuff that is a little out of whack. Firefox throws a fit if the code isn't standardized.

(Just a quick side note: MSIE can't render all standardized code correctly, because of long-standing bugs which its' developers have acknowledged.) Have you ever bothered trying to write standardized code? It *really* isn't hard, it just takes a bit of adjustment from what you are used to. And if you do write standardized code, it should look nearly identical in MSIE, Firefox, and nearly every other browser you can throw at it.

I am sitting here in disbelief that your argument is "write crappy code, who cares cause MSIE can render it anyway". I can only hope to god that you have no web development clients.

Sorry to say but your view on web standards is in the minority, even amongst Microsoft's own IE developers, who openly acknowledge the problems with MSIE vs. standards.

Of course, there are also quite a few who insist the world should narrow their tools and their online experience, just to accomodate standards which really aren't standards outside of one group.

You're advocating the whole world switch to and keep MSIE in one breath and in the next breath claim that Mozilla is trying to force everyone to conform to their own standard? Um, hello, Mr. Pot, I've got Kettle on the line. The standards are standards regardless of what Microsoft thinks...and the standards that "aren't standards outside of one group" are the standards that nearly every single browser except MSIE is developed to. Of course Mozilla & Firefox, but also Opera, Omniweb, Safari, and a number of lesser-known browsers, as well as browsers on alternative platforms like cell phones and PDAs. If you think that coding to standards for a PC web browser is annoying, try writing something for a cell phone or PDA that isn't to standard. I think you'll wake up rather quickly to the fact that the PC browser is unique (again thanks to MSIE) in not requiring standards-based code across the board.

And in regards to your marketshare claim, I have never seen any legitimate site claim Firefox has 40% of the browser market overall. Maybe, on a particular tech-leaning site 40% of that site's users use Firefox, but in general the estimate is somewhere between 3% and 10% depending on who you listen to. (WebSideStory, who is pretty much viewed by much of the industry as a standard marker, shows 4% using Firefox as of the end of October, with that gain coming directly off of MSIE. source Another stat tracker, OneStat.com, shows MSIE losing 5% between May and November 2004, again directly to Firefox.) No matter who you listen to, though, MSIE is losing marketshare. Not to mention that there were 10 million different people who downloaded it the first month after its' 1.0 release. Surely even you realize there aren't 10 million techs out there.

[pgp2003]

Originally Posted by bondjetta

PJ i'm gonna register over there and we're going to work on those templates...they're a MESS.

anyone who seriously feels like contributing to this thread feel free. but if all you're going to do is battle over ie vs ff take it somewhere else.

thank you

and

thank you

[pgp2003]

Thanks John for looking into it and fixing it.. it's fixed now and me and the guys appreciate it alot..

my problem was this <!---->.. dashes with no breaks! lol :hits himself in the forehead:

[bondjetta]

yep

IE's non-standard approach to code interpretation saw <!----------> as <!-- --> which is why IE could display the site but every page was broken for FF. way to go IE-lovers.

[Zachery]

Originally Posted by bondjetta

yep

IE's non-standard approach to code interpretation saw <!----------> as <!-- --> which is why IE could display the site but every page was broken for FF. way to go IE-lovers.

IE handles flawed code much better than it should, but its a good and bad thing, bad code looks good, good code looks good. otherbrowsers have massive issues trying to display flawed code, alot of the time they crash and die hard.

[bondjetta]

Originally Posted by Zachery

IE handles flawed code much better than it should, but its a good and bad thing, bad code looks good, good code looks good. otherbrowsers have massive issues trying to display flawed code, alot of the time they crash and die hard.

which is why i use FF, i want to know if i'm programming bad code....to me bad code is indicitive of bad programmers.

[pgp2003]

Originally Posted by Zachery

IE handles flawed code much better than it should, but its a good and bad thing, bad code looks good, good code looks good. otherbrowsers have massive issues trying to display flawed code, alot of the time they crash and die hard.

yeah.. I learned that the hard way :nervous: