Drupal 8.0 introduce the concept of an entity save/publish dropbutton → . The dropbutton had multiple states, and users could control both the saving and published status of an entity through different submit options in the dropdown that appeared when clicking to the right of the button.
This button was introduced after UX studies and formal design processes identified the need for a button with multiple states (e.g. 'Save as Draft', 'Save and Publish', etc.). Some workflow-oriented systems added options to this button so it could be a more precise way of controlling what happens after a node save.
In Drupal 8.4, issue #2068063: Change "Save and keep un-/published" buttons to a "Published" checkbox and an included "Save" button → removed the dropbutton for entity save, and replaced it with a simple 'Save' button (like in Drupal < 8), and an additional 'Published' checkbox.
While this may be helpful in some simpler use cases, the change not only adds complexity to the node form (and other forms), it also makes it more difficult for administrators used to the new Drupal 8 style of saving entities to understand what will happen with their entity (if there is anything other than 'published' or 'unpublished' states attached to the entity's workflow.
In issue #2068063: Change "Save and keep un-/published" buttons to a "Published" checkbox and an included "Save" button → , there was mention of a study that found the dropbutton overly long and confusing:
In a recent study of the content authoring experience done by Dharmesh users found the newly introduced "Save and keep published" overly long and confusing.
However, I have not been able to see where / when that study was done, or any notes/references pointing to UX advantages of the new style of Published checkbox + Save button over the dropbutton approach. I think if we decide to make such a change to one of the buttons which is probably one of the top 2 or 3 buttons clicked on all Drupal sites, there should be strong evidence it is for the better.
The dropbutton is still used in various other places → in the admin UI.
(Description of the proposed solution, the rationale behind it, and workarounds for people who cannot use the patch.)
Reversion to Drupal 8.0-8.3-style entity save dropbutton.
None.
None.
Closed: won't fix
11.0 🔥
node system
Makes Drupal easier to use. Preferred over UX, D7UX, etc.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Given this has gone stale (~7 years since last comment) and the past few majors haven't changed this I don't think we can revert it now. This could be done in a contrib module ( https://www.drupal.org/project/publishing_dropbutton → still exists)