Re:Retiring Chrome Frame
by EvanAnderson on Thursday June 13, 2013 @03:36PM
(#5876087)
Anybody 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.
[ Parent
| on HN ]
Re:Retiring Chrome Frame
by robertshield on Thursday June 13, 2013 @03:52PM
(#5876167)
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.
Re:Retiring Chrome Frame
by stock_toaster on Thursday June 13, 2013 @05:19PM
(#5876654)
Sounds like a business opportunity for someone. Even based on this thread there seem to be a few shops that would pay for support for it.