Today I made a quick test with my two web browser: Firefox and Konqueror. After this test I’m decided that in the next few hour I’ll use just Konqueror, because after a 3 hour surfing Firefox memory usage is about 150MB.
So, the Konqueror day started. I made some posts, blogged, etc., after I tried to view my iGoogle page. 
Google says:
Your browser may not fully support iGoogle. :sarcastic:
Why?
ps.: I know how to change Browser Identification, but it isn’t a solution. Why Google doesn’t support Konqueror? Their new browser (Chrome) is using some parts from Konqueror’s engine (KHTML), but there is still no support.
This is a common misconception of many web site builders. They should not support browsers. They should produce W3C standards conforming code.
Yeah, I’ve seen that and don’t like it.
Not only Chrome but Safari uses a number of parts of the KHTML engine.
Even with Firefox I get better support but things aren’t as smooth as they are with Firefox on Windows! I go to Google Calendar and it usually shows me nothing. I have to select and de-select each calendar to make it show up and even then it isn’t precise.
When I go to my calendar in Windows it shows up… all of the selected ones with no issue whatsoever!
That’s why I loong for when Google will provide Mail, Calendar, Contacts and maybe even ToDo in a 2-way fashion like work’s Exchange Server and Outlook work. THAT would definitely get Microsoft’s full attention because Exchange Server is one of their biggest cash cows (after Office and Windows OEM, I believe)
I use opera 9.6 in suse 11.0 with gnome and igoogle works perfect.Don’t know if it works under kde.
Yes, I think that it also works in KDE, but I have problem with KDE’s native web-browser: Konqueror.
Have you tried changing the UID in Konqueror to Firefox? Tools>Change Browser Identification>Other>Firefox 1.5.0.4. I was able to login and everything loaded fine.
Ok. Read my first post. I know about Browser Identification. My problem is more philosophy related: Google & KHTML “friendship”. 
I did. There wasn’t much of an indication that we were talking about philosophy. Yes, Google uses KHTML, as does Konqueror, and Safari. However, KHTML is not a CSS issue. Nor is it a javascript issue. Which both CSS and javascript are for browser and OS detection. Let me be more specific. The javascript is in the CSS. This is common place for many web sites. Why? Because browsers render things differently. Don’t believe me? Take the ACID2 test. Try it with a variety of browsers and versions. Firefox 2.x didn’t pass. Firefox 3 is closer. Epiphany bombs horribly. Konqueror passes (with KDE 3.5 and up). Firefox 3.0.4 comes fairly close to passing. I’m running 3.1b2pre and it passes ACID2. And ofcourse Opera passes. SeaMonkey 1.1.13 fails.
So half of this is the browser. Want to talk philosophy, then hit the people who make browsers, to develop their browser in accordance with W3C so that way their browser will render pages correctly. Then we won’t need browser and OS detection except for ActiveX and plugins.
There is a whole lot to consider when talking web coding and browsers. Enough to make your head hurt.
Take shockwave, for example. It’s not available in Linux. Flash is, but not shockwave. There are many other such things that make detection necessary.