Hey guys,
This is my fault. I mis-interpreted the code change. As the change to "fix" this issue was basically a "revert" of the original commit that was supposed to add ChromeFrame support, I incorrectly assumed that reverting the code would prevent special behavior for ChromeFrame (which I figured we needed in order to make it work). Had I read issue #6665 more carefully, I would have realized that this fix was to improve support for ChromeFrame, not remove it entirely.
I'll be sure to fix this statement in the release notes.
However, what *is* our level of support for ChromeFrame? My thought is that we should guarantee support for it, just as we guarantee support for Chrome itself...that's probably a question for the steering committee, though..
Rajeev