locked
Issue with updatepanel on iPad Safari browser with claims authentication (SP 2013 site) RRS feed

  • Question

  • We have migrated MOSS 2007 site (which has custom webparts, JavaScripts, AJAXControlToolkit etc.) to SharePoint 2013, which is working fine on IE but when we open newly migrated site on Safari browser on iPad and hit the button present inside update panel, instead executing the code it refreshes the complete page. While existing MOSS 2007 site works as expected on same Safari browser. If Chrome is used on iPad then it works fine.

     

    We have tried following solutions but no success yet

    1. It works fine with classic mode authentication and not claims based application.
    2. Adding JavaScript code to handle webkit-based browsers like Safari but no success.
    3. Making client side AJAX calls using jQuery which returns “undefined” error.

    Any help is appreciated.

    Monday, August 31, 2015 11:29 AM

Answers

  • Hi,

    Is there any custom code in the web part that use Windows identities?

    According to this documentation from MSDN, “Custom code that uses Windows identities might have to be updated. If you have custom code that uses Windows identities, you can use classic-mode authentication until your code is updated and tested”:

    https://technet.microsoft.com/en-us/library/Hh706161%28v=Office.14%29.aspx?f=255&MSPPError=-2147217396

    As a workaround, I would suggest you create a new web part in SharePoint 2013 environment to implement the similar functionalities and keep testing it on Safari browser.

    What’s more, in SharePoint 2013, we got a new developing option: SharePoint App(aka SharePoint Add-in), it supports creating an App using pure JavaScript, which should be easier to implement the asynchronous refresh.

    More information about SharePoint 2013 development:

    https://msdn.microsoft.com/en-us/library/office/jj164084.aspx  

    Thanks                 

    Patrick Liang


    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    • Proposed as answer by Dennis Guo Monday, September 7, 2015 1:17 AM
    • Marked as answer by Dennis Guo Tuesday, September 8, 2015 1:04 AM
    Wednesday, September 2, 2015 5:19 AM

All replies

  • Hi,

    Is there any custom code in the web part that use Windows identities?

    According to this documentation from MSDN, “Custom code that uses Windows identities might have to be updated. If you have custom code that uses Windows identities, you can use classic-mode authentication until your code is updated and tested”:

    https://technet.microsoft.com/en-us/library/Hh706161%28v=Office.14%29.aspx?f=255&MSPPError=-2147217396

    As a workaround, I would suggest you create a new web part in SharePoint 2013 environment to implement the similar functionalities and keep testing it on Safari browser.

    What’s more, in SharePoint 2013, we got a new developing option: SharePoint App(aka SharePoint Add-in), it supports creating an App using pure JavaScript, which should be easier to implement the asynchronous refresh.

    More information about SharePoint 2013 development:

    https://msdn.microsoft.com/en-us/library/office/jj164084.aspx  

    Thanks                 

    Patrick Liang


    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    • Proposed as answer by Dennis Guo Monday, September 7, 2015 1:17 AM
    • Marked as answer by Dennis Guo Tuesday, September 8, 2015 1:04 AM
    Wednesday, September 2, 2015 5:19 AM
  • Dear Patrick,

    Thanks for your reply. I would like to add following to my question:

    We already created another test webpart with updatepanel to just display simple message, which does not contain any custom code using windows identities, but that also didn't work on Safari.

    We can not consider apps or recreating/redesigning the webpart for now because of timeline constraints. 

    Any thoughts to make updatepanel work on Safari with claims based authentication?

    Thanks

    Arpit

    Tuesday, September 15, 2015 10:03 AM