Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>While checking orientation please take note of these points from apple document - </p> <blockquote> <p><strong>Provide Launch Images :</strong></p> <p><em>iPhone-only applications</em> may only have one launch image. It should be in PNG format and measure 320 x 480 pixels. Name your launch image file Default.png.</p> <p><em>iPad-only applications:</em> Create a launch image for each supported orientation in the PNG format. Each launch image must be 1024 x 748 pixels (for landscape) or 768 x 1004 pixels (for portrait).</p> <p><em>Universal applications:</em> Include launch images for both iPhone and iPad.</p> <p><strong>Update Your Info.plist Settings</strong> Specify values for the UISupportedInterfaceOrientations and UIInterfaceOrientation</p> </blockquote> <p>and </p> <blockquote> <p><strong>Not all browsers recognize the cover keyword for background-size</strong>, and as a result, simply ignore it.</p> </blockquote> <p>So we can overcome that limitation by <em>setting the background-size to 100% width or height, depending on the orientation</em>. We can target the current orientation (as well as the iOS device, using device-width). With these two points I think you can use CSS <code>background-size:cover</code> on iOS in portrait-mode </p> <p>Here are some other resources I also came across while looking for a solution: <a href="http://kimili.com/journal/flexible-scalable-background-image" rel="nofollow noreferrer">Flexible scalable background images</a>, <a href="http://beingwicked.com/development/full-scalable-background-images/" rel="nofollow noreferrer">full scalable background images</a>, <a href="http://css-tricks.com/perfect-full-page-background-image/" rel="nofollow noreferrer">perfect scalable background images</a>, and <a href="http://wordpress.org/support/topic/background-image-problems-on-resize-iphoneipad" rel="nofollow noreferrer">this</a> discussion.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload