Attribution of the Back button on Chrome

Help Activities
, ,
1

I have 2 questions:
image

  1. When opening a webpage by clicking a link on an original webpage, the Back button on the new webpage should be clickable. But when I run my automation, sometimes the Back button might be grey. In this scenario, I have to click the blank area of this webpage manually to activate the button. My browser is Chrome.

  2. In order to solve the first problem, I added a hardware event Click activity in my automation. Since hardware activity tends to be interrupted, I also added a GetAttribution activity for Back button to judge if the hardware activity is needed. It seems the “foreground” attribution is the one (true corresponds to available) as in below figure. However, in the ForEach, it only worked in the first cycle. In the following cycles, the output of GetAttribution seems wrong, that is, although the Back button is grey (and the “foreground” attribution is also “false” in UI Explorer, below figure), the output of GetAttribution is “true”.

image

The first problem used to occur in the initial cycle only, but recently it also occurred in the sequent cycles. I wonder if it is related to the update of the latest community version.

Please share your advice and help me. Thank you in advance.

2

@Li_Eric

can you tell why you want to click back?

there is somuch of work around that you have done

cheers

3

Hi Anil_G
The first webpage is a list and the second is the detail of each row of the list.
Following is the first webpage.

image
image565Ă—610 29.4 KB

4

@Li_Eric

Did you try navigate browser with go backk?

cheers

5

Thank you Anil_G. It worked.

But I’m still curious about the causes of my 2 problems.

1 Like
6

@Li_Eric

Glad it helped

For that as said we might need more info…like what is exactly happening and may be it is not qctive when retreived but might be active after etc

Cheers

7

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.