[
https://issues.apache.org/jira/browse/CB-13242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16161391#comment-16161391
]
Joe Bowser edited comment on CB-13242 at 9/11/17 2:54 PM:
----------------------------------------------------------
This is a browser/device issue and isn't something handled by Cordova itself.
Cordova depends on the WebView that the device uses to actually display the
content, which is why there's different results on the Emulator than on the
device. I'd recommend trying to upgrade your WebView or working around this
issue. This could also be a SAP UI5 issue, since it's a JS validation error.
One of the advantages of using Cordova is that you can serve your www directory
and navigate to it using Google Chrome on your device and see if it works with
the Chrome installed on your device to make sure the non-Cordova parts (i.e.
things like CSS and JS form validation) actually work. This speeds up the
development cycle of having to compile everything all the time, and makes it so
you only have to do the compilation dev step at the very end.
Unfortunately, we can't do anything when it comes to these weird browser
issues, since they are browser issues with how the WebView presents the data.
was (Author: bowserj):
This is a browser/device issue and isn't something handled by Cordova itself.
Cordova depends on the WebView that the device uses to actually display the
content, which is why there's different results on the Emulator than on the
device. I'd recommend trying to upgrade your WebView or working around this
issue. This could also be a SAP UI5 issue, since it's a JS validation error.
One of the advantages of using Cordova is that you can serve your www directory
and navigate to it using Google Chrome on your device and see if it works with
the Chrome installed on your device to make sure the non-Cordova parts (i.e.
things like CSS and JS form validation) actually work. This speeds up the
development cycle of having to compile everything all the time, and makes it so
you only have to do the compilation dev step at the very end.
> SAP UI5 sap.m.Input maxLength issue
> -----------------------------------
>
> Key: CB-13242
> URL: https://issues.apache.org/jira/browse/CB-13242
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
> Affects Versions: 6.3.1
> Environment: Visual Studio Enterprise 2017
> Visual Studio Tools for Apache Cordova 15.113.6201.1
> Toolset Name Cordova 6.3.1
> Cordova-android 5.2.1
> OpenUI5 Distribution: "version": "1.46.7" buildTimestamp: "201705020902"
> Reporter: martin Cooper
> Assignee: Joe Bowser
> Priority: Minor
> Labels: UI5
>
> I have created a hello world UI5 app using a sap.m.input as below:
> var myinput1 = new sap.m.Input("myinput_1", {maxLength: 10});
> My hello world app works fine on a desktop, but when I use Cordova to compile
> it for android, maxlength does not work properly - you can type as many
> characters as you like so long as you don’t enter a space. Once you have
> entered more than maxLength characters, if you enter a space, the string is
> truncated to maxLength.
> The desktop version of the app is available here:
> http://jsfiddle.net/dn5c3z6j/
> As a workaround I have added a liveChange event to all my sap.m.Input
> controls as follows:
> var myinput1 = new sap.m.Input("myinput_1", {liveChange: function (event) {
> setmaxLength(10, event) }, maxLength: 10});
> function setmaxLength(len, event) {
> if (event.mParameters.value.length > len) {
> event.oSource.setValue();//for some reason the value needs to be
> cleared before it can be changed
> event.oSource.setValue(event.getParameters().value);
> }
> }
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
