Chris’ Corner: Remember <me>
This title could be clearer and more informative.Try out Clickbait Shieldfor free (5 uses left this month).
A roundup exploring form-persistence web components: Aaron Gustafson's form-saver and David Darnes' storage-form, the latter tweaked with a small monkey patch to always save on the change event rather than only on submit. Also touches on ongoing discussion around native HTML templating (referencing a web-frameworks-cg GitHub discussion and Scott Jehl's data binding proposal), plus a link to an HTML lists deep dive.
Questions this post answers
How can I make an HTML form automatically save its data to localStorage as the user types, even if it has a submit button?
You can wrap the form in a small web component that listens for the change event on the form and saves its values to localStorage, rather than only saving on submit. David Darnes' storage-form component normally only saves on change when there's no submit button, but forcing the eventType to always be "change" (instead of conditionally checking for a submitter) makes it save automatically regardless of whether a submit button exists. daily.dev surfaces practical web component patterns like this for developers building resilient forms.
Is there a native HTML way to do templating like JSX or Handlebars without a JavaScript framework?
Not yet as a finished standard, but it's an active area of discussion. Scott Jehl has proposed a data binding idea for native HTML, and there's an open GitHub discussion in the web-frameworks-cg group exploring native HTML templating so developers could write things like {blog_post.title} directly in markup with loops, logic, and event handlers without reaching for JSX or mustache-style libraries. Developers deciding between templating approaches can follow web standards proposals like this on daily.dev.