[
https://issues.apache.org/jira/browse/XAP-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Mikhaylov updated XAP-517:
----------------------------------
Attachment: PluginDocumentHandler.js
TextAreaBridge.js
mcoJS.js
I have come up with the fix but that requires a change not only in
TextAreaBridge but also in PluginDocumentHandler. There is also a small change
in mcoJS:
mcoJS.prototype.setText2 = function(element, event) {
element.removeChild(element.firstChild);
var textNode = element.ownerDocument.createTextNode("another\nnew
text");
element.appendChild(textNode);
};
> Widgets: TextArea: TextArea value cannot really be changed without "text"
> attribute
> -----------------------------------------------------------------------------------
>
> Key: XAP-517
> URL: https://issues.apache.org/jira/browse/XAP-517
> Project: XAP
> Issue Type: Bug
> Components: Widgets: TextField / TextArea / PasswordField
> Reporter: Trevor Oldak
> Attachments: mcoJS.js, mcoJS.js, PluginDocumentHandler.js,
> TextAreaBridge.js, textAreaTest.xal
>
>
> Open the attached example.
> The textarea has the following XAL:
> <textArea id="myTextArea">foo</textArea>
> 1) Click "Read textValue' null is returned.
> 2) Click "Read nodeValue. 'foo' is returned.
> 3) Click 'Set nodeValue' - The text does not change. It should.
> 4) Click 'Read nodeValue'. - The correct nodeValue is output
> 5) Click 'Read textValue' - null is still printed.
> 6) Set the textValue. The value changes, even though the text attribute has
> been technically removed.
> 7) Read textValue. This outputs the correct value, which is fine since we
> accept non-schema attributes.
> 8) Read nodeValue. This is now wrong.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
