Raymond is a senior developer evangelist for Adobe. He focuses on document services, JavaScript, and enterprise cat demos.

Latest Posts

Adding Form Participation Support to Web Components

Many years ago when the web platform began to really improve, when everything was "HTML5 this" and "HTML5 that", I remember being particularly excited by the updates to forms. I started my web career doing a lot of form processing and have always thought it was one of the more important aspects of the platform. Anything that improved that was a good thing. In my explorations of web components, I was ecstatic to discover that web components can be participants in forms. So what do we mean by that?

Links For You

Welcome to another "Links For You" post. My queue of links to share seems to be growing quicker than my schedule of posting these (roughly every two weeks), so I may post one next week as well. As always, I hope these posts are useful and informative for yall. Before getting into the links, I'm going to do a bit of a "PBS Fundraiser" request. A while ago, I set up a service for folks to subscribe to the blog and get emails on every new post. This was done via Mailchimp and I documented the process of how you could do it too: Adding an Email Subscription to Your Jamstack Site

Handling Web Component Removal with disconnectedCallback

MDN does a fairly good job of covering the lifecycle events for web components but one in particular got my attention today, disconnectedcallback. As kind of the inverse of connectedCallback, it will be fired when an instance of your custom element is removed from the DOM. While I didn't doubt this worked as advertised, I wanted to build a quick demo myself so I could see it in action. Let's start off with a component that demonstrates why this event is needed.

Want more posts? You can peruse a complete list of my content, or pop over to my search page to find what you're looking for.