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
Hi Enthusiast, I had that problem with a site a while back and in that case it was a hosting problem with IPv6, which didn't work properly on the server this site was on. I updated...
Error when trying to check for updates
Hi. Welcome to Backdrop. Out of the box, there are two places you can set visibility by user ID and they are related: The layout configure screen under "Visibility conditions" (admin/structure/...
Use visibility User by uid
Start with clean URLs, add Pathauto and Metatag modules, submit your XML sitemap to Google Search Console, and keep your content original and well-structured.
How to Improve SEO Performance in Backdrop CMS