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

stopped working again #5

Open
chrisco23 opened this issue Jun 7, 2022 · 5 comments
Open

stopped working again #5

chrisco23 opened this issue Jun 7, 2022 · 5 comments

Comments

@chrisco23
Copy link

Hi, not sure when it started back up as I've kind of been avoiding the dragging lately, but the script has stopped working now.

Is there any news and/or any fix?

Thanks.

@Syphdias
Copy link
Owner

Syphdias commented Jun 8, 2022

Hi @chrisco23, as described in #4, Chromium/Chrome had issues with dragging tabs in and out multiple times now. As far as I can tell, it currently affects multiple desktop environments – not just i3. In some cases you cannot drag a tab back into another window. This is quite annoying especially since there was a time when it worked perfectly – 83.x–95.0.4630.0, I believe. And it is the second time it broke like this.

This script cannot fix this. It needs to be done in Chromium/Chrome. I think it will be fixed with 103.0.5060.42 (currently in beta)

Furthermore: This script should not exists. It was created for the case where you drag out a tab and it is instantly a new tiling window for i3. This lead to jumpy behavior like shown here and will be that way again after the "fix" is in afaict.

Even though, this is not an inherent bug in the script, I will leave the issue open and pin it for people to easily find it.

@Syphdias Syphdias pinned this issue Jun 8, 2022
@chrisco23
Copy link
Author

Hi @Syphdias, thanks for your detailed reply. I will look forward to Chromium 103 (I'm currently on 102, keeping my Arch install very up-to-date). Sorry Chromium issues keep coming back to haunt your script which I've been grateful for.

I only today discovered I can't even drag a tab within a browser window without it creating a new browser window (as mentioned in one of those links). At least I can still Ctrl+Shift+PgUp/PgDown.

@Syphdias
Copy link
Owner

Syphdias commented Jun 9, 2022

At least I can still Ctrl+Shift+PgUp/PgDown.

I didn't know that one! Thank you very much!

@ristomatti
Copy link

ristomatti commented Jun 11, 2022

Things seem to have returned back to normal with Chrome 102.0.5005.115.

As a curious note - I found this repo from the above referenced issue thread and I'm not even using Brave but Chrome 😄. Anyhow, I tried i3-chrome-tab-dragging.py with this version of Chrome, but sadly I could not reproduce the seemingly almost perfect tab dragging on the screen recording. I seem to have more success just by trying to hit the window I want. Then if it does not snap in neatly I try to find a spot where the tiles start going crazy, release the button and hope for the best. 😂

At least I can still Ctrl+Shift+PgUp/PgDown.

I didn't know that one! Thank you very much!

Haha, I also learned about this while running the previous Chrome version. I also realized you can right click a tab and select the window where to move it. Neither of these were of much help though as the most common thing I want to move across windows is a tab group. Those damn things don't have the same right click option and the keyboard shortcut only works on tabs, not tab groups 😒.

I had to stop using tab groups for the time. I tend to sort the tabs groups to be first but this was not possible to do without recreating the group. Huge rellief this got fixed!

@gibsonrng
Copy link

gibsonrng commented Jun 11, 2022

@ristomatti, also just discovered this project and seems you are describing exact same issues and workarounds I have been considering. I created a separate issue few hours ago that probably describes the same problem that you experienced with the script in this project #6

Syphdias added a commit that referenced this issue Jun 13, 2022
Sadly tab dragging was broken again. This time I didn't bisect it. More
details in #5 and #6. But the main gist is: 103-ish should _fix_ this
and will soon be released.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants