Comments on: Create a NoScript Compatible Select Form Element with an onChange Event

By: Jow

Jow — Sat, 10 Sep 2011 22:13:44 +0000

I would just put the button in button here tags and thats it. I find this a little bit easier.

By: Ape Web

Ape Web — Thu, 11 Feb 2010 23:50:30 +0000

The JavasScript should also be binding the onchange event.

By: Slater

Slater — Wed, 03 Feb 2010 14:33:48 +0000

@atom: I can think of one: autocomplete=”off”.

That one is completely indispensable when dealing with sensitive information in forms.

- Not that it was relevant to any of this, I just thought I’d mention it :P

By: atom

atom — Sun, 06 Jul 2008 23:52:24 +0000

@david there is no reason why you shouldn’t have both, in this example and most others, this can be achieved easily with minor modifications. I am just saying, if you use Google’s stuff, the likelihood that it is messy and needs some attention before reusing it is pretty high.

There is almost no case where standards need to / or should be sacrificed for functionality.

By: david

david — Sun, 06 Jul 2008 23:45:19 +0000

@atom: I see your point, but I think in this case that functionality is more important than standards.

By: atom

atom — Sun, 06 Jul 2008 19:58:16 +0000

I think that it is worth mentioning that Google’s client-side code should be taken with a grain of salt. None of Google’s pages are even remotely close to standards compliant, including the code in your example. After all, who do they have to impress?

By: Scaracco

Scaracco — Thu, 03 Jul 2008 15:59:41 +0000

Simply put the submit button inside noscript tags and it became visible only with javascript disabled. No need for other code.

By: Carlo

Carlo — Thu, 03 Jul 2008 14:18:35 +0000

Also updates the example :-)

By: david

david — Thu, 03 Jul 2008 13:58:30 +0000

@Carlo: Thank you! Updated.

By: Carlo

Carlo — Thu, 03 Jul 2008 10:06:28 +0000

For a complete form accessibility, I think it’s necessary insert the label for the select.