Web Isolation Read-Only mode not working for some websites

Products

• Web Isolation Cloud

Issue/Introduction

Read-Only mode in Web Isolation is not functioning as expected on certain websites:

• The Read-Only popup does not appear.
• Users are still able to interact with fields despite policy restrictions

Environment

Web Isolation Cloud

Cause

There are these primary causes for this behavior:

1. Lack of Input Fields: The Read-Only popup is programmatically triggered only when a user interacts with an input field. If a page does not contain standard input fields, the popup will not trigger.
2. Online Service Suites (Google Sign-in): On some websites, the popup triggers a Google sign-in flow. Since Google is part of the Online Service Suites, isolation is intentionally disabled for these frames to allow credential entry. Because the main frame and the popup often reference the same policy object, enabling input for the popup inadvertently enables it for the main frame.
3. Selective Isolation Session Persistency: The Selective Isolation setting in Online Service Suites affects all tabs within a single browser session. If a user tests a URL in a session where an Online Service Suite was active, the 'allow input' state may persist across other tabs in that same session.

Resolution

The workaround for this scenario is to disable Selective Isolation in Online Service Suites in the Rule Advanced Settings.

The issue is resolved in Web Isolation v1.16.271