Hey all,
I really want to turn on Google chrome frame support for the mediawiki projects:
http://code.google.com/chrome/chromeframe/
Basically, it would just involve us putting in a meta tag on our pages that would trigger an IE plugin Google wrote, assuming the IE user had that plugin installed. The plugin essentially causes IE to use google's HTML renderer and JS engine, which are much nicer to develop for than IE. This won't really solve IE development issues, but would be a good move in the right direction as far as I'm concerned.
Any thoughts or compelling reasons why this might not be a good thing to do?
-Nimish
Nimish Gautam wrote:
Hey all,
I really want to turn on Google chrome frame support for the mediawiki projects:
http://code.google.com/chrome/chromeframe/
Basically, it would just involve us putting in a meta tag on our pages that would trigger an IE plugin Google wrote, assuming the IE user had that plugin installed. The plugin essentially causes IE to use google's HTML renderer and JS engine, which are much nicer to develop for than IE. This won't really solve IE development issues, but would be a good move in the right direction as far as I'm concerned.
Any thoughts or compelling reasons why this might not be a good thing to do?
-Nimish
Other than the hassle of having them install a beta plugin on their browser? They could as well install another browser.
On Wed, Feb 3, 2010 at 4:17 PM, Nimish Gautam ngautam@wikimedia.org wrote:
Basically, it would just involve us putting in a meta tag on our pages that would trigger an IE plugin Google wrote, assuming the IE user had that plugin installed. The plugin essentially causes IE to use google's HTML renderer and JS engine, which are much nicer to develop for than IE. This won't really solve IE development issues, but would be a good move in the right direction as far as I'm concerned.
Any thoughts or compelling reasons why this might not be a good thing to do?
The page says "Note: This is an early-stage release, intended for developers and testing." It doesn't sound like it's ready for us to use yet. I've heard anecdotal reports of stability problems (no, no source offhand). Moreover, it's not clear to me whether it would integrate correctly with all IE features. If we do use it, it could only be after significant testing that demonstrated it's actually a clear improvement.
It might be worth making this an opt-in feature now, though. Adventurous IE users can try it out and report whether they like it or not, or if they spot any bugs. If they do, we can tell them to file them with the Chrome Frame team.
On Wed, Feb 3, 2010 at 4:17 PM, Nimish Gautam ngautam@wikimedia.org wrote:
Basically, it would just involve us putting in a meta tag on our pages that would trigger an IE plugin Google wrote, assuming the IE user had that plugin installed. The plugin essentially causes IE to use google's HTML renderer and JS engine, which are much nicer to develop for than IE. This won't really solve IE development issues, but would be a good move in the right direction as far as I'm concerned.
Any thoughts or compelling reasons why this might not be a good thing to do?
The page says "Note: This is an early-stage release, intended for developers and testing." It doesn't sound like it's ready for us to use yet. I've heard anecdotal reports of stability problems (no, no source offhand). Moreover, it's not clear to me whether it would integrate correctly with all IE features. If we do use it, it could only be after significant testing that demonstrated it's actually a clear improvement.
It might be worth making this an opt-in feature now, though. Adventurous IE users can try it out and report whether they like it or not, or if they spot any bugs. If they do, we can tell them to file them with the Chrome Frame team.
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
I think it would be a good idea. It's better than nothing. It would make Mediawiki run faster and allow scripts to work better in IE. A simple opt-in should do.
On Thu, Feb 4, 2010 at 8:17 AM, Nimish Gautam ngautam@wikimedia.org wrote:
Hey all,
I really want to turn on Google chrome frame support for the mediawiki projects:
http://code.google.com/chrome/chromeframe/
Basically, it would just involve us putting in a meta tag on our pages that would trigger an IE plugin Google wrote, assuming the IE user had that plugin installed. The plugin essentially causes IE to use google's HTML renderer and JS engine, which are much nicer to develop for than IE. This won't really solve IE development issues, but would be a good move in the right direction as far as I'm concerned.
Any thoughts or compelling reasons why this might not be a good thing to do?
The issues log at the bottom of the developers guide indicate this is not ready for prime time - i.e. printing doesn't work.
http://code.google.com/chrome/chromeframe/developers_guide.html
More fundamentally, the _user_ should control when a different renderer is used for websites; not the website! Currently this can be done with registry keys.
HKCU\Software\Google\ChromeFrame\OptInUrls
Hopefully they add a GUI to configure the OptIn list, and the ability to import a whitelist like Adblock and IETab.
fwiw, Mozilla-in-IE was at a similar stage three years ago.
http://starkravingfinkle.org/blog/2006/12/xule-what-if/
-- John Vandenberg
On Wed, Feb 3, 2010 at 9:31 PM, John Vandenberg jayvdb@gmail.com wrote:
More fundamentally, the _user_ should control when a different renderer is used for websites; not the website! Currently this can be done with registry keys.
HKCU\Software\Google\ChromeFrame\OptInUrls
Hopefully they add a GUI to configure the OptIn list, and the ability to import a whitelist like Adblock and IETab.
If the user can opt in already, I see no reason for us to support this right now in any capacity.
On 2010-02-04, at 8:21 AM, Aryeh Gregor wrote:
On Wed, Feb 3, 2010 at 9:31 PM, John Vandenberg jayvdb@gmail.com wrote:
More fundamentally, the _user_ should control when a different renderer is used for websites; not the website! Currently this can be done with registry keys.
HKCU\Software\Google\ChromeFrame\OptInUrls
Hopefully they add a GUI to configure the OptIn list, and the ability to import a whitelist like Adblock and IETab.
If the user can opt in already, I see no reason for us to support this right now in any capacity.
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Not many people know about this hack in the Registry. Perhaps it would be easier for the user if someone could make an extension to Mediawiki that allows users to opt-in to Google Chrome Frame.
On Thu, Feb 4, 2010 at 11:40 AM, Techman224 techman224@techman224.com wrote:
Not many people know about this hack in the Registry. Perhaps it would be easier for the user if someone could make an extension to Mediawiki that allows users to opt-in to Google Chrome Frame.
Not many people know about Chrome Frame at all. Nor, as I understand it, should they, since key pieces of functionality are still missing. There's no point in us expending effort or UI space here unless there's actual demand from users, which I haven't seen, personally. The ones advocating this typically don't use IE in the first place.
Techman224 wrote:
On 2010-02-04, at 8:21 AM, Aryeh Gregor wrote:
On Wed, Feb 3, 2010 at 9:31 PM, John Vandenberg jayvdb@gmail.com wrote:
More fundamentally, the _user_ should control when a different renderer is used for websites; not the website! Currently this can be done with registry keys.
HKCU\Software\Google\ChromeFrame\OptInUrls
Hopefully they add a GUI to configure the OptIn list, and the ability to import a whitelist like Adblock and IETab.
If the user can opt in already, I see no reason for us to support this right now in any capacity.
Not many people know about this hack in the Registry. Perhaps it would be easier for the user if someone could make an extension to Mediawiki that allows users to opt-in to Google Chrome Frame.
The current release of Chrome Frame is targeted toward web developers, presumably so they can test their own code in it. I would hope that once its released for use by the general public that it will have a much more sensible system for turning it on and off that doesn't require manually editing the registry. Leaving the decision of whether or not to use it to site owners would be a rather odd system. Making an extension to add the meta tag wouldn't be difficult (there's at least one generic meta tag extension already), but it would likely be made obsolete rather quickly as well.
wikitech-l@lists.wikimedia.org