with gfx text controls enabled, <textarea> doesn't render it's content, problem might be white-space: -moz-pre-wrap;

VERIFIED FIXED in M10

Status

()

Core
Layout
P1
blocker
VERIFIED FIXED
19 years ago
2 years ago

People

(Reporter: buster, Assigned: buster)

Tracking

Trunk
x86
Windows NT
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(1 attachment)

(Assignee)

Description

19 years ago
this worked wednesday, the last time I pulled code before today.
now, I see <TEXTAREA>s don't render their content, whether it's initial content
or typed-in text.

I'm about to attach a test case with 2 <TEXTAREA>s.  One uses white-space:
-moz-pre-wrap and does not render, the other does not use this style and
renders fine.

I think rendering of docs with body style white-space: -moz-pre-wrap; is the
problem.
(Assignee)

Comment 1

19 years ago
Created attachment 1457 [details]
test case containing 2 <textarea>s, one that works and one that does not
(Assignee)

Updated

19 years ago
Blocks: 12793

Updated

19 years ago
Assignee: troy → kipp

Comment 2

19 years ago
And why is this assigned to me, I've never even heard of -moz-pre-wrap?

Kipp, I'm assuming you know something about this.

Updated

19 years ago
Status: NEW → ASSIGNED
Priority: P3 → P1
Target Milestone: M10

Comment 3

19 years ago
I have a fix sitting in my tree; as soon as it opens.

Updated

19 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED

Comment 4

19 years ago
Fixed. An optimization I had put in speculatively was the culprit (I'd stopped
created un-wanted text-frames for compressible white-space).

Updated

19 years ago
Status: RESOLVED → VERIFIED

Comment 5

19 years ago
With Sept 2nd Build, this problems appears to be fixed.
You need to log in before you can comment on or make changes to this bug.