New Case Study:See how Anthropic automated 95% of dependency reviews with Socket.Learn More
Socket
Sign inDemoInstall
Socket

@outloud/ionic-safe-area

Package Overview
Dependencies
Maintainers
0
Versions
3
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@outloud/ionic-safe-area

Capacitor Plugin that exposes the safe area insets from the native iOS/Android device to your web project.

  • 7.0.0-alpha.3
  • latest
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
138
Maintainers
0
Weekly downloads
 
Created
Source


Safe Area

@capacitor-community/safe-area

Capacitor Plugin that exposes the safe area insets from the native iOS/Android device to your web project.


Introduction

On web and iOS the safe area insets work out of the box1. That is, on these platforms the env(safe-area-inset-*) CSS variables will have the correct values by default. On Android (in combination with Capacitor), however, those CSS variables will not have the correct values when Edge-to-Edge mode is enabled. So we need to work some magic in order to have access to the correct values. This plugin does that by detecting the safe area insets on Android, and injecting them as CSS variables to the browser. On web and iOS it will just fallback to the given values (which, again, are working out of the box).

There's one small but important quirck though, since we cannot override the native env(safe-area-inset-*) variables, the values are instead written to custom var(--safe-area-inset-*) variables.

[!NOTE] 1 As with all web applications, you still need to enable the use the variables, by telling the browser to use the whole available space on the screen by adding a new viewport meta value:

<meta name="viewport" content="viewport-fit=cover" />

More info on the Mozilla website

Edge-to-Edge

You'll only need access to the safe area insets when you want to display your app edge-to-edge, by drawing your app content behind the system bars. The system bars are the status bar and the navigation bar. See the comparison table below for clarification:

Edge-to-Edge mode:DisabledEnabledEnabled
Safe Area Plugin installed: N/A.* Plugin not installed Plugin installed
Screenshot:
*Plugin not needed when not in Edge-to-Edge mode. Because the safe area insets will always be 0px in this mode. So it wouldn't have any effect.

This plugin, therefore, also provides utilities for styling those system bars and its content. It enables you to set the color of the bars to any color (e.g. black, white or transparent). It also enables you to set the color of the content (i.e. icon color) to either light or dark.

Installation

npm install @capacitor-community/safe-area
npx cap sync

Usage

Enabling the plugin

This plugin can be enabled either by using the API or by using the Configuration. It's also possible to combine those two.

Enable by using the API
import { SafeArea } from '@capacitor-community/safe-area';

SafeArea.enable({
  config: {
    customColorsForSystemBars: true,
    statusBarColor: '#00000000', // transparent
    statusBarContent: 'light',
    navigationBarColor: '#00000000', // transparent
    navigationBarContent: 'light',
  },
});
Enable by using the Configuration

See the Configuration documentation below for examples.

[!IMPORTANT] If you're enabling this plugin by using the configuration only and not by calling any of the API methods, you should still import the plugin like so:

import '@capacitor-community/safe-area';

Using the CSS variables

Having enabled the plugin, it will inject the correct safe area insets as CSS variables to the browser. This enables you to use those variables inside your CSS. You're now able to do this for example:

#header {
  padding-top: var(--safe-area-inset-top);
}

Or maybe you want to do something like this:

#header {
  padding-top: calc(var(--safe-area-inset-top) + 1rem);
}

