Hello all!
I just recently downloaded Google Chrome web browser. Scalix does not appear to support this browser out of the box so I just wanted to let you guys know.
Here is the errors message.
You have attempted to start Scalix Web Access from an unsupported platform.
Please use Internet Explorer 5.5 SP2 or higher on Windows, Mozilla 1.7 or higher,
or Firefox 1.0 or higher.
Google Chrome
Moderators: ScalixSupport, admin
-
TheDude
- Posts: 119
- Joined: Sat Sep 17, 2005 9:53 pm
- Location: Alabama, USA
- Contact:
Work Around
You can try my "Ice Weasel" hack, details in this thread: viewtopic.php?t=5434
This will at least send your users to the Mobile Mail page when they are using Chrome. At least they can check their mail....
People have been pleading for Safari support in the forum for years and Chrome uses the same back end as Safari and iPhone - Webkit.
If Scalix webmail could work on Chrome, then maybe one day the full version could work on iPhone too (?) wouldn't that be cool...
The Dude
Update: Scalix webmail DOES work with IE8 Beta 2, works quite nicely actually, I highly recomend IE8 beta 2...
This will at least send your users to the Mobile Mail page when they are using Chrome. At least they can check their mail....
People have been pleading for Safari support in the forum for years and Chrome uses the same back end as Safari and iPhone - Webkit.
If Scalix webmail could work on Chrome, then maybe one day the full version could work on iPhone too (?) wouldn't that be cool...
The Dude
Update: Scalix webmail DOES work with IE8 Beta 2, works quite nicely actually, I highly recomend IE8 beta 2...
Last edited by TheDude on Wed Sep 03, 2008 11:16 am, edited 2 times in total.
-
Jon Kruger
-
nvehommes
- Posts: 61
- Joined: Sun Feb 24, 2008 9:22 am
- Location: Erlangen, Germany
Hi,
at least Safari really doesn't work yet, even when one lets it masquerade as Firefox or Internet Explorer. Same for Opera. Each browser has its own kind of non-standard or suboptimal behavior that apparently needs to be considered explicitly in the Scalix code.
Florian wrote a detailed explanation some time ago on this forum.
Jon Kruger wrote:Does Scalix just not work with Safari, iPhone, Chrome, IceWeasel, etc or are they just not supported by Scalix support and then just not allowed to work? Has Scalix been tested on them?
at least Safari really doesn't work yet, even when one lets it masquerade as Firefox or Internet Explorer. Same for Opera. Each browser has its own kind of non-standard or suboptimal behavior that apparently needs to be considered explicitly in the Scalix code.
Florian wrote a detailed explanation some time ago on this forum.
-
gremlin
-
TheDude
- Posts: 119
- Joined: Sat Sep 17, 2005 9:53 pm
- Location: Alabama, USA
- Contact:
Horror
You can't put the Genie back in the bottle Gremlin! What you have unleashed is surely the most disturbing thing ever... an incompatiblity with a new browser!
No worries Gremlin, somebody was gonna mention Chrome, why not you?
:)
No worries Gremlin, somebody was gonna mention Chrome, why not you?
:)
-
billb3
- Scalix Star
- Posts: 464
- Joined: Mon May 26, 2008 8:56 pm
- Location: Kingston, NY
- Contact:
Re: Horror
TheDude wrote:You can't put the Genie back in the bottle Gremlin! What you have unleashed is surely the most disturbing thing ever... an incompatiblity with a new browser!
Considering that it uses WebKit...it is not really a new browser at all. Safari & Konquerer have both been around for a while now. With the increasing number of Mac & Linux users...I think it would be very worthwhile for Scalix to support Webkit.
While both Mac & Linux users can install Firefox, most don't...and stick to the default browser. Which just happens to be Safari for Mac & Konquerer for KDE users.
-
schmoe90
- Scalix
- Posts: 900
- Joined: Mon May 07, 2007 11:51 am
According to: http://blogs.zdnet.com/Howlett/?p=477 it would be political suicide to use Chrome for your webmail...
-
TheDude
- Posts: 119
- Joined: Sat Sep 17, 2005 9:53 pm
- Location: Alabama, USA
- Contact:
Google said today the EULA was a mistake and they are going to change it. http://arstechnica.com/news.ars/post/20 ... ge-it.html
Google wants to bring Chrome where Scalix lives, the Enterprise. Their goal is to be the "IE Killer" so Scalix should consider moving resources to make Scalix compatible soon or this little thread is going to get REAL big.
Plan to "Crush IE": http://www.wired.com/techbiz/it/magazin ... /mf_chrome
Don't bet against Google.
The Dude
Google wants to bring Chrome where Scalix lives, the Enterprise. Their goal is to be the "IE Killer" so Scalix should consider moving resources to make Scalix compatible soon or this little thread is going to get REAL big.
Plan to "Crush IE": http://www.wired.com/techbiz/it/magazin ... /mf_chrome
Don't bet against Google.
The Dude
-
florian
- Scalix
- Posts: 3852
- Joined: Fri Dec 24, 2004 8:16 am
- Location: Frankfurt, Germany
- Contact:
Well, I think the Chrome debate on the political side will go on for a while; the German Interior Ministry's department for Information Systems Security has put out a warning against using Chrome at this time, both because of possible security flaws with such new technology, but also based on the privacy concerns around Google's built-in data collection technology.
We've been carefully looking into Webkit for a while, mostly on the grounds of planning Safari support, and if we decide to do it, it would be designed and tested in such a way that Chrome would be included. No dates for it, but rest assured it will be timely for our customer's needs. I don't see anyone seriously wanting to use it at this point for their production systems.
Just to comment on a couple of general misconceptions in this thread. First, unless it's really a superset of behaviours like IE8 over IE7, there is simply no way that a complex web app like Scalix Web Access could ever work with a new browser, out of the box; the way we use JavaScript and AJAX is way to deep for that to happen. Second, on Webkit, the actual implementations based on Webkit for Konqueror, Safari an Chrome are quite different on the side of what's most relevant to us, JavaScript support. Chrome has rewritten the whole engine, btw., so while there are similarities, supporting one would not give us the other - we've already looked into Safari as I said, and Safari support would not automatically enable Konqueror to work as there are serious differences. Third, IceWeasel, which has been mentioned in this thread, is not based on Webkit, but on Gecko, i.e. the Mozilla engine. It actually does use the unmodified Gecko, so it will work with Scalix Web Access and since 11.3, the hack is no longer necessary. As we don't specifically test it, it will still pop-up a warning, but it works with SWA without any known problems or issues, so in this case it's simply not supported, yet works. Webkit-browsers at this point do not work, same as Opera, and all of them require quite substantial code modifications on our side to change this.
Florian.
We've been carefully looking into Webkit for a while, mostly on the grounds of planning Safari support, and if we decide to do it, it would be designed and tested in such a way that Chrome would be included. No dates for it, but rest assured it will be timely for our customer's needs. I don't see anyone seriously wanting to use it at this point for their production systems.
Just to comment on a couple of general misconceptions in this thread. First, unless it's really a superset of behaviours like IE8 over IE7, there is simply no way that a complex web app like Scalix Web Access could ever work with a new browser, out of the box; the way we use JavaScript and AJAX is way to deep for that to happen. Second, on Webkit, the actual implementations based on Webkit for Konqueror, Safari an Chrome are quite different on the side of what's most relevant to us, JavaScript support. Chrome has rewritten the whole engine, btw., so while there are similarities, supporting one would not give us the other - we've already looked into Safari as I said, and Safari support would not automatically enable Konqueror to work as there are serious differences. Third, IceWeasel, which has been mentioned in this thread, is not based on Webkit, but on Gecko, i.e. the Mozilla engine. It actually does use the unmodified Gecko, so it will work with Scalix Web Access and since 11.3, the hack is no longer necessary. As we don't specifically test it, it will still pop-up a warning, but it works with SWA without any known problems or issues, so in this case it's simply not supported, yet works. Webkit-browsers at this point do not work, same as Opera, and all of them require quite substantial code modifications on our side to change this.
Florian.
Florian von Kurnatowski, Die Harder!
-
florian
- Scalix
- Posts: 3852
- Joined: Fri Dec 24, 2004 8:16 am
- Location: Frankfurt, Germany
- Contact:
Re: Google Chrome
Actually I should remove your post, as it's really offtopic from a Scalix point of view.... changing the so-called user agent string will not make Chrome work with Scalix as the AJAX capabilities of the browsers are actually different. We all hope that HTML5 will finally bring restandardization of the necessary, but it's still kinda to early to really make the transition for us.
Anyway, for other websites that you MAY be able to get to work by fooling around with browser UserAgent strings, I think you'll need something like this for Chrome: http://www.renjusblog.com/2010/03/google-chrome-user-agent-switcher.html
Cheers,hope it helps,
Florian.
Anyway, for other websites that you MAY be able to get to work by fooling around with browser UserAgent strings, I think you'll need something like this for Chrome: http://www.renjusblog.com/2010/03/google-chrome-user-agent-switcher.html
Cheers,hope it helps,
Florian.
Florian von Kurnatowski, Die Harder!
Who is online
Users browsing this forum: No registered users and 2 guests