3 ms·
Yeah, I have 15 extensions running right now. You can still get full themes (called "complete themes", not the skins they call "themes"), and there's even a "co
by sp332 9y ago
Yeah, I have 15 extensions running right now. You can still get full themes (called "complete themes", not the skins they call "themes"), and there's even a "compact" category. https://addons.mozilla.org/en-US/firefox/complete-themes/compact https://addons.mozilla.org/en-US/firefox/complete-themes/com... Not having abilities like vimperator is a bug https://bugzilla.mozilla.org/show_bug.cgi?id=1320332 https://bugzilla.mozilla.org/show_bug.cgi?id=1320332 I can't deny that the new API doesn't have enough power, but that's temporary. Being Chrome-like and having weak extensions are not goals. There's even a meta-bug that tracks new proposed functions that Chrome doesn't have. https://bugzilla.mozilla.org/show_bug.cgi?id=1215059 https://bugzilla.mozilla.org/show_bug.cgi?id=1215059
- Karunamon 9y agoThanks for the link to the themes page (I must have overlooked that and thought they blew up the theme system outright), and there are a couple of promising ones I'm looking at now. That said, given the treatment of how some other bugs are handled, especially one particularly noxious one regarding dupe SSL certs that's been kicking around for nearly a decade now that renders Firefox unusable for technical enterprise users, the fact that it's filed in their tracker doesn't mean much, and their classification of that bug as "(REOPENED bug which will not be worked on by staff, but a patch will be accepted)" tells me that compatibility isn't that much of a priority internally. Why not let it bake a little longer and then release it? Surely Firefox won't turn into a pumpkin if they fail to push it out the door by November?