Closed Bug 571409 Opened 14 years ago Closed 13 years ago

Add Account Manager support to Firefox

Categories

(Firefox Graveyard :: Account Manager, defect)

defect
Not set
normal

Tracking

(blocking2.0 -)

RESOLVED WONTFIX
Tracking Status
blocking2.0 --- -

People

(Reporter: hello, Unassigned)

References

()

Details

Attachments

(7 files, 29 obsolete files)

8.37 KB, patch
Details | Diff | Splinter Review
23.77 KB, patch
Details | Diff | Splinter Review
19.23 KB, patch
Margaret
: feedback+
Details | Diff | Splinter Review
26.42 KB, patch
Details | Diff | Splinter Review
4.29 KB, patch
philikon
: feedback+
Details | Diff | Splinter Review
31.52 KB, patch
Details | Diff | Splinter Review
19.67 KB, patch
ehsan.akhgari
: feedback+
Details | Diff | Splinter Review
Tracking bug for adding Account Manager to Firefox.
Depends on: 571411
Depends on: 571412
Depends on: 571413
Depends on: 571414
Depends on: 571418
Component: General → Account Manager
QA Contact: general → account.manager
Depends on: 575883
Depends on: 564044
Depends on: 575884
Depends on: 575885
Requesting blocking for Firefox 4.
blocking2.0: --- → ?
Final or are you hoping to get this into one of the betas Dan?
With such a large new feature like the Account Manager, it should probably go through at least one beta release before the RCs and final.
We are currently targeting the end of August for landing the final bits, though it will be in multiple patches so some features (e.g. sign in/out) should land earlier.
We can approve patches, but at this time I'm not comfortable blocking on the feature based on schedule. That should not be taken as a statement about not wanting the feature, just about keeping focus on issues that would actually block the release at this time.

We can renominate when we have a better understanding of how close we are on the specific bugs being used to track the Account Manager feature.
blocking2.0: ? → -
Attached patch super diff -U8 40686b8e0b04 (obsolete) — Splinter Review
Initial implementation that has UI/functionality to sign in for saved accounts and sign out.
Attachment #466429 - Flags: feedback?(gavin.sharp)
Attached patch startup glue 8e574050bd89 (obsolete) — Splinter Review
Attachment #466429 - Attachment is obsolete: true
Attachment #467877 - Flags: review?(gavin.sharp)
Attachment #466429 - Flags: feedback?(gavin.sharp)
Attached patch ui bits 8e574050bd89 (obsolete) — Splinter Review
Attachment #467878 - Flags: review?(gavin.sharp)
Attachment #467879 - Flags: review?(gavin.sharp)
Attached patch helper classes 8e574050bd89 (obsolete) — Splinter Review
Attachment #467882 - Flags: review?(gavin.sharp)
Attached patch core service 8e574050bd89 (obsolete) — Splinter Review
Attachment #467883 - Flags: review?(gavin.sharp)
Attachment #467884 - Flags: review?(gavin.sharp)
Attached patch mochitest 8e574050bd89 (obsolete) — Splinter Review
Attachment #467885 - Flags: review?(gavin.sharp)
Awesome to see this pulling together. Have you guys got a tryserver run that you can run through compare-talos to get us some early idea of performance impact?
Gavin: For the service files it may be useful to check in order:

1) helper classes
2) core service

Then the ui bits for firefox integration and profile-specific:

3) ui bits
4) user/pass form profile

Then various other patches can be somewhat individually looked at:

