yes. Something that firefox people has to fix it. On Friday, 19 July 2019 22:17:02 UTC+5:30, Chuck van der Linden wrote: > > > On Sunday, June 16, 2019 at 5:47:51 AM UTC-7, rajagopalan madasami wrote: >> >> Hi Titus, >> >> I have raised this issue in Geckodriver, but I want to ask you whether >> this kind of problem can be resolved from programming level in WATIR >> >> Here is the link >> >> https://github.com/mozilla/geckodriver/issues/1573 >> > > Looks like a geckodriver issue alright, especially if it works fine in > chrome. > > I've sometimes been able to work around this by digging into the code on > the browser side to see if there's a specific event it's looking for and > then firing that event against the element >
-- -- Before posting, please read https://github.com/watir/watir_meta/wiki/Guidelines-for-Posting-to-Watir-General-Google-Group. In short: search before you ask, be nice. [email protected] http://groups.google.com/group/watir-general [email protected] --- You received this message because you are subscribed to the Google Groups "Watir General" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/watir-general/f12584d6-9657-4d40-8770-f230366c6553%40googlegroups.com.
