I’m trying to come to grips with what seems to be an anomaly with the Modal component.
I need to place a modal in a precise location, but if I use a FIXED location, some of the default behavior of the Modal no longer works. For example, if you click outside the modal, it is not closed. Why?
Yes, I know the location is FIXED, but that should not have anything to do with closing the modal.
The same is true if I try some of the other location-specific settings.
Could someone please clarify whether this behavior is intended or a bug?
It would be nice to have precise control over the placement, if possible.
Hi @handshaper
I am working on something with modals and saw the same behaviour. Thouht the problem is on my side but if you have also issues, it‘s probably a bug.
In my case when I position my modal to a defined place on the screen, I can close it by clicking outside of the modal on 3 sides (top, bottom and right). Clicking on the left side doesn‘t do anything.
I send you a separate email with the link, as I do not want to have the project public. By the way, is it correct that I can send you currently no messages via the forum?
Correct, I’m trying to limit the number of places I need to check, so turning of DM’s works. It’s also better for me to answer questions in public, that way everyone benefits
I think you’re seeing issues because your div actually covers the left hand side (see the area highlighted in blue). They’ll be a way to solve this… I just need to have a play and maybe get @ben involved to workout the best solution…
@dan Here is my sample project that shows the issue I was reporting.
There is a fixed navbar with two hamburger triggers; clicking the LEFT one shows a modal that cannot be removed by clicking outside the modal. This modal has a fixed location. The one on the RIGHT behaves as expected. It doesn’t have a fixed location.
Your problem is similar to @WeaverPixel’s - Because of the setting you’ve applied it think the modal div is actually covering the entire screen… I’ll need to dig into this more on Monday with @ben to see if we can build in a workaround for situations like these
