Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tab lastUsed property is being incorrectly set #11769

Closed
lougeniaC64 opened this issue Aug 31, 2022 · 1 comment
Closed

Tab lastUsed property is being incorrectly set #11769

lougeniaC64 opened this issue Aug 31, 2022 · 1 comment
Labels
Bug 🐞 This is a bug with existing functionality not behaving as expected

Comments

@lougeniaC64
Copy link
Contributor

lougeniaC64 commented Aug 31, 2022

Steps to reproduce

  1. Sign into sync on desktop
  2. Navigate to Firefox View and note the tabs in the Tab Pickup section
  3. Open up Firefox Beta and sign into sync
  4. Open up the tab tray
  5. Open up a new tab
  6. Navigate to a site
  7. Navigate to Firefox View and note the tabs in the Tab Pickup section

Expected behavior

The tab created in step 5 should be the most recent tab in the Tab Pickup section of Firefox View followed by the next most recent tabs noted in step 1.

Actual behavior

The tab created in step 5 along with other open tabs in Firefox iOS appear in the Tab Pickup section with a last used time of "Just Now"

Notes

The associated bug with the original STR are in Bugzilla bug 1788111. I was able to reproduce this bug a few times, but not always. I suspect that it stems from the TabManager.saveTabs call to Tab.toRemoteTab, which creates the tabs records to be saved to storage but I'm not completely sure.

┆Issue is synchronized with this Jira Task

@lougeniaC64 lougeniaC64 added the Bug 🐞 This is a bug with existing functionality not behaving as expected label Aug 31, 2022
@data-sync-user
Copy link
Collaborator

➤ Simion Basca commented:

Verified fix on v105.0 (17614)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug 🐞 This is a bug with existing functionality not behaving as expected
Projects
None yet
Development

No branches or pull requests

2 participants