Site is partially broken in Firefox.

I've read a few of these posts, and most of the problems are occuring in firefox only. I am able to fully use the site in IE, but with the latest firefox browser, many images (like the header image and giant E3 banner) do not load. ..also, the buttons are all plain text have appeared to lose their sty1e. This problem has only been happening for the past few days.

When I check my "error console" within firefox, it's telling me that you have several warnings and several outright errors. They read:

"uncaught exception: Permission denied to call method Location.toString"

--Dave

The javascript errors I'm getting from FireFox are

DM_addToLoc is not defined

and

mboxCreate is not defined

It all works fine with IE.

In my case, it doesn't work well in both (firefox and internet explorer)......:cry:

But why in these days?????

Layout / CSS issue in Firefox 2.0.0.6: the "Submit Now" button is located in an invisible area of the form. In other words, I spent a couple of minutes looking for a "Submit" or "Proceed" or "Go" button, only to give up & drop everything & open IE - and of course, there it was!

Note to developers: using "position: relative" and mixing PX and % values for DIV / SPAN widths and heights is a BAD, BAD, BAAAAAD idea!

Different browsers will interpret things like that in wildly different ways - resulting in "fun" effects like 1/4 of the form disappearing from view.

Please, either fix the damn code to work with the browser used by about 35% of the market (and we LOVE it!), or redesign the forms to show the most important elements ***on top***. Seriously.

Layout / CSS issues...

stormcrow1979

(side note: certain words are intentionally misspelled, and have dashes in them, in order to get through the stupidly-paranoid filter)

case in point: viewing the source for the page with the Incredible Missing Submit Button, I've noticed something interesting. Namely, an amazing example of using an IMG tag inside a P element. Wow, I bet the guys who wrote the W3C standards for HTML couldn't even imagine that one!

Why the hell would you enclose an image inside a text element like paragraph? How about

text

If you so desperately need to "s-t-i-l-e" an image display, either apply the CSS directly to the IMG tag (doink), or at least throw it inside a SPAN or a DIV. Which is what they were meant for - GENERIC containers for stuff.

Another little thing (which could have caused this issue), is the apparent love for mixing & matching percentage units, straight PX values, and even esoteric crap like "points". This is the kind of "edge case" that's almost GUARANTEED to break on one browser or another. Pick a value system and go with it - pixels and percentages don't play well with each other.

And last but not least, I decided to run the page through the W3C Markup Validator (http://validator.w3.org/) (just for the sheer, unadulterated hell of it), and it came up with, not the typical dozen-or-so, but THREE HUNDRED EIGHTY-FIVE issues!

Holy *&^%... Thanks for giving me a GREAT example of how NOT to code webpages... I'll be saving a copy and using it in my k-l-a-s-s-e-s.