Funkcionalnosć toś togo sedła se pśez wótwardowańske źěła wobgranicujo, kótarež maju wašo dožywjenje pólěpšyś. Jolic nastawk waš problem njerozwězujo a cośo pšašanje stajiś, wobrośćo se na našo zgromoźeństwo pomocy, kótarež na to caka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomagaś.

Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Dalšne informacije

Understanding the working principle behind the recorder in Selenium IDE

  • 1 wótegrono
  • 2 matej toś ten problem
  • 9 naglědow
  • Slědne wótegrono wót 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.

Wšykne wótegrona (1)

more options