JS Blocker

Posted on by



Amis aptio uefi mmtool. An open source, indie developed, Safari extension that protects your privacy on the web.

  1. Missing JavaScript errors that could potentially be blocking your end users from successfully using your site. For details on this exception see the SDK load failure troubleshooting page.
  2. Jan 13, 2020 ivan-aksamentov changed the title DevTools failed to load SourceMap: Could not load content for browser-polyfill.js.map extension DevTools failed to load SourceMap: Could not load content for browser-polyfill.js.map Jan 13, 2020.
  3. Scan your computer with your Trend Micro product to delete files detected as JSBLOCKER.J. If the detected files have already been cleaned, deleted, or quarantined by your Trend Micro product, no further step is required. You may opt to simply delete the quarantined files. Please check this Knowledge Base page for more information.
  4. Download JS Blocker Features. Quickly and easily block advertisers, tracking agencies, and social media networks from monitoring your online activity. Prevent all scripts on the webpage from being allowed to run. Prevent links from sending referrer information. Block frames, XHRs, embeds, objects, videos, and hide images.

Js Script Blocker

Stay safe and browse the web faster without being tracked. Use user scripts to make websites work how you want them to. Learn more about how webpages collect data on you for tracking purposes over at FixTracking.com, a guide by DuckDuckGo.


This code doesn't currently work in Chrome on Windows. You need to increase the timeout, otherwise it will always say the popup blocker is blocking even when it isn't. I've changed the timeout to 250ms and it seems to work fine in all cases. This appears to be a recent change in Windows Chrome, as it was working before. – CpnCrunch Feb 17 '16.

Features

  • Quickly and easily block advertisers, tracking agencies, and social media networks from monitoring your online activity.
  • Block pop-ups.
  • Prevent all scripts on the webpage from being allowed to run.
  • Prevent links from sending referrer information.
  • Block frames, XHRs, embeds, objects, videos, and hide images.
  • Block many annoyances such as alert dialogs popping up, forms not autocompleting, windows being resized, and more.
  • Full support for Greasemonkey-style user scripts so you can make webpages work exactly how you want them to.
  • Canvas fingerprinting protection.

Deprecated

JS Blocker downloaded from outside the Safari Extension Gallery will cease to function in Safari 12 and macOS Mojave (10.14). Developer-signed Safari extensions are not supported in Safari 12. Safari extensions distributed in the Safari Extension Gallery are deprecated, and Safari 12 is the last release to support them.

Safari App Extension

I have no experience creating native mac apps; it will therefore be impossible for me to re-create JSB as one. Even so, Safari app extensions do not support the features required for JSB to function the way it does now (i.e. lots of functionality will be lost).

Updates

Users who downloaded JS Blocker from the Safari Extension Gallery will not be able to update beyond 5.2.2. Apple is no longer accepting submissions to the gallery.

Js Blocker


Requirements

  • Safari 6.1 to 11.1 (12 if installed from the Safari Extension Gallery)
  • OS X 10.7.5 to macOS 10.13.6

Once downloaded, open the file to install it


About Safari's Content Blocker API

Safari has a feature called 'Content Blockers' that allows for extremely efficient resource blocking on both the desktop and iOS version of Safari. As much as I'd like to incorporate this into JS Blocker, it is not feasible to do so. Using a content blocker will prevent JS Blocker from showing you exactly what's going on on a website (i.e. you won't see what's allowed or blocked.) It'll also break all of JS Blocker's 'other' features, such as showing alerts within the webpage and canvas fingerprinting protection. Besides the loss of features, content blockers are limited to 50,000 rules. While this seems like a high number, it isn't enough for efficient protection and a lot of rules would need to be cut out to even run a content blocker. Until Apple eases the restrictions (or at least raises the number of rules that can be in a content blocker), JS Blocker will not be using this API.

What version of jQuery does the BlockUI plugin require?

Js Blocker Safari 13

BlockUI is compatible with jQuery v1.2.3 and later.
What has changed in version 2 of the BlockUI plugin?
  • Elements are no longer removed from the DOM when unblocking
  • The default overlay color is now black instead of white
  • The available options have been consolidated and sanitized
  • The way in which options are passed to the plugin has changed
  • Support for Opera 8 has been dropped
  • The internals have been restructured for improved readability
  • displayBox functionality removed (other plugins do this better)
Is my code that used the old blockUI plugin compatible with the new 2.0x version?
No, not if that code was passing options to blockUI. The manner in which options are passed has changed slightly. See the Options page for details on how to pass options in the new version.
Blocker
Does the BlockUI Plugin have any dependencies on other plugins?
No.
JS Blocker
Can I use blockUI with TypeScript?
Yes. BlockUI user Joseph Atkinson has kindly provided a TypeScript declaration file for that purpose.
How do I use an external stylesheet to style the blocking message?
See this demo page.
How do I use an external stylesheet to style the blocking overlay?
See this demo page.
Can I change the default message text used when blocking the page?
Yes. The default message is stored in $.blockUI.defaults.message. You can change it simply by assigning a new value, like this:
Can I change the color or transparency of the overlay?
Yes. The default overlay CSS is stored in $.blockUI.defaults.overlayCSS. You can choose a different default overlay color and transparency value like this:
Does BlockUI support Opera 8?
No.
Why don't I see overlays in FF on Linux?
Several people informed me that full page opacity rendering in FF/Linux is crazy slow, so by default it's disabled for that platform. You can enable it by overriding the applyPlatformOpacityRules property like this:
I don't want the message content to be centered. How do override the default position?
See this demo page.