Un-synced Patterns Behave Differently in WP 7

This isn’t necessarily a bug but I have a question about Local Patterns in WordPress 7.0.

This morning, I added a Local Pattern to a page. It’s a standard set of two nested Container blocks with global styles that I use on all my pages. Instead of simply adding the blocks as it normally did pre-version 7, it added a pattern block. Previously, I’d simply start adding my content but now two things are very different about the editing experience.

First, the blocks that are inside the pattern no longer appear in the Document Overview tree. It simply shows a single pattern instead of all the nested blocks.

Second, to edit the content, you now need to click “Edit pattern,” which exposes the blocks in the Document Overview and allows for editing.

At first, I was alarmed, as this behavior seemed to be the same as synced patterns. But I performed an experiment and confirmed that editing the pattern did not effect other implementations of the unsynced pattern.

So I have some final thoughts, a question, and a request: I actually like this new behavior, as it simplifies the interface a bit and makes it clearer that the origin of the page content was a local pattern. My question is whether or not GB plans on changing this in a future release. And my request is that if this behavior doesn’t change that the UI somehow clearly distinguishes between an unsynced and synced local pattern.