problems with xpath about seleniumbasic HOT 4 CLOSED

The web page has two sort down arrows for the same purpose and you picked the wrong one to click on.
One is for the static header and the other one is for the floating header.
Set a breakpoint and evaluate the XPath in Firefox to see where the elements are once the page is s crolled:

$x("//a[@id='ctl00_ctl10_ProductOverviewTable_ProductGrid_DerivativeLever_desc']")

from seleniumbasic.

Hello Florent,

Thanks again for your quick reply.

The problem I am currently facing is that there are quite a lot of instructions that worked with the old version but not now on different web pages.

I understand your explanation, but why did the loading behaviour of the webpage change dependent on the web driver and how could I avoid future headaches? Is there any safe way to prevent those issues for future updates?

If I reinstall the old version v2.0.5.0 all is running as always, but with the new version I am facing those issues.

I have installed:

Firefox 42.0

Excel 2010, completely updated

Windows 7 and Windows 8.1

Best regards

Martin

Von: Florent Breheret [mailto:[email protected]]
Gesendet: Montag, 14. Dezember 2015 16:59
An: florentbr/SeleniumBasic
Cc: martinoclaudio
Betreff: Re: [SeleniumBasic] problems with xpath (#47)

The web page has two sort down arrows for the same purpose and you picked the wrong one to click on.
One is for the static header and the other one is for the floating header.
Set a breakpoint and evaluate the XPath in Firefox to see where the elements are once the page is s crolled:

$x("//a[@id='ctl00_ctl10_ProductOverviewTable_ProductGrid_DerivativeLever_desc']")

—
Reply to this email directly or view it on GitHub #47 (comment) .Das Bild wurde vom Absender entfernt.

from seleniumbasic.

I understand your explanation, but why did the loading behaviour of the webpage change dependent on the web driver and how could I avoid future headaches?

This change of behaviour in the Firefox driver was an attempt to make it interact more like a real user.
With the previous version you were able to click an element that wasn't visible to begin with.
The only issue I see here is that there should be an error telling that the element cannot be clicked.
Here is the issue in question raised in the Selenium project:
SeleniumHQ/selenium#1202

Is there any safe way to prevent those issues for future updates?
No

from seleniumbasic.

Thanks a lot. It is very helpful understanding the background!

Von: Florent Breheret [mailto:[email protected]]
Gesendet: Montag, 14. Dezember 2015 19:12
An: florentbr/SeleniumBasic
Cc: martinoclaudio
Betreff: Re: [SeleniumBasic] problems with xpath (#47)

I understand your explanation, but why did the loading behaviour of the webpage change dependent on the web driver and how could I avoid future headaches?

This change of behaviour in the Firefox driver was an attempt to make it interact more like a real user.
With the previous version you were able to click an element that wasn't visible to begin with.
The only issue I see here is that there should be an error telling that the element cannot be clicked.
Here is the issue in question raised in the Selenium project:
SeleniumHQ/selenium#1202 SeleniumHQ/selenium#1202

Is there any safe way to prevent those issues for future updates?
No

—
Reply to this email directly or view it on GitHub #47 (comment) .Das Bild wurde vom Absender entfernt.

from seleniumbasic.