You are viewing a plain text version of this content. The canonical link for it is here.
Posted to xap-dev@incubator.apache.org by "Trevor Oldak (JIRA)" <xa...@incubator.apache.org> on 2007/10/05 17:00:59 UTC

[jira] Created: (XAP-517) Widgets: TextArea: TextArea value cannot really be changed without "text" attribute

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


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.


[jira] Commented: (XAP-517) Widgets: TextArea: TextArea value cannot really be changed without "text" attribute

Posted by "Trevor Oldak (JIRA)" <xa...@incubator.apache.org>.
    [ https://issues.apache.org/jira/browse/XAP-517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542841 ] 

Trevor Oldak commented on XAP-517:
----------------------------------

correct.

> 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, 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.


[jira] Updated: (XAP-517) Widgets: TextArea: TextArea value cannot really be changed without "text" attribute

Posted by "Trevor Oldak (JIRA)" <xa...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/XAP-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Trevor Oldak updated XAP-517:
-----------------------------

    Attachment: mcoJS.js

> 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, 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.


[jira] Updated: (XAP-517) Widgets: TextArea: TextArea value cannot really be changed without "text" attribute

Posted by "Trevor Oldak (JIRA)" <xa...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/XAP-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Trevor Oldak updated XAP-517:
-----------------------------

    Priority: Critical  (was: Major)

> 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
>            Priority: Critical
>         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.


[jira] Updated: (XAP-517) Widgets: TextArea: TextArea value cannot really be changed without "text" attribute

Posted by "Michael Mikhaylov (JIRA)" <xa...@incubator.apache.org>.
     [ 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.


[jira] Updated: (XAP-517) Widgets: TextArea: TextArea value cannot really be changed without "text" attribute

Posted by "Trevor Oldak (JIRA)" <xa...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/XAP-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Trevor Oldak updated XAP-517:
-----------------------------

    Attachment: textAreaTest.xal

> 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, 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.


[jira] Commented: (XAP-517) Widgets: TextArea: TextArea value cannot really be changed without "text" attribute

Posted by "Michael Mikhaylov (JIRA)" <xa...@incubator.apache.org>.
    [ https://issues.apache.org/jira/browse/XAP-517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542838 ] 

Michael Mikhaylov commented on XAP-517:
---------------------------------------

My understanding is that adding, removing or changing value of "text" attribute should have NO effect on TextArea. Correct?

> 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, 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.