My browser here is pretty fixated on the history, and due to some
unknown reason I got a history fragment string like:
`#v1:=0:=18:=4:::::::` so the "hashes" got into strings, and I was
not able to move them back.
Adding a match here to always try reverse-mapping the hash to the
original input helps to fix that here.
We'd only run into issues if we'd use a integer-string as id, but we
really don't (IIRC not even allowed in extjs) so this is safe to do.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
eslint complains about the window.confirm call, and neither I nor
some other colleagues here did see that dialogue ever in practice.
The confirm here does not adds any real value, as all other back
navigation are unprotected, but have similar potential in loosing
state.
One can always navigate forward via their user agent and for console
(noVNC, xterm.js) we have now a separate check.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
this way, we can control if we want to fire the 'statechanged' event
when we set a value in the stateprovider
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
to show the number in the url fragment instead of 'replication'
also change the itemid in the datacenter to 'replication' from 'replica'
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
use new tree functionality of configpanel
move options,network,dns,console under resources (now system)
move firewall subpanels into tree
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
