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

Extension does not react to tab creation in another window #43

Closed
MitchellMarkGeorge opened this issue Jul 18, 2022 · 6 comments
Closed
Labels
bug Something isn't working M Medium Task UX
Projects
Milestone

Comments

@MitchellMarkGeorge
Copy link
Owner

Describe the bug
Similar to #14. During my testing, I found that if I had another window open and I created a new tab, the currently open tab search modal would not react accordingly. This is a new problem since the inclusion of #12 that we never had to address.

To Reproduce
Steps to reproduce the behavior:

  1. Have two browser windows open with tabs in both
  2. Have the tab search component open in one of the windows. Take note of the number of results.
  3. Go to the second window and create a new tab. The number of results on the tab search modal should remain the same.

Expected behavior
On tab creation, the tab search modal should update.

Platform Info (please complete the following information):

  • OS: Mac
  • Browser Tested on both Chrome and Firefox
  • Version [e.g. 22]

Additional context
This issue should be relatively easy to fix. using an onCreated listener, listen for tab creation. When a new tab is created in another window, send an update to all open tab search modals. This is important to only update the tab search modal in the OTHER window as if a new tab is created in the same window as the current search modal, the modal will be automatically updated when the user returns to that tab. If this issue requires more clarification, please feel free to reach out!

@MitchellMarkGeorge MitchellMarkGeorge added bug Something isn't working M Medium Task UX labels Jul 18, 2022
@MitchellMarkGeorge MitchellMarkGeorge added this to To do in 1.0 via automation Jul 18, 2022
@MitchellMarkGeorge MitchellMarkGeorge added this to the 1.0 milestone Jul 18, 2022
@andrei-g-git
Copy link
Contributor

Hmm I've tested the new build on Chrome, Brave and Firefox and found that I can't replicate the bug on Windows, they look like they work fine, i.e. the tab count updates properly when I open and close new tabs in the other window or close the window outright, and it seems to work both ways, if I open a modal in the new window, it will register changes that happens in the original window even with a modal open in each.

@MitchellMarkGeorge
Copy link
Owner Author

Hmm thats odd. @andrei-g-git while you were testing did the active tab of the original window change at any point. The way I tested it was by having one window for each monitor (I run a dual monitor setup)

@andrei-g-git
Copy link
Contributor

No, it always comes back to the same tab, but I only have 1 monitor. If I could get my hands on a second hdmi cable I could hook it up to my tv (I'll see if I can scrounge one up from my nightmarishly tangled bag of wires :P)

@MitchellMarkGeorge
Copy link
Owner Author

After some testing I think there is a chance that it could have just been a development error. I will leave the issue open for the time being until I can confirm why this happened

@MitchellMarkGeorge
Copy link
Owner Author

Tested this again and it still persists (tested on the production/deployed version). This should be one of the first bugs to be fixed because it is quite noticeable.

@MitchellMarkGeorge
Copy link
Owner Author

Closed with #66

1.0 automation moved this from To do to Done Aug 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working M Medium Task UX
Projects
1.0
Done
Development

No branches or pull requests

2 participants