This behaviour doesn't happen in an incognito tab;
Though it DOES happen after I uninstall and reinstall Chrome.

I do have errors in my browser that pertain to not have sass mapping files correctly installed.
Perhaps that is a factor?  Not sure.
This may somehow be my fault, but I am confused as to how my code could be interfering w dev tools

GOT IT!

Here's what's happening, and I didn't know, because I already had my console window open, but minimized beyond view-

whilst editing a style in the dev tools, it seems to trigger a search for .map files, of which I don't have the correct setup right now, and I know this;

It makes sense that it's good to search for that, but if one doesn't have the console window fully visible, it won't be apparent that this is happening.

In theory, a person with faulty/missing sass .map files, without having their console fully visible, will be oblivious to, and not understand why, the focus is shifting away from the styles editor for these errors.

I guess this really is a question of design, instead of an explicit bug.

For posterity, this is a potential pain point for users, and it might be reasonable to examine if feedback can be seen in the styles window if focus is shifting away for an error in the console. (maybe flip it red or show a warning to check the console window)

Simlpy not stealing focus when displaying error in drawer will eliminate all the friction.

Looks like this is fixed.