22406 2013-06-19 13:34:59 +0000 Navigator is not web-compatible due to missing properties 2013-07-09 20:12:16 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#the-navigator-object P3 normal Unsorted 22553 22555 22556 22557 22558 1 contributor ian bzbarsky ian mike contributor oldest_to_newest 89585 0 contributor 2013-06-19 13:34:59 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/timers.html Multipage: http://www.whatwg.org/C#the-navigator-object Complete: http://www.whatwg.org/c#the-navigator-object Referrer: http://www.whatwg.org/specs/web-apps/current-work/multipage/ Comment: Navigator is not web-compatible due to missing properties Posted from: 98.110.194.206 by bzbarsky@mit.edu User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20130606 Firefox/24.0 89588 1 bzbarsky 2013-06-19 13:58:43 +0000 I ran into this when someone tried to rewrite Navigator to "follow the spec". Specifically: 1) navigator.plugins and navigator.mimeTypes are implemented by everyone and required for web compat. 2) navigator.taintEnabled is implemented by everyone except WebKit and required for web compat unless you duplicate some WebKit layout bugs. See <https://bugzilla.mozilla.org/show_bug.cgi?id=679971>. People don't _call_ it; they just check that it exists. Other things that might be issues: * Everyone (Presto, Gecko, Blink, Trident, WebKit) implements navigator.appCodeName, hardcoded to "Mozilla". * Everyone implements navigator.cookieEnabled (though I haven't tested whether they ever return false). * Everyone implements navigator.javaEnabled (though I haven't tested what it does when called). 90230 2 ian 2013-07-03 14:47:06 +0000 See also bug 20665 comment 1. 90306 3 ian 2013-07-04 00:08:08 +0000 navigator.plugins and navigator.mimeTypes seem like a fingerprinting disaster. See discussion in bug 22553. 90512 4 ian 2013-07-09 20:12:16 +0000 Ok, done. Let me know if you find any others that need adding!