Hope you solve this issue asap. 

All sites using the standard accordion menu stopped working properly. 

Seems to be something about how chrome interpret javascript. 

I'm able to reproduce this issue on M-55
Good Build is 55.0.2875.4
Bad Build is 55.0.2876.0
Bisect Range 
https://chromium.googlesource.com/chromium/src/+log/55.0.2875.0..55.0.2876.0?pretty=fuller&n=10000

Bisect script pointed to https://chromium.googlesource.com/chromium/src/+/902a3d6303dfbfd49a24173777afcb4b70234a17

These pages are broken on Windows 10 Mobile on Edge. It appears to be handling the pointerdown and mousedown events.

Really the pointerdown event listener should probably be calling preventDefault?

Do we know what the global usage of Adobe Muse is? Seems relatively easily fixable on Adobe's end.

There is also an issue with double pointerdown handling, once in jquery-1.8.3.min.js then again on whatinput.js.

Adobe is aware of the issue here:

https://forums.adobe.com/message/9205015#9205015

Confirmed that this is caused by Muse code not preventDefaulting on pointerdown. As a quick test, if a capturing pointerdown listerner at window calls preventDefault, the problem seems to go away:

window.addEventListener("pointerdown", function(e) { if (e.type=="pointerdown") e.preventDefault(); }, true);

Hi, 

menu working fine again with the javascript line of mustaq in the head

 <script type="text/javascript">
//Fix collapse accordion issue chrome update 
 window.addEventListener("pointerdown", function(e) { if (e.type=="pointerdown") e.preventDefault(); }, true);
 </script>

Thanks !!!

Now trying to solve simmilar issue with the standard form in muse.

Please note that my code in #c9 is a hack to prove what's wrong. We are in touch with Adobe Muse team about it.

The correct solution is to call e.preventDefault() in the pointerdown listeners in your site, as mentioned in #c6 above.

Hi again, 

people using Muse are not generating any kind of javascript code. All the code is generated by the Adobe Muse application. Modify the original code is not a solution for much people. 

My only purpose was to give a fast "solution/hack" for those people that see that suddenly their site has stop working correctly. 

I understand that Adobe has to fix his widgets to use proper javascript code. 

Thanks again for your help.

Issue 676390 has been merged into this issue.

@mustaq

You just saved my life man! This bit of code fixes the issue perfectly and it's easy to use. Absolutely brillant! Thank you sooooo much!!! :)

External dependencies don't need to block the release.

FWIW Adobe has provided a temporary fix @ https://forums.adobe.com/message/9244926#9244926 and stated they're working on an update to entirely address the issue.  Should we close this?

Yes, thanks for noting the muse fix.

 Issue 715703  has been merged into this issue.

 Issue 694357  has been merged into this issue.

 Issue 675469  has been merged into this issue.