One of the best performance tips is "do less" - transmit less data and do less processing. There are a million details but we will focus on transmitting less JavaScrip

The following is a guest post by Rob Dodson (@rob_dodson). Rob and I were going back and forth in CodePen support getting Polymer (a web components polyfill,

By default, single-page-applications (SPAs) have a single URL. Navigating between screens does not change the URL; nor is there a mechanism to deep link to a particular screen using an URL. Turns out…

Web Components have been on developers' radars for quite some time now. They were first introduced by Alex Russell at Fronteers Conference 2011. The concept shook the community up and ...

Learn what web components are and how to use them without a JS framework. This article shows you an approach that relies on custom elements.

Single File Web Components. Contribute to 11ty/webc development by creating an account on GitHub.

Editors Note: This article was updated to remove references to deprecated components specifically polymer-ajax which has since been replaced by core-ajax. Thanks to Rob Dodson, developer advocate...

Web Components are a collection of four distinct technologies that come together to form a new way to package and reuse self-contained components built with HTML, CSS, and JavaScript. The four...

Ever think of creating a webpage using HTML with a simple Header and Footer? That's easy, right? But what if your application grows and you need to repeat the same code for the header and footer 5, 10, or say 15 times? Remember the DRY (Don't Repeat...

how to create dual list box in lwc, how to create dual list box in lightning web components, duallist box in lwc, duallistbox in lwc, duallistbox in lighting web components

Pankaj Parashar introduces the new W3C specs for Web Components, and shows us how we can start using its features with the Polymer library created by Google.

A Complete Introduction to building Custom HTML Elements/ Web Components with and without StencilJS

Few things in the frontend world are as hot as Design Systems, the idea of building a design spec or library of reusable components that can be shared across a team or company. Design Systems enforce style and branding guidelines, reduce design fatigue for engineers, and consolidate component engineering to one single set of components […]

The HTML tag shifts the emphasis from component developer to component consumer by allowing anyone to add fresh content to a standard web component.

This blog has information about Salesforce, apex, visualforce, lightning components, lightning web components, lwc

refresh apex data, refresh apex, clear row index after delete the records, clear selected row indexes,

View encapsulation is a way that defines whether components styles will affect the whole application or not i.e it has control over usage of component styles, use stylesglobally or should be limited to a particular angular component (scoped styles).angular components can be styled via inline styles through styles property or via external styles through styleurls which are the property of @component decorator.example in default root component "app.component.ts" adding styleinline styles through styles property.@component({ selector: 'app-root', templateurl: './app.component.html', styles: [ `h1 { color: #369; font-family: arial, helvetica, sans-serif; font-size: 250%; } `]})export class appcomponent { title = 'angular 4 app';}external styles through styleurls property.import { component } from '@angular/core';@component({ selector: 'app-root', templateurl: './app.component.html', styleurls: ['./app.component.css']})export class appcomponent { title = 'angular 4 app';}above mentioned component styles are appended to document head. but by using native shadow dom the component styles will be included in component’s template.what is shadow dom?shadow dom can be defined as web components standard part which is capable of enabling dom tree and style encapsulation i.e it allows elements in the dom to have scoped styles without letting styles to leak outside of component scope.shadow dom in angularin angular, components are built. the component can be defined as a controller class in possession of template and styles. components are shareable i.e reusable across the application. but these angular components are not web components but they can take advantage of or say are inspired by web components. angular components can have scoped styles which are controlled through encapsulation property. view encapsulation typesthere are three view encapsulation types:viewencapsulation.noneviewencapsulation.emulatedviewencapsulation.nativewhenever an angular component is created, angular puts the component template inside shadowroot, which can be considered as shadow dom of that particular component. thus doing this dom tree and style encapsulation can be obtained but what if the browser does not have shadow dom. in such cases, angular does not create shadowroot for component until native shadow dom i.e "viewencapsulation.native" is used. in fact, angular uses "viewencapsulation.emulated" by default.example of view encapsulation types1) viewencapsulation.none: shadow dom is not supported at all, therefore, no style encapsulation. therefore whatever styles applied to an angular component are kept within document head.create a new component student using "ng g component student" command.student.component.tsimport { component, oninit } from '@angular/core';import {viewencapsulation} from '@angular/core';@component({ selector: 'app-student', templateurl: './student.component.html', styles: [ `h1 { color: #367; font-family: arial, helvetica, sans-serif; font-size: 250%; } `], encapsulation: viewencapsulation.none})export class studentcomponent implements oninit { constructor() { } ngoninit() { }}student.component.html (student template)

inside student component

root component "app.component.ts"import { component } from '@angular/core';@component({ selector: 'app-root', template: ''})export class appcomponent { title = 'angular 4 app';}the page "index.html" which is rendered:

welcome to angular 4 demo

when this application runs it will create following domit can be seen that no shadow dom is created as well as student component style are kept within document head. therefore style for the h1 element is not scoped and thereby applied to entire application i.e for student template as well as for index.html.outputviewencapsulation.emulateddoes not support shadow dom but support style encapsulation. it is the default value of angular components styles.change encapsulation type in "student.component.ts" to "viewencapsulation.emulated" rest remain same.@component({ selector: 'app-student', templateurl: './student.component.html', styles: [ `h1 { color: #367; font-family: arial, helvetica, sans-serif; font-size: 250%; } `], encapsulation: viewencapsulation.emulated})export class studentcomponent implements oninit { constructor() { } ngoninit() { }}when this application runs it will create following domit can be seen that no shadow dom is created and student component style is kept within document head. but angular created h1[_ngcontent-c0] selector changing component's style. for scoped styles, angular extended css selector's so that they have higher specificity and collision with other same selectors before they do not happen as a result component’s style selectors only match required particular component and nothing else. to match these selectors template elements are also extended.outputthe styling for h1 element is only applied to student component template.viewencapsulation.nativeit not only supports shadow dom but also supportsstyle encapsulation.change encapsulation type in "student.component.ts" to "viewencapsulation.native" rest remain same.import { component, oninit } from '@angular/core';import {viewencapsulation} from '@angular/core';@component({ selector: 'app-student', templateurl: './student.component.html', styles: [ `h1 { color: #367; font-family: arial, helvetica, sans-serif; font-size: 250%; } `], encapsulation: viewencapsulation.native})export class studentcomponent implements oninit { constructor() { } ngoninit() { }}when this code runs in browser create following domit can be seen that student component style are not within document head instead it appears within shadowroot in the component template.

We provide expert online salesforce training,salesforce lightning training, lightning web component, salesforce developer certification,cloud computing,certi...

Is the modern web development complicated? Yes, and it’s not because we love making things complicated, however, it’s due to the diverse and complex range of platforms, environments, and devices. Web…