Keep status bar color when browser popup about cordova-plugin-inappbrowser

[eradin]

I built with ios 6.1 and InAppBrowser Plugin 4.0. The status bar background is correct (matches my app) but the foreground (text) is black where my app text is white. Since the status bar is created by the plugin, perhaps a statusbar color option would be helpful?

My call is:

options = 'clearcache=yes,clearsessioncache=yes,location=no,toolbar=no,hardwareback=no,zoom=no'
ref = cordova.InAppBrowser.open(url, '_blank', options)

[adammeyer]

The iOS status bar isn't being covered by the IAB, but yet the IAB is changing the status bar text color. Is there anyway to turn this off?

[bruno-delfim]

I have the same problem.
When calling inappbrowser with _blank the statusbar becomes black

[NishantDesai1306]

I'm also stuck at this point, my app does not have status bar at the splash screen (which is how I've set it) but as soon as I open any webpage in inAppBrowser the status bar returns.

[cape-dev]

For now a quiet dirty quickfix is to set the statusbar styles on exit of the InAppBrowser:

const iab = this.browser.create(url, 'blank', this.iabOptions);
const exitSubscription = iab.on('exit').subscribe(() => {
      let counter = 1;
      const intervalId = setInterval(() => {
        if (counter < 20) {
          this.statusBar.styleLightContent();
          counter++;
        } else {
          clearInterval(intervalId);
          exitSubscription.unsubscribe();
        }
      }, 100);
    });

I am setting the style multiple times because somehow the app does not recognize any stylings to the statusBar via the plugin's methods for some time (this time differs on different devices). Maybe the Ionic context is not ready yet.

[Damini17]

Any solution to the above issue @zdd?

Thanks in advance!

[Macfa]

+1

[DigitalTAC]

+1

[breautek]

If this was an issue on ios, #656 was merged in that made a lot of changes with the statusbar while the inappbrowser was displayed. This PR should be included in the latest version of the plugin.

It would be appreciated if one can test against the latest version to see if this issue still is valid.