Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

Шукати в статтях підтримки

Остерігайтеся нападів зловмисників. Mozilla ніколи не просить вас зателефонувати, надіслати номер телефону у повідомленні або поділитися з кимось особистими даними. Будь ласка, повідомте про підозрілі дії за допомогою меню “Повідомити про зловживання”

Докладніше

Ця тема перенесена в архів. Якщо вам потрібна допомога, запитайте.

Understanding the working principle behind the recorder in Selenium IDE

  • 1 відповідь
  • 2 мають цю проблему
  • 3 перегляди
  • Остання відповідь від the-edmeister

more options

We are working on development of a framework on top of Selenium. We want to expose a tool so that users can record actions on the browser. For this, we want to understand how Selenium IDE is able to get information from the controls being recorded.

We feel Selenium IDE is able to record by getting information about the controls by subscribing to the events raised by the firefox browser. Is our understand correct? If not, then we would like to the approach being used to the information from the control.

Any help is highly appreciated.

We are working on development of a framework on top of Selenium. We want to expose a tool so that users can record actions on the browser. For this, we want to understand how Selenium IDE is able to get information from the controls being recorded. We feel Selenium IDE is able to record by getting information about the controls by subscribing to the events raised by the firefox browser. Is our understand correct? If not, then we would like to the approach being used to the information from the control. Any help is highly appreciated.

Усі відповіді (1)