Open Bug 1330816 Opened 3 years ago Updated 3 months ago
users cannot delete synced tabs from synced tabs tab
Users look for delete button within synced tab list. Users cannot find it and there is no link to get them to the preferences item where they can complete the operation. They should be able to complete the operation right there.
Unfortunately, I suspect this will be a WONTFIX, but I've CCed Ryan for comment. Enabling tab sync will sync all open tabs; Sync doesn't offer per-tab or per-window controls. Think of synced tabs as a read-only list of all your tabs on all your devices. The way to "delete" a synced tab is to close that tab on the device that currently has it open, or use a private window. This matches how iCloud and Chrome Sync work. A delete button for synced tabs would be quite tricky to get right. For example, what happens if the first device syncs again, and still has the tab open? What if that tab is closed and reopened; should we still not sync it? Would deleting a synced tab close that tab on the original device? Other devices?
OK fair enough but don't just leave the user hunting all over the place trying to find the delete button. At least have some question mark he can click on that leads him somewhere...
Believe it or not, iCloud does support this in the customizable toolbar item you can drog into the toolbar. I've asked about it, but apparently it's not feasible given the current Sync infrastructure.
(drog => drag)
This is of course (technically) possible and would be a big advantage Usecase for me is: - On the move I read Google+, open some links in Firefox Android / Fennec - At home I realize many tabs (> 30) are open and I prefer to read on a big screen - I open "Synced Tabs" and start reading - Since I do not read Tabs in order I have to use my Smartphone additionally to close the Tabs I read one by one
(In reply to Kit Cambridge (he/him) [:kitcambridge] (UTC-7) from comment #1) > Would deleting a synced tab close that tab on the original device? Bug 1029308 suggests yes.
You need to log in before you can comment on or make changes to this bug.