|
8 | 8 |
|
9 | 9 | # The Document Object Model |
10 | 10 |
|
11 | | -// FIXME custom elements, better transitions, maybe `children`, templates, problems with obvious usage |
| 11 | +// FIXME better transitions, maybe `children`, fragments, problems with obvious usage |
12 | 12 |
|
13 | 13 | {{index drawing, parsing}} |
14 | 14 |
|
@@ -161,10 +161,10 @@ numbers to access the child nodes. But it is an instance of the |
161 | 161 |
|
162 | 162 | Then there are issues that are simply poor design. For example, there |
163 | 163 | is no way to create a new node and immediately add children or |
164 | | -attributes to it. Instead, you have to first create it, then add the |
165 | | -children one by one, and finally set the attributes one by one, using |
166 | | -side effects. Code that interacts heavily with the DOM tends to get |
167 | | -long, repetitive, and ugly. |
| 164 | +((attribute))s to it. Instead, you have to first create it, then add |
| 165 | +the children one by one, and finally set the attributes one by one, |
| 166 | +using side effects. Code that interacts heavily with the DOM tends to |
| 167 | +get long, repetitive, and ugly. |
168 | 168 |
|
169 | 169 | {{index library}} |
170 | 170 |
|
@@ -454,7 +454,7 @@ through a ((property)) of the same name on the element's ((DOM)) |
454 | 454 | object. This is the case for a limited set of commonly used standard |
455 | 455 | attributes. |
456 | 456 |
|
457 | | -{{index "data attribute", "getAttribute method", "setAttribute method"}} |
| 457 | +{{index "data attribute", "getAttribute method", "setAttribute method", attribute}} |
458 | 458 |
|
459 | 459 | But HTML allows you to set any attribute you want on nodes. This can |
460 | 460 | be useful because it allows you to store extra information in a |
|
0 commit comments