eclipse-theia/theia

[Violation] Permissions policy violation: unload is not allowed in this document --> layout is not saved

Open

#17,798 opened on Jul 21, 2026

View on GitHubContributor guide
 (0 comments) (1 reaction) (0 assignees)TypeScript (2,478 forks)batch import
browsercoreelectronhelp wantedlayout restoration

Repository metrics

Stars
 (18,676 stars)
PR merge metrics
 (Avg merge 15d 4h) (75 merged PRs in 30d)

Description

Bug Description:

Hi, This note is from the Chrome Developers site https://developer.chrome.com/docs/web-platform/deprecating-unload: The unload event will be gradually deprecated by gradually changing the default so that unload handlers stop firing on pages unless a page explicitly opts in to re-enable them.

The issue is that we see the "[Violation] Permissions policy violation: unload is not allowed in this document" error now in some environments (I can't tell why only in these environments). This error originates from the store layout method, which is triggered during the unload event. Consequently, the layout is not saved in these environments.

So we need to replace all the unload events in Theia code:

  1. DefaultWindowService
  2. DefaultSecondaryWindowService
  3. WindowService (onUnload is triggered on this event)
  4. ElectronMenuContribution, ElectronWindowService, ElectronSecondaryWindowService

Steps to Reproduce:

  1. I don't have steps to reproduce, but once it happens, the layout is not saved, and you see the error above in the console log

Additional Information

  • Operating System: Mac/Windows
  • Theia Version: 1.73

Contributor guide

Research direction
Examine the five files listed (DefaultWindowService, DefaultSecondaryWindowService, WindowService, ElectronMenuContribution, ElectronWindowService, ElectronSecondaryWindowService) to identify where the 'unload' event is used to save the layout. Replace each 'unload' event listener with 'beforeunload' or 'pagehide', as per Chrome's deprecation guide. Ensure the layout saving logic still triggers correctly. Test locally in different browsers and environments to verify the fix.
Tech stack
typescriptelectron
Domain
desktop
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65