I understand the logic in that from a technical aspect in the workflow of saving layout changes (and being able to cancel those if required), but from an end-user experience point it is not that great. So...
Edit a layout, then edit a custom block and change its text. Save the block (it feels funny by the way that the button says "Save configuration", but lets leave that for another issue*). At this point, a new user would expect that refreshing the page that shows the changes they've just made in the backend would reflect those changes in the front end. That doesn't happen though. They need to return to the layout edit page (thinking that Backdrop "doesn't work") and then they see the "This form has unsaved changes." message that asks them to save the layout (#1656).
As I said, not optimal UX there.
Recent comments
Thank you, this is a very useful workaround for preparing a clean import list. One concern remains, however: if Simplenews 1.x-1.2.3 still treats blocked user accounts as invalid...
Re-enable Simplenews newsletter subscriptions that had been erroneously disabled
@Amilenkov, I have an idea for your use case where you want to avoid re-subscribing people who have explicitly opted out: Build a view of simplenews subscriptions, and filter by Status (...
Re-enable Simplenews newsletter subscriptions that had been erroneously disabled
"modules to help someone monetise their own website"
How to monetize a Backdrop site