Skip to main content

Search and Top Navigation

#9578 closed bug (invalid)

Opened September 30, 2013 12:40AM UTC

Closed December 05, 2013 08:57AM UTC

Dialog: Overlay background incorrect in android browser

Reported by: groupboard2 Owned by: groupboard2
Priority: minor Milestone: none
Component: ui.dialog Version: 1.10.3
Keywords: Cc:
Blocked by: Blocking:

Go to in android browser and click 'open modal dialog'. Zoom in and out of page with pinch zoom. You'll see that the grey modal background is screwed up until you try scrolling. Works perfectly on chrome browser.

Attachments (0)
Change History (6)

Changed October 01, 2013 08:10AM UTC by tj.vantoll comment:1

owner: → groupboard2
status: newpending

Hi groupboard2,

Thanks for taking the time to contribute to the jQuery UI project. Are you seeing the behavior here

Also what version of Android are you using?


Changed October 01, 2013 07:12PM UTC by groupboard2 comment:2

status: pendingnew

Yes, the bug occurs there (although not quite as easy to recreate). If you rotate to landscape you'll see a big white rectangle on the left hand side. Using Android 4.1.2 on a samsung galaxy note.

Changed October 02, 2013 07:31AM UTC by tj.vantoll comment:3

component: ui.coreui.dialog
status: newopen
summary: modal dialog background incorrect in android browserDialog: Overlay background incorrect in android browser

Changed November 20, 2013 04:27PM UTC by arschmitz comment:4

This is not a bug this is how android works because you have not set a viewport meta tag the android browser zooms to what it thinks is a good level when the page loads and then it zooms to a new "good" level when you change orientation. But zooming a fixed position element actually scale elements in android browser ( creating the whitespace you see ). if you set a viewport meta tag like this to enforce the initial scale

 <meta name="viewport" content="width=device-width, initial-scale=1"> 
you will not see this problem any more ( unless you zoom ) While this is less then ideal its just how android decided to implement fixed positioning. using that meta tag no longer exhibits this issue.

Changed November 20, 2013 04:36PM UTC by jzaefferer comment:5

status: openpending

groupboard2, can you confirm that using the meta tag would solve the problem for you?

Changed December 05, 2013 08:57AM UTC by trac-o-bot comment:6

resolution: → invalid
status: pendingclosed

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!