Closed Bug 1258912 Opened 8 years ago Closed 5 years ago

Split pwmgr_common.js into separate content and chrome scripts

Categories

(Toolkit :: Password Manager, enhancement, P2)

enhancement

Tracking

()

RESOLVED FIXED
mozilla67
Tracking Status
firefox67 --- fixed

People

(Reporter: MattN, Assigned: MattN)

References

Details

(Whiteboard: [passwords:tech-debt])

Attachments

(3 files)

pwmgr_common.js was made to work in both content and chrome processes in order to ease the incremental transition to all tests running with support for e10s. This makes it a bit messy as functions which are adjacent in the file could be intended for different processes but that's isn't obvious.

We should split the file into content helpers which send messages to the parent when necessary and the chrome code which talks to the login manager.

As much as possible in the chrome code should move to LoginTestUtils.jsm or re-use what's there so we can share common helpers between test suites.

I think it will be easiest to do this once all tests work in e10s so we can see what remaining helpers we actually need since many things are getting cleaned up with rewrites/ports.
Whiteboard: [passwords:tech-debt]
Assignee: MattN+bmo → nobody
Status: ASSIGNED → NEW
Priority: -- → P3
Priority: P3 → P2
Assignee: nobody → MattN+bmo
Status: NEW → ASSIGNED
Pushed by mozilla@noorenberghe.ca:
https://hg.mozilla.org/integration/mozilla-inbound/rev/c7a12059919a
Split pwmgr_common.js into separate content and chrome scripts. r=jaws
https://hg.mozilla.org/integration/mozilla-inbound/rev/0fccec2f53f8
Enable the no-unused-vars eslint rule in pwmgr tests. r=jaws
https://hg.mozilla.org/integration/mozilla-inbound/rev/16803b8b2997
Enable the no-undef rule in pwmgr tests. r=jaws
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla67
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: