Skip to content

Fix name on essay #3019

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
1cg merged 1 commit into from
Nov 14, 2024
Merged

Fix name on essay #3019

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions www/content/essays/webcomponents-work-great.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -97,7 +97,7 @@ That will give us this table:
<tr>
<td>Sophia
<td><edit-cell name="sophia-carousel" value="Yes"></edit-cell>
<td><edit-cell name="sophia-roller" value="No"></edit-cell>
<td><edit-cell name="sophia-roller" value="Yes"></edit-cell>
</tr>
</table>
<button>Save</button>
Expand Down Expand Up @@ -125,7 +125,7 @@ Let's remove all that redundancy with a web component!
<tr>
<td>Sophia
<td><edit-cell name="sophia-carousel" value="Yes"></edit-cell>
<td><edit-cell name="sophia-roller" value="No"></edit-cell>
<td><edit-cell name="sophia-roller" value="Yes"></edit-cell>
</tr>
</table>
<button>Save</button>
Expand Down Expand Up @@ -158,11 +158,11 @@ But being able to work with both the [Shadow DOM](@/examples/web-components.md)

## Bringing Behavior Back to the HTML

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/):
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/):

> 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.

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).
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).
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/);
disrespecting HTML was best practice.

Expand Down