Skip to content
Browsium Documentation Portal Browsium

[Known Issues]

  • Due to a bug in Microsoft Edge (Chromium) 80, the browser extension will not be automatically enabled. To force enablement, the extension will have to be installed into Edge’s extension install forcelist. Once this bug is addressed by Microsoft the extension will be automatically enabled without this additional step.

  • Due to the forced user notification change in the way Mozilla Firefox handles sideloading of extensions, starting with Firefox 74 Browsium Client requires the use of the ESR to ensure extensions are auto-enabled during installation. Use of the non ESR will prohibit automatic enablement of the Browsium Client Extension.

  • Some users may experience an installation failure, resulting in a loop, with the Microsoft Visual C++ 2017 redistributable (x86 and x64) installers. This is an issue with the prerequisite installation process and not the Browsium Client installer. To resolve this issue, manually install the Visual C++ runtimes prior to installing the Browsium Client.

  • All Chrome, Firefox and Edge (Edge Legacy and Edge Chromium) browsers may need a restart to completely stop evaluating rules after removing Catalyst Configuration on the machine.

  • Firefox and Edge do not support extensions redirecting to file URLs, so custom redirect settings in Catalyst must not use file URLs if using Legacy Edge or Firefox. In this circumstance, the default redirect page will be shown instead in those browsers.

  • Edge (Legacy) browser shows a “spinning dots” loading webpage when Catalyst redirects a web page out of Edge browser using “Same page” target action

  • Catalyst is disabled by default for Internet Explorer’s InPrivate mode as well as Edge (Chromium) and Chrome’s Incognito modes. Catalyst can be enabled manually for these modes.

  • When Project->Project Settings->Override Default Browser is enabled, the default browser may show a warning that it is not the default browser on the system. For Catalyst to be able to evaluate rules from non-browser applications, please select “Don’t ask again” option in Internet Explorer, Firefox and Chrome browsers. These settings can be managed by Group Policy in an enterprise deployment.

  • Catalyst cannot execute a rule against the homepage for Firefox. The homepage will load regardless of Catalyst settings. In general, it is not recommended to set Catalyst rules for URLs that are also set as browser homepages.

  • Catalyst does not support Custom zones in Internet Explorer.

  • When a browser has Block Other Requests enabled, it will not evaluate rules unless those rules have a Starting Browser set to Any. A rule with the Starting Browser set to a specific browser and the Target Browser set to a browser with Block Other Requests enabled may cause a looping condition and should be avoided.

  • When redirecting between browsers via Catalyst rules, the Starting Browser may navigate to a blank page, navigate back one page in the browser history, or close the tab entirely if the navigation crosses between Internet Explorer zones. This is due to an issue with how Internet Explorer exposes its history to Browser Helper Objects. This issue should not interfere with the proper function of any web applications.