1555760 - History entries opened in new tabs should stay in the current container

Status: NEW

(Firefox :: Bookmarks & History, defect, P3)

Description

[eugeneshap]

Attachment: container escape by history.png

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:69.0) Gecko/20100101 Firefox/69.0

Steps to reproduce:

1. Open a tab in container mode
2. Open history list (ctrl+h)
3. Click on a history entity by mouse wheel or by ctrl+click. Or ctrl+click on "Open in a New Tab"
4. A new tab is opened in non-containered mode

Actual results:

New tab is opened in not-containered mode

Expected results:

If I click on a history entity with a simple left button click it is opened in the container - other means of click probably should also open the history entity in the container.

Comment 1

[David Sacal]

Hi,
would you please share more details regarding the reported behavior? Is there any plugin/add-on needed to open container mode? Please also try on the latest nightly , available in here: https://nightly.mozilla.org/ and reach us out back if the problem is still reproducible.

Regards
David

Comment 2

[eugeneshap]

I've updated to the last Nightly 69.0a1 (2019-06-07) (64bit) but I still can reproduce this behaviour.

I open container mode either by long click on a new tab "+", or by right click on an already oppened tab and then clicking "Reopen in Container". Once in a container mode I click ctrl+h and then I need to click on history entity in such a way that it would be opened in a new tab (step 3.). It opens in a new tab but doing so that it is not in a container mode.

I don't think that the plugins or addons are the cause. My guess is that the behaviour could be somehow connected to the bug https://bugzilla.mozilla.org/show_bug.cgi?id=1555367

Comment 3

[David Sacal]

Hi Eugene, you are correct this issue seems to be related to Bug 1555367, I'm not sure if its a duplicate of it or simply a new bug but I will mark this one accordingly. Thanks for taking the time to report this issue.

Also please note that I managed to reproduce this issue on Windows 10 using our latest Nightly Build 69.0a1 (2019-07-07)

Comment 4

[Marco Bonardo [:mak]]

I'm not sure why this is in the Address Bar component, since the reporter is using the history sidebar...