Clément Lefèvre Reporter
	Description • 6 years ago

When quitting the browser, for now some times in nightly we have a "warn on closing multiple tabs" that show a tab count.

However, that tab count is completely wrong:! it only counts the number of tabs in the window currently in foreground and ignore all the other ones.

This count should consider the numbner of tabs in every windows.

	:Gijs (he/him) Assignee
	Comment 1 • 6 years ago

This worked when bug 1438499 landed; it regressed in bug 1475427 which changed warnAboutClosingTabs. The fix is trivial, we just need to remove the `null` parameter from the nsBrowserGlue.js callsite. I'll do up a patch on Monday if nobody beats me to it.

	:Gijs (he/him) Assignee
	Comment 2 • 6 years ago

Bug 1438499 added an optional parameter to warnAboutClosingTabs.
In bug 1475427, the arguments to warnAboutClosingTabs changed, and instead
of passing a closing tab reference as the second argument, we now need to
pass the number of tabs as the first argument. The patch in that bug
updated the callsite in nsBrowserGlue.js to add the new argument, but
didn't remove the `null` argument that we were passing for the 'extra' tab.

Additionally, the change in bug 1475427 bails early from
warnAboutClosingTabs if the number of tabs passed is less than 2. That tab
count, too, needs to take into account multiple windows and not just the
last window iterated over.

This patch fixes both of these issues.

	Mike Conley (:mconley) (:⚙️)
	Comment 3 • 6 years ago

Comment on attachment 9002539 [details]
Bug 1483935 - correctly check all windows for tabs when quitting, r?mconley

Mike Conley (:mconley) (:⚙️) has approved the revision.

	Pulsebot
	Comment 4 • 6 years ago

Pushed by gijskruitbosch@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/00e27ad3f9ff
correctly check all windows for tabs when quitting, r=mconley

	Daniel Varga [:dvarga]
	Comment 5 • 6 years ago
bugherder

https://hg.mozilla.org/mozilla-central/rev/00e27ad3f9ff

	Emil Ghitta, QA [:emilghitta]
	Comment 6 • 6 years ago

Verified that this issue is no longer reproducible using Firefox 63.0b8 (BuildId:20180920135444) on Windows 10 64bit, macOS 10.13.6 and Ubuntu 16.04 64bit.