Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

NoScript Not Available for Latest Firefox

noscript.net

Post reply on HN
Print view View original

71–80 of 84 posts

Re: NoScript Not Available for Latest Firefox

#71

Post by arnvidr »

Endy wrote: post #29
mrich wrote: post #14

The plugin breakage is the only downside of the new Firefox, the rest is just awesome. I'm still looking for a new auto form filler that can have multiple profiles and fills in all fields at once with a hotkey. This is useful for filling in bugzilla bug reports where some fields always get the same data.

"The only downside" Sure. Aside from the number of other extensions that simply won't work in new Firefox. And the lack of any user control to make the browser not work like or look like Chrome.

For Classic Theme Restorer withdrawal, try custom userChrome.css code.

https://github.com/Aris-t2/CustomCSSforFx

Re: NoScript Not Available for Latest Firefox

#72

Post by mixedCase »

eadmund wrote: post #62
jchw wrote: post #40

Earlier quoted context omitted.

Killing the old extension API is a painful, but important, step. From a security standpoint, WebExtensions are a lot better, since they are sandboxed and require explicit permissions to be granted for many things. From a developer standpoint, they are easier to deal with, being JavaScript, and since Chrome and Edge support similar APIs, developers will no longer need multiple codebases to support their extensions on…

> From a security standpoint, WebExtensions are a lot better, since they are sandboxed In a sandbox even I, as the owner of the computer, can't let them out of. That's not cool. > From a developer standpoint, they are easier to deal with, being JavaScript, and since Chrome and Edge support similar APIs, developers will no longer need multiple codebases to support their extensions on multiple browsers. In the sense th…

> In a sandbox even I, as the owner of the computer, can't let them out of. That's not cool.

Yes you can. Extensions can talk to processes running on your machine; meaning you can run a daemon that acts as a backend for your extension. It's how KeePassHttp-Connector works, for example.

Re: NoScript Not Available for Latest Firefox

#74

Post by sebazzz »

sp332 wrote: post #61
shock wrote: post #49

Earlier quoted context omitted.

Moving to Firefox 52 isn't really an option for me because it's a pig compared to 55/56 (it consumes almost 5GBs of RAM compared to 1GB for 56).

I think you can switch to an unbranded build of 57, and enable legacy addons. https://wiki.mozilla.org/Add-ons/Extension_Signing#Latest_Bu... You could also install the Developer Edition or a Nightly build. They're slightly less stable (usually pretty good for me) but they have the same option. https://www.mozilla.org/en-US/firefox/channel/desktop/

> enable legacy addons

Does that mean the XPCOM system has just been flagged as disabled, but not been removed yet?

Re: NoScript Not Available for Latest Firefox

#75

Post by majewsky »

digi_owl wrote: post #46
majewsky wrote: post #16

Earlier quoted context omitted.

Switching browsers just because some extension does not work for a few days after an upgrade seems like blowing it waaaay out of proportion.

People stuck with Firefox because of the old, potent, extension framework. Now they have no reason to stick with Firefox because the extension framework is just another Chrome clone, so why not switch to an actual Chrome clone?

Because I trust Mozilla more than both Google and $random_developer.

Re: NoScript Not Available for Latest Firefox

#76

Post by spystath »

Tharkun wrote: post #66
Amezarak wrote: post #47

Earlier quoted context omitted.

> There's so much to be gained from getting rid of the old extension system for concurrency, extension compatibility, and the health of the ecosystem and individual browser installations. I personally think that while it's clearly great for security and possibly good for Firefox in general, it's also terrible for the extension ecosystem. The set of possible extensions is being reduced from "literally anything computa…

After reading these comments, I basically don't want to upgrade. I've been running Classic Theme Restorer for years to get rid of whatever the latest craze in GUI design is. I like my address bar for addresses and my search bar for searches. I love my tree style tabs. I like having a fair amount of control over my browser. For a few years now, I've had the feeling that Firefox was actively trying to get rid of me as…

This is kind of the feeling I have too. I remember firefox in the 2.x and 3.x days when you could do practically anything XUL and XPCOM. I also remember that firefox was dead slow back then. Although I am kind of dissapointed that so much functionality was removed it is inevitable that, in order to get a better and safer browser, some inconveniences are to be expected. I wish there were some kind of middle ground to accomodate power users as well. But Mozilla is not after power users, they can't afford it. It is kind of a shame though.

Re: NoScript Not Available for Latest Firefox

#77

Post by sp332 »

sebazzz wrote: post #74
sp332 wrote: post #61

Earlier quoted context omitted.

I think you can switch to an unbranded build of 57, and enable legacy addons. https://wiki.mozilla.org/Add-ons/Extension_Signing#Latest_Bu... You could also install the Developer Edition or a Nightly build. They're slightly less stable (usually pretty good for me) but they have the same option. https://www.mozilla.org/en-US/firefox/channel/desktop/

> enable legacy addons Does that mean the XPCOM system has just been flagged as disabled, but not been removed yet?

As far as I know, yes. Firefox has already decided to transaction away from XUL, so the extensions will break eventually. It's just a question of when the particular APIs your extension relies on get removed.

Re: NoScript Not Available for Latest Firefox

#78

Post by zcid »

Karunamon wrote: post #50
jchw wrote: post #40

Earlier quoted context omitted.

Killing the old extension API is a painful, but important, step. From a security standpoint, WebExtensions are a lot better, since they are sandboxed and require explicit permissions to be granted for many things. From a developer standpoint, they are easier to deal with, being JavaScript, and since Chrome and Edge support similar APIs, developers will no longer need multiple codebases to support their extensions on…

From a usability standpoint, WebExtensions have a lot less control of the browser and some use cases are completely closed off. The Webex version of Tree Style Tabs, for instance, requires you to have a redundant tab bar on top because it's not allowed to hide the main one. Pentadactyl can't have it's sub-buffer anymore. Download managers/scrapers like DownThemAll can't even do their main function anymore. On and on…

This is my userChrome.css file to correct the tab issue you describe: https://pastebin.com/5PrwSD5k. More tweaks can be found at https://github.com/piroor/treestyletab/wiki/Code-snippets-fo....

I agree that I'm very disappointed with the transition to Web Extensions. In addition to the items you mentioned, Vimium can no longer be used while on a built-in page such as the about: pages or the start page. This is really frustrating since it requires different commands depending on context and leads to breaks in my flow.

I am hopeful that over time we will see an expansion of the current API to include a lot of the functionality that we are currently missing, but Firefox may never achieve the same level of useability that it has had until this point.

Re: NoScript Not Available for Latest Firefox

#79

Post by akerro »

majewsky wrote: post #75
digi_owl wrote: post #46

Earlier quoted context omitted.

People stuck with Firefox because of the old, potent, extension framework. Now they have no reason to stick with Firefox because the extension framework is just another Chrome clone, so why not switch to an actual Chrome clone?

Because I trust Mozilla more than both Google and $random_developer.

Brave Browser is a product from Brendan Eich, ex-CEO of Mozilla and creator of JS.
Post reply on HN