Erwin Dondorp

note: changes will be on branch `highstate-envs`. note: during build of this feature, I realized that there are several occasions where structured data is read back from the session storage....

@pju51: the configuration parameters have a slightly different name now: `saltgui_show_saltenvs` or `saltgui_hide_saltenvs` to prevent any confusion with pillar-envs; and to indicate that the parameter can take a list of...

@pju51 Can you please give the new HighState page in this branch a try? I guess that this solution should be extended to the "Issues" page. That page tries to...

You are using the correct branch. Even when the behaviour is broken, you should see the new setting on the (hidden) Options page. just in case this is an effect...

I did push out all changes, so that was not the problem. So I'm hoping that the SHIFT-refresh (or even the normal refresh) fixes the issue...

> after a redeployment of saltgui and a refresh of the hidden page, I have the new settings great! > also another problem, when I use your branch, I lose...

> can you take a look at the webbrower console for this one, to spot for any errors? never mind, I already reproduced it here

the problem was in the code that I cleaned up in relation to this issue, that is fixed now.

>  there is something really strange in this screenprint. `pillarenv` and `saltenv` are not specified as named parameters, you seem to be passing a string with the literal value...

note that as part of the solution, a decision had to be made on jobs that do not have a `saltenv=` parameter. these jobs are always displayed, no matter what...