Closed
Bug 798844
Opened 12 years ago
Closed 11 years ago
Metro should unfork its old copy of password manager
Categories
(Toolkit :: Password Manager, defect)
Tracking
()
RESOLVED
FIXED
mozilla23
People
(Reporter: rnewman, Assigned: mbrubeck)
References
Details
(Whiteboard: [mvp])
Attachments
(1 file)
(deleted),
patch
|
bbondy
:
review+
|
Details | Diff | Splinter Review |
As observed in Bug 798835: Component returned failure code: 0x80004002 (NS_NOINTERFACE) [nsISupports.QueryInterface] Stack trace: resource://services-sync/engines/passwords.js:84 Relevant code: 84: return Services.logins.QueryInterface(Ci.nsIInterfaceRequestor) .getInterface(Ci.mozIStorageConnection);
![]() |
||
Updated•12 years ago
|
Whiteboard: [metro-mvp?]
Comment 1•12 years ago
|
||
Can someone explain why we need this for v1? What is the impact of having or not having it?
Reporter | ||
Comment 2•12 years ago
|
||
Unless I'm mistaken, passwords won't sync, instead logging an exception.
Comment 3•12 years ago
|
||
Well, that's kind of important :) Blocking the sync tracker for now. If we're going to sync in v1, we should certainly try to sync the passwords.
Blocks: metro-sync
Summary: Password manager doesn't implement mozIStorageConnection on Metro → work - Password manager doesn't implement mozIStorageConnection on Metro
Whiteboard: [metro-mvp?] → [mvp]
Updated•12 years ago
|
No longer blocks: metro-sync
Updated•12 years ago
|
No longer blocks: 849312
Summary: work - Password manager doesn't implement mozIStorageConnection on Metro → Work - Password manager doesn't implement mozIStorageConnection on Metro
Comment 4•11 years ago
|
||
This should be a straightforward fix -- jettison the password mananger fork that came over with fennec/xul, and just use the existing toolkit version. IIRC, the fork was intended to be a temporary measure to get the password manager working in E10S fennec when that was in omgship-mode.
Comment 5•11 years ago
|
||
I'm just going to morph, as my last comment suggests. That will both fix the mozIStorageConnection issue, and allow Metro Firefox to take advantage of significant upcoming password manager changes (856470 and 853549).
Assignee | ||
Comment 6•11 years ago
|
||
We might need some slight changes to our nsILoginManagerPrompter to make sure it implements the correct interface and works with toolkit's nsILoginManager implementation. Or maybe we can use toolkit's prompter code, and just override its strings and use CSS to change the labels and buttons.
Assignee | ||
Comment 7•11 years ago
|
||
I decided to go with the path of least resistance and keep our LoginManagerPrompter for now. We use somewhat different UX for our notifications, and just overriding the toolkit strings would be a pain if we ever want to make changes that require updating the property names. The new code here is copied from toolkit, to bring our LoginManagerPrompter more in line with theirs.
Updated•11 years ago
|
Attachment #731976 -
Flags: review?(netzen) → review+
Assignee | ||
Comment 8•11 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/9437f13fa3d2
Comment 9•11 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/9437f13fa3d2
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla23
Updated•11 years ago
|
Summary: Metro should unfork it's old copy of password manager → Metro should unfork its old copy of password manager
Updated•10 years ago
|
OS: Windows 8 Metro → Windows 8.1
You need to log in
before you can comment on or make changes to this bug.
Description
•