The last part focused on using observedAttributes() to switch what the main action button did, depending on the current document state. In this part we'll cover the functionality behind the search button and the save.
There are always challenges when moving from something familiar to something similar but different. When you've been working with that "something familiar" for a very long time, some things become second nature. But when you move to "something similar but different", sooner or later you hit an error and become convinced it's not working like it used to. This is even more probable if enhancements mean you more frequently come across a specific paradigm. The rash developer starts throwing accusations, assuming they must be right because they have years of experience on their side. The wise developer double-checks first...and may find out that they were mistaken.
Welcome to my new blog. It may seem a lot of effort to switch from one blog to another. But I've been working with Material for MKDocs for some years, thanks to Stephan Wissel, and it's a great framework for documentation. I've been aware of the blog plugin for some time, so it made sense to consider it as a good fit for the future.