Stop using LWTPersister on Android
Categories
(WebExtensions :: Themes, defect)
Tracking
(firefox68 verified)
| Tracking | Status | |
|---|---|---|
| firefox68 | --- | verified |
People
(Reporter: kmag, Assigned: kmag)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
| Assignee | ||
Updated•7 years ago
|
| Assignee | ||
Comment 1•7 years ago
|
||
The Android front-end cannot directly load moz-extension: URIs, which means
that theme resources ordinarily loaded via extension URIs need to be handled
some other way.
Prior to this patch, we used the antiquated LightweightThemePersister logic to
copy those resources to external files and load them as file: URIs. This is
unideal for a number of reasons, not least that it requires that we keep
around over-complicated logic which was initially designed to persist theme
images from web URLs.
This patch instead just resolves any substituting protocol handler URI to the
underlying resource URI, which will be either a file: or jar: URI which Java
can handle directly.
Comment 2•7 years ago
|
||
Yes, this sound better than what I came up with, thank you.
| Assignee | ||
Comment 3•7 years ago
|
||
Comment 4•7 years ago
|
||
| bugherder | ||
Comment 5•7 years ago
|
||
Will this fix require manual validation? If yes, please provide a few steps to correctly test it and set the "qe-verify+" flag. Thanks!
| Assignee | ||
Comment 6•7 years ago
|
||
Just need to test that themes with header images still work.
Comment 7•7 years ago
|
||
Verified as Fixed on Nightly 68.0a1 for Android using several themes containing header images.
Description
•