5 ms·

Maybe Mozilla could take a few days off from Flash and PDF and build in some good white-listing features. It's the last feature browsers actually need. After th

Maybe Mozilla could take a few days off from Flash and PDF and build in some good white-listing features. It's the last feature browsers actually need. After that it's nothing but speed and security.

DeepYogurt 10y ago
I for one would love if mozilla built in some javascript controls in by default.
TD-Linux 10y ago
Like this, released last week? https://testpilot.firefox.com/experiments/tracking-protection https://testpilot.firefox.com/experiments/tracking-protectio...
- Sylos 10y ago
  That wasn't really released last week. It's been in Firefox and default-enabled in Private Browsing for probably a year already. This just enables it in normal browsing as well, and they've only published it via Test Pilot for testing, as you could already enable it in normal browsing before by setting "privacy.trackingprotection.enabled" in about:config to true.
- nercht12 10y ago
  It tells me I need Javascript. Ironic, no?
- digi_owl 10y ago
  That do not seem to offer the detailed control that noscript does.
  - TD-Linux 10y ago
    Nor would I expect it to - that's what extensions are for. This is a one-click tool.
acqq 10y ago
The old Opera had javascript per-url white-listing built-in, and the same for the extensions, and I believe that the new Chromium based doesn't. The Chrome extension also lacks what the old Opera had.
PhantomGremlin 10y ago
It's the last feature browsers actually need. What browsers still actually need is a really good way of dealing with certificates. The current mess is a sad joke. I've tried things like Certificate Patrol, but that has tremendous problems in everyday usage. Browsers do a little bit of pinning, but security for the vast majority of sites is still dependent on the non-malfeasance of each and every one of the hundreds of certificate authorities that are trusted by default. IMO that is problem #1, and it's been problem #1 for a decade or more. Mozilla takes in about $300 million a year, but I guess certificates are just too difficult a problem to solve properly with such a paltry sum of money.

Maybe Mozilla could take a few days off from Flash and PDF and build in some good white-listing features. It's the last feature browsers actually need. After that it's nothing but speed and security.

DeepYogurt 10y ago

I for one would love if mozilla built in some javascript controls in by default.

TD-Linux 10y ago

Like this, released last week? https://testpilot.firefox.com/experiments/tracking-protection https://testpilot.firefox.com/experiments/tracking-protectio...

Sylos 10y ago
That wasn't really released last week. It's been in Firefox and default-enabled in Private Browsing for probably a year already. This just enables it in normal browsing as well, and they've only published it via Test Pilot for testing, as you could already enable it in normal browsing before by setting "privacy.trackingprotection.enabled" in about:config to true.
nercht12 10y ago
It tells me I need Javascript. Ironic, no?
digi_owl 10y ago
That do not seem to offer the detailed control that noscript does.
- TD-Linux 10y ago
  Nor would I expect it to - that's what extensions are for. This is a one-click tool.

acqq 10y ago

The old Opera had javascript per-url white-listing built-in, and the same for the extensions, and I believe that the new Chromium based doesn't. The Chrome extension also lacks what the old Opera had.

PhantomGremlin 10y ago

It's the last feature browsers actually need. What browsers still actually need is a really good way of dealing with certificates. The current mess is a sad joke. I've tried things like Certificate Patrol, but that has tremendous problems in everyday usage. Browsers do a little bit of pinning, but security for the vast majority of sites is still dependent on the non-malfeasance of each and every one of the hundreds of certificate authorities that are trusted by default. IMO that is problem #1, and it's been problem #1 for a decade or more. Mozilla takes in about $300 million a year, but I guess certificates are just too difficult a problem to solve properly with such a paltry sum of money.