Perspective reset does not close Help or Welcome views

[basilevs]

Steps to reproduce

On a fresh Eclipse Platform and a new workspace (new workspace is important)

• Close Welcome view
• Select menu item Help/Show Context Help
• Reset perspective
  • Select menu item Window/Perspective/Reset Perspective
    • Confirm the dialog
  • or use context menu on perspective button

Expected result

No Help view. The reset should cause the same workbench layout independently of initial state.

Actual result

Help view survives reset. Same for Welcome view.

If perspective is closed, the affected view stays.

If views are moved to a different tab group, perspective reset starts to affect them. The change is saved in the workspace.

It looks like the views are not initially managed by perspectives.

Tested under this environment:

• Reproducible on Linux and MacOS
• Eclipse Platform Version: 2025-06 (4.36) Build id: I20250507-1500 (staging Eclipse Platform installed by Oomph)

Impact

The perspective reset functionality is very important for automated tests, as there is no other way to conveniently and automatically close additional views hogging screen space.

[iloveeclipse]

Would you like to provide a patch?

[basilevs]

Would you like to provide a patch?

I do not understand why are parts outside perspective needed, also there is a special dance in org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.hideLocalPlaceholders(MWindow, MPerspective) to support them, so apparently, they can't be just hidden.
This seems to require a decision from an owner of E4 model design.

[iloveeclipse]

Probably you want a different API to reset workbench state to some "default" perspective with nothing else.

[basilevs]

Probably you want a different API to reset workbench state to some "default" perspective with nothing else.

I have a workaround for that - I'll just close everything returned from org.eclipse.ui.IWorkbenchPage.getViewReferences() before the reset.

UPDATE: huh, it is bugged out too 😫

[basilevs]

An Eclipse command resetting the state would be better instead of Java API. This would allow end user and RCPTT to work in a matching manner.