Having this issue with WebDatePicker (Ultimate UI for ASP.NET 4.5 v20.1)
Behavior is the same in Chrome, Opera, Edge. I see no javascript error in the dev console, at a lost how to fix this.
What is missing for the WebDatePicker to work after navigation postback ?
My only solution so far is to not use the WebDatePicker and roll my own, which is a PITA...
Edit : striked postback mentions, as they did not cause the issue
Hello Francois,
I have created a small sample trying to reproduce the described behavior. I am using WebDatePicker version 20.1. On my side everything works as expected and I am able to open the calendar of the WebDatePicker after postback and navigation to another page. I am testing the sample in Chrome, Internet Explorer, Edge, Opera and Firefox.
Attached you will find my sample for your reference. Please test it on your side and let me know how it behaves. If this is not an accurate demonstration of what you are trying to achieve please feel free to modify it and send it back to me along with steps to reproduce. Alternatively, if the behavior cannot be replicated please feel free to provide your own sample. Remove any external dependencies and code that is not directly related to the issue, zip your application and attach in in this case.
Having a working sample on my side, which I can debug, is going to be very helpful in finding the root cause of this behavior.
Thank you for your cooperation.
Looking forward to hearing from you.
Regards,
Monika Kirkova,
Infragistics
WebDatePicker.zip
Hi Monika,
I have pinpointed the cause of the issue : Server.Transfer.
When using Server.Transfer, the WebDatePicker doesn't work on the new page. When using url navigation, or after a PostBack, the WebDatePicker works as expected.
Is there a way to make the WebDatePicker work with Server.Transfer, or should we use another type of navigation ?
Thank you for your help !
Hello Francois ,
I am glad that you were able to solve your issue.
Thank you for using Infragistics components.
We switched the navigation to use Response.Redirect and the issue is gone, the WebDatePicker popup is now working.
Thanks!
What I could suggest is using “Response.Redirect” for navigation through the pages. By using “Server.Transfer” the url is not being changed, only the content of the target page is being displayed and I assume this is a possible reason for the calendar of the WebDatePicker not to open.
Please let me know if you need any further information regarding this matter.