Large blank space at the bottom of modals

[rjmackay]

In most cases this is added so that modal content can be scrolled above the modal-actions div, but when there is no modal-actions div the padding is still present.

[brandonrosage]

.modal-body and .modal-actions are intended to work in concert. So if you have a modal window with no actions, just refrain from wrapping the "body" in the .modal-body container -- simply don't use that wrapper.

Aside

The upcoming "free-form surveys" solution reinforces the use of the "mainsheet" pattern, which is particularly useful for interactions like "Add field," where there's a single-click interaction -- not configure-and-confirm.

In practice, "Add field" then looks like this on small-screen:

...and like this on large-screen:

[rjmackay]

.modal-body and .modal-actions are intended to work in concert. So if you have a modal window with no actions, just refrain from wrapping the "body" in the .modal-body container -- simply don't use that wrapper.

Ok. In principle that makes sense. However the dynamic height of modals relies on having a modal-body div. The PL uses the modal-body container, and we do the same in client.

[brandonrosage]

If conditional use of the .modal-body wrapper isn't possible, I'd lobby for supporting the .mainsheet pattern in the client, since it exists primarily to serve as an interstitial window with no window-level actions (like Save or Cancel).

I've ensured the develop branch has the HTML, CSS, and JS necessary to support it.

If you'd like, @rjmackay, I can create an issue dedicated to the task of implementing support in the client. On the other hand, I can see this issue essentially serving that purpose -- that fixing the issue you've raised is accomplished by building support for mainsheet.

[rjmackay]

@middle8media if you could flag where we need to replace modals with mainsheet patterns, I can update in the client. or given @ryanchristo already built the pattern maybe you could just swap the functions on the client