RE: input readonly or disabled

2002-03-11 Thread Brian Scandale
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

RE: input readonly or disabled

2002-03-11 Thread Semrau, Steven L Mr RDAISA/SRA
; -Original Message- From: Brian Scandale [mailto:[EMAIL PROTECTED]] Sent: Monday, March 11, 2002 3:25 AM To: CF-Talk Subject: RE: input readonly or disabled EXCEPT that this.blur() causes the TabKey Sequencing to get caught in the blurred field... you have to use the mouse and click out

RE: input readonly or disabled

2002-03-10 Thread Steve Oliver
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,