Popup: add a check to not add ui-popover-container if it's already on the page

[frequent]

I'm feeding content to a page via AJAX.

Most content blocks contain a few popups, which once pulled into DOM add the ui-popover-container div. All good.

However, once I remove a content section (including the embedded popups), the popover-containers stay in the DOM. Next time I re-loaded the content, the popover containers get added again, so eventually my DOM is mostly popover-containers :-)

I'm now removing them by hand when leaving the page.

A better solution would be for the popover to check if the corresponding container was already there, and if so, don't add it again.

[gabrielschulhof]

How are you removing them? Are you calling .remove()? popup has code to clean up after itself, including the removal of its container and screen. Is that code running? Put a breakpoint in popup's _destroy() function and see if it gets hit.

[mspisars]

Running into this issue with custom select menu's.
When a custom select closes we do not remove the ui-popup-container ui-selectmenu-hidden (probably for good reason, i.e. don't want to have to recreate the listview and everything inside the container for the custom select next time the user clicks on the select menu.

Probably would be best to register/tie the ui-popup-container ui-selectmenu-hidden to it's select menu.
This is a problem primarily for dynamically generated pages where portions of the page changes without transitioning to a new page.

[frequent]

@gabrielschulhof

Sorry, I missed to answer on this issue. @mspisars is correct, I'm pulling in a lot of dynamic content via Ajax, so for stuff like news messages, I use a shell page and pull in/out blocks of content (including popups). Content blocks are removed using remove(), but - understandably - this will probably not remove any dependent elements outside of the ditched content.

So right now, I feel like uninstalling something from windows and having all sorts of leftover files cluttering the DOM :-D

Just thinking... could elements such as the overlay have a data-dependency-on="some_element_id" to auto-remove once the dependent element is removed (but how to check without wasting resources)? I'm also hoping these things can eventually be made global elements (global overlay, global popup container, global toolbar... just as the loader...).

[gabrielschulhof]

OK. Popups should be removing themselves correctly, but custom select menus may not be doing likewise because they do not implement _destroy, so the popups they create never get the message.

[frequent]

@gabrielschulhof - I haven't updated my JQM version which I'm using popups in, so this was a very early popup widget. Might be this is working now. Let me try to update JQM and see what happens. Then you could close I think.

[mspisars]

I'm on 1.2.0 (not a latest master build but the released version). It is definitely an issue with custom selects, I do not use popup's outside of custom selects.

[mspisars]

thank you!