We have received reports that encrypted downloads fail in environments with restricted browser settings, specifically when the "File editing" permission is blocked in Chromium-based browsers (e.g., Chrome, Edge), which is sometimes applied at the organisational level.

This restriction prevents the showSaveFilePicker window from opening, which is required for encrypted downloads to complete.

Error Message: Failed to execute 'showSaveFilePicker' on 'Window': The request is not allowed by the user agent or the platform in the current context.

Question: Is this behavior by design, or is there a potential solution to allow encrypted downloads in environments with these restrictions? We are seeking clarification on whether a workaround or alternative approach is possible.

Steps to Reproduce

1. Configure a Chromium-based browser with the "File editing" permission blocked.
   • For Edge: This can be done through settings at edge://settings/content/fileEditing.
2. Attempt to download an encrypted file.
3. Observe that the download fails, and no "Save As" dialog appears.

Expected Behavior

The download should either:

• Succeed by utilizing an alternative method for saving the encrypted file that does not require the blocked permission, if such a method is available.
• Provide a clear error message to the user explaining that the download is blocked due to restricted permissions.

Additional Information

This issue is likely to affect users in clinical or other sensitive environments where browser permissions are centrally managed for compliance/regulatory reasons.