We have an asp.net 2.0 web application that works fine in Windows Mobile 5 (using mobile IE).
We're trying to get it to work with a new Windows Mobile 6 device (Samsung Epix) and running into a lot of problems. The first issue was that linkbuttons stoppped working entirely. This was solved, or at least work-around, by setting the ClientTarget to
"ie5" or "uplevel".
However, a second problem has now arose; RequiredFieldValidators are causing buttons to fail. As soon as an rfv is added to a control, a javascript error occurs trying to activate the control; "Object expected; source (null)". Nothing seems to help; take
the rfv out (or even change to another validation group) and the control works, add the rfv and the control fails. We're not using any form of custom validation, just 'plain vanilla' required fields.
Now, we could rewrite the application without using the validators, but that would be a lot of work, and I can't help but wonder if there's something else I'm missing here; these are two very 'simple' .Net elements, linkbuttons and rfvs, and neither of them
are working on this device. However, we are seeing no issues using the Windows Mobile 6 emulators. Javascript seems to be working otherwise on the device, but I've heard the js functionality changed between mobile 5 and 6. We've also tried using one of the
mobile ie .browser files to no avail.
I'm not sure I follow, I don't need information on how to redevelop the application; we're certainly able to do that if needed. The problem is that two very basic asp .net controls seem to be nonfunctional in the implementation of IE on this device, which
means that either the javascript is being rendered improperly or the js implementation on the device is somehow crippled or nonfunctional. I suppose this is possible, but I was hoping someone else who has developed web apps for Windows Mobile might have a
solution, or at least an explanation as to why this has suddenly stopped working.... Normally I would try to debug the javascript, but I'm not sure how to do that on a mobile device.
smanchir2
0 Points
2 Posts
Mobile IE javascript issue - required field validator
Apr 09, 2009 08:20 AM|LINK
Hi all,
We have an asp.net 2.0 web application that works fine in Windows Mobile 5 (using mobile IE).
We're trying to get it to work with a new Windows Mobile 6 device (Samsung Epix) and running into a lot of problems. The first issue was that linkbuttons stoppped working entirely. This was solved, or at least work-around, by setting the ClientTarget to "ie5" or "uplevel".
However, a second problem has now arose; RequiredFieldValidators are causing buttons to fail. As soon as an rfv is added to a control, a javascript error occurs trying to activate the control; "Object expected; source (null)". Nothing seems to help; take the rfv out (or even change to another validation group) and the control works, add the rfv and the control fails. We're not using any form of custom validation, just 'plain vanilla' required fields.
Now, we could rewrite the application without using the validators, but that would be a lot of work, and I can't help but wonder if there's something else I'm missing here; these are two very 'simple' .Net elements, linkbuttons and rfvs, and neither of them are working on this device. However, we are seeing no issues using the Windows Mobile 6 emulators. Javascript seems to be working otherwise on the device, but I've heard the js functionality changed between mobile 5 and 6. We've also tried using one of the mobile ie .browser files to no avail.
Any ideas where I can look next for a solution?mobile .net web ie
SKT_01
Participant
1930 Points
435 Posts
Re: Mobile IE javascript issue - required field validator
Apr 10, 2009 06:16 AM|LINK
Hello,
I think you will not get the answer in this forum because such information is only sold by consulting firms and professional developers.
smanchir2
0 Points
2 Posts
Re: Mobile IE javascript issue - required field validator
Apr 10, 2009 05:44 PM|LINK
I'm not sure I follow, I don't need information on how to redevelop the application; we're certainly able to do that if needed. The problem is that two very basic asp .net controls seem to be nonfunctional in the implementation of IE on this device, which means that either the javascript is being rendered improperly or the js implementation on the device is somehow crippled or nonfunctional. I suppose this is possible, but I was hoping someone else who has developed web apps for Windows Mobile might have a solution, or at least an explanation as to why this has suddenly stopped working.... Normally I would try to debug the javascript, but I'm not sure how to do that on a mobile device.