On Blogger’s home page (looks like they’ve been doing some tweaking on their own since Doug Bowman helped them redesign a couple of years ago) there is a script that writes the login form to the page. If scripting is not available, a fallback is provided in a
The lesson to be learned is to put submit buttons in the actual markup that all browsers receive, not in a
noscript element (which is a sign of outdated development methods anyway).
The second service to break down was Bloglines. Ian notes the problems he encountered in Bloglines Is Broken (for me, at least).
Next up is Ma.gnolia, a service which in Ian’s words (and I agree) is Using a sledgehammer to crack a nut.
If I may make a suggestion, here’s the approach I would use if a visual designer pointed a gun at my head, threatening to pull the trigger unless I get rid that default, horribly ugly, and user-recognisable button:
- Put a normal, honest, bullet proof, works-everywhere submit button in the markup.
- Do not use CSS to hide it.
- If JS is available, hide or remove it and insert the fancy-schmancy styled link instead.
Done. Progressive enhancement (if you can call that enhancement) instead of dis-graceful degradation.
How many others are making similar mistakes?
I thought we were over the reckless scripting practices of the 20th century. Apparently I was wrong.