As upstream did. Reproducible: Always
Upstream gtk3 is still a while from ready, but once it is considered ready by upstream we will offer a use flag for it. In the meantime, see bug 552060
(In reply to Ian Stakenvicius from comment #1) > Upstream gtk3 is still a while from ready, but once it is considered ready > by upstream we will offer a use flag for it. > > In the meantime, see bug 552060 Well, I'd somewhat agree , though... The reporter might be referring to https://bugzilla.mozilla.org/show_bug.cgi?id=1186229, though that's not quite the same as https://bugzilla.mozilla.org/show_bug.cgi?id=1186748...
it looks like gtk3 is going to be the upstream default for mozilla-42 (current mozilla-central repo, I believe), but that's still a long ways off from being part of the release. There's also a rather large number of bugs open for the GTK2->GTK3 port, so i guess we'll see how that goes. At any rate, just for fun, I added GTK3 support to mozconfig (which can be enabled in ebuilds that want to give the option), and a firefox-40 ebuild that lets you enable GTK3, on mozilla-overlay. Have fun with it -- I won't be exposing the gtk3 flag in the portage tree ebuilds until mozilla-42 though, fyi.
...still given the flags on the already closed bugs, it seems firefox 42 will be the target... Coincidentally, that's the same version electrolysis is planed to be turned on on release... ...yay...
Firefox +gtk3 have issue CTRL+K in <x11-libs/gtk+-3.18 gtk+-3.18 have simple patch: https://git.gnome.org/browse/gtk+/patch/?id=15411aa032ca0c36f8a9adc9c1c2ee71a5131fbf "This interferes with a well-loved firefox shortcut, and we are more interested in a gtk3 firefox than in legacy keybindings." Upstream issue https://bugzilla.mozilla.org/show_bug.cgi?id=1176929
(In reply to Maxim Britov from comment #5) > Firefox +gtk3 have issue CTRL+K in <x11-libs/gtk+-3.18 > Actually, regardless of that, gtk3 was postponed (at 41.0 release) at least one version (to 43.0). That's still a few weeks off, so we might get gtk+ 3.18 in the tree before that.
...so, the upstream delayed the switch again (to 45), but this time for a very mozilla reason, instead of a technical one (go and see the upstream bugs). If you disregard that, gtk3 is working pretty well, though just like with webkit-gtk gtk2 dep will need to remain due to plugins (though unlike in that case, the wrapper lib is quite small).
GTK3 support was officially added to Firefox 46 https://www.mozilla.org/en-US/firefox/46.0/releasenotes/
This is probably obsolete or fixed now For better compat with gtk3, I would opt for building the gtk3 backend for firefox >= 48, while keep using gtk2 for current stable (45 was?)
(In reply to Pacho Ramos from comment #9) > This is probably obsolete or fixed now > > For better compat with gtk3, I would opt for building the gtk3 backend for > firefox >= 48, while keep using gtk2 for current stable (45 was?) Agreed. As backporting the gtk+-3.20 compatibility patches are not really an option, I've disabled gtk3 support in the 45.x series starting with firefox-45.3.0 ; firefox-48.0 continues default gtk3 support.
