Allow toggling Config Enforce UI window on and off

What I'm wondering is how to approach this from a UI point of view. Do we want a toggle on every form page that can be/is enforced? If so, where do we place it so it doesn't get in the way? Can we insert it into the form itself inline, or should it also float above stuff? I have other questions, but this seems like the first things to ask before we get into implementation details.

I agree, it's a tricky question. I was imagining a X icon in the "floaty window" itself, when it's present. The harder part seems to be how you bring it back- where does the button go? One option could be that it just disappears, but the "floaty window" reappears the next time you reload the page- this could probably go a long way to improving the UX for a developer. Most of the time, when I find this thing in the way, it's temporary- I need to see the rest of the config page I'm on better, but once those settings are back, I don't mind the CED form returning.

Alternately, maybe we can collapse down to a micro-version of the floaty window (the CE logo?), to minimize its overlap with anything else on the page. Again, we're looking for a quick and dirty stopgap here more than anything, until we can invest the time to refactor the floaty window into its own off-canvas dialog (and separate form).

@spiderman Other than the floating part, you're basically just describing the behaviour of a a '#type' => 'details'. 😉 Honestly, coming up with a bunch more UI to toggle the floating form and figure out how to make it work well enough without causing new problems seems like a sunk cost issue if we're going to end up redoing at a certain point. I still stand by my short term proposal in #3188474-2: Improve usability of Config Enforce Devel's UI → to just wrap the thing in a <details> element and plop it inline at the start or end of the parent form - it solves the immediate problems, it delegates the details of the implementation to browsers and the theme (Claro has some great accessibility for these), and while it's better, it's still not 100% convenient so we'll still be motivated to improve on it when we have the time and budget.

For an 1.0.0 release, just an "X" on the CE form that sets 'display: none' (via JS) would suffice. It should probably be added to the base CE form, rather than in Config Enforce Devel overrides.

@ergonlogic That's what a sane person would do, yeah. 🤓 Alas, that's not me. By the time you posted that, I'd already converted the floating form and was cleaning it up. Take a look at ✨ Improve usability of Config Enforce UI Postponed and ✨ Improve usability of Config Enforce Devel's UI Postponed .

This looks like a good intermediate solution.

In the long run (ie. ✨ Improve usability of Config Enforce Devel's UI Postponed ) I think we really need to go with the off-canvas dialog. There's no reason that the same 'save' action should handle both configs (the config being enforced, and config_enforce's registry)

Agreed, that would be good in the long term. Thanks!

Closing this as a duplicate of ✨ Improve usability of Config Enforce Devel's UI Postponed