Release Notes ✧ 4.1.1
New: Added a more comprehensive list of effective top-level domains.
New: Support for page-based rules. This will only be available in the "Adding a Rule" poppies. User scripts will be re-evaluated and new rules will be created, fully respecting the @include, @match, and @exclude directives.
New: Added the ability to randomize environmental information revealed by window.navigator and window.screen. This feature can be enabled from the "Other Features" tab of the settings page. If a webpage seems broken after enabling this, try creating a rule to allow it first.
New: Added a new setting to further simplify the display of items (e.g. Google Tracking, Google Advertisements, Facebook, Twitter, etc.) It is enabled by default. This will be displayed only when in simple view.
Changed: The @version directive will now be checked for before determining if a user script is capable of being updated.
Changed: User scripts that contain multiple blocks of metadata will now be fully parsed.
Changed: User scripts using @installURL instead of @downloadURL can now be automatically updated.
Changed: Developer mode scripts will now re-download only if it is allowed on the page being loaded.
Changed: Inline alerts and XHR notifications will now always be displayed on the top page, never within a frame, to ensure its visibility.
Changed: The control buttons in an XHR notification are now always visible; no longer need to scroll the view to see them.
Changed: The close button on notifications is now always visible and no longer an image.
Changed: The document.hidden property is now checked before updating the popover.
Fix: Resolves an issue where some events (most notably XHR) would stop working if a page is inactive for more than 2 minutes.
Fix: Resolves an issue where user scripts may fail to update if it took longer than 5ms to download.
Fix: Having the XHR blocker set to "Ask when necessary" will no longer cause JSB to incorrectly count the number of allowed/blocked resources.
Fix: The user scripts update checker will no longer set the last update time when a developer mode script is re-downloaded. This had prevented non-developer-mode scripts from being updated.