ICEfaces
  1. ICEfaces
  2. ICE-10287

mobi:sms in dataTable and ui:repeat fails if using HTML input components

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Minor Minor
          • Resolution: Invalid
          • Affects Version/s: 4.0
          • Fix Version/s: EE-4.0.0.GA
          • Component/s: MOBI-Components
          • Labels:
            None
          • Environment:
            ICEfaces4 trunk rev. 42669
            Safari/ iOS7/ iPhone4S
            Chrome/Android4.4.2/ Galaxy S4 Mini
          • Workaround Exists:
            Yes
          • Workaround Description:
            Workaround is to use ace:textEntry instead of HTML input type="text".

            Description

            QA test app: http://dev.icesoft.com/svn/repo/qa/trunk/Regression-Icefaces4/Sparkle/Manual/sms

            Test page: /smsDataTable.jsf, /smsAceDataTable.jsf, /smsRepeat.jsf

            The sms in h:dataTable or ace:dataTable tests pass only if using ACE components (ace:textEntry) for the message and phone number.
            When using HTML input components (input type "text"), the messages are sent out properly only from first table row.
            When sending sms from any other row, the phone and message values from the first row are being sent.


            Steps:
            - go to /smsDataTable.jsf (or /smsAceDataTable.jsf, or /smsRepeat.jsf), scroll down to the table using HTML input components.
            - enter phone number1, message1, click SMS in first row (row1) -> redirection to messaging app, message sent/received.
            - in second row (row2), enter phone number2, message2, click SMS -> redirection to messaging app, however values displayed are the previous ones: phone number1, message1.
            If removing the typed values from row1, and typing values in row2, click SMS in row2 -> there is no redirection to bridgeIt/ messaging application.

              Activity

              Ascending order - Click to sort in descending order
              Carmen Cristurean created issue -
              Carmen Cristurean made changes -
              Field Original Value New Value
              Fix Version/s 4.0 [ 11382 ]
              Carmen Cristurean made changes -
              Description QA test app: http://dev.icesoft.com/svn/repo/qa/trunk/Regression-Icefaces4/Sparkle/Manual/sms

              Test page: /smsDataTable.jsf

              The sms in h:dataTable test passes only if using ACE components (ace:textEntry) for the message and phone number.
              When using HTML input components (input type "text"), the messages are being sent and received, however the first values that have been entered are always rendered when being redirected to the messaging app, and user must re-type these values each time.

              Steps:
              - enter phone number1, message1, click SMS in any table row -> redirection to messaging app, message sent/received.
              - in another table row, enter phone number2, message2, click SMS -> redirection to messaging app, however values displayed are the previous ones: phone number1, message1.
              		QA test app: http://dev.icesoft.com/svn/repo/qa/trunk/Regression-Icefaces4/Sparkle/Manual/sms

              Test page: /smsDataTable.jsf

              The sms in h:dataTable test passes only if using ACE components (ace:textEntry) for the message and phone number.
              When using HTML input components (input type "text"), the messages are being sent and received, however the first values that have been entered are always rendered when being redirected to the messaging app, and user must re-type these values each time.

              Steps:
              - go to /smsDataTable.jsf, scroll down to the table using HTML input components.
              - enter phone number1, message1, click SMS in any table row -> redirection to messaging app, message sent/received.
              - in another table row, enter phone number2, message2, click SMS -> redirection to messaging app, however values displayed are the previous ones: phone number1, message1.
              Ken Fyten made changes -
              Workaround Description Workaround is to use ace:dataTable instead of h:dataTable.
              Assignee Arturo Zambrano [ artzambrano ]
              Security Private [ 10001 ]
              Fix Version/s EE-4.0.0.GA [ 11171 ]
              Fix Version/s 4.0 [ 11382 ]
              Priority Major [ 3 ] Minor [ 4 ]
              Workaround Exists Yes [ 10007 ]
              Carmen Cristurean made changes -
              Workaround Description Workaround is to use ace:dataTable instead of h:dataTable. Workaround is to use ace:textEntry instead of HTML input type="text".
              Carmen Cristurean made changes -
              Description QA test app: http://dev.icesoft.com/svn/repo/qa/trunk/Regression-Icefaces4/Sparkle/Manual/sms

              Test page: /smsDataTable.jsf

              The sms in h:dataTable test passes only if using ACE components (ace:textEntry) for the message and phone number.
              When using HTML input components (input type "text"), the messages are being sent and received, however the first values that have been entered are always rendered when being redirected to the messaging app, and user must re-type these values each time.

              Steps:
              - go to /smsDataTable.jsf, scroll down to the table using HTML input components.
              - enter phone number1, message1, click SMS in any table row -> redirection to messaging app, message sent/received.
              - in another table row, enter phone number2, message2, click SMS -> redirection to messaging app, however values displayed are the previous ones: phone number1, message1.
              		QA test app: http://dev.icesoft.com/svn/repo/qa/trunk/Regression-Icefaces4/Sparkle/Manual/sms

              Test page: /smsDataTable.jsf, /smsAceDataTable.jsf

              The sms in h:dataTable or ace:dataTable tests pass only if using ACE components (ace:textEntry) for the message and phone number.
              When using HTML input components (input type "text"), the messages are being sent and received, however the first values that have been entered are always rendered when being redirected to the messaging app, and user must re-type these values each time.

              Steps:
              - go to /smsDataTable.jsf (or /smsAceDataTable.jsf), scroll down to the table using HTML input components.
              - enter phone number1, message1, click SMS in any table row -> redirection to messaging app, message sent/received.
              - in another table row, enter phone number2, message2, click SMS -> redirection to messaging app, however values displayed are the previous ones: phone number1, message1.
              Carmen Cristurean made changes -
              Summary mobi:sms in h:dataTable fails if using HTML input components mobi:sms in dataTable fails if using HTML input components
              Carmen Cristurean made changes -
              Description QA test app: http://dev.icesoft.com/svn/repo/qa/trunk/Regression-Icefaces4/Sparkle/Manual/sms

              Test page: /smsDataTable.jsf, /smsAceDataTable.jsf

              The sms in h:dataTable or ace:dataTable tests pass only if using ACE components (ace:textEntry) for the message and phone number.
              When using HTML input components (input type "text"), the messages are being sent and received, however the first values that have been entered are always rendered when being redirected to the messaging app, and user must re-type these values each time.

              Steps:
              - go to /smsDataTable.jsf (or /smsAceDataTable.jsf), scroll down to the table using HTML input components.
              - enter phone number1, message1, click SMS in any table row -> redirection to messaging app, message sent/received.
              - in another table row, enter phone number2, message2, click SMS -> redirection to messaging app, however values displayed are the previous ones: phone number1, message1.
              		QA test app: http://dev.icesoft.com/svn/repo/qa/trunk/Regression-Icefaces4/Sparkle/Manual/sms

              Test page: /smsDataTable.jsf, /smsAceDataTable.jsf, /smsRepeat.jsf

              The sms in h:dataTable or ace:dataTable tests pass only if using ACE components (ace:textEntry) for the message and phone number.
              When using HTML input components (input type "text"), the messages are sent out properly only from first table row.
              When sending sms from any other row, the phone and message values from the first row are being sent.


              Steps:
              - go to /smsDataTable.jsf (or /smsAceDataTable.jsf, or /smsRepeat.jsf), scroll down to the table using HTML input components.
              - enter phone number1, message1, click SMS in first row (row1) -> redirection to messaging app, message sent/received.
              - in second row (row2), enter phone number2, message2, click SMS -> redirection to messaging app, however values displayed are the previous ones: phone number1, message1.
              If removing the typed values from row1, and typing values in row2, click SMS in row2 -> there is no redirection to bridgeIt/ messaging application.
              Carmen Cristurean made changes -
              Summary mobi:sms in dataTable fails if using HTML input components mobi:sms in dataTable and ui:repeat fails if using HTML input components
              Carmen Cristurean made changes -
              Assignee Arturo Zambrano [ artzambrano ] Carmen Cristurean [ ccristurean ]
              Hide
              Permalink
              Carmen Cristurean added a comment -

              Marking this as 'invalid', after finding issues in the QA test app.
              Updated test application, changes have been checked in at rev. 39540.

              Show
              Carmen Cristurean added a comment - Marking this as 'invalid', after finding issues in the QA test app. Updated test application, changes have been checked in at rev. 39540.
              Carmen Cristurean made changes -
              Status Open [ 1 ] Resolved [ 5 ]
              Resolution Invalid [ 6 ]
              Ken Fyten made changes -
              Status Resolved [ 5 ] Closed [ 6 ]

                People

                • Assignee:
                  Carmen Cristurean
                  Reporter:
                  Carmen Cristurean
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: