[ https://issues.apache.org/jira/browse/IGNITE-7837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Kuznetsov closed IGNITE-7837. ------------------------------------ Not relative any more. > Web console: list-editable new item button behaves incorrectly > -------------------------------------------------------------- > > Key: IGNITE-7837 > URL: https://issues.apache.org/jira/browse/IGNITE-7837 > Project: Ignite > Issue Type: Bug > Components: wizards > Reporter: Ilya Borisov > Assignee: Ilya Borisov > Priority: Minor > > *How to reproduce:* > # Open advanced configuration, domain model editing. > # Open query section, add one alias, click elsewhere. > # Click on added alias to enter edit mode again. > # Click on "Add new alias to query". > > *What happens:* > First alias edit form closes, but new alias is not added. > > *What should happen:* > First alias edit form should close, another (second) alias should be added, > second alias should be in edit mode. > > *Notes:* > I did some research on the issue, the possible cause of the issue lies either > in {{on-focus-out directive}} (used inside {{list-editable}}) or > {{list-editable}} directive, or both. If the {{delete this._cache[idx]}} > expression in {{stopEditView}} method of {{list-editable}} component > controller is wrapped with a {{$timeout(..., 150)}} everything works as > expected, except that 150ms of added delay makes UX perceptibly worse. > > *What to do:* > Investigate the cause of the issue described above and fix the incorrect > behavior, preferably not the way described in notes section. -- This message was sent by Atlassian Jira (v8.3.4#803005)