If the purpose is for focus, then change the background color slightly around the module or put a dark border around the module. Plus usually the module being worked on is above the fold and the others are out of sight, unless the module is pretty small.

The dimming happens when the mouse is outside of any module and that shouldn't happen. There are better UI ways to bring something into focus. Dimming is mostly used when a window (part of the screen) is popped up and the rest of the screen is behind so that the user works on the pop up until they are done and it closes, to ensure proper workflow. DNN is using dimming unconventionally

FYI there was some discussion on this at https://dnntracker.atlassian.net/brow... - I don't think any of us particularly like the opacity option, but previous solutions such as adding a bold border caused content to shift, and this was somewhat of a least bad option (unless we remove it and then get complaints because user's aren't sure what is being edited when modules are close together). I'm sure we would welcome good suggestions as this has bounced back and forth a few times without a satisfactory solution

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US

If users were not complaining about not being able to know which module is being edited and you add a UI feature which many users do not like, you have to seriously consider removing it. I am asking if there was ever a need for this based on feedback from users.