Modify selector - click button not by name

[Hadzin]

Hi Experts,

Please, help solve the problem.

The standard selector looks like this and it works. Triggered by button name “Edit”

Default Selector

My button can be in different languages and I want to click on the button not by name "Edit", but in some other way.

Its button code in the browser

<button data-l10n-id="about-config-pref-edit-button" class="button-edit semi-transparent" title="Edit"></button>

Code full table with button “Edit”

<table id="prefs" has-visible-prefs="">
  <tr class="has-user-value ">
    <th scope="row">
      <span>general.<wbr>test</span></th>
    <td class="cell-value">
      <span data-l10n-args="{&quot;value&quot;:&quot;test&quot;}" data-l10n-id="about-config-pref-accessible-value-custom" aria-label="test (custom)">
        <span aria-hidden="true">test</span></span></td>
    <td class="cell-edit">
      <button data-l10n-id="about-config-pref-edit-button" class="button-edit semi-transparent" title="Edit"></button></td>
    <td class="cell-reset">
      <button data-l10n-id="about-config-pref-delete-button" class="button-delete ghost-button semi-transparent" title="Delete"></button></td></tr></table>

I tried to substitute parameters in the selector element "Button ‘Edit’". Did not help.

Class - button-edit semi-transparent

ID - about-config-pref-delete-button

Perhaps there is a solution for this problem?

[Nived_Nambiar]

Hi @Hadzin 

I think the atttribute seems to be unqiue one for each button [edit, delete etc]

Could u try with the css selector below 

  button[data-l10n-id="about-config-pref-edit-button"]

Let me know if it worked or not

[Hadzin]

Hi @Nived_Nambiar 

Tried two options. They didn't have success.

1.

2. 

[Nived_Nambiar]

Hi @Hadzin 

The way u have wrote selector is wrong

Only write the selector which I have mentioned don't include other parts 

[Hadzin]

I understand correctly that the selector needs to be edited in a text editor?

[Nived_Nambiar]

Hi @Hadzin 

Try writing the selector this way

[Hadzin]

Hi @Nived_Nambiar 

my result on the screen

[Nived_Nambiar]

Hi @Hadzin 

Could u try to run it and see ?

[Hadzin]

Hi @Nived_Nambiar 

Run, result below

[Nived_Nambiar]

Could u try the below actions ?

For automating websites, you should try browser automation actions not UI Automation actions. UI Automation actions are used for desktop automations 

[Nived_Nambiar]

@Hadzin 

Did this worked for you?

[Hadzin]

This is part of the flow on setting up advanced settings for the Firefox browser.

The PAD treats the settings page as a desktop application and does not create WEB selectors in some cases.

When I tried to create an action “Press button on web page” the selector was created, in the picture #1 - in the block of desktop selectors.

For example, under #2 selector created for a button from the Google site - a WEB selector was created.

While executing the flow, the action “Press button on web page” did not work and did not stop by mistake, the next action stopped by mistake because the edit button was not pressed.

The "Click link on web page" action creates a selector in the selector's application block, named Button ‘Edit’ 3 (in the picture) and does not see the created object.

For this reason, I work with desktop automation.

[Hadzin]

Strange, I sent the answer and it was lost 🤔. I repeat.

This is part of the thread on setting up advanced settings for the Firefox browser.

The PAD treats the settings page as a desktop application and does not create WEB selectors in some cases.

When I tried to create an action “Press button on web page” the selector was created, in the picture #1 - in the block of desktop selectors.

For example, under #2 selector created for a button from the Google site - a WEB selector was created.

While executing the flow, the action “Press button on web page” did not work and did not stop by mistake, the next action stopped by mistake because the edit button was not pressed.

The "Click link on web page" action creates a selector in the selector's application block, named Button ‘Edit’ 3 (in the picture) and does not see the created object.

For this reason, I work with desktop automation.

[Nived_Nambiar]

Hi @Hadzin 

I did not get the point, did you mean that there is some issues with firefox browser?

[Hadzin]

Everything is Ok with the browser.
I need to configure additional parameters using the PAD, on the about:config page.
It looks like the PAD does not understand that this is a browser, since there is no http:// in the address bar.

Maybe that's why PAD works as a desktop application.

[Nived_Nambiar]

I think there is some issue with browser extension, have you checked that ?

[Hadzin]

Everything seems to be OK.

Some things in the stream can be processed.
In the same browser settings window, via UI Automation not Browser Automation.
Only some elements cannot be processed, for example, the Edit button.

[Aakashch_1998]

Hi @Hadzin 

The Buttons/field where Desktop elements are working use that only.
and before clicking on Button use 'Get window' action (Image 1) & in that select Specific window from dropdown and pass UI element of window (image 2) also ON the toggle of Bring Window to front option
Image 1

image 2

you can use the above Button selector given by @Nived_Nambiar 

  button[data-l10n-id="about-config-pref-edit-button"]

Thanks
@Aakashch_1998 

[Hadzin]

Hi @Aakashch_1998 

I tried two options.
1)
2)
after calling a button press, as suggested @Nived_Nambiar   

button[data-l10n-id="about-config-pref-edit-button"]
without success ☹️

There is no other way to define a field with a button in the selector. Only by name (title).

[Aakashch_1998]

Hi @Hadzin 

can you try this seletor in button after Get window action
button[ data-l10n-id="about-config-pref-edit-button"][title]

i have tried similar type of seletor 

Thanks
@Aakashch_1998