Return-Path: X-Original-To: apmail-cordova-dev-archive@www.apache.org Delivered-To: apmail-cordova-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A9DDC189F6 for ; Sun, 6 Mar 2016 20:01:16 +0000 (UTC) Received: (qmail 39599 invoked by uid 500); 6 Mar 2016 20:01:16 -0000 Delivered-To: apmail-cordova-dev-archive@cordova.apache.org Received: (qmail 39560 invoked by uid 500); 6 Mar 2016 20:01:16 -0000 Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cordova.apache.org Delivered-To: mailing list dev@cordova.apache.org Received: (qmail 39548 invoked by uid 99); 6 Mar 2016 20:01:15 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 06 Mar 2016 20:01:15 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 6C601C17BA for ; Sun, 6 Mar 2016 20:01:15 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.179 X-Spam-Level: * X-Spam-Status: No, score=1.179 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id Q152Oshx5YFr for ; Sun, 6 Mar 2016 20:01:14 +0000 (UTC) Received: from mail-qk0-f182.google.com (mail-qk0-f182.google.com [209.85.220.182]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id CACB65F3F2 for ; Sun, 6 Mar 2016 20:01:13 +0000 (UTC) Received: by mail-qk0-f182.google.com with SMTP id s5so40000468qkd.0 for ; Sun, 06 Mar 2016 12:01:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to; bh=+xDnfdHQj2Tq2CTPJAG3hp9JNYKXz5kSVGRLvoIaEsA=; b=M/V0yT3TDSXjHeAAW2CoIroMSrNna43u1WPboqUuU1uE8i1mtoAbHM4/uh7oSVe7Tv f0398/7K15V3Cwvj6JmNtQURXBNIqX8fn4EWZ1MVc8+iyAtBAB2wOP0Dj5h/L8qeEaUc k2hvCp/jGP+c7lO25oYvUWNiF5yF2OwUBvuBgIEGkd0j0o4uCd+Da64/JdfzQtO9ABb7 jEguPuNg9AXhFUmnoJVxCc27JD6LXUHC/WvppzIukgWG94b6aZXc/3XC/YvpS1loHe0j TIjuVWNAQ7JfnRlNtqRzeVmZWEZwptQSxd1/UBREHr3MVY8T1YjDP7RuRc1xH2rXEDNE rKKw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=+xDnfdHQj2Tq2CTPJAG3hp9JNYKXz5kSVGRLvoIaEsA=; b=AtA5pgtR3YEiCCRHFYVW/wQUsPCyL70YFtScKjrbl4hoLfqN+X/hJBycQOejgxacyg Jac4yIkrUbHNq+9Q/HmfW03eeK8MwXn6/8Tgj7fQv3+R/7LiDuivi6Tw4nI6CbFFxsjA Cj/oWW+V2pDIg4ttCJvYxTELs4v+H4crkoWLoLpiPQCThjv+g+qZmFlR5LpALHfDQK7q KGTwuATw3Wj2+eoGzdHwoI1Rk/wtDMQaJtMvXpEXfLGh4ynvxsjlirbjpe4chQILUjQ2 VA/Q9HUmSlil2X0IYXlyoKCxThclqpKxDIPIcM8bKsjuH0H9G7vHZcDwoiGFNh869QlL 03Ew== X-Gm-Message-State: AD7BkJLVpln711H1+nZP+m9s0XsoMdMmfYiKaOZH/k8E9PS7G9Tt4Xf6gFUnVPfgz+vV+7EP4QhkrQ/TBC3KDg== MIME-Version: 1.0 X-Received: by 10.55.71.135 with SMTP id u129mr24621144qka.26.1457294466689; Sun, 06 Mar 2016 12:01:06 -0800 (PST) Received: by 10.140.105.203 with HTTP; Sun, 6 Mar 2016 12:01:06 -0800 (PST) Date: Sun, 6 Mar 2016 21:01:06 +0100 Message-ID: Subject: [iOS][statusbar plugin] How is StatusBarOverlaysWebView supposed to work? From: julio cesar sanchez To: "dev@cordova.apache.org" Content-Type: multipart/alternative; boundary=001a114a7d200530bb052d66cf43 --001a114a7d200530bb052d66cf43 Content-Type: text/plain; charset=UTF-8 Yesterday I closed an issue because I think the plugin is working as expected, but the user reopened it saying that I'm wrong, so I want to know if it really works as expected or if only I expect it to work the way it works. The issue is this one: https://issues.apache.org/jira/browse/CB-10796 He is using the default value: That means the webview has the full screen size and the statusbar overlays it. I think we can all agree on that. The problem appears when the in-call or hotspot status bar appears as it has 40 point height on iPhones. The user thinks that the webview should be pushed 20 points down (not 40) because that's how it works when the plugin isn't installed or he uses 1.0.1 version of the plugin. I think it shouldn't be pushed as StatusBarOverlaysWebView is true, so the webview should be full screen, it doesn't matter if the statusbar is 20 or 40 points. So, what should happen? 1. The webview is pushed 20 points down as the user wants 2. The webview ins't pushed down and remains full screen as I think it should work. 3. The webview is pushed 40 points down as the statusbar is 40 points (I think most native apps do this) If using StatusBarOverlaysWebView false the webview is pushed 20 points down so the app is not hidden under the statusbar, or 40 points if the in-call or hotspot statusbar is present --001a114a7d200530bb052d66cf43--