Handling Chrome Frame #14
Comments
Yeah, this looks like it can now be done from the UA string. That was not always true. Will fix. |
OK, didn't know the history behind that. Is this something you want to do in the YAML regexes or in the Python code directly? |
It should be in the YAML regexes so all parsers benefit. |
Awesome. You do the work. I benefit. I like that. :) |
And I'll swing that into here too: https://github.com/toolmantim/user_agent_parser |
Fixed in 191a6d8 |
Awesome, thanks Lindsey! I've released v0.1.2 of the user_agent_parser Ruby gem with this Chrome Frame support. |
Revert "move Netfront to prevous place"
In the python implementation Chrome Frame is handled through parsing the user agent string accessible by JavaScript. This seems contrary to how Chrome Frame user agent strings are describe to work. It's also not very practical. How do you determine the UA of a CSS request, for example?
The text was updated successfully, but these errors were encountered: