Closed Bug 1888872 Opened 1 year ago Closed 1 year ago

Default has Tabs load in the background

Categories

(Thunderbird :: Untriaged, enhancement)

Thunderbird 125
enhancement

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1886653

People

(Reporter: siffe, Unassigned)

Details

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

Steps to reproduce:

Clicked a message to open it.

Actual results:

The message opened in a new background tab.

Expected results:

The message should have opened in a new foreground tab, as it always has in the past.

See https://forums.mozillazine.org/viewtopic.php?t=3119859. mail.tabs.loadInBackground is set to true by default, but hasn't been working that way until now.

mail.tabs.loadInBackground is set to true by default

In version 102.15.1
mail.tabs.loadInBackground is set to 'True' or 'False'

Email double click open in new tab will have auto focus.

Testing Version beta 125.0b2
To have immediate focus on email which is opened in a new tab:
mail.tabs.loadInBackground' change setting to 'False'

In other words it's actually now working correctly - that 'true' setting now has email opening in background - no focus.
However, the default is set as 'True' is not desirable - it should be changed to 'False' so that emails open with focus.

Exactly. When 125 lands, there will be a million confused users unless the default is changed to false.

(In reply to Ed from comment #3)

Exactly. When 125 lands, there will be a million confused users unless the default is changed to false.

I agree, it's good to know this preference finally works correctly, but setting by default to open in background will cause much unnecessary confusion and irritation, it needs the default setting to be:
mail.tabs.loadInBackground set to False

Summary: Tabs load in the background → Default has Tabs load in the background
Type: defect → enhancement
Status: UNCONFIRMED → RESOLVED
Closed: 1 year ago
Duplicate of bug: 1886653
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.