[!IMPORTANT] It's important to note that the used CSS variables are var(--safe-area-inset-*) and not env(safe-area-inset-*). Unfortunately it's not (yet) possible to override the native env( variables. So therefore custom variables are injected instead.

[!NOTE] On web and iOS both var(--safe-area-inset-*) and env(safe-area-inset-*) variables will be available. It's recommended to only use var(--safe-area-inset-*) for consistency though. The initialize call will make sure those variables are available on all platforms, including web and iOS.

Using the plugin in an SSR environment

This plugin can be used in an SSR environment. But you should manually call initialize like so:

import { initialize } from '@capacitor-community/safe-area';

initialize();

Note that this step is only needed for users using this plugin in an SSR environment.

Background information on calling initialize

Calling initialize will set initial safe area values. It will inject var(--safe-area-inset-*) CSS variables with the values set to max(env(safe-area-inset-*), 0px) as properties to the document root. This makes sure the CSS variables can be used immediately and everywhere. This is especially important for Android when the plugin isn't enabled (yet) and always for web and iOS. Because otherwise - in those cases - var(--safe-area-inset-*) won't have any values.

API

enable(...)

enable(options: { config: Config; }) => Promise<void>
ParamType
options{ config: Config; }

disable(...)

disable(options: { config: Config; }) => Promise<void>
ParamType
options{ config: Config; }

Interfaces

Config
PropTypeDescriptionDefault
customColorsForSystemBarsbooleanFlag indicating that you are responsible for drawing the background color for the system bars. If false it will fallback to the default colors for the system bars.true
statusBarColorstringSpecifies the background color of the status bar. Should be in the format #RRGGBB or #AARRGGBB. Will only have effect if customColorsForSystemBars is set to true.'#000000'
statusBarContent'light' | 'dark'Specifies the color of the content (i.e. icon color) in the status bar.'light'
navigationBarColorstringSpecifies the background color of the navigation bar. Should be in the format #RRGGBB or #AARRGGBB. Will only have effect if customColorsForSystemBars is set to true.'#000000'
navigationBarContent'light' | 'dark'Specifies the color of the content (i.e. icon color) in the navigation bar.'light'
offsetnumberSpecifies the offset to be applied to the safe area insets. This means that if the safe area top inset is 30px, and the offset specified is 10px, the safe area top inset will be exposed as being 40px. Usually you don't need this, but on iOS the safe area insets are mostly offset a little more by itself already. So you might want to compensate for that on Android. It's totally up to you. The offset will be applied if Edge-to-Edge mode is enabled only.0

Configuration

For ease of use and speed, these configuration values are available:

PropTypeDescriptionDefault
enabledbooleanFlag indicating whether of not the plugin should be enabled from startup.false
customColorsForSystemBarsbooleanFlag indicating that you are responsible for drawing the background color for the system bars. If false it will fallback to the default colors for the system bars.true
statusBarColorstringSpecifies the background color of the status bar. Should be in the format #RRGGBB or #AARRGGBB. Will only have effect if customColorsForSystemBars is set to true.'#000000'
statusBarContent'light' | 'dark'Specifies the color of the content (i.e. icon color) in the status bar.'light'
navigationBarColorstringSpecifies the background color of the navigation bar. Should be in the format #RRGGBB or #AARRGGBB. Will only have effect if customColorsForSystemBars is set to true.'#000000'
navigationBarContent'light' | 'dark'Specifies the color of the content (i.e. icon color) in the navigation bar.'light'
offsetnumberSpecifies the offset to be applied to the safe area insets. This means that if the safe area top inset is 30px, and the offset specified is 10px, the safe area top inset will be exposed as being 40px. Usually you don't need this, but on iOS the safe area insets are mostly offset a little more by itself already. So you might want to compensate for that on Android. It's totally up to you. The offset will be applied if Edge-to-Edge mode is enabled only.0

Examples

In capacitor.config.json:

{
  "plugins": {
    "SafeArea": {
      "enabled": true,
      "customColorsForSystemBars": true,
      "statusBarColor": '#000000',
      "statusBarContent": 'light',
      "navigationBarColor": '#000000',
      "navigationBarContent": 'light',
      "offset": 0
    }
  }
}

In capacitor.config.ts:

/// <reference types="@outloud/ionic-safe-area" />

import { CapacitorConfig } from '@capacitor/cli';

const config: CapacitorConfig = {
  plugins: {
    SafeArea: {
      enabled: true,
      customColorsForSystemBars: true,
      statusBarColor: '#000000',
      statusBarContent: 'light',
      navigationBarColor: '#000000',
      navigationBarContent: 'light',
      offset: 0,
    },
  },
};

export default config;

Keywords

FAQs

Package last updated on 14 Feb 2025

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc