[BUG] Firefox containers forced enabled

[Toastbroti]

Actual Behavior

Tampermonkey force enables Firefox containers. It is only possible to disable this feature after turning off the extension. The feature clutters the UI and defaults to off.

"Tampermonkey manages the tab environments. [Disable extension]"

Expected Behavior

Tampermonkey should not force that option to be enabled.

Environment

• Browser and Version: Firefox 151.0.1
• Tampermonkey version: 5.5.0
• Operating System and Version: Windows 11

Additional context

This appears to be caused by the most recent update of Tampermonkey.

[MonfGeiger]

i can confirm the same thing. I can temporarily turn off container tabs by going into about:config, and searching for "privacy.userContext.enabled" and "privacy.userContext.ui.enabled" and setting those both to false. that temporarily turns that option off until i close/open firefox again, then it returns

if this is truly a bug, i hope it gets fixed, because i do not like the containers tab. it feels useless and un-needed, and tampermonkey worked just fine without them

Browser: Firefox 150.0.3
Tampermonkey version: 5.5.0
OS: Windows 10 Pro (64-Bit, 22H2, Build Number 19045.7291)

[MonfGeiger]

i managed to find a workaround to keeping the "new containers tab" option disabled

follow the steps outlined here, but for the contents of the firefox.cfg file, make it the following (do not put just line 2 and 3, keep it 1-1 the same as below, otherwise it will not work)

// IMPORTANT: Start your code on the 2nd line
lockPref("privacy.userContext.enabled", false);
lockPref("privacy.userContext.ui.enabled", false);

do this, and the "new containers tab" option WILL STAY DISABLED

[derjanb]

As far as I remember this didn't happen at the ESR version. 😯 Will check...

In the meantime you can also downgrade with version from here: https://addons.mozilla.org/en-US/firefox/addon/tampermonkey/versions/

[derjanb]

I can't convert contextualIdentities to an optional permission. So either userscripts can't

• open container tabs and
• start container downloads at all

or users have to disable this feature by themselves. :-/

From Firefox 57 onwards, if an extension that uses the contextualIdentities API is installed, then the contextual identities feature will be enabled automatically. Note though that it's still possible for the user to disable the feature using the "privacy.userContext.enabled" preference. If this happens, then contextualIdentities method calls will reject their promises with an error message.

Thought?

Uncaught Error: Type error for parameter permissions (Error processing permissions.0: Value "contextualIdentities" must either: 
    must either [
        must either [
            be one of ["idle"],
            be one of ["menus.overrideContext"], 
            be one of ["search"], 
            be one of ["tabGroups"], 
            be one of ["cookies"], 
            be one of ["activeTab"], 
            be one of ["scripting"],
            or be one of [
                "webRequest",
                    "webRequestAuthProvider",
                    "webRequestBlocking",
                    "webRequestFilterResponse",
                    "webRequestFilterResponse.serviceWorkerScript"
            ]
        ],
        be one of [
            "clipboardRead",
            "clipboardWrite",
            "geolocation",
            "notifications"
        ],
        be one of ["bookmarks"],
        be one of ["devtools"],
        be one of ["find"],
        be one of ["history"],
        be one of ["pkcs11"],
        be one of ["browsingData"],
        be one of ["sessions"],
        be one of ["topSites"],
        be one of ["browserSettings"],
        be one of ["declarativeNetRequestFeedback"],
        be one of [
            "downloads",
            "downloads.open"
        ],
        be one of ["management"],
        be one of [
            "tabs",
            "tabHide"
        ],
        be one of ["privacy"],
        be one of ["proxy"],
        be one of ["webNavigation"],
        or be one of ["nativeMessaging"]
    ],
    or must either [
        be one of [],
        be one of ["userScripts"],
        or be one of ["trialML"]
    ]
) for permissions.request.

[derjanb]

More information:

https://bugzilla.mozilla.org/show_bug.cgi?id=1947602
https://bugzilla.mozilla.org/show_bug.cgi?id=1386673#c17

However, [contextualIdentities] does have the side effect of enabling the Container Tabs feature that is otherwise disabled by default. To support extensions that want to use containers only if it enabled by the user, without activating the functionality themselves, we are supportive of introducing a mechanism to allow extensions control over the mode of operation, for example in the form of a new permission.

We're (still) supportive of a contextualIdentities.readOnly permission

[carlsagan5656]

So, after tampermonkey updated today, the "container tab" setting got forcefully enabled. I think the real kick in the nuts is, as another user wrote above, the fact that after disabling it in about:config, it just gets forcefully reenabled after restarting the browser. So it would be really nice if you could fix that. I don't wanna be forced to switch to another script manager, but I really hope you can understand that forcefully enabling settings that add pointless menu clutter is just unacceptable.

I can't convert contextualIdentities to an optional permission.
With all due respect, what are you even talking about? I've been using tampermonkey for several months and it worked just fine with that setting disabled.

So either userscripts can't

    open container tabs and
    start container downloads at all

Sounds good to me, since I want that feature disabled.

Gonna give it a few days before I start looking into greasemonkey/violentmonkey.

[alessiot89]

This happens also in last Firefox ESR version.

[derjanb]

Gonna give it a few days

In the meantime you can also downgrade with versions from here: https://addons.mozilla.org/en-US/firefox/addon/tampermonkey/versions/