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

Update article.md

Browse source 
Wording on why use attribute vs classes question
This commit is contained in:
paroche 2019-10-19 21:15:54 -06:00 • committed by GitHub
parent 15d0394161
commit 676ffb718a
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
2-ui/1-document/06-dom-attributes-and-properties/article.md
View file

@ -298,9 +298,9 @@ For instance, here for the order state the attribute `order-state` is used:
</div>
```
Why the attribute may be preferable to classes like `.order-state-new`, `.order-state-pending`, `order-state-canceled`?
Why would using an attribute be preferable to having classes like `.order-state-new`, `.order-state-pending`, `order-state-canceled`?
That's because an attribute is more convenient to manage. The state can be changed as easy as:
Because an attribute is more convenient to manage. The state can be changed as easy as:
```js
// a bit simpler than removing old/adding a new class