From a7706fef5853bf5fbc584fd6089baa515db21880 Mon Sep 17 00:00:00 2001
From: Mosab A <47486787+mosabab@users.noreply.github.com>
Date: Sun, 12 Jan 2020 16:46:24 +0200
Subject: [PATCH] Update readme.md by adding missing info (#239)
* Update readme.md by adding missing info
* Update README.md
* Update README.md
* Update README.md
* Update text as standard
* Update README.md
* Update README.md
---
README.md | 24 ++++++++++++++----------
1 file changed, 14 insertions(+), 10 deletions(-)
diff --git a/README.md b/README.md
index d377a76..dd5a20c 100644
--- a/README.md
+++ b/README.md
@@ -91,17 +91,19 @@ projectRoot
```xml
-
-
-
-
-
+
+
+
+
+
+
-
-
-
-
-
+
+
+
+
+
+
@@ -159,6 +161,8 @@ Apple is moving away from legacy launch images. There is no official support for
The preferred method of providing launch images is to use a launch storyboard. For native app developers, the ideal launch storyboard is an unpopulated version of the app's user interface at launch. For non-native app developers who don't wish to learn Interface Builder, however, this plugin simulates the legacy launch image method as much as is feasible.
+**Note:** Since iOS 11, for iPhone X devices and greater (with notch screen), you should switch to the new storyboard splash screens, taking into account to add `viewport-fit=cover` to the viewport meta tag in your `index.html` file to display the app correctly like so: `` and make some modification to your app style by adding: `padding: env(safe-area-inset-top)` to your `index.css` file to avoid the unsafe areas behind notches in the screen.
+
#### Legacy launch images
If you choose to use legacy launch images, you will use the following syntax in `config.xml`: