<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>HTML on Duma's website</title><link>https://dumaron.github.io/tags/html/</link><description>Recent content in HTML on Duma's website</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 14 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://dumaron.github.io/tags/html/index.xml" rel="self" type="application/rss+xml"/><item><title>&lt;code&gt;inputMode&lt;/code&gt; HTML attribute</title><link>https://dumaron.github.io/notes/tils/2026-02-13_inputmode_attribute/</link><pubDate>Sat, 14 Feb 2026 00:00:00 +0000</pubDate><guid>https://dumaron.github.io/notes/tils/2026-02-13_inputmode_attribute/</guid><description>&lt;p&gt;While working on a form with numeric inputs, I noticed Claude putting this attribute on them: &lt;code&gt;inputMode=&amp;quot;numeric&amp;quot;&lt;/code&gt;.&lt;/p&gt;&#10;&lt;p&gt;Intrigued, I looked at the &#10;&#10;&lt;a href="https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Global_attributes/inputmode" rel="noopener" target="_blank"&gt;MDN page&lt;/a&gt; and it turns out the attribute exists to support different input styles, mostly related to what a smartphone will show in the keyboard tray. It can take values like &lt;code&gt;tel&lt;/code&gt;, &lt;code&gt;email&lt;/code&gt;, &lt;code&gt;numeric&lt;/code&gt; and so on.&lt;/p&gt;&#10;&lt;p&gt;The attribute&amp;rsquo;s effect is limited to the keyboard, and it relies on the specific vendor to act on it. Nevertheless, I find it pretty useful to be able to change the keyboard between &lt;code&gt;numeric&lt;/code&gt; and &lt;code&gt;decimal&lt;/code&gt; depending on the value that needs to be entered in a form field.&lt;/p&gt;</description></item><item><title>&lt;code&gt;datalist&lt;/code&gt; for range inputs</title><link>https://dumaron.github.io/notes/tils/2024-08-27_datalist_for_range_inputs/</link><pubDate>Tue, 27 Aug 2024 00:00:00 +0000</pubDate><guid>https://dumaron.github.io/notes/tils/2024-08-27_datalist_for_range_inputs/</guid><description>&lt;p&gt;The &lt;code&gt;datalist&lt;/code&gt; tag has surprised me at least a couple time already. While I still consider native HTML inputs as inadequate and too rigid, I admit that thanks to the &lt;code&gt;datalist&lt;/code&gt; tag the UX can improve a bit.&lt;/p&gt;&#10;&lt;p&gt;Today I was how far the native range inputs are from for &#10;&#10;&lt;a href="https://eui.elastic.co/#/forms/range-sliders" rel="noopener" target="_blank"&gt;ElasticUI range inputs&lt;/a&gt;, the one I currently use. I stumbled upon the MDN Web docs page and particularly &#10;&#10;&lt;a href="https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/range#list" rel="noopener" target="_blank"&gt;on the &lt;code&gt;list&lt;/code&gt; attribute&lt;/a&gt;: it can contain the &lt;code&gt;id&lt;/code&gt; of a &lt;code&gt;datalist&lt;/code&gt; component and to enhance the user experience of the input. It seems the only three ways these two tags can interact are:&lt;/p&gt;</description></item></channel></rss>