@ui5/webcomponents 1.0.0-rc.8 → 1.0.2

package/dist/types/TabContainerTabsPlacement.js

@@ -2,19 +2,19 @@ import DataType from "@ui5/webcomponents-base/dist/types/DataType.js";
 
 /**
  * @lends sap.ui.webcomponents.main.types.TabContainerTabsPlacement.prototype
- * @public
+ * @private
  */
 const TabContainerTabsPlacements = {
 	/**
 	 * The tab strip is displayed above the tab content (Default)
-	 * @public
+	 * @private
 	 * @type {Top}
 	 */
 	Top: "Top",
 
 	/**
 	 * The tab strip is displayed below the tab content
-	 * @public
+	 * @private
 	 * @type {Bottom}
 	 */
 	Bottom: "Bottom",
@@ -26,7 +26,7 @@ const TabContainerTabsPlacements = {
  * @constructor
  * @author SAP SE
  * @alias sap.ui.webcomponents.main.types.TabContainerTabsPlacement
- * @public
+ * @private
  * @enum {string}
  */
 class TabContainerTabsPlacement extends DataType {
@@ -35,6 +35,6 @@ class TabContainerTabsPlacement extends DataType {
 	}
 }
 
-TabContainerTabsPlacement.generataTypeAcessors(TabContainerTabsPlacements);
+TabContainerTabsPlacement.generateTypeAccessors(TabContainerTabsPlacements);
 
 export default TabContainerTabsPlacement;

package/dist/types/TabLayout.js

@@ -35,6 +35,6 @@ class TabLayout extends DataType {
 	}
 }
 
-TabLayout.generataTypeAcessors(TabLayouts);
+TabLayout.generateTypeAccessors(TabLayouts);
 
 export default TabLayout;

package/dist/types/TableGrowingMode.js

@@ -0,0 +1,15 @@
+import GrowingMode from "./GrowingMode.js";
+
+/**
+ * @class
+ * Defines the growing mode, used in the <code>ui5-table</code>.
+ * @constructor
+ * @author SAP SE
+ * @alias sap.ui.webcomponents.main.types.TableGrowingMode
+ * @public
+ * @enum {string}
+ */
+class TableGrowingMode extends GrowingMode {
+}
+
+export default TableGrowingMode;

package/dist/types/TableMode.js

@@ -0,0 +1,47 @@
+import DataType from "@ui5/webcomponents-base/dist/types/DataType.js";
+
+/**
+ * @lends sap.ui.webcomponents.main.types.TableMode.prototype
+ * @public
+ */
+const TableModes = {
+	/**
+	 * Default mode (no selection).
+	 * @public
+	 * @type {None}
+	 */
+	None: "None",
+
+	/**
+	 * Single selection mode (only one table row can be selected).
+	 * @public
+	 * @type {SingleSelect}
+	 */
+	SingleSelect: "SingleSelect",
+
+	/**
+	 * Multi selection mode (more than one table row can be selected).
+	 * @public
+	 * @type {MultiSelect}
+	 */
+	MultiSelect: "MultiSelect",
+};
+
+/**
+ * @class
+ * Defines the type of <code>ui5-table</code>.
+ * @constructor
+ * @author SAP SE
+ * @alias sap.ui.webcomponents.main.types.TableMode
+ * @public
+ * @enum {string}
+ */
+class TableMode extends DataType {
+	static isValid(value) {
+		return !!TableModes[value];
+	}
+}
+
+TableMode.generateTypeAccessors(TableModes);
+
+export default TableMode;

package/dist/types/TableRowType.js

@@ -0,0 +1,40 @@
+import DataType from "@ui5/webcomponents-base/dist/types/DataType.js";
+
+/**
+ * @lends sap.ui.webcomponents.main.types.TableRowType.prototype
+ * @public
+ */
+const TableRowTypes = {
+	/**
+	 * Indicates that the table row does not have any active feedback when item is pressed.
+	 * @public
+	 * @type {Inactive}
+	 */
+	Inactive: "Inactive",
+
+	/**
+	 * Indicates that the table row is clickable via active feedback when item is pressed.
+	 * @public
+	 * @type {Active}
+	 */
+	Active: "Active",
+};
+
+/**
+ * @class
+ * Different types of TableRow.
+ * @constructor
+ * @author SAP SE
+ * @alias sap.ui.webcomponents.main.types.TableRowType
+ * @public
+ * @enum {string}
+ */
+class TableRowType extends DataType {
+	static isValid(value) {
+		return !!TableRowTypes[value];
+	}
+}
+
+TableRowType.generateTypeAccessors(TableRowTypes);
+
+export default TableRowType;

package/dist/types/TitleLevel.js

@@ -63,6 +63,6 @@ class TitleLevel extends DataType {
 	}
 }
 
