The way things work right now is totally intentional. Only code that actually deals with area geometry (ScrEdges and ScrVerts) should use ScrArea.vn. The bounds of ScrArea.totrct and the v1, v2, v3, v4 vertices are not supposed to match. Doing so would reduce the space between editors:

Current	With patch

I'm a bit skeptical about using the number keys for mode changing too. When changing a mode, users also typically change the task they are doing (object mode is an exception). That is exactly what workspaces should handle though - each workspace would have it's own mode set, e.g. the "Animation" workspace would be in pose mode, the "Retopo" workspace would be in edit mode with necessary tools, add-ons and viewport settings loaded. See T55246 & T53389.
So in the big picture, the workspace mode and multi-object editing would mean users switch modes far less frequent. Instead they would change workspaces. They'd probably still regularly toggle between Object Mode and the workspace mode.

mprovements to BLI_str_format_bytes

Stumbled over this today and made some changes. Should be ready to go now.

This is most likely a graphics driver failure, you can try if updating your driver fixes the issue.

It should definitely be possible to hide it by dragging its edge - just like the lower part of the top-bar.

Not sure if there are currently specific rules for triaging Code Quest reports, but guess it's reasonable to tag this as high priority.

Same happens in Text Editor and Console (note, you have to draw over main region, not over the header). This is caused by rB6e40b2de7ae81653f.
Another way to reproduce this is by using --debug-memory and joining any areas.

This fixes the issue:

For the records, this is pretty high on my priority list. I'm planning to look into it asap. Unfortunatly that may only be after the weekend though.

Why would we move those settings into the top-bar? It's nice to have all tool-settings in a single place, however some of the mentioned settings are merely 3D View settings. And the ones that are shared across multiple editor types usually vary depending on the editor type. E.g.:

I actually agree on what @Linus Wiklander (wiklander) said, I'd also prefer keeping the Render Size Percentage at 50% to force people into discovering it ;)

Hmm, I'd say screen-verts must never have a negative coordinate, if so there's probably a bug. So the assert seems to be right. Would still have to check details though.

Thanks a lot! I did work on a patch taking the same direction as yours, just didn't get around to finish it. Glad it's fixed now!

Huuuuge thumbs up for the general proposal! I've been very worried about the complexity of the new layer/collection system; this addresses my concerns just fine and is in fact quite similar to what I had in mind.
No more linking, instead you define you're hierarchy once and define a sub-set of it for each layer -- so much yes!

Also, RegionEmbossSide is unused now and should be removed.

This is removing region emboss, but in the commit message you speak about area emboss. So either you removed the wrong emboss or used the wrong term :) What was your intention?

Hey and happy lekker Sunday! ;)

I think this depends a bit on how we want to handle scrolling in the top-bar. If we don't want any scrolling and instead do things like moving tabs into a '...' menu if there are to many to display, the second solution sounds better. If we want to make sections scrollable option one should be the way to go.

Forgot to add, debugged this with @Campbell Barton (campbellbarton). I wouldn't just commit such a change in makesdna without clearance ;)

Managing the workspaces of the workspaces.blend is actually something I hoped to allow through the new Blender settings design, see T54115.

For the records, I agree Ctrl + Q → Enter should still work, I can have a look at it after the code quest.
EDIT: Didn't mean after the code quest, but once I'm back home. That is next week.