Setting title.closable = false on a widget doesn't prevent it from being closed via context menu.
title.closable = false in constructor/init.@Hanksha the closable field is provided by the @phosphor API and is only actionable at the moment for titles.
/**
* Set the closable state for the title.
*
* #### Notes
* This controls the presence of a close icon when applicable.
*/
closable: boolean;
Do you suggest we update the isEnabled of CLOSE commands to respect the property?
If so, I wonder the UX implications it might have. If a user opens a widget, that widget can no longer be closed successfully unless somehow programatically triggered.
If you'd like, you can submit a pull-request to address the issue, it looks like you'd need to update the isEnabled for the following commands:
Something like the following POC (for close):

@vince-fugnitto I think it should not have any implications on widgets in this repo, since they are all closable. By if an end product wants to add a widget which is never can be closed. It should be possible for them.
Most helpful comment
@vince-fugnitto I think it should not have any implications on widgets in this repo, since they are all closable. By if an end product wants to add a widget which is never can be closed. It should be possible for them.