4 ms·
Extensions are limited though. One simple example is an extension can't see cross origin iframes. This means it could never do soemthing like fill out a paymen
by johnsmith1840 9mo ago
Extensions are limited though.
One simple example is an extension can't see cross origin iframes. This means it could never do soemthing like fill out a payment form for you if it's an extension.
Limited computation and action space is another as well as bot detection systems.
For example a javascript method trying to automate something like microsoft word in an iframe will have a tough time because the second you inject code in there they will block you.
- arjunchint 9mo ago> One simple example is an extension can't see cross origin iframes Sounds like a skill issue, our web agent is able to interact with cross origin iframes to for example solve captchas: https://www.youtube.com/watch?v=LD3afouKPYc https://www.youtube.com/watch?v=LD3afouKPYc We honestly haven't faced any bot detection or blocking issues. Owning the browser layer exposes to you much more detection just look at Comet getting blocked on Amazon etc.
- johnsmith1840 9mo agoWith specific user permission to do so sure but in general it is blocked.
- johnsmith1840 9mo agoYou're still limited in lots of annoying ways though
- quarkcarbon279 9mo agowhat permissions are you talking about? No user permissions/any insecure permissions are needed to navigate cross origin iframes, shadow DOMs and likewise. It comes down to your architecture choices and capabilities - rtrvr can navigate these diff realms without ever taking debugger or such insecure permissions