Automatic Mode don't instantly open new tabs not working #453
Comments
|
Thanks for letting me know, I'll try to reproduce. In this specific case a debug log (see wiki for instructions) would be very helpful if you could maybe obtain one. |
|
Tell me if you can reproduce using these steps:
If https://www.whatismyip.com/ doesn't elicit the behavior, the issue seems to occur on slow sites that takes a few seconds to load, so find another site that takes several seconds to load may elicit the behavior. I think the issue is related to a bug where if a site takes too long to load out of a New Tab, the extension fails to put it into a container. Please verify if you can reproduce. Thanks |
|
Unfortunately can't reproduce on my end with the given STR, even though the site takes a long time to load (the request is almost immediately put into a TC after pressing enter, then it keeps loading). |
|
Have you tried with a new profile (about:profiles)? |
|
I cant reproduce it now either. There may be other factors affecting this, like RAM usage, number of tabs, etc but I'll keep an eye out next time this happens and hopefully pin down the culprit. |
|
It happened again. I'm attaching a screenshot. You can see the tabs without the colored coding are the ones that for some reason the Automatic Mode fail to place into a temp container.
Here is the debug log. It's quite long. |
|
Shorter one that contains the issue. |
|
Interesting, thanks for providing the log. So what happens is that the request to |
|
Thanks for the quick response. It appears so. I've disabled Multi-Account Containers for now since I realize I don't need both extensions. Let's see if the issue persists, if not then it's likely due to the restrict feature as you said. |
|
Caught it in the act again, this time with Multi-Account Container extension disabled. |
|
Thanks. Ah, I see now what's going on. Your new tabs ( In either case, it's a bug, since that can and should be caught by automatic mode. |
|
Fixed in v1.9 |
|
Looks like the issue is still around, this time with a Pocket website. |
|
Fri, 14 Aug 2020 18:27:20 GMT "[onCreated] tab created" {"id":1185,"index":7,"windowId":3,"highlighted":true,"active":true,"attention":false,"pinned":false,"status":"complete","hidden":false,"discarded":false,"incognito":false,"width":1680,"height":965,"lastAccessed":1597429640985,"audible":false,"mutedInfo":{"muted":false},"isInReaderMode":false,"sharingState":{"camera":false,"microphone":false},"successorTabId":-1,"cookieStoreId":"firefox-default","url":"about:blank","title":"getpocket.com/explore/item/sylvester-stallone-feels-robbed-of-an-ownership-stake-in-rocky-i-was-furious"} background.js:468:25 |
|
Never mind, it's working as intended. It looks like getpocket was added to domains that is ignored. |
As of FF 78-79, I've been noticing increasingly frequent occurrences of Temporary Containers automatic mode not opening sites in a container. I have automatic mode set to "Don't instantly open new tabs..." selection. I prefer the Instant option but it loses characters, so I use the alternative. However, it doesn't place my navigated tabs in a container...
Rough steps to reproduce:
Cmd+N to create new Tab, navigate to a site.
Expected Behavior:
The site loads in a new container
Actual Behavior:
The site loads in no container
I've seen issue #332, but I already have my New Tabs page set to Firefox Home.
My preferences file
The text was updated successfully, but these errors were encountered: