In the last couple of months we received questions from several customer regarding the JavaScript mutation events deprecation/removal from Chrome and Edge Browsers as discussed in the following articles:
- Mutation events will be removed from Chrome.
- Site compatibility-impacting changes coming to Microsoft Edge
Symptoms:
Users of SharePoint might have noticed a warning similar to the following in the Console of affected browsers:
Resolution:
The issue itself does not impact any product functionality.
A fix for SharePoint Server Subscription Edition is currently in the works. I will update this blog post when a fix is available.
Be aware that there is no currently no plan to release a fix for this issue for SharePoint Server 2016 and SharePoint Server 2019 as these products are in extended support and this issue doesn’t block the product functionality.
Permalink
Will this change also affect Microsoft Edge?
Permalink
Hi Matthias,
yes as Edge is based on Chromium. See here for details on Edge:
https://learn.microsoft.com/en-us/microsoft-edge/web-platform/site-impacting-changes?tabs=latest
I have updated the post to clarify this.
Cheers,
Stefan
Permalink
Hi,
if “this issue doesn’t block the product functionality.” do you have an example what won’t work in the future?
Or does this just affect own Solutions.
Kind Regards
Christoph
Permalink
Hi Christoph,
sorry – I do not have any such details.
But you can evaluate the impact on your specific sites using the beta version of Chrome which already has the mutation events disabled:
https://developer.chrome.com/blog/chrome-127-beta
Cheers,
Stefan
Permalink
Dear Stefan,
CU July 2024 for SharePoint SE had been installed but warning about deprecation is still present in chromium based browsers. How is it so ?
Is firefox affected too ?
thank you
Permalink
Hello Stefan,
A large number of our customers are reporting this issue now occurring in SP2019 on prem version.
Despite saying that this will not affect productivity, this is having an impact on our SharePoint sites.
Do you know if a fix for this will be issued forthwith
Permalink
Hi Scott,
there is currently no plan to release a fix for SP2016 and SP2019 as there should NOT be any productivity impact.
If there IS an impact it is important to identify if this occurs due to a problem with SharePoint itself or a 3rd party feature/software/customization installed – which might itself be affected by the issue.
If the issue occurs with pure SharePoint and affects productivity ensure to open a support case with Microsoft to get this analyzed and the decision not to release a fix for SP2016/2019 reevaluated.
Cheers,
Stefan
Permalink
Further to my last comment, by changing the library to open in Classic mode, this appears to resolve the issue.
However, this requires each customer to navigate to the settings.aspx page, and changing the settings, which as you can imagine is not a practical solution
Permalink
Hi Stefan,
I’ve noticed these warning messages are being flagged from a msquery.js file and I have no idea what it is and what it does. I assume it is a SharePoint specific file rather than a custom one but should we be changing this file on SharePoint 2016?
Kind Regards,
Chris
Permalink
Hi Chris,
yes this is from SharePoint. You don’t have to do anything.
As soon as the mutation events are no longer in the browser the javascript code will detect this and use an alternate execution path which does not require mutation events.
Cheers,
Stefan