deepl: clicking elements #30124
-
|
https://www.deepl.com/en/translator How to click |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 10 replies
-
|
Like change |
Beta Was this translation helpful? Give feedback.
-
|
As far as I understand the second button only exists after the first one has opened the popup. So the order of the scriplets execution shouldn't matter? |
Beta Was this translation helpful? Give feedback.
-
|
Hmm, you're right. Didn't know the scriptlet 'waits for' an element to appear. |
Beta Was this translation helpful? Give feedback.
-
@Yuki2718 I am looking at the scriptlet's logic again and I am thinking of a better approach for dealing with delays. What if we just insert the needed delays inside the list of selectors? This would allow different delays (or no delay) at different point in the sequence of clicks. For example: Given that a pure integer is not a valid selector, it would be assumed to be a delay before the next element is clicked. The downside is to break compatibility of AdGuard with uBO when it comes to that one scriptlet -- though they could also adopt the change if they want. I see that AdGuard further extended the scriptlet to allow forcing a reload, and eventually I could also adopt this capability as a sequence action to take, for example: |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, that sounds more flexible. Regarding compatibility, it doesn't matter too much as this is a trusted scriptlet. |
Beta Was this translation helpful? Give feedback.
-
|
Is it beneficial to avoid the delay and use something like below instead? |
Beta Was this translation helpful? Give feedback.
Like
change
translator-lang-option-enfor a preferred language.