18 January 2026:


This forum is now archived and is in read-only mode. Please continue discussions on our improved new Sahi Pro Community forum.



Sahi Pro is an enterprise grade test automation platform which can automate web, mobile, API, windows and java based applications and SAP.

_setSelected not triggering onChange action in IE

dasspunkdasspunk Members
edited April 2011 in Sahi - Open Source
_setSelect is failing to trigger the blur action on a select in IE (does NOT occur in Chrome). I finally found a workaround and wondered if there's a more elegant solution. Seems that I need to focus on the select, select a value, blur and then click on the select object to kind of nudge it... eg. just the _setSelect doesn't work but this does:

_focus(_select(1));
_setSelected(_select(1), "18");
_blur(_select(1));
_click(_select(1));

Anyone have a suggestion for a better way to handle it?

Thanks,
Brian

Comments

  • narayannarayan Administrators
    Hi Brian,

    We will look deeper into this. Which IE version is this?

    Regards,
    Narayan
  • dasspunkdasspunk Members
    Hi Narayan,

    I'm running IE 8.0.7600.16385. I'm actually not sure what we're using to do the auto select (which is likely onChange and not blur). This is in one of our production apps and works manually on all browsers and Sahi works on all browsers NOT IE (sigh). Sahi also works fine on a straight up onChange in IE like below so I'm not sure where the problem is.


    <html>
    <head>
    <title>Option test...</title>
    </head>
    <body>
    <select onChange='alert("Thanks")'>
    <option value="1">One</option>
    <option value="2">Two</option>
    <option value="3">Three</option>
    </select>
    </body>
    </html>

    Thanks for the help sir,
    Brian
  • PachatPachat Members
    edited November 2011
    Hi,

    Has this been solved ?

    For I have the same problem : onchange is not fired on a select under IE (8), but is correctly fired under FF.

    Any workaround ?
  • dasspunkdasspunk Members
    I'm still waiting for one... perhaps this is just a bug?
Sign In or Register to comment.