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.
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.
