This topic contains 3 replies, has 2 voices, and was last updated by  Sid 9 years, 1 month ago.

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
  • Popover conflict #77763

    Sid
    Participant

    I have two side-by-side popovers (shown in jsEditor here). I’ve based this implementation on this demo

    I am having two separate issues:

    1. The arrow offset of the popovers seems to be additive if you add more than one popover.
      • If I just make the first popover (i.e. comment out the $(“#prop-second-popover”).popover(…) call) everything works, and the arrow offset points at the correct place (i.e. the middle of the first tile)
      • Uncommenting the $(“#prop-second-popover”).popover(…) call affects the offset of the arrow of my first popover. This results in the offset arrow for the first tile being in the wrong position.
    2. I have added a loader div to this page. The loader shows when I close a popover (either for the first-popover or the second-popover). The problem exists that when I close the loader (hitting the escape key). Upon closing the loader, the close event for the first-popover is triggered (evidence is in the console). The close event for the first-popover is also triggered when I close the second-popover.
      • I would like to have an ajax request occur upon closing the popovers, but I cannot allow this cross-talk to occur between close events.

    Please advise on both of these issues.

    Popover conflict #77789

    Hristo
    Participant

    Hi sidkdbl07,

    Thanks about this feedback.
    We will make research on both of these issues.

    Best Regards,
    Hristo Hristov

    jQWidgets team
    http://www.jqwidgets.com

    Popover conflict #77835

    Hristo
    Participant

    Hi sidkdbl07,

    Thanks again for this feedback.
    This will be fixed in next version.

    Best Regards,
    Hristo Hristov

    jQWidgets team
    http://www.jqwidgets.com

    Popover conflict #78013

    Sid
    Participant

    Until we wait for the next version, I’ve created a work-around in the jsEditor linked above.

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.