5) startup glue
6) header parser + generated
7) mochitest
Attached patch helper b2ce53f22083 (obsolete) — Splinter Review
Attachment #467882 - Attachment is obsolete: true
Attachment #468233 - Flags: review?(gavin.sharp)
Attachment #467882 - Flags: review?(gavin.sharp)
Attached patch service b2ce53f22083 (obsolete) — Splinter Review
Attachment #467883 - Attachment is obsolete: true
Attachment #468234 - Flags: review?(gavin.sharp)
Attachment #467883 - Flags: review?(gavin.sharp)
Attached patch ui b2ce53f22083 (obsolete) — Splinter Review
Attachment #467878 - Attachment is obsolete: true
Attachment #467878 - Flags: review?(gavin.sharp)
Attached patch profile b2ce53f22083 (obsolete) — Splinter Review
Attachment #467879 - Attachment is obsolete: true
Attachment #468236 - Flags: review?(gavin.sharp)
Attachment #467879 - Flags: review?(gavin.sharp)
Attached patch startup b2ce53f22083 (obsolete) — Splinter Review
Attachment #467877 - Attachment is obsolete: true
Attachment #468237 - Flags: review?(gavin.sharp)
Attachment #467877 - Flags: review?(gavin.sharp)
Attached patch parser b2ce53f22083 (obsolete) — Splinter Review
Attachment #467884 - Attachment is obsolete: true
Attachment #468238 - Flags: review?(gavin.sharp)
Attachment #467884 - Flags: review?(gavin.sharp)
Attached patch test b2ce53f22083 (obsolete) — Splinter Review
Attachment #467885 - Attachment is obsolete: true
Attachment #468239 - Flags: review?(gavin.sharp)
Attachment #467885 - Flags: review?(gavin.sharp)
Attachment #468235 - Flags: review?(gavin.sharp)
Depends on: 578406
No longer depends on: 578406
I pushed several runs of Ts to maple with some baseline of the pre-merged changeset:

(platform: 2 base runs, 4 merged runs, %overhead)

linux:   b456 b455 472 464 472 483 3.7%
linux64: b429 b419 434 434 441 431 2.6%
os x:    b660 b663 660 672 672 658 0.6%
os x64:  b715 b787 793 806 801 799 1.6%
winxp:   b348 b341 359 361 360 359 4.4%
win7:    b454 b448 450 461 460 464 1.7%
Do we know what's consuming so much time on startup on XP and Linux? Or do we at least have an idea?
I don't have a specific answer, but we do have some juicy targets for Ts speedup.  There are a couple of things we do right now that we shouldn't, and they possibly affect Linux and XP more than the rest - I don't know the platform differences well enough to say.
Attached patch helper c8672a625590 (obsolete) — Splinter Review
Attachment #468233 - Attachment is obsolete: true
Attachment #468722 - Flags: review?(gavin.sharp)
Attachment #468233 - Flags: review?(gavin.sharp)
Attached patch service c8672a625590 (obsolete) — Splinter Review
Attachment #468234 - Attachment is obsolete: true
Attachment #468723 - Flags: review?(gavin.sharp)
Attachment #468234 - Flags: review?(gavin.sharp)
Attached patch ui c8672a625590 (obsolete) — Splinter Review
Attachment #468235 - Attachment is obsolete: true
Attachment #468724 - Flags: review?(paul)
Attachment #468235 - Flags: review?(gavin.sharp)
Attached patch profile c8672a625590 (obsolete) — Splinter Review
Attachment #468236 - Attachment is obsolete: true
Attachment #468725 - Flags: review?(paul)
Attachment #468236 - Flags: review?(gavin.sharp)
Attached patch makefile c8672a625590 (obsolete) — Splinter Review
Attachment #468237 - Attachment is obsolete: true
Attachment #468726 - Flags: review?(dolske)
Attachment #468237 - Flags: review?(gavin.sharp)
Attached patch parser c8672a625590 (obsolete) — Splinter Review
Attachment #468238 - Attachment is obsolete: true
Attachment #468728 - Flags: review?(dolske)
Attachment #468238 - Flags: review?(gavin.sharp)
Attached patch test c8672a625590 (obsolete) — Splinter Review
Attachment #468239 - Attachment is obsolete: true
Attachment #468730 - Flags: review?(dolske)
Attachment #468239 - Flags: review?(gavin.sharp)
I reran the Ts tests (5 times) with the removal of the xpcom component and moved startup to the browser delayed startup:

