an IE6 bug with <textarea wrap="virtual">

  • Thread starter Thread starter Euclid
  • Start date Start date
E

Euclid

(Sorry if this isn't the correct NG for this query, but my choices seem
limited. I asked on a more specific IE NG but got no response.)

My IE6 has developed a bug while typing text into a composition box with the
attribute wrap="virtual" (or "soft"). It doesn't wrap the lines correctly.
Of course that's the default for IE, so it doesn't need to be told, but most
websites include that attribute in their code line, such as:
<TEXTAREA NAME="message" ROWS=8 COLS=68 WRAP=VIRTUAL WRAP=SOFT>
</TEXTAREA>

Interesting(?) but this particular IE6 bug does not happen if the wrap
attribute is omitted from the code line, such as:
<textarea COLS=55 ROWS=10 name="body"></textarea>

How would I go about repairing this operation in IE6?

I'm not sure if I need to give details about the bug. I will if requested,
but perhaps you can trust me that text composition boxes aren't working
exactly right in my IE6 browser. The lines don't wrap correctly. Somehow a
particular IE6 file(s) is probably corrupted. Unfortunately sfc /scannow
doesn't fix it, nor does changing the IE fonts.

I'm running Windows XP Home.
-E
 
(Sorry if this isn't the correct NG for this query, but my choices seem
limited. I asked on a more specific IE NG but got no response.)
Click to expand...

If you don't get an answer in an IE newsgroup, you are unlikely to get one
in a group devoted to programming Forms in Microsoft Access, the database
product!

I'd try again in the original, or other, IE newsgroups.

TC
 
Thanks, I'll try, but note that whenever I've encounted this bug, the
<textarea> tag always occurs inside a <form> tag, so forms are involved. So
I hoped that a NG devoted to forms might have enountered such a problem. You
compose your forms to be perfect and bug free, but surely some end users of
the forms (customers) develop bugs in their software (IE6) so they won't
work right. I have such a bug, apparently, although that's not entirely
clear. Someone suggested that it might be caused by a faulty cgi script,
perhaps a popular and widely distributed/used script, but that's beyond my
personal knowledgebase.
-E

(Sorry if this isn't the correct NG for this query, but my choices seem
limited. I asked on a more specific IE NG but got no response.)
Click to expand...

If you don't get an answer in an IE newsgroup, you are unlikely to get one
in a group devoted to programming Forms in Microsoft Access, the database
product!

I'd try again in the original, or other, IE newsgroups.

TC
 
Ok, now I see where you're coming from!

The "forms" discussed in this newsgroup, are the forms that are used in the
Microsoft Access database product. They are nothing to do with HTML forms.
Someone here might be the world's best expert in Access forms, but never
have heard of HTML, at all.

Good luck :-)
TC
 
Back
Top