Muse 2017 Composition Problems

[i-b-tex]

It seems that the 2017 release of Muse has issues with compositions when the exported site is viewed in Chrome. The problem I'm having is that it's causing the wrong triggers to be selected when first loading a page. In the past, whichever trigger was in the back layer would be selected, but now it seems to be totally random. This is only happening to me in Chrome, but it's a big enough issue I've had to revert to the previous version of Muse until it's resolved.

[Preran]

Please report your issue to the support team Contact us | Adobe  and continue using the previous version if everything works fine in it.

Thanks,

Preran

[i-b-tex]

Thanks, I went to the "reporting a bug" link on that page you mentioned, but Muse is not listed as one of the products to report. How can I make sure this reaches the right team?

[Preran]

The link that I shared above was a support link to contact the support team. The wish list form that you speak of isn't updated for Muse. You can use the Ideas section on this forum to post your request.

[i-b-tex]

Well I contacted support, and they told me to post here and ensured me this would reach the correct team. This isn't an "idea" anyway. It's definitely a bug. Anyway, since the people I talked to in support told me the post I placed here was in the right place and would reach the Muse team, I don't understand a reason to now post in yet another place, but I will if that's what you want.

[Anthony_Weller]

I have a very similar problem with Muse 2017 inasmuch that slideshows in Chrome don't start with the first image in the sequence. The problem doesn't occur in Preview and when I switched my default browser from Chrome to MS Edge I don't have the problem in Edge. Is this a bug with Muse or with Chrome?

[i-b-tex]

Definitely sounds like what I'm experiencing in compositions. Edge was one of the browsers I tested on too. Seems like it would have to be a Muse bug rather than Chrome, just because reverting back to the 2015 release fixes it again. Something must have changed in the way it's exporting that Chrome is not liking.

[i-b-tex]

Okay the 2017.0.1 release has fixed this bug. Thanks for the quick update on this!