Closed Bug 1805710 Opened 2 years ago Closed 2 years ago

The “Tab Pickup” callout message from the “Continuous Onboarding” tour is not displayed on the “Firefox View” page unless the page is refreshed

Categories

(Firefox :: Messaging System, defect, P2)

Desktop
All
defect

Tracking

()

RESOLVED WONTFIX
Tracking Status
firefox108 --- wontfix
firefox109 --- wontfix
firefox110 --- wontfix

People

(Reporter: avarro, Assigned: mviar)

References

(Blocks 1 open bug)

Details

[Affected versions]:

  • Firefox Nightly 110.0a1 - Build ID: 20221214033416
  • Firefox Beta 109.0b2 - Build ID: 20221213185929
  • Firefox Release 108.0 - Build ID: 20221208122842

[Affected Platforms]:

  • Windows 10x64
  • macOS 12.6
  • Linux Mint 20.2x64

[Prerequisites]:

  • Have a new Firefox profile created and opened.

[Steps to reproduce]:

  1. Navigate to the "Firefox view" page.
  2. Click the "See how it works" button from the “Welcome Spotlight”.
  3. Click the "Next" button from the "Hop between devices with tab pickup" callout message.
  4. Click the "Next" button from the "Get back your closed tabs in a snap" callout message.
  5. Click the "Got it" button from the "Add a splash of color" callout message.
  6. Close the browser and change the system time to 1 day in the future.
  7. Reopen the browser with the same profile and navigate to the “Firefox View” page.
  8. Switch to another opened tab and click again the "Firefox View" icon.
  9. Observe the behavior.

[Expected result]:

  • The “Tab Pickup” callout message from the “Continuous Onboarding” tour is successfully displayed on the “Firefox View” page.

[Actual result]:

  • The “Tab Pickup” callout message from the “Continuous Onboarding” tour is NOT displayed on the “Firefox View” page.

[Notes]:

  • I managed to trigger the “Tab Pickup” callout message only by refreshing the “Firefox View” page.
  • Attaching here a screen recording of the issue.

NI product for feedback on this issue thanks

Flags: needinfo?(vtay)
Priority: -- → P2
Assignee: nobody → mviar

Given the traffic to Firefox View, the likelihood of this bug and overall the experience does not negatively impact the user, I would recommend won't fix.

Status: NEW → RESOLVED
Closed: 2 years ago
Flags: needinfo?(vtay)
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.