When talking about webComponents, people tend to think that shadown DOM is a requirement. In fact, that is a misconception and if you don´t need shadow DOM, you don´t use it. It is not tied to webComponents and can be used by itself.

We often forget that the browser has a built-in state container readily available to us, the url! In this post i´ll cover a simple use-case for storing filters in the url.

Custom elements like complex multi-selects or datepickers won´t get picked up by a parent form element during form submission, but why is that?

While we´re used to input elements and submit buttons that just work inside forms. Getting our custom elements working within forms can be tricky if we´re also using shadow DOM.