Assignee: Giorgio Maone Link to add-on: https://addons.mozilla.org/en-US/firefox/addon/tab-mix-plus/ Contact info for add-on: http://tmp.garyr.net/ Add-on ID: {dc572301-7619-498c-a57d-39143191b318} How well does it work?: 100% Steps to reproduce working features: * Tab extra commands / properties -> right click on any tab and select the TMP-added menu items, such as "Protect" or "Lock", then try to close the tab or load a link to a different page in the same tab (both actions should fail) * Link navigation behavior: in a content page featuring both external and internal links, try different click variants (right/left/middle, with or without modifier) to test consistency with the behavior configured in TMP options. * UI enhancements: try enabling some from TMP's options panel, and check whether they're reflected in Firefox's tab strip Steps to reproduce broken features: --- Any obvious performance problems? no Chromium version: none, likely because the modifications to the tab strip and the single tabs allowed by XUL, both visual and behavioral, cannot currently be matched by Chromium's extensions API.

Tested on firefox x64 52.0b3 running on Windows 7 sp1 x64 User Agent Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:52.0) Gecko/20100101 Firefox/52.0 Multiprocess Windows 1/1 (Enabled by user) tab mix plus version: 0.5.0.2 * Tab extra commands / properties -> right click on any tab and select the TMP-added menu items, such as "Protect" or "Lock", then try to close the tab or load a link to a different page in the same tab (both actions should fail) -this works fine for me. I'm able to protect a tab and click on links within the tab without it locking up. Same result when I lock a tab. When I lock a tab, I can also close the tab. * Link navigation behavior: in a content page featuring both external and internal links, try different click variants (right/left/middle, with or without modifier) to test consistency with the behavior configured in TMP options. -this also works fine for me. * UI enhancements: try enabling some from TMP's options panel, and check whether they're reflected in Firefox's tab strip I will try this with 300+ tabs next. But in my initial tests, I do not see any problems with the current version of this extension when e10s is forced to be enabled. Considering the extension author set the flag for it to be compatible with e10s, I think we should stop blocklisting their extension. This extension was working with e10s just a week or 2 ago while I was testing the 51 beta version. Was it decided to blocklist it in the 52 beta?

What is the reason that Tab Mix Plus is still on the e10s blocklist for Fx53? (according to "extensions.e10s.rollout.blocklist") Is it still about Bug 1192585? (Or ultimately Bug 1037179?) Meaning performance regression in loadtime with e10s in comparism to non-e10s during parallel tab-opening. Can this issue still be reproduced with the latest version with significant differences? Since the last comment by the add-on author on those bugs (releasing 0.5.0.2pre.161225a1 which already should improve the situation) there have been four new versions (0.5.0.2pre.170102a1, 0.5.0.3pre.170314a1, 0.5.0.3pre.170405a1, 0.5.0.3pre.170421a1) with many changes. (Changelog: http://tabmixplus.org/support/viewtopic.php?t=1) It would be nice to consider a removal of the e10s blocklisting. I guess the 700k users of Tab Mix Plus would be happy about it. This would also resolve the confusions why Firefox won't enable e10s even though the "arewee10syet.com"-page and also the Add-on Compatibility Reporter say "compatible" for Tab Mix Plus. (Like here for example: http://tabmixplus.org/forum/viewtopic.php?f=2&t=19761)

With Firefox 57 only WebExtensions are permitted and are, by default, e10s compatible.