when the popup blocker is active, nw is undefined and nw.focus() throws
an error and the touchend event is not finished, causing
extjs to retry the touchevent and click handler, which tries to open
a popup which gets blocked here, and so on
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
and change to a better code formatting of the properties
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
we sometimes want/need to do something when the api call
finished and need to know whether it was successful or need the result
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
we did only check if the first field of a mulitfield key is being deleted,
resulting in showing no pending change at all when deleting any other,
and as long as only deletions were taking place
also when deleting the 'main' key of a multikey field, we
showed the deletion of the whole line, even when already showing
a different pending line
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
we do not want to focus on hidden/disabled fields,
because that focus gets lost and prevents some things
e.g. cancelling with ESC
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
with this, you can now put items in the
advancedColumn1/2/B and show/hide it with
setAdvancedVisible
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
the combination of firefox, touchscreen, mouse input and extjs
prevents normal click/touch input for buttons, lists, etc.
the workaround on firefox was to set
dom.w3c_touch_events.enabled
to 0 (in about:config)
or to upgrade to extjs >= 6.5.1 (of which there is no gpl release as of now)
so we introduce that workaround as it seems to not disrupt 'normal'
browsers and non-touchscreen devices
we then still have an issue with scrolling though, since extjs
now expects the user to drag the content instead of using the wheel
but it is still better than a completely non working interface
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
let our users decide if the want to show a TaskProgress window or a
TaskViewer window, so that they do not always must create the Viewer
their self
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
this should not be here, rather where we include the language files
(like in pve), because this is not ecma conform and behaves very
different in different browsers (e.g. safari ignores the if check
completely and simply uses that function definition)
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
if we use a component with cbind in a static declaration,
we do not want to traverse the 'config' property, as this can lead
to properties of base classes which produce errors on copying
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
we renamed them in the helpButton, we also have to rename them here
this prevented the help button to show up in the vm/ct creation wizard
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
Reviewed-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
allow to access sub elements of configuration items for binding.
E.g., if the following configuration is present:
foo: {
bar: true
}
one could do:
xtype: 'displayfield',
cbind {
value: '{foo.bar}'
}
[...]
This mirrors the abillity of ExtJS's 'bind', which can do this also.
Simple implementation mirroring the surrounding code.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
