Keep awesomeplete dialog within visible bounds

[cynicaloptimist]

[BlairStewart]

I think that this can be resolved by removing the overflow-y:auto declaration on the .prompts class.

I understand that this is not a great solution, but I did some local tests and I cannot see any rendering issues on Chrome anyways. (The alternative might require us to move away from awesomeplete or maybe bump to a newer version that allows us to declare a custom ul tag)

I looked and this declaration was added in 2017, do you know if this app still requires this, or is it just an artifact of older ui decisions?

If you don't think that there would be any unintended consequences that maybe I didn't think to check, I can toss in a pr to get this issue off the backlog.

Cheers.

[cynicaloptimist]

That declaration was probably there to handle very large amounts of prompts that were rendering weird on some device. Looks like it was part of @ryanmurray1's UI refresh. In any case, since the prompts section is a bit of a mess right now it's probably fine to delete. I'd take a PR for it.

Thanks!