Let’s go!

Unfortunately, I don't think this is so incredibly broken such that they'll be forced to change path.

I'll get used to it, but it's the one area of the new design system that feels like an unequivocal mistake.

I can probably get over this last one, but it also confuses the primary controls on the window.

Are these controlling the window or the sidebar?

But then if it's not floating on top of anything, the effect is incredibly weird and ugly.

The answer to "what is it floating on top of," most often, is nothing.

After all, if there were something there, the user would never be able to access it in most contexts (content scrolls vertically, not horizontally, about 99% of the time).

Apple's framework has this as an option.

The worst is that the sidebar is often confused about what it's supposed to be floating on top of.

This is the *Finder*... what is happening!?

But beyond that, it's just awkward beyond belief.

First, all the margin required by floating it creates a lot of wasted space.

If that were the worst of it, whatever.

The entire concept is wrong from the start: the sidebar is secondary, supporting content.

Bringing it to the foreground flips that in ways that are at best distracting and, at worst, confusing.

Well, this is just a wonderful piece of writing.

Mostly visual bugs. Not bad.

But keep in mind that it’s my iPad, not iPhone, so my usage is much less intense.