Last modified: 2008-11-20 00:41:35 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 T18379, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 16379 - Core Javascript (wikibits.js, ajax.js, etc.) should not be loaded from different server
Core Javascript (wikibits.js, ajax.js, etc.) should not be loaded from differ...
Status: RESOLVED INVALID
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Normal major (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-11-18 06:59 UTC by Lupo
Modified: 2008-11-20 00:41 UTC (History)
0 users

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


Attachments

Description Lupo 2008-11-18 06:59:39 UTC
Someone changed the setup such that the core Javascript files such as wikibits.js, ajax.js, ajaxwatch.js, etc. are now loaded from http://upload.wikimedia.org. While I can understand the desire to centralize things, this is a bad idea. It breaks for all people surfing with off-site scripts disabled. Since these scripts provide essential functionality, they really should be loaded from the same server as the page itself.

Please revert this change.
Comment 1 Splarka 2008-11-18 07:11:29 UTC
Site configuration change on WMF, not a software change, adjusting component field.
Comment 2 Brion Vibber 2008-11-20 00:41:35 UTC
If you choose to break HTML standard by disabling offsite scripts, you'll find a lot of the net doesn't work. Offsite scripts are already used for cross-wiki sharing, maps, etc, and are required for any sort of data interchange. We'll only see more of that in the future.

Now, if you just want to disable scripts, you can continue to get the no-script experience which will be missing some extra goodies but should still basically work.

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


Navigation
Links