Description of the need This is a long standing confusion. In Drupal there are multiple issues for this:
- https://www.drupal.org/project/drupal/issues/502430
 - https://www.drupal.org/project/drupal/issues/848470
 - https://www.drupal.org/project/drupal/issues/2862291
 
The first issue describes it well:
It is somewhat disconcerting to users who have the 'administer book outlines' permission to see the 'outline' tab and 'outline' fieldset on every single node type, regardless of whether that node type has been configured to be allowed in books. I can see a use-case where that might be a desired feature, but i think its probably relatively rare.
Note, that book module seems to be the oddball here. If you disable menus for a content type not even user 1 has ability to add them to a menu from within the content type.
Proposed solution
Create an additional checkbox in the content/book/settings form that when checked allows book outlines for any content type, not just the designated book-types. By default this is checked, so that any current sites that might rely on "seeing outline information on all content types regardless of config settings" won't be broken by this after upgrading.
  
Recent comments
Thanks for your prompt reply. I tried the Autosave module that you mentioned, but it saves to the database, and the behavior I am looking for is to save to localStorage, in other words,...
Implementing autosave in Ckeditor 5
Hi lloyddunn, the important thing is: don't mix up CKEditor "autosave" (client side) and node save. Node save means, that the current form gets validated and saved to the Backdrop...
Implementing autosave in Ckeditor 5
Thanks, that's very helpful
Where can I find webform submitted emails?