-
Notifications
You must be signed in to change notification settings - Fork 1.2k
feat: capture browser url in windows #1489
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Someone is attempting to deploy a commit to the louis030195's projects Team on Vercel. A member of the Team first needs to authorize it. |
Curious if this works with browsers like Arc as they don't render the URL UI Element |
checking it! |
frames |
chrome is fine, just need to fix for arc browser |
I am getting null URL as well, but noticed one thing it only happens when I have chrome windows opened more than 2 |
focus?? |
One chrome window was in focus. But it give null URL |
logs?? |
Hey @tribhuwan-kumar I was traveling and it night now. Is it okay if I share the logs tomorrow morning Indian time at 11 ? |
i couldn't find any way to capture url from arc browser & there is no such native thing like osascript for windows. one way is working that is sending ctrl+l and ctrl+c key on some interval, but i can be annoying cz ctrl+l opens the search bar dialog of arc browser. for all the other browser its working tho cc: @louis030195 |
i guess we can merge for the hackathon tomorrow and see if we find out anything to make it work for arc in the future |
/approve |
@louis030195: The claim has been successfully added to reward-all. You can visit your dashboard to complete the payment. |
@tribhuwan-kumar thx! btw we'd love some help on this in coming weeks since it will likely be powered by same lib we're going to rework a bit the mac version first though to have a good API design |
sure, I'm working on #703 |
/claim #1415
/closes #1415
description
brief description of the changes in this pr.
related issue: #
how to test
add a few steps to test the pr in the most time efficient way.
if relevant add screenshots or screen captures to prove that this PR works to save us time (check Cap).
if you are not the author of this PR and you see it and you think it can take more than 30 mins for maintainers to review, we will tip you between $20 and $200 for you to review and test it for us.