When Accounts are added to the Australis menu panel (http://cl.ly/image/231s1Y1C0b0k) we will need the ability to highlight this item as we do for Add-ons and other items within the menu (http://cl.ly/image/2E1x0t1B0N3A). Question: Will Sync be presented as a separate item in the menu panel, or will it be considered part of Accounts in the UI?

I think Sync is one of the services that FF Account can provide, but currently it's the only service we have. So at least for the first stage Sync is FF account. And the current proposal is place account above "customize" as a non-removable item that take up an entire row in the menu panel.

This is how accounts/sync will be presented in the menu panel. Signed in user - https://www.dropbox.com/s/uu2znj2xn1khbxe/Desktop_Custom_Menu_Signed_In.png Signed out user - https://www.dropbox.com/s/jvtqpr28m353bxh/Desktop_Custom_Menu_Signed_Out.png For specific accounts/sync questions contact Ryan Feeley and John Gruen.

mmaslaney said we can do the same as the Customize target and highlight the glyph. The target name already started with "PanelUI-" so the panel auto-opens when annotating.

To test, set the pref identity.fxaccounts.enabled to true and restart. One thing I just realized is that if a user has non-FxA sync setup and we try to highlight this target, it won't be visible. This may be weird if the messaging on the page relies on it being there. I guess the page will have to checkSyncSetup and only highlight the button if sync is not enabled. agibson, jbertsch: Will that work for you when we start highlighting this?

(In reply to Matthew N. [:MattN] from comment #4) > To test, set the pref identity.fxaccounts.enabled to true and restart. > > One thing I just realized is that if a user has non-FxA sync setup and we > try to highlight this target, it won't be visible. This may be weird if the > messaging on the page relies on it being there. I guess the page will have > to checkSyncSetup and only highlight the button if sync is not enabled. when a user already has old sync, can we remove/replace the sync step entirely, to avoid confusion mentioned above? More ideally, we should just not show the new sync button in the menu to old sync users(but that's a separate bug)

(In reply to Zhenshuo Fang (:fang) - Firefox UX Team from comment #5) > when a user already has old sync, can we remove/replace the sync step > entirely, to avoid confusion mentioned above? Yes, the webpage can do that if they use checkSyncConfiguration and skip the step if sync is setup at all since no user will have new FxA sync upon prior to 29. > More ideally, we should just > not show the new sync button in the menu to old sync users(but that's a > separate bug) The new sync button already only appears if FxA sync is being used.

We should probably add an option to getConfiguration to get the status of fxaccounts too.

Replacing broken links with attachments. How 'Signed In' user and 'Not Signed In' user is represented in menu panel.

(In reply to Blair McBride [:Unfocused] from comment #7) > We should probably add an option to getConfiguration to get the status of > fxaccounts too. I thought about it but didn't think it was necessary for the first usage of UITour for Australis so I figured we can handle that when the need arises.

(In reply to Matthew N. [:MattN] from comment #4) > To test, set the pref identity.fxaccounts.enabled to true and restart. > > One thing I just realized is that if a user has non-FxA sync setup and we > try to highlight this target, it won't be visible. This may be weird if the > messaging on the page relies on it being there. I guess the page will have > to checkSyncSetup and only highlight the button if sync is not enabled. > > agibson, jbertsch: Will that work for you when we start highlighting this? Thanks, Matt. I've enabled the preference and can see the "Sign in to Sync" menu panel. The highlight for "accountStatus" doesn't seem to be working yet, but I think I just need to wait for Nightly to update. As far as checking if sync is already set up, I think using `Mozilla.UITour.getSyncConfiguration` should be fine. We can work out how to deal with the conditional messaging.

(In reply to Zhenshuo Fang (:fang) - Firefox UX Team from comment #5) > when a user already has old sync, can we remove/replace the sync step > entirely, to avoid confusion mentioned above? More ideally, we should just > not show the new sync button in the menu to old sync users(but that's a > separate bug) In the interest of time available before this needs to ship, it might be a better option to show some alternative messaging/highlight a different item if the user already has old sync. Removing an entire step of the tour conditionally might be a push in the time we have left.

Clearing needinfo