Seems to be broken

[ghost]

This is a great extension but it stopped working after the release of 135. I really hope it can be fixed.

[Celerii]

I confirm that the extension no longer works after updating Firefox to v135 version. I hope it can be fixed, too... This extension is very useful!

[loaykhalifa]

+1 need this extension too

[sai-educ]

This is a fantastic extension however, the extension does not work with Firefox v135. I am on Zen, which is also on the same version.

[KJL316]

I can confirm it was the update to FF 135 - my desktop updated first and this extension stopped working, then on my laptop it was on 134 still working until I updated to 135.

[loaykhalifa]

I am on Zen

Hope Zen browser add this behavior as default

[MaxKoll]

Could this change in FF 135 have caused the extension to break? User Interaction Tracking should be considered for initial history entries

This feature, requested three years ago, would probably make fixing the extension very simple: Add canGoForward and canGoBack to Extensions API

[MaxKoll]

I just found out that Navigation.canGoBack was implemented three days ago and is scheduled to be available in FF 137 (to be released on April 1): Implement 'Navigation.canGoBack' and 'Navigation.canGoForward'

In Chrome this is implemented in such a way that navigation.canGoBack is true only for same-origin navigations. I don't know how it will be in Firefox. I tried the current nightly, but window.navigation was not available, yet. The MDN article is not specific about this.

As I understand it, this is in the context of a content script. I have not yet looked into future WebExtension APIs.

Edit: I found this note on MDN which also states that the Navigation API is limited to same-origin contexts. So this is probably not useful here.

[CennoxX]

I just found out that Navigation.canGoBack was implemented three days ago and is scheduled to be available in FF 137 (to be released on April 1): Implement 'Navigation.canGoBack' and 'Navigation.canGoForward'

In Chrome this is implemented in such a way that navigation.canGoBack is true only for same-origin navigations. I don't know how it will be in Firefox. I tried the current nightly, but window.navigation was not available, yet. The MDN article is not specific about this.

As I understand it, this is in the context of a content script. I have not yet looked into future WebExtension APIs.

Edit: I found this note on MDN which also states that the Navigation API is limited to same-origin contexts. So this is probably not useful here.

This will not allow to activate the back button, only let us track the current history entry. You'll still need to use something like the backbutton to close the tab, this can already be accomplished.

[MaxKoll]

This will not allow to activate the back button, only let us track the current history entry.

True, and I have no idea how to accomplish this.

For me personally, it wouldn't make a difference, since I navigate using the thumb buttons on my mouse rather than by clicking the browser buttons. A custom command that navigates back if possible and closes the current tab otherwise would suffice in this case.