Šime Vidas
“I can see how this would be good to have fixed at the browser level.” adactio.com/links/17604 A good mindset. The more browsers can fix, the less websites have to deal with.
I can see how this would be good to have fixed at the browser level.
“I can see how this would be good to have fixed at the browser level.” adactio.com/links/17604 A good mindset. The more browsers can fix, the less websites have to deal with.
Garrett talks through some handy HTML attributes: spellcheck
, autofocus
, autocapitalize
, autocomplete
, and autocorrect
:
While they feel like small details, when we set these attributes on inputs, we streamline things for visitors while also guiding the browser on when it should just get out of the way.
When I was in Amsterdam I was really impressed with the code that Rose was writing and I encouraged her to share it. Here it is: drop this script into a web page with a form to have its values automatically saved into local storage (and automatically loaded into the form if something goes wrong before the form is submitted).
I realised, progressive enhancement isn’t only about supporting that 1%. It’s about testing your app without JavaScript to ensure 100% of your users have a more performant, usable, available, and resilient experience.
A really good explanation of progressive enhancement as an approach to building anything on the web:
Progressive enhancement does not mean you need to provide the exact same UI without JavaScript. The enhanced experience should be better and it should do more, otherwise the enhanced experience is not needed at all. It enhances a degraded experience that also allows the user to accomplish their goal. For example, entering a postal code manually into a text box might be the degraded experience, and the progressively enhanced experience would prefill the text box based on Geolocation data.
The capture
attribute is pretty nifty—and I just love that you get so much power in a declarative way:
<input type="file" accept="image/*" capture="environment">
A handy little script from Aaron to improve the form validation experience.
Some buggy behaviour has been fixed in iOS 18 but now there’s a new bit of weirdness.
If you’re going to toggle the display of content with CSS, make sure the more complex selector does the hiding, not the showing.
It should be safe to visit a web page.
A defensive enhancement to avoid losing everything you just typed into a textarea.
Some code to show a progress bar for file uploads.