<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Loading Indicators on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/loading-indicators/</link><description>Recent content in Loading Indicators on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 04 Dec 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/loading-indicators/index.xml" rel="self" type="application/rss+xml"/><item><title>Chapter 7: Indicators and Loading States: Providing User Feedback</title><link>https://ai-blog.noorshomelab.dev/htmx-mastery-2025/indicators-loading-states/</link><pubDate>Thu, 04 Dec 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/htmx-mastery-2025/indicators-loading-states/</guid><description>&lt;h2 id="chapter-7-indicators-and-loading-states-providing-user-feedback"&gt;Chapter 7: Indicators and Loading States: Providing User Feedback&lt;/h2&gt;
&lt;p&gt;Welcome back, future HTMX maestro! In the previous chapters, you&amp;rsquo;ve mastered the art of making your web pages dynamic and interactive using HTMX. You&amp;rsquo;ve learned how to fetch and swap content with &lt;code&gt;hx-get&lt;/code&gt;, &lt;code&gt;hx-post&lt;/code&gt;, and various &lt;code&gt;hx-swap&lt;/code&gt; strategies. But what happens when these requests take a little longer than expected? How do you let your users know that something is happening behind the scenes, preventing them from clicking furiously or wondering if their action registered?&lt;/p&gt;</description></item></channel></rss>