IBrowse vs. Peecee, go figure.

[AmiGR]

In this order on any OS, I'd use: Any KHTML browser (I currently use Safari), Camino (the fastest Gecko browser in my experience), IE7, Firefox, Opera, IE6, Mozilla.

[Waccoon]

Chances are this is caused by bad Javascript.  Given that few if any browsers warn developers about syntax erors, and simply plow ahead "fixing" things as they go, almost all the code on the Internet is broken.  Chances are the developer only tested with one version of IE and nothing else.

IE is far from perfect, but it's not horrible.  I have very few problems making CSS for it.  Also, IE uses different rendering depending on what DOCTYPE you use.  IE will use a much more standards-compliant rendering if you format the header correctly.  It's assumed that if a web developer uses a proper DOCTYPE, they're serious about standards-compliance.

Funny how nobody complains about Firefox's horrible GUI problems.  Copy/paste work intermittently, and my media buttons do not work at all, which makes browsing with Firefox a REAL pain.  I prefer media keys to all that other gimmicky crap, like mouse gestures.  It figures that Firefox would completely fail in this department, and has been faulty for YEARS.  There's no need for a Linux-based browser to work properly on Windows.

AmiGR:  even IE7 does not render the Acid2 test correctly (at least it understands min-height and the PNG alpha channel).

Nothing renders it properly except the unreleased Firefox alpha.  Current versions of Firefox display a real mess.  Don't yell at IE if nothing else works, either, including the endlessly-praised darling of the open source browser movement.

Do you really think the acid tests are designed to work with any closed-source browsers?  It's hardly fair to test browsers with acid tests that do not support graceful degredation, either.  Nothing shows at all?  No kidding!  That's because the code violates the whole reason for using HTML in the first place.

[zyphoid]

AmiGR wrote:
In this order on any OS, I'd use: Any KHTML browser (I currently use Safari), Camino (the fastest Gecko browser in my experience), IE7, Firefox, Opera, IE6, Mozilla.

I'm assuming that we should all be in favor of the new potential KHTML browser sputnik for amiga OS then light,fast, modern browser!!  Any updates on progress....demos, which systems and OS?  :roll:

[AmiGR]

IE is far from perfect, but it's not horrible.

It is not, it's just not "the best browser" the other guy wanted to claim it is,

I have very few problems making CSS for it. Also, IE uses different rendering depending on what DOCTYPE you use. IE will use a much more standards-compliant rendering if you format the header correctly. It's assumed that if a web developer uses a proper DOCTYPE, they're serious about standards-compliance.

We do use the DOCTYPE forcing it to strict mode. It just renders things differently regardless.

Funny how nobody complains about Firefox's horrible GUI problems. Copy/paste work intermittently, and my media buttons do not work at all, which makes browsing with Firefox a REAL pain. I prefer media keys to all that other gimmicky crap, like mouse gestures. It figures that Firefox would completely fail in this department, and has been faulty for YEARS. There's no need for a Linux-based browser to work properly on Windows.

I do, I never liked the Firefox GUI and behaviour and as I said earlier, it's just not snappy enough for me. People tend to use arguments like "it starts up slowly", which is quite laughable a problem in comparison.

Nothing renders it properly except the unreleased Firefox alpha. Current versions of Firefox display a real mess. Don't yell at IE if nothing else works, either, including the endlessly-praised darling of the open source browser movement.

Do you really think the acid tests are designed to work with any closed-source browsers?

Huh? It displays correctly on KHTML/Webcore after some Apple patches,  Opera and iCab. That was looooong before Firefox betas got anywhere near rendering it correctly. Opera and iCab are not open source and Webcore is really a commercial effort on an open base (KHTML).

It's hardly fair to test browsers with acid tests that do not support graceful degredation, either. Nothing shows at all? No kidding! That's because the code violates the whole reason for using HTML in the first place.

Something always gets displayed, what that something is is the problem. Also, Acid2 *does* check how correctly the browser falls back. Read this for more info. It is pretty heavy in data URLs but it does include a version without them for browsers that do not support them (like IE6/7).