[ https://issues.jboss.org/browse/JBIDE-21815?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-21815 at 3/3/16 2:54 PM: ----------------------------------------------------------------------- [~xcoulon], [~jcantrill], I finally reproduced it with the mock model, and it is very strange use case. So, even if there may be a problem with docker model, there is one in UI too. When I make wizard high enough for 'Environment variables:' and 'Data volumes:' tables to show all entries without scroll, they are updated perfectly. When I make height of wizard so low, that table(s) need scroll, it is not updated until I just pass mouse over it (a magician pass, indeed). I checked that all requests getEnvironmentVariables() and getVolumes() are made before I switch to the second page, that means that during the mouse pass table only updates labels, it already has correct data, but is too lazy too refresh items. was (Author: scabanovich): [~xcoulon], [~jcantrill], I finally reproduced it with the mock model, and it is very strange use case. So, even if there may be a problem with docker model, there is one in UI too. When I make wizard high enough for 'Environment variables:' and 'Data volumes:' tables to show all entries without scroll, they are updated perfectly. When I make height of wizard so low, that table 'Data volumes:' needs scroll, it is not updated until I just pass mouse over it (a magician pass, indeed). That does not happen to table 'Environment variables:' which never has scrolling (is not it a bug by itself, user will not be able to see all variables if they are too many?) I checked that all requests getVolumes() are made before I switch to the second page, that means that during the mouse pass table only updates labels, it already has correct data, but is too lazy too refresh items. -- This message was sent by Atlassian JIRA (v6.4.11#64026)