Should not have to use inputElem.setAttribute("value", inputValue);

NEW
Unassigned

Status

MailNews Core
Composition
16 years ago
9 years ago

People

(Reporter: neil@parkwaycc.co.uk, Unassigned)

Tracking

Trunk
x86
Windows 95
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
Spun off from bug 190153.

A textbox should always have a value property which correctly reflects the
current value. For some reason this isn't working properly, which caused bug
90337. Composer was working around it by using setAttribute, however the
band-aid to bug 90337 broke the workaround, so now Composer is working around it
some more.

Once bug 90337 (or its cause, if it gets spun off) is really fixed these
setAttribute workarounds should become unnecessary and the value property should
be used exclusively.

Comment 1

16 years ago
Anyone (well, Neil?) interested in trying it now without setAttribute?

Updated

15 years ago
Blocks: 108482
Product: MailNews → Core
IIUC bug 108482, this has "baked long enough". What do you think (Neil? Jean-François?)
QA Contact: esther → composition
(Assignee)

Updated

10 years ago
Product: Core → MailNews Core

Updated

9 years ago
Assignee: ducarroz → nobody
You need to log in before you can comment on or make changes to this bug.