Date: Sun, 06 May 2018 07:55:21 +0000 From: bugzilla-noreply@freebsd.org To: gecko@FreeBSD.org Subject: [Bug 226476] www/firefox: update to 60.0 Message-ID: <bug-226476-21738-tLsgl3mXII@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-226476-21738@https.bugs.freebsd.org/bugzilla/> References: <bug-226476-21738@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226476 --- Comment #48 from Graham Perrin <grahamperrin@gmail.com> --- > … disabled Tab Session Manager, > re-enabled Session Boss, > re-enabled e10s, quit. … I forgot to re-enable e10s. > The same number, restored with Session Boss: … – was OK. > … use Tip Tab to load some (restored) YouTube tabs. Within the restored session I found (with Tip Tab) and loaded three YouTube videos. At some point during the session – maybe whilst the three videos played concurrently – there was, in response to a click on (or load of) a tab, _momentary_ appearance of a content process. The momentary multi-process surprised me, but I don't know whether it's a bug: - is it _ever_ appropriate to have more than one process when browser.tabs.remote.force-disable is true? I guess that Mozilla may invalidate any bug report that involves browser.tabs.remote.force-disable with Firefox Quantum. Jan, any thoughts? Would you like this spun off to a separate bug report in either the Mozilla or FreeBSD area? TIA -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-226476-21738-tLsgl3mXII>