IE vs NS text areas

Anon

In IE, setting the text area control attribute READONLY makes the text area so. In NS, no dice, you can still edit the text area. I tried using READONLY="true" but it's still not working, e.g. :

TEXTAREA NAME="Notes" READONLY="true" WRAP=SOFT

Anybody know what the correct parameter is?

opticmike

Hmm my buddy had a problem like this too. He used something on the line of this.
code:--------------------------------

TYPE="text" NAME="test" Rules" onFocus="this.blur()"

But I don't think this works in ns 6.0+. Hope this helps you a little.

opticmike

O yea still put readonly="true"

Anon

I know Microsquish and Netscape hate each other's guts, but you would think that their web controls would all act the same via the HTML standards set up.

Yeah, I know. The Tooth Fairy really does exist.

BTW, what was that "rules" part?

opticmike

ah the 'rules' was the name of it i start to type nothing important in the case

Anon

"READONLY" is part of HTML 4, which is properly supported in Netscape 6 & 7 as well as Mozilla. It did not exist when Netscape 4 was written.

opticmike

I just downloaded 6.2.3 and 7.0 Preview Release 1 'full install' of Netscape and both of them do support readonly="true" or disable="true".
BTW Disable is like readonly but it makes the text grey instead of black of whatever color you assigned it.

Anon

So Netscape jumped the gun with its version numbers ahead of the HTML standard, not catching up until Version 6. IOW, Netscape 4 was written for HTML 3. If I ran a co. I'd make sure Marketing reports to IS, and not the other way around!

Anon

I need to use read-only here so the user can at least see what's in the text area. He can then decide whether or not to edit the text by going to another page (hit the edit button) that turns off read-only.

Disable (at least in IE) greys out the whole control with no scrolling.

The interesting thing in all this is, just having the attribute READONLY between the tags does the trick for IE. No ="true" is necessary.

Anon

Maybe, but XHTML requires that all attributes have a value.

Diego

Anon

That's a good point to keep in mind! I haven't done much with XML yet, but I see your point. Guess I better clean up my coding practices before the coming XML stampede.

BTW, I don't use Netscape. But the spec says this is a Boolean value. I wonder if a 1 or 0 would do just as well as a "true" or "false"? I guess that really depends upon the browser.

wshost

Netscape sux. Do a browser test, if it is netscape echo some headers:

header("Location: http://www.netscapesux.com");

or something like that.

Perhaps a header for microsofts IE 6 page. AOL owns netscape now so it's all downhill from here anyways.