Open Bug 1876417 Opened 2 years ago Updated 1 year ago

When tab is sent when retrying after error, the message stays red

Categories

(Firefox for Android :: Accounts and Sync, defect)

Firefox 121
All
Android
defect

Tracking

()

REOPENED

People

(Reporter: 5i13ghzt462u, Unassigned)

Details

(Whiteboard: [qa-triaged])

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:121.0) Gecko/20100101 Firefox/121.0

Steps to reproduce:

  1. Send a tab from Fenix to Fireox Desktop
  2. SOmehow it fails with a red message with a retry button (dunno how or why)
  3. Cick retry button.

Actual results:

It works, but you get the message:

Tab has been sent

( or similar), but:

  • still with the retry button
  • still in red

Expected results:

  • no retry button
  • in green or grey, neutral as always

121.1.0 (Build #2015996455), 62d5117f79+
GV: 121.0.1-20240108143603
AS: 121.0
2024-01-08T20:51:30.487180180

Android 14
Device: Fairphone 4 (FP4)
OS: Android 14, CalyxOS 5.3.1.
source: Google Play
Build-ID: UQ1A.240105.004.24503012

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

For more information, please visit BugBot documentation.

Flags: needinfo?(tthibaud)

rugk, have you seen this bug again? Can you share a screenshot?

Component: General → Accounts and Sync
Flags: needinfo?(tthibaud)
Flags: needinfo?(5i13ghzt462u)
Severity: -- → S3

(In reply to Chris Peterson [:cpeterson] from comment #2)

rugk, have you seen this bug again? Can you share a screenshot?

rugk?

No I have not. That said its hard to reproduce, because 2. aka making that operation fail, obviously is not reproducible. At least I don't know.

My main point after all was the color change of the messages.

Flags: needinfo?(5i13ghzt462u)

I was not able to reproduce this on the latest versions of Firefox for Android 130.0, 131.0, Nightly 132.0a1, nor Beta 131.0b9.
Based on this, and on the reporter comment from above, I'll close this ticket as WORKSFORME.

Status: UNCONFIRMED → RESOLVED
Closed: 1 year ago
Resolution: --- → WORKSFORME
Whiteboard: [qa-triaged]

I was not able to reproduce this

Were you able to correctly reproduce the "step 2" part of this? ie, that you saw the red error message, then retried before seeing the final "Tab Sent" message?

Status: RESOLVED → REOPENED
Ever confirmed: true
Flags: needinfo?(mlobontiuroman)
Resolution: WORKSFORME → ---

Hello, Mark,

No, I was not able to trigger the red allert except when I cut off really fast the internet connection and the tab was not sent yet.

Flags: needinfo?(mlobontiuroman)

(In reply to miralobontiu from comment #7)

Hello, Mark,

No, I was not able to trigger the red allert except when I cut off really fast the internet connection and the tab was not sent yet.

Thanks for the fast response, but I'm still a little confused as you seem to both say you could not reproduce the red alert and that you could :)

My question is really whether you were able to follow the complete STR as described, including that important step. If so (ie, the red alert box was immediately followed by a normal "success" alert box after a retry) then we should re-close this. However, if you were unable to follow that complete STR due to the timings, we should keep it open as it probably does continue to exist.

Flags: needinfo?(mlobontiuroman)

Sorry for the confusion.

I was unable to reproduce the reporter's steps, could not trigger the red allert described in Comment 0.

Flags: needinfo?(mlobontiuroman)
You need to log in before you can comment on or make changes to this bug.