Chome Frame detection #3077

Closed
robocoder opened this Issue Mar 31, 2012 · 4 comments

1 participant

@robocoder

http://www.chromium.org/developers/how-tos/chrome-frame-getting-started/understanding-chrome-frame-user-agent

Propose reporting as IE (currently reported as Chrome)

Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; chromeframe/11.0.660.0)
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) chromeframe/11.0.660.0
  • At present, we don't report any IE variants (e.g., by add-ons installed), so I don't think we'll diverge from this.

Continue to report as Chrome:

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; chromeframe/11.0.660.0) AppleWebKit/534.18 (KHTML, like Gecko) Chrome/11.0.660.0 Safari/534.18
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/534.18 (KHTML, like Gecko) Chrome/11.0.660.0 Safari/534.18
@robocoder

(In [6136]) fixes #3077

@robocoder

Re-opening to classify as Chrome Frame.

Will need a piwik.js change.

@robocoder

Cursory inspection says we don't need to change piwik.js as the UA is grabbed by server-side tracker and then parsed.

@robocoder

(In [6141]) fixes #3077 - identify Chrome Frame as a browser

@robocoder robocoder added this to the 1.12.x - Piwik 1.12.x milestone Jul 8, 2014
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment