Last modified: 2014-04-29 17:40:45 UTC
Reportedly, OOjs fails to load on Mozilla Camino 2.1.2 when loaded as a Component of MediaViewer, with the error "Module oojs has failed dependencies". Reported here: https://www.mediawiki.org/w/index.php?title=Talk%3AMultimedia%2FAbout_Media_Viewer&oldid=984398#Media_Viewer_problems Maybe related to the .super issue (bug 63303)?
Camino is deprecated and should not be used anymore, according to Camino's website: http://caminobrowser.org/ "After a decade-long run, Camino is no longer being developed, and we encourage all users to upgrade to a more modern browser. Camino is increasingly lagging behind the fast pace of changes on the web, and more importantly it is not receiving security updates, making it increasingly unsafe to use." Recommend wontfix?
This browser is sufficiently old that feature detection or ES5 shim is out of the question. This is the kind of browser in the category of: We don't want to serve javascript of any kind as our baseline support (not to mention edge feature projects like OOjs, but baseline support) has surpassed the level that this browser can support. If anything, we should blacklist this browser in the startup module of MediaWiki core. Though I think this browser is obscure enough that it doesn't justify space in our global initialisation footprint (we don't blacklist Netscape either..)
MW is roughly meant to target "full compatibility" for browsers with > ~2.5% usage, "basic compatibility" for browsers with ~2.5% > x > 0.1% of usage, and everything else is just happenstance. Camino is so far below our support standard that we can't even justify blacklist it, so I agree with Timo that it's just a WONTFIX.
