Skip to content

Issues with Essentials Tabs and Extensions: Random Behavior after Shortcut Activation #2918

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

Closed
4 tasks done
albu-ali opened this issue Nov 11, 2024 · 1 comment
Closed
4 tasks done
Labels

Comments

@albu-ali
Copy link

Captchas

  • I have read the instructions.
  • I have searched existing issues and avoided creating duplicates.
  • I am not filing an enhancement request.

What happened?

We've observed issues with the Essentials tabs that occur randomly when using certain extensions.

  • The essentials tabs are affected by some extensions, causing problems.
  • However, this behavior is very random and difficult to reproduce consistently.
  • On the other hand, NoScript can be easily reproduced with this issue:
    1. Add one or more tab to Essentials.
    2. Install NoScript.
    3. Use the shortcut of the extension twice (alt+shift+n for NoScript).
    4. Verify that the issue occurs after using the shortcut.

Reproducible?

  • I have checked that this issue cannot be reproduced on Mozilla Firefox.

Version

1.0.1-a.18

What platform are you seeing the problem on?

Linux

Relevant log output

No response

Copy link

dosubot bot commented Dec 12, 2024

Hi, @albu-ali. I'm Dosu, and I'm helping the desktop team manage their backlog. I'm marking this issue as stale.

Issue Summary:

  • Inconsistent behavior with Essentials tabs when using NoScript on Linux.
  • Problem occurs after adding tabs to Essentials and using NoScript's shortcut twice.
  • Issue does not occur on Mozilla Firefox.
  • No comments or further developments have been made.

Next Steps:

  • Please let us know if this issue is still relevant to the latest version of the desktop repository by commenting here.
  • If there is no further activity, this issue will be automatically closed in 7 days.

Thank you for your understanding and contribution!

@dosubot dosubot bot added the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label Dec 12, 2024
@dosubot dosubot bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 19, 2024
@dosubot dosubot bot removed the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Archived in project
Development

No branches or pull requests

1 participant