-TitleLevel.generataTypeAcessors(TitleLevels);
+TitleLevel.generateTypeAccessors(TitleLevels);
 
 export default TitleLevel;

package/dist/types/ToastPlacement.js

@@ -1,6 +1,5 @@
 import DataType from "@ui5/webcomponents-base/dist/types/DataType.js";
 
-
 /**
  * @lends sap.ui.webcomponents.main.types.ToastPlacement.prototype
  * @public
@@ -87,6 +86,6 @@ class ToastPlacement extends DataType {
 	}
 }
 
-ToastPlacement.generataTypeAcessors(ToastPlacements);
+ToastPlacement.generateTypeAccessors(ToastPlacements);
 
 export default ToastPlacement;

package/dist/types/WrappingType.js

@@ -0,0 +1,41 @@
+import DataType from "@ui5/webcomponents-base/dist/types/DataType.js";
+
+/**
+ * Different types of wrapping.
+ * @lends sap.ui.webcomponents.main.types.WrappingType.prototype
+ * @public
+ */
+const WrappingTypes = {
+	/**
+	 * The text will be truncated with an ellipsis.
+	 * @public
+	 * @type {None}
+	 */
+	None: "None",
+
+	/**
+	 * The text will wrap. The words will not be broken based on hyphenation.
+	 * @public
+	 * @type {Normal}
+	 */
+	Normal: "Normal",
+};
+
+/**
+ * @class
+ * Defines how the text of a component will be displayed when there is not enough space.
+ * @constructor
+ * @author SAP SE
+ * @alias sap.ui.webcomponents.main.types.WrappingType
+ * @public
+ * @enum {string}
+ */
+class WrappingType extends DataType {
+	static isValid(value) {
+		return !!WrappingTypes[value];
+	}
+}
+
+WrappingType.generateTypeAccessors(WrappingTypes);
+
+export default WrappingType;

package/dist/webcomponentsjs/CHANGELOG.md

