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

Current tab is duplicated when boosting #117

Closed
eloydegen opened this issue Aug 21, 2023 · 5 comments · Fixed by #115
Closed

Current tab is duplicated when boosting #117

eloydegen opened this issue Aug 21, 2023 · 5 comments · Fixed by #115
Labels
bug Something isn't working

Comments

@eloydegen
Copy link

Bug description

When installing the plugin and clicking on boost on a different mastodon server, it opens a new tab of the different server instead of boosting the post to my profile.

I have an account on a Mastodon glitch-soc instance, https://hsnl.social

Steps to reproduce

  1. Install extension and make sure my handle is filled in in the settings
  2. Go to different server
  3. Boost post
  4. Current tab is duplicated

System

  • Plugin: 2.1
  • Firefox: 109
  • Fedora Linux 36
@eloydegen eloydegen added the bug Something isn't working label Aug 21, 2023
@rugk
Copy link
Owner

rugk commented Aug 21, 2023

Hi and thanks for your bug report. Does this always happen or only sometimes? I have experienced something like that too, but it did not happen that often…

Could you provide a concrete link/URL to the toot, please?

@austinhuang0131
Copy link
Contributor

By "Current tab is duplicated" does it add the fragment #interact at the end of the URL?

If so then fixed by #115

@willhansen
Copy link

By "Current tab is duplicated" does it add the fragment #interact at the end of the URL?

If so then fixed by #115

I'm running into this months after it's been fixed. Probably because the version Firefox has on the addon page is 4 months old:
Selection_411

@rugk rugk linked a pull request Jan 1, 2024 that will close this issue
@rugk
Copy link
Owner

rugk commented Jan 1, 2024

Fair enough, I have just released v2.2. Could you try it again with this version?

I assume the issue is fixed, so I'll close it for now.

@rugk rugk closed this as completed Jan 1, 2024
@eloydegen
Copy link
Author

Yeah, it's fixed, thank you! And sorry for forgetting to reply earlier.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
4 participants