This section explains how you can configure UI5 Web Components globally, and what configuration settings are available.

There are several configuration settings that affect all UI5 Web Components globally.

The theme setting values above are the technical names of the supported themes:

• The sap_horizon is known as Morning Horizon and it's the latest theme and default theme.
• The sap_horizon_dark is known as Evening Horizon.
• The sap_horizon_hcb is known as High Contrast Black.
• The sap_horizon_hcw is known as High Contrast White.
• The sap_fiori_3 is known as Quartz Light.
• The sap_fiori_3_dark is known as Quartz Dark.
• The sap_fiori_3_hcb is known as Quartz High Contrast Black.
• The sap_fiori_3_hcw is known as Quartz High Contrast White.

The default theme (sap_horizon) is built in all UI5 Web Components. Thus, components are always themed. Configuring another theme will additionally fetch and use that theme. Any theme is fetched just once.

To use additional themes (other than sap_horizon):

• Import the Assets.js module of each component library you're using, for example:

import "@ui5/webcomponents/dist/Assets.js";
import "@ui5/webcomponents-fiori/dist/Assets.js";

For more about assets, see the dedicated Assets section.

• Configure the additional theme either via the configuration script or module imports.

Example:

import { setTheme } from "@ui5/webcomponents-base/dist/config/Theme.js";
setTheme("sap_horizon_hcb");

• To reset the theme to the default one:

import { setTheme, getDefaultTheme } from "@ui5/webcomponents-base/dist/config/Theme.js";
setTheme(getDefaultTheme());

Note: Deprecated themes

The following themes are deprecated and no longer maintained - out of maintenance and left for compatibility only. The themes will be removed in the next major version. We recommend using Horizon (sap_horizon) and Quartz (sap_fiori_3) theme families.

The language configuration setting does not have a default value (the default value is technically null).

This is how the language to use is determined:

• If a language is configured, it will be used.
• If no language is configured (the setting is null), the user's browser language is checked, and if in the supported list, used.
• If the user's browser language is not in the supported list, but is a variation of a supported language, this language will be used (e.g. fr_** -> fr )
• The en language will be used.

The en language is built in all UI5 Web Components that have translatable texts. Thus, components are always translated. Configuring another language will additionally fetch and use that language. Any language is fetched once.

To use additional languages (other than en):

• Import the Assets.js module of each component/icon library you're using (in general, each library that provides languages assets), for example:

import "@ui5/webcomponents/dist/Assets.js";
import "@ui5/webcomponents-fiori/dist/Assets.js";
import "@ui5/webcomponents-icons/dist/Assets.js";

For more about assets, see the dedicated Assets section.

• Configure the additional language either via the configuration script or module imports.

Example:

import { setLanguage } from "@ui5/webcomponents-base/dist/config/Language.js";
setLanguage("fr");

• To reset the langauge to the default one:

import { setLanguage, getDefaultLanguage } from "@ui5/webcomponents-base/dist/config/Language.js";
setLanguage(getDefaultLanguage());

This setting only applies to components that run animations.

Animation modes allow to specify different animation scenarios or levels.

• When full, all animations run unrestricted.
• When basic, more light-weight set of animations would run.
• When minimal, animations of fundamental functionalities are included.
• When none, all animations are completely suspended.

Note: Please, note that each component determines which animations would run for a specific mode.

This setting determines the default calendar type for all date-related components such as ui5-date-picker, ui5-datetime-picker, etc.

You can always override the calendar type for each instance via component-specific properties. See the documentation of each component for details.

The Gregorian calendar type is built in all date-related UI5 Web Components.

Calendar types are opt-in features, see Using Features for details. Setting another calendar type via configuration or component properties requires that the respective calendar type be explicitly imported.

Example:

• Make sure you've bundled the required calendar type:

import "@ui5/webcomponents-localization/dist/features/calendar/Islamic.js"; 

• Configure this calendar:

<script data-ui5-config type="application/json">
{
    "calendarType": "Islamic"
}
</script>

Now all date-related components will use the Islamic calendar type by default.

By default, UI5 Web Components fire all custom events twice - once with the documented name (e.g. change), and once more with a ui5- prefix (e.g. ui5-change). For example, when the ui5-switch is toggled, it fires a change event, but also a ui5-change event.

The noConflict configuration setting allows certain control over this behavior:

• When false (default value), all custom events are fired with and without the ui5- prefix.
• When true, all custom events are fired with the ui5- prefix only. Hence the noConflict semantic in the name of the setting. This is handy, for example, if the name of an event, fired by a component, happens to collide with the name of an event provided by a third-party library.
• When an object is supplied, just the specified events will be fired with the ui5- prefix only. All other events will be fired normally - once with the prefix, and once without it. The format of this object is as follows:

