DISCLOSURE: THIS POST MAY CONTAIN AFFILIATE LINKS, WHICH MEANS WE MAY RECEIVE A COMMISSION IF YOU CLICK A LINK AND PURCHASE SOMETHING. PLEASE CHECK OUT OUR DISCLOSURE POLICY FOR MORE DETAILS.
In what has to be one of the strangest browser glitches I’ve seen since nested tables in Netscape 4.0, the ongoing battle between Safari and GadgetMadness has been ended with the removal of a single “/h2” tag. In one of the site templates we opened an “h3” tag and closed it with an “/h2” instead of an “h3.” Yes it was our mistake, but every other web browser in EXISTENCE was able to forgive this error: IE, Camino, Firefox, Netscape – but not Safari. Noooooooo, over a single tag error Safari instead pukes all over the page and ruins the entire GadgetMadness experience for Mac users everywhere (or at least for the 5 who read our site.)
Seriously though, thanks to all of you who brought this to our attention. We still recommend Firefox over Safari, but in the end we want the site to be viewable simultaneously by all beings everywhere. Thanks for being patient while we got our p’s, q’s, and h3’s straight.
On a side note, we have recevied fewer than 10 entries for the Laserpod contest, which means your chances of winning are really good if you enter.
Seriously though, thanks to all of you who brought this to our attention. We still recommend Firefox over Safari, but in the end we want the site to be viewable simultaneously by all beings everywhere. Thanks for being patient while we got our p’s, q’s, and h3’s straight.
On a side note, we have recevied fewer than 10 entries for the Laserpod contest, which means your chances of winning are really good if you enter.
If you use Firefox I would recommend this “Web Developer” extension.
http://www.chrispederick.com/work/firefox/webdeveloper/
I use it all the time to find out where I have been too lazy. 😉
regards,
Scott
I always thought you guys were just bad designers… go figure!
good job~
I worked at a big HTML sweatshop and the truth was they don’t care about quality – quantity was king. You were expected to churn out the code, and quickly, and mistakes did not matter so long as the page loaded in IE and Netscape and the QA guys could load it. Perhaps my old “habits” (which I have tried to break) snuck in when I misclosed those tags…
It looks fine for me in lynx, and that’s all that matters.