1817329 - Don't offer to send more tabs than is possible.

Status: NEW

(Firefox :: Sync, defect, P2)

Description

[Mark Hammond [:markh] [:mhammond]]

From a thread in slack, someone reported trying to send 300 tabs, but ended up rate-limited by the server. Worse, they then got rate-limited, so the feature was entirely broken for some period after that.

That means there is a practical upper-limit on how many tabs can be sent, and that number is effectively a constant. Firefox really shouldn't offer to send more tabs than it can confidently know will fail.

(Tricky part here is UX. Current flow is "Select all tabs" -> "Click 'Send 300 tabs to Device'" - not clear how this flow should change when 300 tabs are selected but our limit is less than that?)

Comment 1

[Mark Hammond [:markh] [:mhammond]]

Will, is it possible to get any insights into how often the invoke_command endpoint finds itself throttled?

Comment 2

[Wil Clouser [:clouserw]]

Attachment: image.png

I'm not an expert here, but guessing based on what the customs server is logging, I'd say, hundreds a day? link

Comment 3

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:lougenia, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 4

[Lougenia Bailey]

:mhammond Gonna set the severity to S3, feel free to update it.