List of recent viewed repositories forgets entries on page refresh in bitbucket cloud

[Simone Burol]

When I click on the magnifying glass on the left I'm shown the list of recent repositories.

This was always the same length and the entries were not expiring. Now they stay there till the first page refresh.

I'm using Chrome on Windows 10

Steps:

Select some repos and click on the magnifying glass to open this menu that contains the listo of recent repos from the last opened to the older:

Click F5 to update the page (or open a new tab)

Click on the magnifying glass and see only the current repo:

[Tyler T · Accepted solution]

Can you post a screenshot of before and after to help show the difference?

[Simone Burol]

Done

[Tyler T]

Thanks.. which page are you on when that happens? For example, Source, Branches, Pull Requests, etc?

And the bug is that the list changes when you refresh the same page or go from one page to another? 

Thank you

[Simone Burol]

Hy Tyler,

I've just tested and I'm very surprised 

This happens in:

• /src/master/
• commits/

when I press F5 the page forgets the list of recent repos.

It doesn't happen in:

• branches/
• pull-requests/
• addon/pipelines/home#!/getting-started
• /addon/pipelines/deployments
• downloads/

when I press F5 the page keeps the list of recent repos.

Thank you

[Marc Bertrand]

I can report similar behavior.

Although, I've found I don't necessarily need to use the page refresh. It occurred when I viewed a specific commit, then chose Commits from the repo navigation. The recently viewed repos was then reset to only the current one.

It may happen in other places, as I've noticed this behavior for a while now in the following browsers:

- Safari on macOS

- Firefox on Windows 10

[Tyler T]

Thanks for the extra information. I can reproduce this and have flagged it with the dev team. Will post an update here ASAP.

[Tyler T]

We have a bug filed with the team and plan to address it soon. Thank you for the detailed bug report!

[Simone Burol]

It looks like the bug is fixed

Thank you :)