popup with long content initial positioning #5605

stanleystanev opened this Issue Feb 6, 2013 · 4 comments


None yet

4 participants


When a popup has a long content and its height does not fit the viewport then the popup is visualized with its header being not visible.

It makes sense that in this particular case, the positioning of the popup is being done in such a way, so the initial visualization places the popup with its header at the top of the viewport.

Also, the popup should not be re-positioned when user swipes up and down to allow him to see the entire content of the popup.

I believe these should not be difficult to do since popup is already working pretty nice. Just need some additional conditions when the height of the popup does not fit the viewport.

We really need this enhancement.




Please provide a test page that illustrates the issue. See the contributing guidelines for instructions and JS Bin template. Thanks!


Sure, I created a test page at


Tested with iPhone5 Chrome and Safari.

Please let me know if the test page is clear enough to understand the issues.

I added the steps to reproduce in the test page content, but here they are again:

  1. Scroll down and find the "Test Long Content Popup" button.
  2. Click on it and notice the popup with long content is positioned in such a way that its header is way above the viewport.
  3. It is important to us that the header always stays visible during the initial visualization no matter if the popup fits the viewport or not.
  4. Also, while the popup is visualized, try some swipes up and down, there are times when the popup positions itself hence it is impossible to review its entire content. This does not happen with all swipes I tried, but play with it and you will get there.
  5. I believe that if the popup's content does not fit the viewport, it should not position itself at all to allow users to see the entire popup's content.


ldeluca commented Nov 5, 2014

@stanleystanev sorry it's taken so long for someone to look into your issue. It looks like it's been over a year and a half. I'd be happy to take a look but before I do can you please confirm whether or not this is still an issue using the latest jQM?


Im going to close this as stale will reopen if this is still a problem.

@arschmitz arschmitz closed this Nov 5, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment