As we have it currently, when there's a modal open ("Add block" dialog in the Layout admin UI for example), the only thing that one can do with the background is scroll up/down. I don't know if that was intentional or not, but it was proven helpful quite a few times in the past for me in cases where accomplishing a task in the modal required me to see what is in the back of it. So, please do not disable that.
The other thing is that we lock the admin bar menu and treat it as if it is part of the background. I had numerous cases where I needed to navigate to another page in order to fill in information in the modal. In such cases, I resort in opening another tab, navigating to the site in question and then using the admin bar in the new tab to navigate to the admin section I was looking for. Now, if it were that the admin bar was not locked, I would have simply used the admin menu and would have right-clicked -> open in new tab on the link I needed.
The alternative is to close the dialog, right-click -> open in new tab on the link that you need and then re-open the dialog. This is really annoying though and might be ok if you realized that you need to do it right after the dialog opens. If you have actually filled in something in the dialog already, then :angry: ...pisses me off.
Not sure what the implications would be on mobile mode, but there is nothing I can think of right now. If not on by default, then can we at least have a "Keep active when a modal dialog is open." setting under /admin/config/administration/admin-bar?
Recent comments
well @herb I cannot believe it, but the webform module was there in modules on the disc, but missing in the listed modules, so I delete the module folder, and downloaded it again. Then...
My Webform Worksheets have disappeared
The only thing I can think of is to make sure Webform module is enabled and that the content type that needs to contain the webforms has Webform enabled for it. Edit the content type and make...
My Webform Worksheets have disappeared
@yorkshirepudding, In the end I fixed it by deleting the config/active folder contents, copying the config/staging/ files into config/active, importing the database again and clearing the caches...
Importing the staged config throws an error: another field with the same name already exists