It doesn't look like you're doing
anything wrong. That's exactly the same code I'd use.
If you double click the elementBtnProf array in the watch list, what do you see? What is the value of elementBtnProf_count? If it's 0, it's not finding that element, which means maybe it's in a frame?
This may help you if that's the case.
If it is 1, it
should be clicking it. If it's >1 then maybe you're clicking on the wrong one.
I've found that sometimes trying one of the other attributes works. Maybe see what happens if you use
title="Sélectionner la profession">
Code: Select all
ChromeFindElements>session_id,xpath,//a[@title='Sélectionner la profession'],elementBtnProf
ChromeElementAction>session_id,elementBtnProf_1,click
One thing to consider is (and I am amazed at how many people don't do this) - does the button even need to be clicked? Very often people will click through a long succession of buttons and menus when they could have quite easily just navigated to that page in the first place. I'm sure that's not the case here but it never hurts to mention it.