Closed Bug 1207252 Opened 9 years ago Closed 3 years ago

Investigate: Do NS_XPCOM_CURRENT_PROCESS_DIR and Context.getApplicationInfo().dataDir always point to the same writable path?

Categories

(Firefox for Android Graveyard :: General, defect)

All
Android
defect
Not set
normal

Tracking

(firefox44 affected)

RESOLVED INCOMPLETE
Tracking Status
firefox44 --- affected

People

(Reporter: sebastian, Unassigned)

References

Details

In bug 1197717 we added support for loading fonts from NS_XPCOM_CURRENT_PROCESS_DIR/fonts to later download fonts to that directory from Java. But there are some open questions that need further investigation and testing:

* Do NS_XPCOM_CURRENT_PROCESS_DIR and Context.getApplicationInfo().dataDir always point to the same direction? -> How does nsDirectoryService resolve that constant to the actual path (on Android)?

* Can it happen that this directory is readable-only?

* Are we facing any problems if the app is installed in /systems/app?
Note: nsHyphenationManager is loading hyphenation dictionaries from NS_XPCOM_CURRENT_PROCESS_DIR/hyphenation:

https://dxr.mozilla.org/mozilla-central/source/intl/hyphenation/glue/nsHyphenationManager.cpp?offset=100#161-171
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.