I have seen this happen too and I think that it may only have been with Private scores. Had it again today with a private score but worked after I made the score public.
I'd rather believe this to be a plain musescore.com issue, that page comes directly from there, so a fix is probably completely independent from the MuseScore program and version. Also it is not a 3.5.1 regression and not even a 3.5.0 regression, it is much older IIRC
FWIW, I started noticing the problem maybe a month ago, I've forgotten the details, but I do remember thinking it did not seem connected with a particular update. So my memory and @Jojo-Schmitz's logic both point to it being a musescore.com issue rather than a MuseScore issue per see - except for the stray QtWebEngine process that apparently results.
I can reproduce it with MuseScore 3.3.4 (Windows 10, the Microsoft Store version).
It it had been the case ever since 3.3, it had been reported much earlier, yet another hint at some issue on musescore.com, it got to have worked at a time.
Comments
I have seen this happen too and I think that it may only have been with Private scores. Had it again today with a private score but worked after I made the score public.
Confirmed
Workaround is to change those settings directly on musescore.com
Relates to #311174: [EPIC] UI/UX issues and suggestions
Confirmed.
I would argue that this ought to be fixed for 3.5.2.
I'd rather believe this to be a plain musescore.com issue, that page comes directly from there, so a fix is probably completely independent from the MuseScore program and version. Also it is not a 3.5.1 regression and not even a 3.5.0 regression, it is much older IIRC
I really wonder why we don't get more such reports?
I wasn't sure if the problem was with the software or .com, but it's a good question.
For example, I think it worked in 3.4.2 (I've only just upgraded to 3.5.1), but I might be wrong.
Nope, same issue in 3.4.1 but not in 3.2.3, which doesn't use that new dialog. Don't have a 3.3 to test
Got to be 3.3, which is when this method got introduced, see https://musescore.org/en/handbook/developers-handbook/release-notes/rel…
When it broke on musescore.com is the other question...
Would you consider adding it to the lssues page on GitHub until we know for sure where the problem lies?
Added to https://github.com/musescore/MuseScore/issues/6505
Mentioned it in the developers' chat on Telegram too
This leaves behind a stray QtWebEngineProcess, which in turn leads to problems later, like #311727: Can't save a score online, brings up empty dialog, but also potentially to problems with online updating to a later MuseScore version and crashes after that, like #275837: MuseScore crashes during start-up while displaying "Start center"
Workaround for that is to kill it via Task Manager.
FWIW, I started noticing the problem maybe a month ago, I've forgotten the details, but I do remember thinking it did not seem connected with a particular update. So my memory and @Jojo-Schmitz's logic both point to it being a musescore.com issue rather than a MuseScore issue per see - except for the stray QtWebEngine process that apparently results.
maybe a month ago exactly matches the age of this issue too ;-)
I can reproduce it with MuseScore 3.3.4 (Windows 10, the Microsoft Store version).
It it had been the case ever since 3.3, it had been reported much earlier, yet another hint at some issue on musescore.com, it got to have worked at a time.
Seems to no longer happen, of can aynone reproduce it now?
Hasn't happened to me in some time, but I never understood the exact steps to reproduce.
I can't reproduce in 3.6.1.
I think stuff pertaining to ensemble etc has been removed; maybe that was the issue?
Let's mark it fixed then
Automatically closed -- issue fixed for 2 weeks with no activity.