[Chrome] Opening a link from bookmarks toolbar, after not opening a new tab for a while, opens the link at the end

[PuppetMaster000]

Hoping the extension is still supported. Starting from about 2 months ago roughly, I believe the new Chrome update broke the extension. Whenever I would open a new link from the bookmarks toolbar (using the middle mouse button) but ONLY after not opening anything for about a minute, the first new tab would always go all the way right. Then on the second click, it would go back to normal and open to the right.

It only happens when no new tabs have been opened for a minute, easiest way to test is just to not touch anything, leave the browser running, then after a minute use the scroll wheel (middle mouse button) to open a new link from the bookmarks toolbar.
It opens all the way on the right, but then you can click the exact same link again and it would open to the right as it is suppose to.

The weird part is, you can then keep opening links from the toolbar normally for about 30 seconds, but the moment you don't touch the browser for a minute, it is like the extension "goes to sleep" and needs to wake up again. I should also mention this only happens with the bookmarks toolbar, normal links from a site seem to act as they should.

[autonome]

Hi, thanks for filing!

I can reproduce this in latest Chrome by emulating middle mouse button via cmd+click on a bookmark on the bookmarks bar.

Confirmed that a little wait is required to reproduce.

I'll take a look and see what's happening.

[PuppetMaster000]

I can't believe I waited this long to report it just because I thought it would never be seen...
You are awesome, thank you!

[autonome]

A bit more testing, and this appears to be about tabs.onCreated not firing after a minimum of 25 seconds of delay.

And confirmed that you can reproduce just by cmd+t to open a new tab. The bookmarks bar and middle-click are not relevant. Appears not to matter what the source of the event is.

[PuppetMaster000]

Thanks for looking into it so quickly. Yeah, that sounds about right. I personally only use the middle mouse button (scroll wheel) to open tabs, which is why I referenced it, but I was sure it applied to other ways too. I just wasn't familiar with all of them.
In any case, do you believe this is something that can be fixed? And if so, is it something we should do from user side or should we just wait for the update?

[autonome]

Ok I confirmed with a minimal extension in a clean profile that it is likely not solely related to tab events, and could be a bug in the extension.

Extension code:

chrome.tabs.onCreated(() => console.log('🤪'));

Fires immediately upon opening a new tab, even after the 25s delay.

[PuppetMaster000]

I suppose that is good news, better if it is in the extension than Chrome itself right? I would assume the extension is easier to control compared to the browser, so hopefully it can be fixed.

[autonome]

Yes and no. I'm experiencing the observer/observed problem at the moment 😂 https://bsky.app/profile/burrito.space/post/3kqpght7j7c2y

…

On Tue, Apr 23, 2024, at 03:02, PuppetMaster000 wrote: I suppose that is good news, better if it is in the extension than Chrome itself right? I would assume the extension is easier to control compared to the browser, so hopefully it can be fixed. — Reply to this email directly, view it on GitHub <#34 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAMHN7W72EV6HJKXRKWTZTY6WXJTAVCNFSM6AAAAABGRPZJICVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZRGIYDQOBYHA>. You are receiving this because you commented.Message ID: ***@***.***>

[autonome]

This is likely the Chromium bug: https://issues.chromium.org/issues/40805401

I'm testing a workaround: https://stackoverflow.com/a/66618269/4096929

[autonome]

Ok looks like it's working so far.

I'll ship an update so you can try.

[autonome]

Hrm, nope. Just tested opening external link after 25s delay and still opened at end.

[PuppetMaster000]

Damn, this bug seems so simple at first, but seems like a nightmare to figure out actually. Thank you for the hard work, hope you can find a fix.

[autonome]

I might just ship with this attempted mitigation and call it a day, hope it happens at least a bit less. This is clearly a bug in Chrome's implementation of mv3 extensions... which they do not consider a bug. All the other workarounds add both complexity and unnecessary resource consumption, and put the extension at risk of getting flagged and booted.

…

On Wed, Apr 24, 2024, at 07:47, PuppetMaster000 wrote: Damn, this bug seems so simple at first, but seems like a nightmare to figure out actually. Thank you for the hard work, hope you can find a fix. — Reply to this email directly, view it on GitHub <#34 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAMHN5CJHN6QSWINCJNYUTY65BOZAVCNFSM6AAAAABGRPZJICVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZUGA4DMMZVGU>. You are receiving this because you commented.Message ID: ***@***.***>

[PuppetMaster000]

I checked out the extension called "Open Tabs Next to Current" from the Chrome store, which seems to not have the issue, but it acts differently when opening multiple tabs. I much preferred yours because when opening more tabs from the current tab location, it would open to the right in order clicked (current tab, 1st, 2nd, 3rd clicked), but their extension always opens everything to the right of the current tab you are on only (current, 3rd, 2nd, 1st clicked) if that makes any sense. Any tab opened is forced exactly to the right of the current one.
I am only mentioning this if you wish to (although not sure if you can even) check that extension out and see why that one doesn't have the 25s delay thing. Here is a direct link to it in Chrome store:
https://chromewebstore.google.com/detail/open-tabs-next-to-current/gmpnnmonpnnmnhpdldahlekfofigiffh

Again, sorry if what I am saying is ignorant, I have no idea how any of this works, just sharing what I have noticed.

[autonome]

Super helpful, thanks! I'll if the source is available, see what they're doing differently.

…

On Wed, Apr 24, 2024, at 12:01, PuppetMaster000 wrote: I checked out the extension called "Open Tabs Next to Current" from the Chrome store, which seems to not have the issue, but it acts differently when opening multiple tabs. I much preferred yours because when opening more tabs from the current tab location, it would open to the right in order clicked (current tab, 1st, 2nd, 3rd clicked), but their extension always opens everything to the right of the current tab you are on only (current, 3rd, 2nd, 1st clicked) if that makes any sense. Any tab opened is forced exactly to the right of the current one. I am only mentioning this if you wish to (although not sure if you can even) check that extension out and see why that one doesn't have the 25s delay thing. Here is a direct link to it in Chrome store: https://chromewebstore.google.com/detail/open-tabs-next-to-current/gmpnnmonpnnmnhpdldahlekfofigiffh Again, sorry if what I am saying is ignorant, I have no idea how any of this works, just sharing what I have noticed. — Reply to this email directly, view it on GitHub <#34 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAMHN2CQ2XHHYGMQGXIWKLY657HDAVCNFSM6AAAAABGRPZJICVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZUGU3TMMBQGQ>. You are receiving this because you commented.Message ID: ***@***.***>