overwolf.windows.onStateChanged.addListener returns 'opened' state

Issue Description:
According to the docs:

window_state_ex can return:
closed
minimized
hidden
normal
maximized

However, it also seems to be returning objects that contain a state of “opened”:

{

app_id: "ghbomnkccchohiipncdmlnopmmogedndpmcoolch"
window_id: "Window_Extension_ghbomnkccchohiipncdmlnopmmogedndpmcoolch_scores"
window_name: "scores"
window_previous_state: "minimized"
window_previous_state_ex: "hidden"
window_state: "normal"
window_state_ex: "normal"

}


{

app_id: "ghbomnkccchohiipncdmlnopmmogedndpmcoolch"
window_id: "Window_Extension_ghbomnkccchohiipncdmlnopmmogedndpmcoolch_scores"
window_name: "scores"
window_previous_state: "closed"
window_previous_state_ex: "closed"
window_state: "opened"
window_state_ex: "opened"

}

Where does it come from, what does it mean, how does it differ, and what to do with these events?

@heartharena please attach your ow logs folder

To see the event being thrown, use the HearthArena 2.0 alpha OPK i placed in Slack #heartharena_channel and go into an arena draft. As soon as the scores show up you will notice:

overwolf.windows.onStateChanged.addListener triggers 2 events, one of which is using the “opened” window_state.

However, considering the “opened” window_state is undocumented and maybe not intended it will be best to just check overwolf internal API to see where the string “opened” is used for window_state.

Thanks, we’ll check if this state should / shouldn’t be sent and release a fix if needed

We revmoved the State ‘Opened’.
Fix will be released in version 0.159 this week.

Thanks.