Hi, we have a customer who is wanting to use the Browser Form functionality of their Office 365 instance. They have built one or two simpler forms themselves and then asked us to create a Customer Complaint Management / Issues / Problems system for them using InfoPath-based browser forms. We created the form as browser-enabled and firstly built it to work in their test SharePoint Online site. We used InfoPath 2013 and did all the standard data connection stuff, then once we were happy and knew it to be 95% built switched into their live site to do the final changes and extras etc.
All works OK with the logic of the form and they are happy with different people taking responsibility etc. The form has only a couple of different Views (one for the base 'problem' or 'complaint' and a second for a supporting document. There is a reasonable level of logic in the form with probably 7 status etc.
It works well and in testing, the users and project manager were happy until one tester was 'sent' the form to complete their bit and was asked to select a date by which a step should be completed. At that point they clicked on the datepicker icon, and the form skipped up to the top of the page! We each tested this as it was an odd glitch. (note - the form didn't close or shut down, just move position).
We discovered that any version of IE worked with no problem at all whereas current versions of Chrome and FireFox (as of April 2017) both had the problem. We have added date fields at a number of points on the form, and it didn't matter which of these we tested, if you clicked the datepicker it caused the form to just move right up to the top/start.
I do remember a long time ago with non-IE browsers there was an issue with post-backs causing a form to move around when you went from field to field, and also there being a trick we had to employ around the heights of fields, but nothing as major as this. In the past I believe we have used a full range of browsers with limited problems.
Has anyone come across this problem before and if so, is there a way we can either minimise this or remove it altogether? Any help will be gratefully received.
Regards Alan C.