Just terrible - most of my Enterprise users can't upgrade.
Is there an open-source alternative to Chrome Frame?
Retiring Chrome Frame
11–20 of 102 posts
Re: Retiring Chrome Frame
#12I'd never heard of Chrome Frame and had to look it up. Apparently it is (was) a way to run Google's web browser inside Internet Explorer:
> Google Chrome Frame is a plug-in designed for Internet Explorer based on the open-source Chromium project.
Re: Retiring Chrome Frame
#13Just terrible - most of my Enterprise users can't upgrade. Is there an open-source alternative to Chrome Frame?
Chrome Frame is open source. http://src.chromium.org/viewvc/chrome/trunk/src/chrome_frame...
Re: Retiring Chrome Frame
#14Just terrible - most of my Enterprise users can't upgrade. Is there an open-source alternative to Chrome Frame?
Chrome frame is the open source alternative to chrome frame.
Re: Retiring Chrome Frame
#15Re: Retiring Chrome Frame
#16This is a huge deal for enterprise app developers. We've been able to develop on a modern web platform, but have our customers use our app with IE 6, 7 and 8 (via ChromeFrame). Now we're going to have to add support for at the very least IE8, since XP (still over 50% market share in business) isn't going anywhere anytime soon, despite Microsoft EOLing it. Most IT admins I've dealt with refuse to install any other bro…
It seems like the enterprise grade solution would be to checkout the svn or git repo some time in the next 6 months and then rebrand it to "your company name here" frame.
http://src.chromium.org/viewvc/chrome/trunk/src/chrome_frame...
:)
Re: Retiring Chrome Frame
#17Why not set the date to April 2014, the end of support of XP?
That would be the perfect date to sunset chrome frame.
Re: Retiring Chrome Frame
#18Anybody familiar with the architecture of Chrome Frame? In terms of how Chrome/Chromium is integrated, I'm wondering if it would be viable to maintain a fork of the Chrome Frame code or if there are "concessions" made for Chrome Frame in the Chrome/Chromium code that, if they go away, makes it impossible for Chrome Frame to function.
Re: Retiring Chrome Frame
#19This is a huge deal for enterprise app developers. We've been able to develop on a modern web platform, but have our customers use our app with IE 6, 7 and 8 (via ChromeFrame). Now we're going to have to add support for at the very least IE8, since XP (still over 50% market share in business) isn't going anywhere anytime soon, despite Microsoft EOLing it. Most IT admins I've dealt with refuse to install any other bro…
It seems like the enterprise grade solution would be to checkout the svn or git repo some time in the next 6 months and then rebrand it to "your company name here" frame. http://src.chromium.org/viewvc/chrome/trunk/src/chrome_frame... :)
The viability of this strategy depends on whether the Chrome/Chromium bits will continue to integrated with the "Frame" bits. I'm not getting a good feel for the architecture from just a quick glance at their repo, but I'd definitely like to find out how viable, long-term, a fork might be.
Re: Retiring Chrome Frame
#20Anybody familiar with the architecture of Chrome Frame? In terms of how Chrome/Chromium is integrated, I'm wondering if it would be viable to maintain a fork of the Chrome Frame code or if there are "concessions" made for Chrome Frame in the Chrome/Chromium code that, if they go away, makes it impossible for Chrome Frame to function.
It would be a fair bit of work but it wouldn't be impossible. There are really only a couple of places in the main Chrome code base that are CF-specific - the automation interface and the external tab container.