It depends.
For the "iStat Menus is partially rendered inside the notch" problem, the developers seem to have done everything right. This is
probably a bug on Apple's end. The thing is, the fix to that will be that, in this scenario, iStat Menus will be
entirely invisible. I'm not sure anyone will love that?
This is not how software development works. We use (ideally) libraries from the platform vendor (in this case, iStat Menus say they did), and that means that as long as you stick with the guidelines, the platform vendor is now responsible for such basics as drawing things correctly.
It definitely should be consistent, yes.
If you excuse the crude ASCII art:
Code:
Safari File Edit View History Bookmarks Develop Window Help |||||||(notch)||||||| ? ? ? Wed 27. Oct 13:24
Some Additional Menus Go Here |||||||(notch)|||||||
Here we have two rows of menus. The first shows some status items to the right (in this scenario, a lot more status items would fit). But instead of continuing the menus to the right of the notch (at which point they will eventually overlap with status items, like with what Quinn is complaining about), we're
wrapping the menus, and we continue just after the application menu. We might even vertically center the Apple and application menus, and the status items:
Code:
File Edit View History Bookmarks Develop Window Help |||||||(notch)|||||||
Safari |||||||(notch)||||||| ? ? ? Wed 27. Oct 13:24
Some Additional Menus Go Here |||||||(notch)|||||||
Here's the problem: what happens if you click File? Do you obscure the second row of windows? Does the first item in the file menu start where, previously, the second row was? Do you leave a gap (maybe you continue to show the second row, but with 30% opacity?)? None of those will look quite right, and none of them will be easy to use.
That's why
some developers back in the 90s (I think IBM may have started this) thought: in that case, we
flip the order; if you want something from the second row, it gets moved over to the first row first, so that it looks right again. But that's obviously very awkward to use, too.
And I think that's why Apple's approach in the past 20 years has been "lalala this isn't a problem!".