Last modified: 2010-05-15 15:51:53 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 10203 - Site js inclusion error
Site js inclusion error
Product: MediaWiki
Classification: Unclassified
Interface (Other open bugs)
All All
: High enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2007-06-09 02:00 UTC by Ekin
Modified: 2010-05-15 15:51 UTC (History)
0 users

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


Description Ekin 2007-06-09 02:00:03 UTC
I noticed this on wikipedia's html sources. You can see this line at the top of every page:

<script type="text/javascript" src="/w/index.php?title=-&amp;action=raw&amp;gen=js"><!-- site js --></script>

this should return raw text of "MediaWiki:Common.js" but since it's linked wrong, it returns the page about "-".

That's because the link itself is html encoded somehow.


should have been


that way it works.
Comment 1 Aryeh Gregor (not reading bugmail, please e-mail directly) 2007-06-10 01:48:28 UTC
You're mistaken.  & in URLs must be HTML-encoded when used in HTML.  Any occurrence of & in HTML that's not part of a character entity is invalid (okay, unless in CDATA or a comment or whatever).  You can fairly easily verify that the JavaScript page is in fact being included on Wikipedia.
Comment 2 Ekin 2007-06-10 02:40:16 UTC
I noticed after filing the bug report so i tagged it as "INVALID". You're right, it works just fine.

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