Last modified: 2010-06-07 14:17:57 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T25296, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 23296 - Iceweasel user-agent
Iceweasel user-agent
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
UsabilityInitiative (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Trevor Parscal
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-04-23 12:09 UTC by Liangent
Modified: 2010-06-07 14:17 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Liangent 2010-04-23 12:09:55 UTC
Currently Iceweasel is not treated as a UsabilityInitiative-compatible user-agent, according to my test on http://prototype.wikimedia.org/s-6/index.php , though it's built from Firefox's source, and a "like Firefox" tag exists in its user-agent line.

Maybe we can check "Gecko" instead of "Firefox" in browser feature check.
Comment 1 Trevor Parscal 2010-04-23 17:15:08 UTC
If we know it to be compatible or not, we should just add it to our tables. Our compatibility tables are only meant to be exclusive to browsers we are actually testing - all other user agents are treated as 100% working.
Comment 2 Roan Kattouw 2010-04-23 17:53:57 UTC
Iceweasel is the same software as Firefox, it just has a different name and logo, so we should be fine there.
Comment 3 Ævar Arnfjörð Bjarmason 2010-04-23 20:43:02 UTC
They have a few more patches than that. Here's the patches from Debian testing:

   39 0001-Avoid-wrong-sessionstore-data-to-keep-windows-out-of.patch
   24 0002-Avoid-spurious-Run-items-in-application-handlers-con.patch
   40 0003-Fix-misalignments-in-help-command-line.patch
   25 0004-browser-components-build-Makefile.in-Link-against-ns.patch
   33 0005-Remove-leaktest-files-in-make-clean.patch
   23 0006-Remove-automation.py-in-make-clean.patch
   35 0007-Remove-general.useragent.locale-prefs-from-firefox-..patch
  137 0008-Rename-Firefox-to-Iceweasel.patch
   27 0009-Set-MOZ_APP_NAME-to-iceweasel.patch
   27 0010-Our-name-should-be-Iceweasel-not-Firefox.patch
   24 0011-Set-the-profile-path-explicitly.patch
   58 0012-Replace-APP-with-firefox-in-some-places.patch
   42 0013-Use-googpub-phish-shavar-instead-of-goog-phish-shava.patch
   25 0014-Force-to-not-use-fshort-wchar.patch
  157 0015-Check-less-things-during-configure-when-using-libxul.patch
  716 total

No changes during the rendering engine that I can see. So it's safe to count it as Firefox for usability initiative purposes.
Comment 4 Liangent 2010-04-24 09:54:20 UTC
(In reply to comment #1)
> If we know it to be compatible or not, we should just add it to our tables. Our
> compatibility tables are only meant to be exclusive to browsers we are actually
> testing - all other user agents are treated as 100% working.

But I can only see the traditional edit toolbar there in Iceweasel. Nothing from UsabilityInitiative appears.
Comment 5 Roan Kattouw 2010-06-07 11:20:26 UTC
(In reply to comment #4)
> (In reply to comment #1)
> > If we know it to be compatible or not, we should just add it to our tables. Our
> > compatibility tables are only meant to be exclusive to browsers we are actually
> > testing - all other user agents are treated as 100% working.
> 
> But I can only see the traditional edit toolbar there in Iceweasel. Nothing
> from UsabilityInitiative appears.
Which version of Iceweasel do you use? Could you provide us with the exact User-Agent string your browser sends (or the value of the JavaScript variable navigator.userAgent)?
Comment 6 Liangent 2010-06-07 11:39:34 UTC
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.5) Gecko/20091123 Iceweasel/3.5.8 (like Firefox/3.5.8)
Comment 7 Roan Kattouw 2010-06-07 14:17:57 UTC
Fixed in r67535, will be deployed later today.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links