Closed Bug 1587228 Opened 5 years ago Closed 3 years ago

Remove support for "old" sendtab clients.

Categories

(Firefox :: Sync, enhancement, P3)

enhancement

Tracking

()

RESOLVED FIXED
92 Branch
Tracking Status
firefox92 --- fixed

People

(Reporter: markh, Assigned: teshaq)

Details

Attachments

(1 file)

All our mobile browsers support "new" send tab and supporting "old" sendtab adds complexity leading to bugs like bug 1587227.

ni? Ana to tell us when we should pull the trigger (I assume after we migrate Fennec users to Fenix).

Flags: needinfo?(amedinac)

(In reply to Edouard Oger [:eoger] from comment #1)

ni? Ana to tell us when we should pull the trigger (I assume after we migrate Fennec users to Fenix).

Oops, my bad, I thought Fennec already moved to the new system. I agree we can't do this for some time, so I'll take the ni? off Ana, then add it back in a few months :)

Flags: needinfo?(amedinac)

After discussing this with Ana, the rough timeline for this is around September 2020 based on current Fennec/Fenix schedule. However that can change at any point.

Priority: -- → P3

ni? myself to provide a bit more context on how to actually do this

Flags: needinfo?(rfkelly)

The place to start for this bug is in the sendTabToDevice function, which is what gets invoked from browser UI in Desktop when sending a tab. If you step through the code in that function, you'll see that it first tries to send the tab via FxA device commands, and if that doesn't work then it sends via Sync.

The smallest fix for this issue is to just delete the second part where it falls back to Sync.

If you enjoy deleting code, one could also track down the code for Weave.Service.clientsEngine.sendURIToClientForDisplay and fully delete it from there as well, since I don't believe it will ever be used again for anything else.

Flags: needinfo?(rfkelly)
Assignee: nobody → teshaq
  • Removes the fallback to the old sent-tab
  • Deletes the api to send URIs using commands
  • Modifies tests that depended on that api to now use
    other commands, namely the wipeEngine command
Pushed by teshaq@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/0a18936814a7
Removes support for old send-tab clients. r=markh

Oof, sorry Tarik, looks like some test bustage here. We'll need to see if we can repro those test failures locally, then make sure we get a clean run on the try servers before attempting to land this again.

We'll need to see if we can repro those test failures locally

FYI, something like ./mach test ./browser/base/content/test/sync/ should be able to run just the subset of tests of interest, for faster debugging.

Apologies!!! That was my bad - I should have looked more carefully at other tests. I wasn't aware of those tests.

For context here's what went wrong:

The tests in browser/base/content/test/sync/ include test cases that test old send tab clients. The tests expect that those clients show up in popups and such. With my patch, we remove support for old clients, so those clients will not show up in the popups.

I'll fix the tests right away.

Flags: needinfo?(teshaq)

https://treeherder.mozilla.org/jobs?revision=3b16659cf078a640747ebdea93dfd5f620e05d37&repo=try

There are a few failures, but they all seem unrelated to send-tab and sync, there's the browser/base/content/test/tabcrashed/browser_aboutRestartRequired_buildid.js that is also unrelated, but I don't see an issue filed for it. I can repro the failure with a clean build though, so it's unrelated to the change

Pushed by teshaq@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/5738d1a06fe6
Removes support for old send-tab clients. r=markh
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 92 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: