Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "webextensions"
-
Great. Just FUCKING great. When I was looking at devrant, suddenly some add-ons crashed (correction: ALL add-ons crashed!). All other tabs flooded with ads. I go to the add-ons manager, and what is their SHITTY excuse?
"Starting in Firefox version 57, only extensions built using WebExtensions APIs will work. Not sure if your add-ons are affected? See Firefox add-on technology is modernizing and these Frequently Asked Questions for details."
Anyone of you fuckwits ever heard of LEGACY SUPPORT? Leaving some time so the other devs can adapt to your new brainfart technology?! Even fucking C++ has that. FUCK!
Thank god devrant doesn't have ads.8 -
FUCKING MOZILLA!
>Quantum
>over9999 times faster
-Ughm, okay, but what is the trick?..
-THE TRICK IS THAT NONE OF YOUR FAVORITE ADDONS WILL WORK!!!
Seriously this is fucking insane! Several of my addons which were essential for me to stay sane is gone and I don't even know how to live without them. And all this bullshit is happening because these idiots in Mozilla decided to enforce use of WebExtensions. For ones who unaware, WebExtensions is much, much poorer framework and many cool addons simply unable to work under WebExtensions because of its limitations.
Are you the one who loved the speed and joy of using mouse gestures? GUESS WHAT — IT'S GONE.
Maybe you made your browsing activity super efficient with use of the “Tab Groups” addon that used to allow you to group your browser sessions? SAY BYE-BYE TO IT!
And many more!
Most importantly, I cannot understand why would a company enforce use of a framework that will decrease functionality of a product.
Anyway, it seems like Firefox is not a browser for addon enthusiasts like me anymore; got to find a new one, any recommendations?11 -
Okay but
Webextensions api can go fuck itself with an exhaust pipe
Ive been debugging for a fucking day because apparently a script that i embed in a site doesnt have the same csp as the fucking site3 -
Trying to port a legacy Firefox add-on I didn't write to WebExtension. Failing so amazingly...
Vague explanations, no tutorials. Mdn has a nice documentation but no tutorials. What's up with that??
Also, JavaScript. And stuff I didn't write. Just perfect. 😑😑😑2 -
Once the WebExtensions process of Firefox crashes, one must restart each extension individually.
This means one has to open the add-on manager and double-click these small toggles with the cursor. When one does not double-click fast enough, the listed extension moves from the "enabled" down to the "disabled" section, and the add-on manager lacks a search feature, (Ctrl+F just actuates the "Search addons.mozilla.org" search bar), meaning one has to manually scroll and find it.
It almost seems like it is deliberately designed to annoy users.6 -
https://developer.mozilla.org/en-US...
When I see a js project or other with instructions to "start by creating a manifest.json" I as a beginner expect this level of explanation about the available manifest options. What each line is for, why you would use it, and if it is optional or not.
Otherwise it's just another cryptic and useless file occupying space in the symbol table that exists in my head, floating there without reason, description or purpose..kind of like a js lib without adequate documentation on its manifest.json.
One more arbitrary thing I have to remember, (and thus will forget) each time I have to use that library.1 -
TMW you have to practically rewrite your extension 'cause the vendor deprecated and replaced the entire SDK