4 ms·
Downside of most HTMX examples (such as the form in TFA) seems to be lack of graceful degradation with non-JS-enabled user agents. But then, the rest of the pa
by strogonoff 5y ago
Downside of most HTMX examples (such as the form in TFA) seems to be lack of graceful degradation with non-JS-enabled user agents.
But then, the rest of the page is server-generated (taking care of SEO), and handling interactivity without JS may not be a priority for most sites nowadays.
- recursivedoubts 5y agoprogressive enhancement is possible with htmx (e.g. the hx-boost attribute is p/e friendly) but often requires thought by the programmer for example, the active search example can be made p/e'd by wrapping the input with a form that submits to the same page: https://htmx.org/examples/active-search/ https://htmx.org/examples/active-search/ but it requires work by the end developer the idea here is to be pragmatic: obviously some people care deeply about p/e and are unwilling to sacrifice it for more advanced U/X, but others are willing to do so, so let's make it possible for both camps to improve their sites with the tool