@@ -0,0 +1,61 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic
+Versioning](https://semver.org/spec/v2.0.0.html).
+
+<!-- ## [Unreleased] -->
+
+## [2.6.0] - 2021-08-02
+
+- Add TS externs. ([#457](https://github.com/webcomponents/polyfills/pull/457))
+
+## [2.5.0] - 2020-10-21
+
+- Polyfill `Element#matches`.
+  ([#400](https://github.com/webcomponents/polyfills/pull/400))
+- Remove function declarations from platform polyfills to sastisfy internal lint
+  after import transforms.
+  ([#396](https://github.com/webcomponents/polyfills/pull/396))
+- Polyfill `Element#getAttributeNames`.
+  ([#393](https://github.com/webcomponents/polyfills/pull/393))
+- Add polyfills for ChildNode APIs.
+  ([#390](https://github.com/webcomponents/polyfills/pull/390))
+- Add polyfills for select ParentNode APIs.
+  ([#389](https://github.com/webcomponents/polyfills/pull/389))
+- Add `classList` support to `SVGElement`.
+  ([#391](https://github.com/webcomponents/polyfills/pull/391))
+- Add new entrypoints to webcomponentsjs for the 'platform' polyfills.
+  ([#385](https://github.com/webcomponents/polyfills/pull/385))
+
+## [2.4.4] - 2020-07-20
+
+- Fixed bug where Object.assign polyfill would copy non-enumerable properties.
+- Convert platform (`Array.from`, `CustomEvent`, `Promise` etc.) polyfills to
+  TypeScript ([#292](https://github.com/webcomponents/polyfills/pull/292))
+- Improve types for JSCompiler compatibility
+  ([#307](https://github.com/webcomponents/polyfills/pull/307))
+- README improvements
+  ([#128](https://github.com/webcomponents/polyfills/pull/128),
+  [#212](https://github.com/webcomponents/polyfills/pull/212),
+  [#214](https://github.com/webcomponents/polyfills/pull/214))
+
+## [2.4.3] - 2020-03-16
+
+- Maintenance release (no user-facing changes)
+
+## [2.4.2] - 2020-02-26
+
+- Remove unnecessary externs
+  ([#272](https://github.com/webcomponents/polyfills/pull/272))
+
+## [2.4.1] - 2020-01-09
+
+- Maintenance release (no user-facing changes)
+
+## [2.4.0] - 2019-11-12
+
+- Add on-demand patching mode
+  ([#189](https://github.com/webcomponents/polyfills/pull/189))

package/dist/webcomponentsjs/README.md

@@ -1,29 +1,31 @@
 [![Build Status](https://travis-ci.org/webcomponents/webcomponentsjs.svg?branch=master)](https://travis-ci.org/webcomponents/webcomponentsjs)
 
-webcomponents.js (v1 spec polyfills)
-================
+# webcomponents.js (v1 spec polyfills)
 
 > **Note**. For polyfills that work with the older Custom Elements and Shadow DOM v0 specs,
-see the [v0 branch](https://github.com/webcomponents/webcomponentsjs/tree/v0).
+> see the [v0 branch](https://github.com/webcomponents/webcomponentsjs/tree/v0).
 
 > **Note**. For polyfills that include HTML Imports,
-see the [v1 branch](https://github.com/webcomponents/webcomponentsjs/tree/v1).
+> see the [v1 branch](https://github.com/webcomponents/webcomponentsjs/tree/v1).
 
 A suite of polyfills supporting the [Web Components](http://webcomponents.org) specs:
 
-- **Custom Elements v1**: allows authors to define their own custom tags ([spec](https://w3c.github.io/webcomponents/spec/custom/), [tutorial](https://developers.google.com/web/fundamentals/getting-started/primers/customelements), [polyfill](https://github.com/webcomponents/custom-elements)).
+- **Custom Elements v1**: allows authors to define their own custom tags ([spec](https://w3c.github.io/webcomponents/spec/custom/), [tutorial](https://developers.google.com/web/fundamentals/getting-started/primers/customelements), [polyfill](https://github.com/webcomponents/polyfills/tree/master/packages/custom-elements)).
 - **Shadow DOM v1**: provides encapsulation by hiding DOM subtrees under shadow roots ([spec](https://w3c.github.io/webcomponents/spec/shadow/), [tutorial](https://developers.google.com/web/fundamentals/getting-started/primers/shadowdom),
-[shadydom polyfill](https://github.com/webcomponents/shadydom), [shadycss polyfill](https://github.com/webcomponents/shadycss)).
+  [shadydom polyfill](https://github.com/webcomponents/polyfills/tree/master/packages/shadydom), [shadycss polyfill](https://github.com/webcomponents/polyfills/tree/master/packages/shadycss)).
 
 For browsers that need it, there are also some minor polyfills included:
-- [`HTMLTemplateElement`](https://github.com/webcomponents/template)
+
+- [`HTMLTemplateElement`](https://github.com/webcomponents/polyfills/tree/master/packages/template)
 - [`Promise`](https://github.com/taylorhakes/promise-polyfill)
 - `Event`, `CustomEvent`, `MouseEvent` constructors and `Object.assign`, `Array.from`
-(see [webcomponents-platform](https://github.com/webcomponents/webcomponents-platform))
-- [`URL constructor`](https://github.com/webcomponents/URL)
+  (see [webcomponents-platform](https://github.com/webcomponents/webcomponents-platform))
+- [`URL constructor`](https://github.com/webcomponents/polyfills/tree/master/packages/url)
 
 ## How to use
+
 ### Install polyfills
+
 ```bash
 npm install @webcomponents/webcomponentsjs
 ```
@@ -76,6 +78,7 @@ For example:
 ```
 
 #### Synchronous
+
 When loaded synchronously, `webcomponents-loader.js` behaves similarly to `webcomponents-bundle.js`.
 
 The appropriate bundle will be loaded with `document.write()` to ensure that WebComponent polyfills are available for subsequent scripts and modules.
@@ -94,8 +97,9 @@ Here's an example:
 ```
 
 #### Asynchronous
+
 When loaded asychronously with the `defer` attribute, polyfill bundles will be loaded asynchronously,
-which means that scripts and modules that depend on webcomponents APIs *must* be loaded
+which means that scripts and modules that depend on webcomponents APIs _must_ be loaded
 using `WebComponents.waitFor` function.
 
 The `WebComponents.waitFor` function takes a callback function as an argument, and will evaluate that callback after the polyfill bundle has been loaded.
@@ -107,7 +111,10 @@ Here's an example:
 
 ```html
 <!-- Load polyfills; note that "loader" will load these async -->
-<script src="node_modules/@webcomponents/webcomponentsjs/webcomponents-loader.js" defer></script>
+<script
+  src="node_modules/@webcomponents/webcomponentsjs/webcomponents-loader.js"
+  defer
+></script>
 
 <!-- Load a custom element definitions in `waitFor` and return a promise -->
 <script type="module">
@@ -133,7 +140,10 @@ Here's a more complicated example:
 
 ```html
 <!-- Load polyfills; note that "loader" will load these async -->
-<script src="node_modules/@webcomponents/webcomponentsjs/webcomponents-loader.js" defer></script>
+<script
+  src="node_modules/@webcomponents/webcomponentsjs/webcomponents-loader.js"
+  defer
+></script>
 
 <script type="module">
   WebComponents.waitFor(async () => {
@@ -141,11 +151,10 @@ Here's a more complicated example:
       await import('node_modules/fetch-polyfill/fetch.js');
     }
     return import('my-element.js');
-  })
+  });
 </script>
 
-<script type="module">
-</script>
+<script type="module"></script>
 ```
 
 ### WebComponentsReady event
@@ -153,9 +162,10 @@ Here's a more complicated example:
 The `WebComponentsReady` event is fired when polyfills and user scripts have loaded and custom elements have been upgraded. This event is generally not needed; however, it may be useful in some cases like testing. If imperative code should wait until a specific custom element definition has loaded, it can use the platform `customElements.whenDefined` API.
 
 ### `custom-elements-es5-adapter.js`
-According to the spec, only ES6 classes (https://html.spec.whatwg.org/multipage/scripting.html#custom-element-conformance) may be passed to the _native_ `customElements.define` API. For best performnace, ES6 should be served to browsers that support it, and ES5 code should be serve to those that don't. Since this may not always be possible, it may make sense to compile and serve ES5 to all browsers. However, if you do so, ES5-style custom element classes will now **not** work on browsers with native Custom Elements because ES5-style classes cannot properly extend ES6 classes, like `HTMLElement`.
 
-As a workaround, if your project has been compiled to ES5, load `custom-elements-es5-adapter.js` before defining Custom Elements.  This adapter will automatically wrap ES5.
+According to the spec, only ES6 classes (https://html.spec.whatwg.org/multipage/scripting.html#custom-element-conformance) may be passed to the _native_ `customElements.define` API. For best performance, ES6 should be served to browsers that support it, and ES5 code should be serve to those that don't. Since this may not always be possible, it may make sense to compile and serve ES5 to all browsers. However, if you do so, ES5-style custom element classes will now **not** work on browsers with native Custom Elements because ES5-style classes cannot properly extend ES6 classes, like `HTMLElement`.
+
+As a workaround, if your project has been compiled to ES5, load `custom-elements-es5-adapter.js` before defining Custom Elements. This adapter will automatically wrap ES5.
 
 **The adapter must NOT be compiled.**
 
@@ -164,24 +174,50 @@ As a workaround, if your project has been compiled to ES5, load `custom-elements
 The polyfills are intended to work in the latest versions of evergreen browsers. See below
 for our complete browser support matrix:
 
-| Polyfill   | Edge | IE11+ | Chrome* | Firefox* | Safari 9+* | Chrome Android* | Mobile Safari* |
-| ---------- |:----:|:-----:|:-------:|:--------:|:----------:|:---------------:|:--------------:|
-| Custom Elements | ✓ | ✓ | ✓ | ✓ | ✓ | ✓| ✓ |
-| Shady CSS/DOM | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
+| Polyfill        | Edge | IE11+ | Chrome\* | Firefox\* | Safari 9+\* | Chrome Android\* | Mobile Safari\* |
+| --------------- | :--: | :---: | :------: | :-------: | :---------: | :--------------: | :-------------: |
+| Custom Elements |  ✓   |   ✓   |    ✓     |     ✓     |      ✓      |        ✓         |        ✓        |
+| Shady CSS/DOM   |  ✓   |   ✓   |    ✓     |     ✓     |      ✓      |        ✓         |        ✓        |
 
 \*Indicates the current version of the browser
 
 The polyfills may work in older browsers, however require additional polyfills (such as classList, or other [platform](https://github.com/webcomponents/webcomponents-platform)
 polyfills) to be used. We cannot guarantee support for browsers outside of our compatibility matrix.
 
+## Known Issues
+
+- [Style encapsulation (inline styling in components) does not work out of the box](#shadycss)
+- [Custom element's constructor property is unreliable](#constructor)
+- [ShadyCSS: :host(.zot:not(.bar:nth-child(2))) doesn't work](#nestedparens)
+
+### Style encapsulation (inline styling in components) does not work out of the box. <a id="shadycss"></a>
+
+The ShadowDOM polyfill does not properly support CSS in ShadowDoM out of the box:
+
+- Any styles inside components have an effect on the whole document (instead of on the component only - the encapsulation is broken).
+- Any shadow-dom specific selectors (like `:host`) do not work.
+
+You can fix those issues by manually calling the `ShadyCSS` APIs. See [ShadyCSS usage](https://github.com/webcomponents/shadycss#usage).
+
+### Custom element's constructor property is unreliable <a id="constructor"></a>
+
+See [#215](https://github.com/webcomponents/webcomponentsjs/issues/215) for background.
+
+In Edge and IE, instances of Custom Elements have a `constructor` property of `HTMLUnknownElementConstructor` and `HTMLUnknownElement`, respectively. It's unsafe to rely on this property for checking element types.
+
+It's worth noting that `customElement.__proto__.__proto__.constructor` is `HTMLElementPrototype` and that the prototype chain isn't modified by the polyfills(onto `ElementPrototype`, etc.)
+
+### ShadyCSS: :host(.zot:not(.bar:nth-child(2))) doesn't work <a id="nestedparens"></a>
+
+ShadyCSS `:host()` rules can only have (at most) 1-level of nested parentheses in its argument selector under ShadyCSS. For example, `:host(.zot)` and `:host(.zot:not(.bar))` both work, but `:host(.zot:not(.bar:nth-child(2)))` does not.
 
 ### Manually Building
 
 If you wish to build the bundles yourself, you'll need `node` and `npm` on your system:
 
- * install [node.js](http://nodejs.org/) using the instructions on their website
- * use `npm` to install [gulp.js](http://gulpjs.com/): `npm install -g gulp`
- * make sure you have Java installed per https://www.npmjs.com/package/google-closure-compiler#java-version
+- install [node.js](http://nodejs.org/) using the instructions on their website
+- use `npm` to install [gulp.js](http://gulpjs.com/): `npm install -g gulp`
+- make sure you have Java installed per https://www.npmjs.com/package/google-closure-compiler#java-version
 
 Now you are ready to build the polyfills with:
 
@@ -204,26 +240,7 @@ Copyright (c) 2015 The Polymer Authors. All rights reserved.
 
 ## Changes in version 2.x
 
-* The HTML Imports polyfill has been removed. Given that ES modules have shipped in
-most browsers, the expectation is that web components code will be loaded via
-ES modules.
-* When using `webcomponents-loader.js` with the `defer` attribute, scripts that rely on the polyfills *must* be loaded using `WebComponents.waitFor(loadCallback)`.
-
-## Known Issues
-
-  * [ShadowDOM CSS is not encapsulated out of the box](#shadycss)
-  * [Custom element's constructor property is unreliable](#constructor)
-  * [ShadyCSS: :host(.zot:not(.bar:nth-child(2))) doesn't work](#nestedparens)
-
-### ShadowDOM CSS is not encapsulated out of the box <a id="shadycss"></a>
-The ShadowDOM polyfill is not able to encapsulate CSS in ShadowDOM out of the box. You need to use specific code from the ShadyCSS library, included with the polyfill. See [ShadyCSS instructions](https://github.com/webcomponents/shadycss).
-
-### Custom element's constructor property is unreliable <a id="constructor"></a>
-See [#215](https://github.com/webcomponents/webcomponentsjs/issues/215) for background.
-
-In Edge and IE, instances of Custom Elements have a `constructor` property of `HTMLUnknownElementConstructor` and `HTMLUnknownElement`, respectively. It's unsafe to rely on this property for checking element types.
-
-It's worth noting that `customElement.__proto__.__proto__.constructor` is `HTMLElementPrototype` and that the prototype chain isn't modified by the polyfills(onto `ElementPrototype`, etc.)
-
-### ShadyCSS: :host(.zot:not(.bar:nth-child(2))) doesn't work <a id="nestedparens"></a>
-ShadyCSS `:host()` rules can only have (at most) 1-level of nested parentheses in its argument selector under ShadyCSS. For example, `:host(.zot)` and `:host(.zot:not(.bar))` both work, but `:host(.zot:not(.bar:nth-child(2)))` does not.
+- The HTML Imports polyfill has been removed. Given that ES modules have shipped in
+  most browsers, the expectation is that web components code will be loaded via
+  ES modules.
+- When using `webcomponents-loader.js` with the `defer` attribute, scripts that rely on the polyfills _must_ be loaded using `WebComponents.waitFor(loadCallback)`.