Comment #3 on issue 22795 by kyberneticist: Chrome frame causes <!DOCTYPE HTML> to become invalid http://code.google.com/p/chromium/issues/detail?id=22795
I find the alternate mime solution very interesting. Doing that would be more convenient than the meta tag for triggering chrome frame (yes, unrelated to the validation issue). However, it seems the correct thing is rather than detect UA, and changing mime, to simply always set an X-UA-Compatible header of chrome=1 Hopefully issue 22802 will be fixed soon. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
