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 T11488, the corresponding Phabricator task for complete and up-to-date bug report information.

Bug 9488 - optimize js/css output

Summary:	optimize js/css output

Status: RESOLVED WONTFIX Product: MediaWiki Classification: Unclassified Component: General/Unknown (Other open bugs) Version: unspecified Hardware: All All Importance: Lowest enhancement (vote) Target Milestone: --- Assigned To: Nobody - You can work on this! URL: http://phpclasses.mkdata.net/browse/p... Whiteboard: Keywords: Depends on: Blocks:   Show dependency tree / graph		Reported: 2007-04-03 20:06 UTC by Carl Fürstenberg Modified: 2007-04-03 20:13 UTC (History) CC List: 0 users See Also: Web browser: --- Mobile Platform: --- Assignee Huggle Beta Tester: ---

Attachments Add an attachment (proposed patch, testcase, etc.)

Description Carl Fürstenberg 2007-04-03 20:06:33 UTC The question I have is: Would the code-size reduction by using something similar to GzOutput, on mainly js/css, result in a net gain of performance/bandwidth throughput? If so I propose to implement/use the package linked. Comment 1 Rob Church 2007-04-03 20:08:41 UTC We already use output compression, where supported by the browser and web server. Comment 2 Carl Fürstenberg 2007-04-03 20:10:22 UTC I know you have compression, I was thinking more to remove comments and whitespaces and such things also. Comment 3 Rob Church 2007-04-03 20:13:15 UTC (See previous discussion on wikitech-l)