Closed Bug 1205011 Opened 9 years ago Closed 3 years ago

Make FxAccountsWebChannel.jsm react to changing fxa-content-server prefs

Categories

(Firefox for Android Graveyard :: General, defect)

defect
Not set
normal

Tracking

(firefox43 affected)

RESOLVED INCOMPLETE
Tracking Status
firefox43 --- affected

People

(Reporter: nalexander, Unassigned, NeedInfo)

References

Details

On day one, the code from Bug 1191064 won't handle changing the fxa-content-server prefs.  That freezes out self-hosters.  This ticket tracks listening for Gecko pref changes and updating the WebChannel binding; and possibly killing about:accounts tabs that might be in-flight and suddenly not have a WebChannel backing them.
vivek: this might be interesting.  Use a pref watcher (like at https://dxr.mozilla.org/mozilla-central/source/mobile/android/chrome/content/SelectionHandler.js#108) to observe the relevant pref, and tear-down and re-initialize the WebChannel registration when necessary.
Flags: needinfo?(vivekb.balakrishnan)
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.