Skip to content

Commit 82eb2a6

Browse files
authored
Fix name on essay (#3019)
Fix name on essay
1 parent ccbc101 commit 82eb2a6

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

www/content/essays/webcomponents-work-great.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -97,7 +97,7 @@ That will give us this table:
9797
<tr>
9898
<td>Sophia
9999
<td><edit-cell name="sophia-carousel" value="Yes"></edit-cell>
100-
<td><edit-cell name="sophia-roller" value="No"></edit-cell>
100+
<td><edit-cell name="sophia-roller" value="Yes"></edit-cell>
101101
</tr>
102102
</table>
103103
<button>Save</button>
@@ -125,7 +125,7 @@ Let's remove all that redundancy with a web component!
125125
<tr>
126126
<td>Sophia
127127
<td><edit-cell name="sophia-carousel" value="Yes"></edit-cell>
128-
<td><edit-cell name="sophia-roller" value="No"></edit-cell>
128+
<td><edit-cell name="sophia-roller" value="Yes"></edit-cell>
129129
</tr>
130130
</table>
131131
<button>Save</button>
@@ -158,11 +158,11 @@ But being able to work with both the [Shadow DOM](@/examples/web-components.md)
158158

159159
## Bringing Behavior Back to the HTML
160160

161-
A couple of years ago, W3C Contributor (and Web Component proponent, I think) Leah Verou wrote the following, in a blog post about ["The failed promise of Web Components"](https://lea.verou.me/blog/2020/09/the-failed-promise-of-web-components/):
161+
A couple of years ago, W3C Contributor (and Web Component proponent, I think) Lea Verou wrote the following, in a blog post about ["The failed promise of Web Components"](https://lea.verou.me/blog/2020/09/the-failed-promise-of-web-components/):
162162

163163
> the main problem is that HTML is not treated with the appropriate respect in the design of these components. They are not designed as closely as possible to standard HTML elements, but expect JS to be written for them to do anything. HTML is simply treated as a shorthand, or worse, as merely a marker to indicate where the element goes in the DOM, with all parameters passed in via JS.
164164
165-
Leah is identifying an issue that, from the perspective of 2020, would have seemed impossible to solve: the cutting-edge web developers targeted by Web Components were not writing HTML, they were writing JSX, usually with React (or Vue, or what have you).
165+
Lea is identifying an issue that, from the perspective of 2020, would have seemed impossible to solve: the cutting-edge web developers targeted by Web Components were not writing HTML, they were writing JSX, usually with React (or Vue, or what have you).
166166
The idea that [behavior belongs in the HTML](https://unplannedobsolescence.com/blog/behavior-belongs-in-html/) was, in the zeitgeist, considered [a violation of separation of concerns](https://htmx.org/essays/locality-of-behaviour/);
167167
disrespecting HTML was best practice.
168168

0 commit comments

Comments
 (0)