Seeking Help with Modal Component Issues and Suggestions

Quinn B. · 2025-07-09 21:42:42.509845+00

Hi There! I'm running in to some issues with a modal component. Wondering if anyone has any suggestions. Please see video below Also.... here is a of the page

Seeking Help with Modal Component Issues and Suggestions | Relume Community

9 comments

· Sorted by Oldest

Matt J.
·
·
Hey Quinn B. 👋 - appreciate the video for context - super helpful! So you have two options in this situation:
1.
You can move the modal component to be at the very top of your HTML stack. Downside is you'll need to make sure that the button is targeting that modal directly - right now its likely targeting because its a "sibling" of the button.
2.
You can use Finsweet Smart Lightbox - which will automatically move this modal component to the top of the HTML stack and/or change the z-index of it dynamically. Upside: No additional changes need to be made to the modal or button interactions. This attribute also has some added features not otherwise possible without. Downside: additional custom code.
Let me know if you have any additional questions!
Quinn B.
·
·
Matt J. You're the man! Thanks for always being on top of it! I'll report back on how I solve this or if I have additional questions.
Quinn B.
·
·
Matt J. So I got the modal to display properly using the Finsweet option. But a new problem has risen On the published site,
1.
Click "Open Modal"... modal opens and displays properly
2.
Close Modal... closes just fine
3.
Click "Open Modal" again, the button disappears?
4.
Come to find out, if you scroll to the bottom of the page, you can see it there?
Any idea what going on?
Matt J.
·
·
Quinn B. woah! That is wild.....never seen anything like that before
Matt J.
·
·
Quinn B. I would look over the smart lightbox attributes again. I think we want the attribute on the modal1_component to be the lightbox attribute and the trigger-open to be on the open modal button. Currently there is no attribute on the open modal button. So I'm thinking the script is likely making that shift for some reason.
Matt J.
·
·
Matt J.
·
·
and for good measure, better add the trigger-close to the close button as well as the overlay div.
Aurelien S.
·
·
Quinn B. since Webflow released the custom components I've been using the native html dialog. If you still have issues I'm happy to share.
Christian F.
·
·
[]

Loading comments

Matt J.
·
·
Hey Quinn B. 👋 - appreciate the video for context - super helpful! So you have two options in this situation:
1.
You can move the modal component to be at the very top of your HTML stack. Downside is you'll need to make sure that the button is targeting that modal directly - right now its likely targeting because its a "sibling" of the button.
2.
You can use Finsweet Smart Lightbox - which will automatically move this modal component to the top of the HTML stack and/or change the z-index of it dynamically. Upside: No additional changes need to be made to the modal or button interactions. This attribute also has some added features not otherwise possible without. Downside: additional custom code.
Let me know if you have any additional questions!
Quinn B.
·
·
Matt J. You're the man! Thanks for always being on top of it! I'll report back on how I solve this or if I have additional questions.
Quinn B.
·
·
Matt J. So I got the modal to display properly using the Finsweet option. But a new problem has risen On the published site,
1.
Click "Open Modal"... modal opens and displays properly
2.
Close Modal... closes just fine
3.
Click "Open Modal" again, the button disappears?
4.
Come to find out, if you scroll to the bottom of the page, you can see it there?
Any idea what going on?
Matt J.
·
·
Quinn B. woah! That is wild.....never seen anything like that before
Matt J.
·
·
Quinn B. I would look over the smart lightbox attributes again. I think we want the attribute on the modal1_component to be the lightbox attribute and the trigger-open to be on the open modal button. Currently there is no attribute on the open modal button. So I'm thinking the script is likely making that shift for some reason.
Matt J.
·
·
Matt J.
·
·
and for good measure, better add the trigger-close to the close button as well as the overlay div.
Aurelien S.
·
·
Quinn B. since Webflow released the custom components I've been using the native html dialog. If you still have issues I'm happy to share.
Christian F.
·
·
[]