Closed unsciorg closed 1 year ago
Hello, thanks for the PR, I have a few questions to confirm.
I tested two positioning clicking schemes, and they all seem to have the same effect.
This is the click in PR:
This is the click in main branch:
Hello, The new challenge button looks like this
The existing code in the main branch is unable to locate and click on the corresponding component.
The target website is https://chat.xxxxai.com/auth/login . ( as you know π )
based on the windows platform.
Ok I got it, I reproduced the problem.
Thank you again for your great work on this PR,@unsciorg. π Will be merged after resolving those comments above.
The advantage of this pr is that no matter how many iframe there are on the page, it will always find the one that contains the challenge input box and click on it.
there is something wrong in the code, closed
Can you tell me what's wrong? I'm already planning to merge it.
Due to an oversight, I mistakenly used the await keyword in a non-async section.
Peanut @.***> δΊ2023εΉ΄6ζ7ζ₯ε¨δΈ 11:08ειοΌ
Can you tell me what's wrong? I'm already planning to merge it.
β Reply to this email directly, view it on GitHub https://github.com/vvanglro/cf-clearance/pull/33#issuecomment-1579803289, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADYQ2QY4SQRXLIW6AOYTAFLXJ7WCXANCNFSM6AAAAAAY37OH7M . You are receiving this because you modified the open/close state.Message ID: @.***>
I think this method of judgment seems somewhat imprecise. We should check if the URL of the iframe contains "challenge.cloudxxxx.com". To avoid detection. Therefore, we will only check for the presence of "challenge" in the URL.
What is your opinion
add a new type of challenge button