Open GoogleCodeExporter opened 9 years ago
Well, installing Google Chrome Frame plugin for IE fixes the problem, but I'm
not sure if, from the Google Refine developers point of view, this
configuration has to be considered mandatory or just a workaround.
You might just mention it in the installation doc.
Original comment by runuppat...@gmail.com
on 19 Sep 2012 at 10:09
Did you not get prompted to install the Chrome Frame plugin the first time
Google Refine opened in IE? That's what happened with my IE 9 installation.
Original comment by tfmorris
on 19 Sep 2012 at 10:52
Sure it prompted, but I didn't install it on the first time because I didn't
find anywhere a statement saying I should install a Google Chrome related
software upon Internet Explorer to make Refine work.
I think the shown message is misleading because tells about how to improve your
web experience with Chrome technology and not that you actually need it to use
the page.
Maybe this is obvious for the developer who added the tag, but not for the
common user.
Secondly I don't see the point in the Google strategy piggybacking Internet
Explorer deficiencies with Chrome technology.
I looked at the installation directories of Chrome Frame and it seems that the
occupation is roughly equivalent to a standard Chrome installation, and this
probably means that you when installing Chrome Frame are actually installing
Chrome, even though not fully enabled.
From the Chrome Frame FAQ I understand that it slips in replacing the rendering
and the js engines when directed by a tag.
I think among many other people, especially web developers, that IE is inferior
compared to the other browsers, and in fact I don't use it, but if the IE
support means using Chrome in the shadow, well, why should I use IE at all?
Original comment by runuppat...@gmail.com
on 20 Sep 2012 at 7:17
OK, we'll look at making it clearer to the user that the Chrome Frame plugin is
mandatory for Refine. It's also possible that IE 9 has improved enough over IE
7 & 8 that the Chrome Frame isn't really needed for that release.
The reason for not just telling people to use a different browser is that in
many corporate environments users don't have a choice. The use of Chrome Frame
is a low cost way for the Refine team to support these users without having to
implement extensive workarounds.
Original comment by tfmorris
on 20 Sep 2012 at 3:34
Original issue reported on code.google.com by
runuppat...@gmail.com
on 19 Sep 2012 at 7:09