You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 9, 2023. It is now read-only.
You provide an option target. Ок, nice option. But with this option two modal contents are on the page. The one is a mark-up of modal content that is target, you suggest to use attribute style="display: none;" (see your Modal example 2). And the second one is that markup inside the
generated modal.
I have a button in my modal. And so that I end up with two buttons on the page with the same id attribute. And of course jQuery selector by ID doesn't work. What do you suggest how to avoid it? Or do you consider two modal content on the page is normal?
You provide an option
target
. Ок, nice option. But with this option two modal contents are on the page. The one is a mark-up of modal content that istarget
, you suggest to use attributestyle="display: none;"
(see your Modal example 2). And the second one is that markup inside thegenerated modal.
I have a button in my modal. And so that I end up with two buttons on the page with the same
id
attribute. And of course jQuery selector by ID doesn't work. What do you suggest how to avoid it? Or do you consider two modal content on the page is normal?The same question on Stackoverflow: http://stackoverflow.com/questions/28714086/pgwmodal-using-a-trigger-option-duplicates-a-html-markup-of-a-content-of-a-moda
The text was updated successfully, but these errors were encountered: