Väljalaskemärkmed

• Fixed an issue where the DNR rule didn't work when opening the browser with a URL (e.g., when clicking a link in another app to open it in the browser).
  • To address this, we changed the DNR rules from Session Rules, which reset every time the browser launches, to Dynamic Rules, which persist across browser launches. Learn more
  • Previously, we intentionally used Session Rules as a workaround for an issue where unnecessary rules sometimes remained enabled. However, since version 8.0.0, this issue has been resolved, so we can now use Dynamic Rules.
• Fixed a minor UI issue related to popovers.

• [Mac] Fixed an issue where the Target Browsers option of a rule didn't work correctly when the specified browser option was added by the user.
• Fixed a minor UI issue

(This version is only for the app that is available in the App Store.)

• [Mac] Support the new look of macOS Tahoe.
• [Mac] Fixed that the non-Safari extensions couldn't recognize the app on macOS Ventura 13.7.8. (This was caused by a failure of setting up the manifest files of native messaging hosts.)
• Fixed other minor bugs and improved performance.

(This version is only for the app that is available in the App Store.)

• Fixed an issue where soft line breaks in rule comments written in Markdown were ignored. (Our Markdown implementation is supposed to follow GitHub's Markdown style.)
• [Mac] The Edit Rule screen has some options you can remove its items, such as Excluded URL Patterns, but the buttons to remove them were hard to press. Now they are easier to press.

(This version is only for the app that is available in the App Store.)

• Now you can show bold texts, link, etc. for rule's comments using Markdown or AsciiDoc! You can choose it in the Edit Rule screen. (You can still use plain text if you prefer.)
• [Microsoft Edge] Fixed an issue where the extension's icon was not correctly shown in the toolbar.
• [iOS] Now you can dismiss the keyboard by sliding down in the Edit Rule screen.
• Improved the performance of screens, especially the Library screen.
• [iOS, macOS] Support iOS/macOS 26 style app icons.
  • (Full iOS/macOS 26 support is still work in progress.)
• [iPad] Fixed an issue where the UI of the Rule Details screen is broken when the device is rotated.
• Other minor bug fixes and performance improvements.

• [macOS app] Fixed an issue where the extension did not work on macOS Ventura and Monterey. See more details here.

This version is only available for the app available in the Mac App Store.

• [iOS Safari] Fixed an issue where the extension sometimes failed to detect a page load for rules with the Original type. For example, a rule redirecting Reddit to its old domain occasionally didn't work when the user entered the URL in the address bar.
  • To address this, we added another page load event handling in case the extension misses a page load.
  • This issue had occurred since 8.0.0. So far, we have confirmed it only in Safari on iOS, but since it could potentially affect other browsers and the added error handling only applies when a page load is clearly missed, we applied the same change across all browsers.

• [Firefox] Fixed an issue where the extension didn't handle in-page navigation correctly. This issue caused a problem where the redirection didn't happen on sites like Google Maps, for example.

This version is only available for the extension in Firefox Add-ons (AMO). There is no equivalent version for other browsers or the native app.

• Now supports navigation to the localized support website. For example, Japanese users are directed to the Japanese version of the site.
• Fixed an issue where the QuickLook preview was not displaying correctly.
• [macOS] Fixed an issue where JSON files couldn't be opened by dragging and dropping them onto the app icon in the dock.
• Tweaked translations.

• [macOS] Fixed an issue where extensions for Firefox couldn't connect to the Redirect Web app. The problem occurred when the folder for manifest files of native messaging hosts didn't exist. Mozilla considers it the browser’s responsibility to create this folder, but they haven't done so as noted in their 8-year-old bug report. To address this, we added a check that creates the folder if it's missing. This fallback mechanism is applied to all supported browsers just in case.