{"action":"opened","issue":{"url":"https://api.github.com/repos/cuongquay/node-red-contrib-selenium-webdriver/issues/2","repository_url":"https://api.github.com/repos/cuongquay/node-red-contrib-selenium-webdriver","labels_url":"https://api.github.com/repos/cuongquay/node-red-contrib-selenium-webdriver/issues/2/labels{/name}","comments_url":"https://api.github.com/repos/cuongquay/node-red-contrib-selenium-webdriver/issues/2/comments","events_url":"https://api.github.com/repos/cuongquay/node-red-contrib-selenium-webdriver/issues/2/events","html_url":"https://github.com/cuongquay/node-red-contrib-selenium-webdriver/issues/2","id":184636202,"number":2,"title":"click-on and findElement nodes keep locating and render the whole flow inusable ","user":{"login":"mrummuka","id":14860687,"avatar_url":"https://avatars.githubusercontent.com/u/14860687?v=3","gravatar_id":"","url":"https://api.github.com/users/mrummuka","html_url":"https://github.com/mrummuka","followers_url":"https://api.github.com/users/mrummuka/followers","following_url":"https://api.github.com/users/mrummuka/following{/other_user}","gists_url":"https://api.github.com/users/mrummuka/gists{/gist_id}","starred_url":"https://api.github.com/users/mrummuka/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mrummuka/subscriptions","organizations_url":"https://api.github.com/users/mrummuka/orgs","repos_url":"https://api.github.com/users/mrummuka/repos","events_url":"https://api.github.com/users/mrummuka/events{/privacy}","received_events_url":"https://api.github.com/users/mrummuka/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-10-22T15:24:01Z","updated_at":"2016-10-22T15:24:01Z","closed_at":null,"body":"I've experimented a while how the node-red-contrib-selenium-webdriver works using \r\n\r\n> docker run -d -P --name selenium-hub selenium/hub\r\n> docker run -d --name node-chrome --link selenium-hub:hub selenium/node-chrome\r\n> docker run -d -P --name node-red --link selenium-hub:hub cuongquay/node-red-ui-automation\r\n\r\nand got the provided example working after replacing the google button label text to local language.\r\nHowever, when trying to use this for logging in to another site (i.e. setting form values and submitting the form by clicking a button), I get the whole flow to 'hang' very easily by trying different cssSelectors in find object or click on buttons. What happens, is that the flow executes fine until the node in question (click on or find object) executes and turns into \"selecting\" status, and remains there without timeouting.\r\nAlso, redeploying the flow / re-running the flow does not any more  work after this has occurred. \r\n\r\nI suspect that the node-chrome webdriver has crashed or gone into non-recoverable state, or it has simply thrown some error that node-red-contrib-selenium-webdriver is unable to handle.\r\n"}}
{"actor":{"display_login":"mrummuka"}}