Last modified: 2009-07-29 22:45:55 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 6274 - skin setting changing to 'simple' after saving unrelated settings
skin setting changing to 'simple' after saving unrelated settings
Product: MediaWiki
Classification: Unclassified
User preferences (Other open bugs)
PC Windows XP
: Low minor (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2006-06-11 11:07 UTC by MiG
Modified: 2009-07-29 22:45 UTC (History)
2 users (show)

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


Description MiG 2006-06-11 11:07:48 UTC
The 'MonoBook' skin (claiming to be the default skin) changes to the 'simple'
one after saving settings, without even having looked at the 'skins' section.

Found this one out after validating my email-address for half a dozen wiki
projects this morning (en/, en/,, then ticking the 'disable email from
other users' box (and saving) - each wiki mentioned displays this behaviour.

Browser: Firefox
Comment 1 MiG 2006-06-11 12:36:00 UTC
Just repeated this with and Internet Explorer
(6.0.2900.2180.xpsp_sp2_gdr.050301-1519) and this combination does not display
said behaviour. I suppose it's Firefox specific.
Comment 2 Niklas Laxström 2009-07-29 18:28:04 UTC
Works for me, please reopen if you can still reproduce it.
Comment 3 MiG 2009-07-29 22:45:55 UTC
That was three years ago :)
Can't reproduce it either at present. I assume that whatever bit of code caused it, has at some point been rewritten. Or one of the many firefox updates released since solved it...

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