We've fixed one issue that we saw lead to a crash in our locator code while working with your example. The fix has been applied to SmartClient 11.0p and newer branches, and will be in the nightly builds dated 2-8-2017 and beyond. We didn't see any issue generating and using a locator to the "Login" button in FF45 ESR in WIndows 10 using your example with that fix in place, so please try to install the patched release and see if it resolves the issue.
Thanks for the information; we'll try it.
If we want to test the latest Web Driver, does it mean we must also update the JS files ?
Until the reported issue is verified as fixed, you should use the WebDriver/Selenium JARs shipped with the release, which should be Selenium v2.53.0, so we know we're looking at the same configuration. Once it's working, you can likely update to v2.53.1 without issue - but not v3 of course as discussed.
If you're refering to our WebDriver-related JARs, then as mentioned earlier you should always use the exact same version as the installation you downloaded.
We targeted the login window created by your sample code with a test WebDriver script in Windows 10 running against the exact build of SC 11.0p that you mentioned, and saw no problems. We were able to click into the text fields and click on the button, and saw the image triggered by the button click show up. (Note that your code seems to be missing a symbol, xyzCompanyApplication, but it probably didn't change the result of the investigation.)
If you want to arrange a support call by contacting Jenny, that may be offer the fastest potential for resolution at this point. Otherwise, we need to see the full WebDriver script you're using, and - either at the same time or if that leads nowhere - a complete standalone app rather than the RPCManager override sample code you provided. For example, we'd like to see your web.xml, what server interactions (DMI calls, etc.) are triggering the loginRequired(), etc.
We've applied a fix to resolve this issue for SmartClient 11.0p and newer releases. It should be in the nightly builds dated 2-20-2017 (today) and beyond.
Note that the issue arises because of the presence of StretchImgButton - the title sits in a separate DIV centered inside the button's DIV. You may want to modify your custom skin to avoid using StretchImgButton as it's possible such a configuration receives less testing since it's no longer used in our most current skins.
To elaborate on the StretchImgButton point - all recent skins (Enterprise, EnterpriseBlue, Graphite, Tahoe) do not use the StretchImgButton in modern browsers (IE9+ and all others), instead using the simpler Button widget and achieving rounding via CSS. Similarly for several other key components such as ListGrid headers and TabSet tabs. Overall this creates a fairly large performance difference and causes much less media to be required. See the CSS3Mode discussion in the Skinning chapter for more information.
Comment