linux: 2.1%
lin64: 2.4%
macos: 0.5%
mac64: 2.2%
winxp: 2.9%
win 7: 0.3%
Depends on: 581560
Depends on: 589362
Attached patch helper af9c96341d4c (obsolete) — Splinter Review
Attachment #468722 - Attachment is obsolete: true
Attachment #469382 - Flags: review?
Attachment #468722 - Flags: review?(gavin.sharp)
Attached patch service af9c96341d4c (obsolete) — Splinter Review
Attachment #468723 - Attachment is obsolete: true
Attachment #469383 - Flags: review?
Attachment #468723 - Flags: review?(gavin.sharp)
Attached patch ui af9c96341d4c (obsolete) — Splinter Review
Attachment #468724 - Attachment is obsolete: true
Attachment #469384 - Flags: review?
Attachment #468724 - Flags: review?(paul)
Attached patch profile af9c96341d4c (obsolete) — Splinter Review
Attachment #468725 - Attachment is obsolete: true
Attachment #469386 - Flags: review?
Attachment #468725 - Flags: review?(paul)
Attached patch makefile af9c96341d4c (obsolete) — Splinter Review
Attachment #468726 - Attachment is obsolete: true
Attachment #469387 - Flags: review?
Attachment #468726 - Flags: review?(dolske)
Attached patch parser af9c96341d4c (obsolete) — Splinter Review
Attachment #468728 - Attachment is obsolete: true
Attachment #469388 - Flags: review?
Attachment #468728 - Flags: review?(dolske)
Attached patch test af9c96341d4c (obsolete) — Splinter Review
Attachment #468730 - Attachment is obsolete: true
Attachment #469389 - Flags: review?
Attachment #468730 - Flags: review?(dolske)
We simplified the ui a bit to get rid of the inline svg/clip-path and reran Ts:

From 2 base and 6 test runs (5 test runs for windows as it's still building..):

linux: 1.7%
lin64: 2.4%
macos: 0.2%
mac64: 2.0%
winxp: 1.3%
win 7: 0.5%

That's an average of 1.35% across all 6 platforms, but we're probably hitting noise on some of the platforms, so that might not be totally accurate.
Attachment #469382 - Attachment is obsolete: true
Attachment #471257 - Flags: feedback?(sdwilsh)
Attachment #469382 - Flags: review?
Attachment #469383 - Attachment is obsolete: true
Attachment #471258 - Flags: feedback?(sdwilsh)
Attachment #469383 - Flags: review?
Attached patch ui f47972d05473Splinter Review
Attachment #469384 - Attachment is obsolete: true
Attachment #471259 - Flags: feedback?(sdwilsh)
Attachment #469384 - Flags: review?
Attachment #469386 - Attachment is obsolete: true
Attachment #471260 - Flags: feedback?(sdwilsh)
Attachment #469386 - Flags: review?
Attachment #469387 - Attachment is obsolete: true
Attachment #471261 - Flags: feedback?(sdwilsh)
Attachment #469387 - Flags: review?
Attachment #469388 - Attachment is obsolete: true
Attachment #471262 - Flags: feedback?(sdwilsh)
Attachment #469388 - Flags: review?
Attachment #469389 - Attachment is obsolete: true
Attachment #471263 - Flags: feedback?(sdwilsh)
Attachment #469389 - Flags: review?
Comment on attachment 471259 [details] [diff] [review]
ui f47972d05473

The popup notifications bit looks like it makes sense to me, although I'm not an expert :) However, for css rules using the popup notification id, you should be aware of bug 591026, which appends "-notification" to the id you supply when building the notification.

Also, this patch may eventually cause a conflict with bug 567814 and bug 588309, which are moving save password behavior to popup notifications.
Comment on attachment 471263 [details] [diff] [review]
test f47972d05473

I took a look at the sjs files and the tests in general.  They all looked sane to me, but I don't know anything about how the account manager works, so this feedback should be taken with a grain of salt.
Attachment #471263 - Flags: feedback+
Comment on attachment 471261 [details] [diff] [review]
makefile f47972d05473

Nit: license header copied w/o updating the info ;)

>+DIRS = \
>+  browser
>+  $(NULL)

You're missing browser/Makefile.in. Looks good otherwise.
Attachment #471261 - Flags: feedback+
Comment on attachment 471259 [details] [diff] [review]
ui f47972d05473

Oops, missed the feedback flag!
Attachment #471259 - Flags: feedback+
Blocks: 631042
No longer blocks: 569993
Attachment #471257 - Flags: feedback?(sdwilsh)
Attachment #471258 - Flags: feedback?(sdwilsh)
Attachment #471259 - Flags: feedback?(sdwilsh)
Attachment #471260 - Flags: feedback?(sdwilsh)
Attachment #471261 - Flags: feedback?(sdwilsh)
Attachment #471262 - Flags: feedback?(sdwilsh)
Attachment #471263 - Flags: feedback?(sdwilsh)
I talked with thunder today, and this is going to be changing.  With that being said, whoever ends up actually implementing this should chat with me about approaches since I'm *very* likely to be on the hook for reviews.
We're changing direction and putting the previous Account Manager protocol on hold for a while. Closing these bugs to reflect reality.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
Product: Firefox → Firefox Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: