Closed Bug 1250527 Opened 4 years ago Closed 4 years ago
[Sync Tabs Sidebar] Sidebar and panel "sync now" buttons should use the same terminology
58 bytes, text/x-review-board-request
[Sync Tabs] has "Sync Now" as a sync option and the same option in [Sync Tabs Sidebar] is called Refresh. The UI should be kept similar as much as possible for usability sake since it's basically the same feature from sync point of view. Another note here against using "Refresh" as a label for sync in this case is that when you sync the Sync Tabs Sidebar you do it vs the cloud and not actually versus another device/machine. The user might be mislead to think that pressing Refresh will bring the new tabs he changed on the target machine without syncing before the target. Therefore, for the above reasons I would suggest at least renaming the "Refresh" option from Sync Sidebar to "Sync Now".
Ryan, thoughts on this?
Summary: [Sync Tabs Sidebar] Sidebar should be aligned with Sync Tabs on labels used for the same elements → [Sync Tabs Sidebar] Sidebar and panel "sync now" buttons should use the same terminology
On Mac, I see "Refresh List" and I agree that "Sync Now" is better. Good catch Adrian!
Ryan, should this block the sidebar riding the trains? It's possible we can uplift since it doesn't introduce a new string change.
Priority: -- → P2
This is definitely NOT a blocker.
Assignee: nobody → kcambridge
Status: NEW → ASSIGNED
Review commit: https://reviewboard.mozilla.org/r/38001/diff/#index_header See other reviews: https://reviewboard.mozilla.org/r/38001/
Attachment #8726450 - Flags: review?(markh)
Comment on attachment 8726450 [details] MozReview Request: Bug 1250527 - Use the "Sync Now" string in the Synced Tabs sidebar. r=markh https://reviewboard.mozilla.org/r/38001/#review34567
Attachment #8726450 - Flags: review?(markh) → review+
verified fixed on: Version 47.0a1 Build ID 20160307030208 / Mozilla/5.0 (X11; Linux i686; rv:47.0) Gecko/20100101 Firefox/47.0 Also verified on windows10 and MacOsX.
You need to log in before you can comment on or make changes to this bug.