Thread: Help - anyone with IE7

If its any help I use Opera and its all messed up in the first one...

Messed up on IE7 too...

ok, thanks guys

I'm the same person lol - Although was last time I checked?

Hey, what you talking about? I'm not you :p

oops, sorry
just read the text, and not the names

Horribly messed up in Safari.

Originally Posted by Alex D

Horribly messed up in Safari.

Everything is screwed in Safari. Stupid Mac software

Both pages display fine in Camino (uses same rendering engine as Firefox) and Safari 3 on Mac OS X. I don't use (or have access to) IE7. Judging by the content of those page, your target audience is programmers and/or system architects, neither of whom are likely to use IE7 and both of whom can certainly figure out how to install Firefox if a certain web page necessitates it.

Originally Posted by webmaster

Everything is screwed in Safari. Stupid Mac software

1. You don't provide any basis for either argument.
2. Argumentative posts like this that are non-constructive, heavily biased, and uncorroborated are uncalled for and make you sound like an idiot.
3. If you have any specific criticisms of Mac OS X that don't also apply to Microsoft Windows, feel free to make a thread dedicated to such OS debate and post your arguments there.

Wait, is OS X Safari 3 out? I thought it was part of Leopard.

The final release of Safari 3 will be included in Leopard, but you can download the public beta for Tiger. There is also a Windows version, but a friend of mine said that it's too buggy for daily use.

Just tried Safari on windows then... sokay. But I can't live without tabs so now I'm back on trusty, old FireFox.

Safari 3 supports tabbed browsing. Just hit Command-T on Mac OS X or Control-T on Windows to open a new tab. My main problem with Safari 3 is that it doesn't support keyword searches from the URL bar (Camino and Firefox have built-in support; Safari 2 has the extension Sogudi).

Originally Posted by dsr

1. You don't provide any basis for either argument.
2. Argumentative posts like this that are non-constructive, heavily biased, and uncorroborated are uncalled for and make you sound like an idiot.
3. If you have any specific criticisms of Mac OS X that don't also apply to Microsoft Windows, feel free to make a thread dedicated to such OS debate and post your arguments there.

You're right, that really wasn't a good post - sorry. I do web design as a business, and the tendency is for IE and Firefox to display a page correctly, and for Safari to display it incorrectly. It's usually a minor table issue, or an unsupported Javascript feature, or something like that. But when I email a client telling them I added a rollover effect to the table cell navigation bar, and they're using Safari, I look stupid because it doesn't do anything.

Originally Posted by webmaster

You're right, that really wasn't a good post - sorry. I do web design as a business, and the tendency is for IE and Firefox to display a page correctly, and for Safari to display it incorrectly. It's usually a minor table issue, or an unsupported Javascript feature, or something like that. But when I email a client telling them I added a rollover effect to the table cell navigation bar, and they're using Safari, I look stupid because it doesn't do anything.

Ah, I do understand your frustration, though ironically not because of Safari but because of IE. Versions prior to 7 would @#$% up CSS rules so badly that one would need to add special cryptic-looking style rules just to deal with IE. Now IE7 conforms better to W3C standards, breaking compatibility with those special IE-only rules and forcing web developers to unconform to the strange world of Microsoft. Go figure.

Fortunately for you, Safari 3 uses a newer version of WebKit that seems to have better compatibility with the current standards. I'm glad you agree that "Stupid Mac software" was not a fair extrapolation of your (then having been unexpressed to us) grief. If you really have trouble writing web pages that render properly in Safari, you could write a simple JavaScript function that forces clients to switch to Firefox or IE7 if they want to view the content.

Originally Posted by dsr

Ah, I do understand your frustration, though ironically not because of Safari but because of IE. Versions prior to 7 would @#$% up CSS rules so badly that one would need to add special cryptic-looking style rules just to deal with IE. Now IE7 conforms better to W3C standards, breaking compatibility with those special IE-only rules and forcing web developers to unconform to the strange world of Microsoft. Go figure.

Fortunately for you, Safari 3 uses a newer version of WebKit that seems to have better compatibility with the current standards. I'm glad you agree that "Stupid Mac software" was not a fair extrapolation of your (then having been unexpressed to us) grief. If you really have trouble writing web pages that render properly in Safari, you could write a simple JavaScript function that forces clients to switch to Firefox or IE7 if they want to view the content.

I considered that, but as a web designer it looks bad... saying that pages I design require a download for some people. I usually just "dumb down" the page to be simpler without flashy stuff that doesn't work with all browsers.
As for the fault being with IE... I'm not one to disagree. I don't know much about the standards. But IE is the most popular browser, so it pretty much is the standard, W3C or not.

The biggest problem for me was that there was no way for me to test compatability with Safari, as I don't own a mac). Now that they released Safari for Windows, I think i'll download it just to check my pages.

Oh, and thanks for your understanding, and I'm sorry I didn't explain myself earlier

Heres a quick and easy solution!



download firefox :l

Originally Posted by bob_barker

Heres a quick and easy solution!



download firefox :l

The whole point of this thread is to determine whether Ynot's pages display in IE7. I assume he already uses Mozilla Firefox on his own computer(s), but not all viewers of his web page will.

I'm using some semi-ancient JS,
it was part of the JS spec, but now depreciated

IE never supported it, ever, even when it was new
Mozilla does support it, however use is discouraged

currently re-doing it the new way