jeena/en.javascript.info
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

#8: fix unordered list

Browse source
This commit is contained in:
Anton Yershov 2019-04-25 23:47:38 +03:00
parent 9f06601c34
commit 65c5793733
1 changed files with 2 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

3
8-web-components/1-webcomponents-intro/article.md
View file

@ -56,7 +56,8 @@ Components may have subcomponents, e.g. messages may be parts of a higher-level
How do we decide, what is a component? That comes from intuition, experience and common sense. Usually it's a separate visual entity that we can describe in terms of what it does and how it interacts with the page. In the case above, the page has blocks, each of them plays its own role, it's logical to make these components.
- A component has its own JavaScript class.
A component has:
- its own JavaScript class.
- DOM structure, managed solely by its class, outside code doesn't access it ("encapsulation" principle).
- CSS styles, applied to the component.
- API: events, class methods etc, to interact with other components.