Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Avatar for Username

Mozilla サポートの検索

サポート詐欺に注意してください。 私たちはあなたに通話やショートメッセージの送信、個人情報の共有を求めることはありません。疑わしい行為を見つけたら「迷惑行為を報告」からご報告ください。

詳しく学ぶ
このスレッドは閉じられました。 必要であれば新たに質問してください。
Locked

Trouble using private containers with the new Floorp update (Version 12.16.3)

Firefox Undefined
Denys replied
Isolde Valmont
Isolde Valmont

Hiii, I am using Floorp 12.16.3@153.0 on Debian 13 with KDE Plasma. Since the latest update, navigation from Floorp’s Private Container no longer stays inside the container.

Steps to reproduce:

1. Open a new tab in Floorp’s Private Container. 2. Type either a URL or a search query in the address bar. 3. Press Enter or click the arrow button. 4. Instead of loading the address in the current container tab, the browser creates a new regular tab outside the container.

The new tab does not show the container indicator and uses my normal browsing cookies. However, clicking one of the shortcuts displayed on the new-tab page correctly loads the website inside the Private Container.

I have already tried the following:

  • Confirmed that `browser.urlbar.openintab` is set to `false`.
  • Confirmed that `browser.search.openintab` is set to `false`.
  • Restarted the browser.
  • Disabled Floorp Start.
  • Opened `https://example.com` inside the Private Container and then entered another URL or search query in the address bar. It still opened a new regular tab.
  • Tested by pressing only Enter, without Alt or any other modifier key.

Expected behavior: entering a URL or search query should navigate within the current Private Container tab.

Actual behavior: a new regular, non-container tab is created.

This previously worked correctly and appears to have started after updating to Floorp 12.16.3, based on Firefox 153. Is this related to a change in Firefox 153’s container behavior, or is it likely to be a Floorp-specific bug? Please help, I'm a huge floorp fan :(

Hiii, I am using Floorp 12.16.3@153.0 on Debian 13 with KDE Plasma. Since the latest update, navigation from Floorp’s Private Container no longer stays inside the container. Steps to reproduce: 1. Open a new tab in Floorp’s Private Container. 2. Type either a URL or a search query in the address bar. 3. Press Enter or click the arrow button. 4. Instead of loading the address in the current container tab, the browser creates a new regular tab outside the container. The new tab does not show the container indicator and uses my normal browsing cookies. However, clicking one of the shortcuts displayed on the new-tab page correctly loads the website inside the Private Container. I have already tried the following: * Confirmed that `browser.urlbar.openintab` is set to `false`. * Confirmed that `browser.search.openintab` is set to `false`. * Restarted the browser. * Disabled Floorp Start. * Opened `https://example.com` inside the Private Container and then entered another URL or search query in the address bar. It still opened a new regular tab. * Tested by pressing only Enter, without Alt or any other modifier key. Expected behavior: entering a URL or search query should navigate within the current Private Container tab. Actual behavior: a new regular, non-container tab is created. This previously worked correctly and appears to have started after updating to Floorp 12.16.3, based on Firefox 153. Is this related to a change in Firefox 153’s container behavior, or is it likely to be a Floorp-specific bug? Please help, I'm a huge floorp fan :(

すべての返信 (1)

Denys
Denys
  • モデレーター
  • トップ 10 の貢献者

Hi,

In v153, containers became a default feature in Firefox, so there definitely were some changes. However, I'm not aware of any similar issues in Firefox, so the one you're facing must be Floorp-specific. If you want to make sure, try installing Firefox and see if the issue is present there.

Please also note that this forum is intended to help users with Mozilla products, such as Firefox. Your question, therefore, appears to be outside the scope of our support forum, so as a moderator, I’m going to lock the thread and mark it as off-topic. Please see Mozilla Support rules and guidelines for more information.

If you find out that the issue reproduces in Firefox, feel free to submit a new question.