This appears to be an issue with how the MVF1 GraphQL API handles things, although technically a work-around solution is possible. As all the user needs to do to fix this is to click the button to toggle always-on-top status, it doesn't seem worth the effort to fix it at the moment.
This appears to be an issue with how the MVF1 GraphQL API handles things, although technically a work-around solution is possible. As all the user needs to do to fix this is to click the button to toggle always-on-top status, it doesn't seem worth the effort to fix it at the moment.