{
    "events": ["selection-change", "header-click"]
}

Note: Please, note that other keys may be added to this object in the future for the purpose of name conflict resolution.

In the above example, only the selection-change and header-click events will be fired with a prefix. You can still use them by listening to ui5-selection-change and ui5-header-click, but the names selection-change and header-click will be free for use by other UI components and libraries without name collision.

This setting allows to override locale-specific settings for date-related controls.

For example, to force the first day of week to Sunday, no matter the locale:

{
	"formatSettings": {
		"firstDayOfWeek": 0
	}
}

Note: legacyDateCalendarCustomizing takes affect only if following features are imported:

@ui5/webcomponents-base/dist/features/LegacyDateFormats.js

As described in the language configuration option section, the en language is built in all components that have translatable texts. All other languages are fetched as additional assets.

Normally, you would never want to change that setting, but if for technical reasons you prefer even the default language to be fetched over the network, although it's built-in, then set fetchDefaultLanguage this to true

Example:

<script data-ui5-config type="application/json">
{
	"fetchDefaultLanguage": true
}
</script>

This configuration option controls whether default font faces are fetched over the network.

Typically, you would not need to modify this setting. However, if for technical reasons you prefer the default font faces to not be fetched over the network, you can set defaultFontLoading to false.

Example:

<script data-ui5-config type="application/json">
{
	"defaultFontLoading": false
}
</script>

This configuration option controls whether components will display default tooltips in specific cases.

Default tooltips are generally recommended to cover accessibility standards and typically you would not need to modify this setting. However, in rare cases you may want to implement custom tooltip visualization and turn off the default tooltips. To do so, set enableDefaultTooltips to false.

Example:

<script data-ui5-config type="application/json">
{
	"enableDefaultTooltips": false
}
</script>

The time zone should be an IANA time zone ID, e.g. "America/New_York". It can be set to the timezone property in the configuration script.

Example:

<script data-ui5-config type="application/json">
{
	"timezone": "Europe/Sofia"
}
</script>

Allows you to set a URL, from which the framework will fetch the theme styles (CSS variables).

Note: This configuration setting is only applicable to custom themes, created with SAP Theme Designer.

Example:

<script data-ui5-config type="application/json">
{
	"themeRoot": "https://my-example-host.com/"
}
</script>

In order to provide configuration settings, include a <script> element in your HTML page with:

• data-ui5-config attribute
• type="application/json" attribute

Provide the desired configuration settings in a JSON object, as shown in the example below.

Example:

<script data-ui5-config type="application/json">
{
	"theme": "sap_horizon_hcb",
	"language": "ja",
	"animationMode": "none",
	"calendarType": "Japanese",
	"formatSettings": {
		"firstDayOfWeek": 0
	},
	"noConflict": {
		"events": ["selection-change", "header-click"]
	},
	"fetchDefaultLanguage": true,
	"timezone": "Europe/Sofia",
	defaultFontLoading
}
</script>

The configuration script is used to set the initial configuration in a declarative manner. However, reading/modifying the configuration reliably can only be done programmatically.

To do so, please import the desired functionality from the respective "@ui5/webcomponents-base/dist/config/" module.

• theme

import { getTheme, setTheme } from "@ui5/webcomponents-base/dist/config/Theme.js";

• language

import { getLanguage, setLanguage } from "@ui5/webcomponents-base/dist/config/Language.js";

• animationMode

import { getAnimationMode, setAnimationMode } from "@ui5/webcomponents-base/dist/config/AnimationMode.js";

• calendarType - can only be set initially in the configuration script.

import { getCalendarType } from "@ui5/webcomponents-base/dist/config/CalendarType.js";

• noConflict

import { getNoConflict, setNoConflict } from "@ui5/webcomponents-base/dist/config/NoConflict.js";

• formatSettings - can only be set initially in the configuration script.

import { getFirstDayOfWeek } from "@ui5/webcomponents-base/dist/config/FormatSettings.js";

• fetchDefaultLanguage

import { getFetchDefaultLanguage, setFetchDefaultLanguage } from "@ui5/webcomponents-base/dist/config/Language.js";

• defaultFontLoading

import { getDefaultFontLoading, setDefaultFontLoading } from "@ui5/webcomponents-base/dist/config/Fonts.js";

• enableDefaultTooltips

import { getEnableDefaultTooltips, setEnableDefaultTooltips } from "@ui5/webcomponents-base/dist/config/Tooltips.js";

• timezone - can only be set initially in the configuration script.

import { getTimezone } from "@ui5/webcomponents-base/dist/config/Timezone.js";

• themeRoot

import { getThemeRoot, setThemeRoot } from "@ui5/webcomponents-base/dist/config/ThemeRoot.js";