New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Browser plugin version detection #5766
Comments
Also consider adding Silverlight/Moonlight detection to the mix. |
I’ve been experimenting with this feature — part of the reason why #355 is taking so long to fix ;) — and I don’t know if it’s that useful of a feature, as it’s very Windows IE-centric. 1) ActiveX objects don’t have a standard method or property for version info. Each plugin is different; each requires plugin-specific code to query the version info, if it exists. 2) For other browsers, navigator.plugins[] doesn’t have a version property; version info is sometimes embedded in the name or description properties… 3) should we collect the version number only? do we detect only genuine plugins or do we include the compatible ones? (eg totem) The above also adds overhead: more code increases the size of piwik.js and initialization time. (A first party session cookie could be used to avoid plugin version detection on subsequent page visits to this site.) |
I think it would be nice to detect Silverlight. Concerning the new feature “detecting the version number”, that would be a nice to have indeed, however it is low priority compared to getting the new piwik.js with the perfect api and tests cases. Concerning the overhead added by plugin detection, I would think that the overhead of download/outlink tracking is much bigger especially on pages with 200+ links. |
I would also love to see the Silverlight’s… |
Hmm, may it wouldn’t be difficult for you to add plugins’ version detection?
I found: http://www.builtfromsource.com/2007/06/26/detecting-plugins-in-internet-explorer-and-a-few-hints-for-all-the-others/
Just adapt your tracker’s code and implement additional functionality in back-end, please. ;]
The text was updated successfully, but these errors were encountered: