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.
Anyone (well, Neil?) interested in trying it now without setAttribute?
IIUC bug 108482, this has "baked long enough". What do you think (Neil? Jean-François?)
QA Contact: esther → composition
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.