Damn! Why you do this?
You look like a bot, Cmon, at least answer the question.
It can be on the devtalk thread, at least tacle the subject a bit, you are the interface designer.

We don't normally use the bug tracker for feature requests or feedback. Anyway, here goes:

There seems to be some bugs related to switching the tools when you are using multiple editors. Currently it doesn't always update correctly to show the correct tool properties if you switch between tools in the 3d view vs the UV Editor, for example.

As for your suggestion, we could do that, but those things are not per viewport. Also might be problems with fitting in things like the sculpting settings if it was put inside the viewport.

The top bar concept was mainly conceived of before I got on board for 2.8, but the idea was to move global things there that aren't per viewport, such as the mode and other things like the commands adjustments (redo), which were previously inside the 3D View.

It ended up being paired back and things were removed from it, but it does serve as a consistent place to find tool settings.

I'm not really sure how the per-editor top bar would work in different scenarios, but you are of course welcome to make examples of how this would work and look and we can take a look at it.

Thanks for a good answer, now, I can understand a bit what happened, the fact that a thing designed to display global settings is being used to display local properties, is really alkward.
,A per-editor bar doesn't exclude topbar, it moves local settings like tools into it, while topbar can keep the global mode-related settings.
Many users are concerned that it's too disconnected from the editors when working with multiple splits in the screen, the topbar switch like crazy and is seemingly disconnected from the editors that it inherits settings from.