Re: Next form element
Available news archives: comp.lang.tcl - comp.lang.python - comp.security.firewalls - sci.crypt - comp.lang.php - comp.lang.javascript
Google
 
Web news.hping.org


comp.lang.javascript archive

Re: Next form element

From: Randy Webb <HikksNotAtHome@aol.com>
Date: Wed Feb 01 2006 - 22:00:06 CET

Dr John Stockton said the following on 2/1/2006 11:16 AM:
> JRS: In article <XuNDf.4478$tb3.2396@newssvr24.news.prodigy.net>, dated
> Tue, 31 Jan 2006 17:53:59 remote, seen in news:comp.lang.javascript,
> BootNic <Bootnic@bounce.prodigy.net> posted :
>> <button type="button" onclick="x.readOnly=(x.readOnly)?false:true;
> ^^^^^^^^^^^^ Ugh!
>> x.focus(); x.select();">toggle readOnly</button>
>
>
> As is well-known, I dislike using new-fangled constructs instead of
> older equivalents as soon as they become available in the latest
> systems, since that handicaps those with older software.

<button> is not a "new-fangled" construct though. It is at least 7 years
old and probably older.

> And I don't recall ever seeing <button ... > in anyone else's source.

It is seen quite a lot.

> But (with or without type=button) it works in my IE4, and is acceptable
> to two local testers.

> In which versions, at about what date, did it appear in browsers?

It is supported by IE4+, NS6+ and any later (modern) browser. NN4 didn't
support button though.

> Are there other special cases of <input type=... > that are widely
> implemented?

Such as what?

-- 
Randy
comp.lang.javascript FAQ - http://jibbering.com/faq & newsgroup weekly
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/
Received on Tue Feb 7 21:30:30 2006