553443 - Consider stripping useless chrome files from our jars

Status: RESOLVED INCOMPLETE

(Camino Graveyard :: General, defect)

Description

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

There's a lot of things in mozapps/ (and sometimes passwordmgr/) in our jars that's clearly only applicable to toolkit apps.  Some of it is stuff that shouldn't even be packaged for us (bug 553438 and bug 553436)!

We'd need viewsource/ and at least the locale file for places/ (which is not in mozapps) (and possibly plugins/, depending on whether plugins/ actually works); other domains would require more selective pruning--but there's possibly a lot of low-hanging dead weight to strip.  Not sure how much space it would save to be worth it or not.

Comment 1

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

(In reply to comment #0)
> Some of it is stuff that
> shouldn't even be packaged for us (bug 553438 and bug 553436)!

Those bugs are probably going to be WONTFIXed, alas :-(

> other domains would require more selective pruning--but there's possibly a lot
> of low-hanging dead weight to strip.  Not sure how much space it would save to
> be worth it or not.

There's about half a meg (of a 2 MB toolkit.jar) in passwordmgr/ and mozapps/, so it's probably worth doing this.

In addition, comm.jar consists entirely of a cookie dialogue we don't use, and <marquee> support.  We should just pack the marquee files in toolkit.jar (like is done already on 1.9.3) and register them using our pinstripe/jar.mn.