SeleniumHQ / selenium-ide

Open Source record and playback test automation for the web.
https://selenium.dev/selenium-ide/
Apache License 2.0
2.81k stars 765 forks source link

Selenium IDE freezing on specific element in Django+Angular #1187

Open bonezinger opened 3 years ago

bonezinger commented 3 years ago

🐛 Bug Report

This is probably related to issue 717. Whenever I click a specific field while recording with Selenium IDE, the browser page freezes. Someone in there mentioned something about how Selenium finds the elements, so I tried giving it a name attribute, but the problem persisted. I've tried it both with Chromium and Firefox, in both cases the problem happened.

The application uses Django + Angular.js

To Reproduce

I am not 100% where the problem lies, but this is what the field looks like in the components/DateAction.js

<DatePicker
                  name={this.date} //this is only to ensure it has a unique name
                  format='DD/MM/YYYY'
                  disabledDate={this.disabledDate}
                  onChange={this.handleChange}
                  size={'small'}
                  style={{ width: '150px' }}
                  allowClear={false}
                  showToday={false}
                  value={this.date}
                />

And this is what the field looks like when inspecting it from the browser. <input readonly="" placeholder="Selecionar data" class="ant-calendar-picker-input ant-input ant-input-sm" name="1611889200000" value="29/01/2021">

Steps to reproduce the behavior: Start recording with selenium, click on the aforementioned element.

Expected behavior

Selenium records the click on the element instead of freezing.

Environment

OS: Ubuntu 20.04 Selenium IDE Version: 3.17.0 Selenium SIDE Runner Version: n/a Browser: Firefox 84 64-bit, Chromium 88 64-bit

bonezinger commented 3 years ago

An addendum, I've just tried using the "select target" button from the Selenium IDE. Clicking on that element froze the page (not the browser window), simply hovering over it did not, and Selenium was still fully responsive. I tried going back to the base address (localhost:3000) and even that was slow.