docs(elements): use Angular Elements naming in nav (#23213)
PR Close #23213
This commit is contained in:
parent
b5f41f2c35
commit
eb9968ab2a
|
@ -1,10 +1,10 @@
|
|||
# Custom Elements Overview
|
||||
# Angular Elements Overview
|
||||
|
||||
[Custom elements](https://developer.mozilla.org/en-US/docs/Web/Web_Components/Using_custom_elements) are a Web Platform feature currently supported by Chrome, Opera, and Safari, and available in other browsers through polyfills (see [Browser Support](#browser-support)).
|
||||
A custom element extends HTML by allowing you to define a tag whose content is created and controlled by JavaScript code.
|
||||
The browser maintains a `CustomElementRegistry` of defined custom elements (also called Web Components), which maps an instantiable JavaScript class to an HTML tag.
|
||||
|
||||
The `createCustomElement()` API provides a bridge from Angular's component interface and change detection functionality to the built-in DOM API.
|
||||
The `@angular/elements` package exports a `createCustomElement()` API that provides a bridge from Angular's component interface and change detection functionality to the built-in DOM API.
|
||||
|
||||
Transforming a component to a custom element makes all of the required Angular infrastructure available to the browser. Creating a custom element is simple and straightforward, and automatically connects your component-defined view with change detection and data binding, mapping Angular functionality to the corresponding native HTML equivalents.
|
||||
|
||||
|
|
|
@ -186,8 +186,8 @@
|
|||
},
|
||||
{
|
||||
"url": "guide/elements",
|
||||
"title": "Custom Elements",
|
||||
"tooltip": "Convert components to custom elements."
|
||||
"title": "Angular Elements",
|
||||
"tooltip": "Convert components to Custom Elements."
|
||||
},
|
||||
{
|
||||
"url": "guide/dynamic-component-loader",
|
||||
|
|
Loading…
Reference in New Issue