Open Bug 932015 Opened 6 years ago Updated 6 years ago

Ship branding favicon inside Android resources

Categories

(Firefox for Android :: Favicon Handling, defect)

27 Branch
All
Android
defect
Not set

Tracking

()

People

(Reporter: rnewman, Unassigned)

References

(Blocks 1 open bug)

Details

We load

jar:jar:file:///data/app/org.mozilla.fennec_rnewman-1.apk!/assets/omni.ja!/chrome/chrome/content/branding/favicon64.png

from the JAR on startup. Then we write it into the DB, from which we load it every time we start.

We should be doing something smarter, like loading it from resources.
Sigh.  Until Bug 928151 lands, this is going to be ugly.  But:

Add the favicon{32,64}.png files to ANDROID_GENERATED_RESFILES in m/a/b/moz.build.  Duplicate the icon .png logic in Makefile.in to install the files from branding into $OBJDIR/m/a/b/res.  Hate yourself.
Note that on a shitty Moto RAZR XT910 with Android 2.3, fetching the icon from the JAR takes 4msec. Loading from resources is unlikely to be a giant win…
Blocks: 999920
Component: General → Favicon Handling
You need to log in before you can comment on or make changes to this bug.