Socket
Socket
Sign inDemoInstall

@ui5/webcomponents-base

Package Overview
Dependencies
Maintainers
5
Versions
482
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@ui5/webcomponents-base - npm Package Compare versions

Comparing version 1.22.0-rc.3 to 1.22.0

16

dist/delegate/ItemNavigation.d.ts

@@ -6,3 +6,3 @@ import NavigationMode from "../types/NavigationMode.js";

id: string;
_tabIndex: string;
forcedTabIndex: string;
}

@@ -31,4 +31,4 @@ type ItemNavigationOptions = {

* Each item passed to ItemNavigation via "getItemsCallback" must be:
* - A) either a UI5Element with a "_tabIndex" property
* - B) or an Object with "id" and "_tabIndex" properties which represents a part of the root component's shadow DOM.
* - A) either a UI5Element with a "forcedTabIndex" property
* - B) or an Object with "id" and "forcedTabIndex" properties which represents a part of the root component's shadow DOM.
* The "id" must be a valid ID within the shadow root of the component ItemNavigation operates on.

@@ -39,7 +39,7 @@ * This object must not be a DOM object because, as said, ItemNavigation will not set "tabindex" on it. It must be a representation of a DOM object only

*
* Whenever the user navigates with the keyboard, ItemNavigation will modify the "_tabIndex" properties of the items.
* It is the items' responsibilities to re-render themselves and apply the correct value of "tabindex" (i.e. to map the "_tabIndex" ItemNavigation set to them to the "tabindex" property).
* If the items of the ItemNavigation are UI5Elements themselves, this can happen naturally since they will be invalidated by their "_tabIndex" property.
* If the items are Objects with "id" and "_tabIndex" however, it is the developer's responsibility to apply these and the easiest way is to have the root component invalidated by ItemNavigation.
* To do so, set the "affectedPropertiesNames" constructor property to point to one or more of the root component's properties that need refreshing when "_tabIndex" is changed deeply.
* Whenever the user navigates with the keyboard, ItemNavigation will modify the "forcedTabIndex" properties of the items.
* It is the items' responsibilities to re-render themselves and apply the correct value of "tabindex" (i.e. to map the "forcedTabIndex" ItemNavigation set to them to the "tabindex" property).
* If the items of the ItemNavigation are UI5Elements themselves, this can happen naturally since they will be invalidated by their "forcedTabIndex" property.
* If the items are Objects with "id" and "forcedTabIndex" however, it is the developer's responsibility to apply these and the easiest way is to have the root component invalidated by ItemNavigation.
* To do so, set the "affectedPropertiesNames" constructor property to point to one or more of the root component's properties that need refreshing when "forcedTabIndex" is changed deeply.
*

@@ -46,0 +46,0 @@ * 2) Call the "setCurrentItem" method of ItemNavigation whenever you want to change the current item.

@@ -19,4 +19,4 @@ import { isDown, isUp, isLeft, isRight, isHome, isEnd, isPageDown, isPageUp, } from "../Keys.js";

* Each item passed to ItemNavigation via "getItemsCallback" must be:
* - A) either a UI5Element with a "_tabIndex" property
* - B) or an Object with "id" and "_tabIndex" properties which represents a part of the root component's shadow DOM.
* - A) either a UI5Element with a "forcedTabIndex" property
* - B) or an Object with "id" and "forcedTabIndex" properties which represents a part of the root component's shadow DOM.
* The "id" must be a valid ID within the shadow root of the component ItemNavigation operates on.

@@ -27,7 +27,7 @@ * This object must not be a DOM object because, as said, ItemNavigation will not set "tabindex" on it. It must be a representation of a DOM object only

*
* Whenever the user navigates with the keyboard, ItemNavigation will modify the "_tabIndex" properties of the items.
* It is the items' responsibilities to re-render themselves and apply the correct value of "tabindex" (i.e. to map the "_tabIndex" ItemNavigation set to them to the "tabindex" property).
* If the items of the ItemNavigation are UI5Elements themselves, this can happen naturally since they will be invalidated by their "_tabIndex" property.
* If the items are Objects with "id" and "_tabIndex" however, it is the developer's responsibility to apply these and the easiest way is to have the root component invalidated by ItemNavigation.
* To do so, set the "affectedPropertiesNames" constructor property to point to one or more of the root component's properties that need refreshing when "_tabIndex" is changed deeply.
* Whenever the user navigates with the keyboard, ItemNavigation will modify the "forcedTabIndex" properties of the items.
* It is the items' responsibilities to re-render themselves and apply the correct value of "tabindex" (i.e. to map the "forcedTabIndex" ItemNavigation set to them to the "tabindex" property).
* If the items of the ItemNavigation are UI5Elements themselves, this can happen naturally since they will be invalidated by their "forcedTabIndex" property.
* If the items are Objects with "id" and "forcedTabIndex" however, it is the developer's responsibility to apply these and the easiest way is to have the root component invalidated by ItemNavigation.
* To do so, set the "affectedPropertiesNames" constructor property to point to one or more of the root component's properties that need refreshing when "forcedTabIndex" is changed deeply.
*

@@ -102,3 +102,3 @@ * 2) Call the "setCurrentItem" method of ItemNavigation whenever you want to change the current item.

this._getItems().forEach((item, idx) => {
item._tabIndex = (idx === this._currentIndex) ? "0" : "-1";
item.forcedTabIndex = (idx === this._currentIndex) ? "0" : "-1";
});

@@ -271,3 +271,3 @@ }

for (let i = 0; i < items.length; i++) {
items[i]._tabIndex = i === this._currentIndex ? "0" : "-1";
items[i].forcedTabIndex = i === this._currentIndex ? "0" : "-1";
}

@@ -274,0 +274,0 @@ this._affectedPropertiesNames.forEach(propName => {

const VersionInfo = {
version: "1.22.0-rc.2",
version: "1.22.0-rc.3",
major: 1,
minor: 22,
patch: 0,
suffix: "-rc.2",
suffix: "-rc.3",
isNext: false,
buildTime: 1706804744,
buildTime: 1707121089,
};
export default VersionInfo;
//# sourceMappingURL=VersionInfo.js.map
{
"name": "@ui5/webcomponents-base",
"version": "1.22.0-rc.3",
"version": "1.22.0",
"description": "UI5 Web Components: webcomponents.base",

@@ -48,3 +48,3 @@ "author": "SAP SE (https://www.sap.com)",

"@openui5/sap.ui.core": "1.120.3",
"@ui5/webcomponents-tools": "1.22.0-rc.3",
"@ui5/webcomponents-tools": "1.22.0",
"chromedriver": "120.0.0",

@@ -59,3 +59,3 @@ "clean-css": "^5.2.2",

},
"gitHead": "7ff123775e38dc646e3a1c70311e33b0c6d7105a"
"gitHead": "34db17e2bd84915eca435fd68d9ccebddafedcae"
}

Sorry, the diff of this file is too big to display

Sorry, the diff of this file is not supported yet

Sorry, the diff of this file is too big to display

Sorry, the diff of this file is too big to display

Sorry, the diff of this file is not supported yet

Sorry, the diff of this file is not supported yet

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