EXCEPT that this.blur() causes the TabKey Sequencing to get caught in the blurred field... you have to use the mouse and click out of it. Kinda screws up tab key navigation... ugh!
Is that the ONLY way to protect it in Netscape? At 03:10 AM 3/11/02 -0500, you wrote: >No your right, not until Netscape 6 was readonly and disabled >introduced, whereas IE as supported it since version 4.0 > >There is a way to get around this though :) > ><input type="text" name="blah" onfocus="this.blur()"> > >_____________________________ >steve oliver >senior internet developer >atnet solutions, inc. >http://www.atnetsolutions.com > > >-----Original Message----- >From: Brian Scandale [mailto:[EMAIL PROTECTED]] >Sent: Monday, March 11, 2002 2:57 AM >To: CF-Talk >Subject: <input readonly or disabled > > >I've been using disabled in text form fields quite a bit lately when I >need to gray out something and keep users from changing it... > >Today I notice that Netscrape seems to not honor the readonly/disabled. > >Am I just coding this wrong or does Netscrape truly not recognize these >two attributes to the <input tag? > > > ______________________________________________________________________ Why Share? Dedicated Win 2000 Server · PIII 800 / 256 MB RAM / 40 GB HD / 20 GB MO/XFER Instant Activation · $99/Month · Free Setup http://www.pennyhost.com/redirect.cfm?adcode=coldfusionc FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
