Last modified: 2010-05-15 15:38:50 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 1480 - Classic skins displayed as XML tree in Firefox with XHTML content-type
Classic skins displayed as XML tree in Firefox with XHTML content-type
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Interface (Other open bugs)
1.5.x
Macintosh Mac OS X 10.3
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks: html
  Show dependency treegraph
 
Reported: 2005-02-06 14:43 UTC by Brion Vibber
Modified: 2010-05-15 15:38 UTC (History)
0 users

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


Attachments

Description Brion Vibber 2005-02-06 14:43:49 UTC
With $wgMimeType = 'application/xhtml+xml' set to send browsers into 
strict XML parsing mode, Firefox 1.0 seems to get confused on the classic 
skins (tested Classic and Cologne Blue): it shows the 'This XML file does not 
seem to have style information associated with it' and shows a node tree.

MonoBook displays correctly with this setting, so there must be some 
difference in the markup that triggers the different behavior.

Classic seems to work fine in Safari 1.2.4, so this may be a Mozilla bug or it 
may be a Safari bug in showing the styles. ;)
Comment 1 Tom Gilder 2005-02-07 14:03:18 UTC
Was a MediaWiki bug, wasn't sending the correct xmlns attribute. Fixed in HEAD and 1.4.

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


Navigation
Links