Forum Discussion

isaacchua's avatar
isaacchua
Copper Contributor
Dec 17, 2021

Bug: Certain extensions cause the Back button to misbehave on Edge

Hello everyone. I have been experiencing this problem for several months now and unfortunately I don't remember since which version, but it still exists in 96.0.1054.57.

 

What happens is when certain Extensions are enabled in Edge, the following issue occurs and here is how it is reproduced:

1. In a first tab, open a link in a new tab. (E.g. when opening a search result on Bing with "Open links in new tab" on).

2. Normally, when a link is opened in a new tab, the Back button is enabled, which when clicked, closes the tab. However, with these Extensions enabled, the Back button on the new tab is disabled.

3. In that new tab, click on any link. The Back button becomes enabled, as expected. However, when the Back button is clicked, the tab is closed instead of going back to the previous page. This is annoying and frustrating.

 

I should also add that I don't think the Back button should close the tab if it were created by opening a link from another tab.

 

The thing is, this only happens for when certain Extensions are enabled on my Edge. I have tested each Extension I have individually, and it occurs for two (I have four installed):

1. Keeper: https://microsoftedge.microsoft.com/addons/detail/keeper%C2%AE-password-manager-/mpfckamfocjknfipmpjdkkebpnieooca

2. Shopback: https://microsoftedge.microsoft.com/addons/detail/shopback-button-cashbac/mppnmimhlcolakeoadpehdjljppkmfda

 

This didn't happen until an Edge update a couple of months ago. So I don't think it is an Extension problem — in any case, it is strange for an Extension to affect the Back button or the browsing history of a tab without any interaction with said Extension on my part.

 

Please look into this. I thought this issue would have been quickly identified by others but apparently it wasn't.

 

Isaac

  • isaacchua's avatar
    isaacchua
    Copper Contributor
    Hello, I'm now on 97.0.1072.62 and the same bug still exists. Is this the right place to report bugs?

Resources