373 bytes, text/html
Turns out this is caused by misusing the value returned from nsIDOMSettingsManager.createLock() which returns an nsIDOMSettingsLock object and not a DOMRequest one (which would have the |onerror| property).
blocking-b2g: --- → leo?
Summary: The wifi switch remains grayed out when hitting a mozSettings error upon turning wifi on → The wifi switch remains grayed out when hitting an error upon turning wifi on
Created attachment 745892 [details] Pointer to Github pull request: https://github.com/mozilla-b2g/gaia/pull/9572/files Pointer to Github pull-request
Attachment #745892 - Flags: review?(kaze)
status-b2g18: --- → affected
status-b2g18-v1.0.1: --- → wontfix
Triage 5/8 - leo+ because when the bug is hit, wifi is unusable and recovery is not easy.
blocking-b2g: leo? → leo+
Comment on attachment 745892 [details] Pointer to Github pull request: https://github.com/mozilla-b2g/gaia/pull/9572/files Moving the review to Alive, as he originally reviewed this code in bug 859993
Attachment #745892 - Flags: review?(kaze) → review?(alive)
Comment on attachment 745892 [details] Pointer to Github pull request: https://github.com/mozilla-b2g/gaia/pull/9572/files r=me, my previous review failed :/ Thanks!
Attachment #745892 - Flags: review?(alive) → review+
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Uplifted 3f766bccdd9c0961b33f2085089c1f575143bd8b to: v1-train: 913769b05882bb4faa448604b7fc6ea2e06c9c2d
status-b2g18: affected → fixed
Flags: in-moztrap? → in-moztrap+
QA Contact: amiller
You need to log in before you can comment on or make changes to this bug.