Refreshing Comments...

It just seems to be a bunch of iframes and it renders the website in your browser. HTML is just downloaded through CORS proxy...
Some websites have a Same-Origin policy that won't allow rendering in an iframe. The CORS proxy lets you bypass the restriction.
But this is a tool for development. So if you're loading up a site for development, don't you work on that site and can control the Same-Origin policy?
It's possible to be testing a live version of your own site when you can't easily change the Same-Origin policy for just yourself.
Not sure if people still do the "upload PHP file automatically to production server via FTP on save" way of development. Most web developers I know run servers locally for development, where you can easily set your own headers and/or meta tags.
Nice. But there will always be that client browsing on a corporate install of Internet Explorer that will complain about an obscure bug. In that case, avoid any bickering and counterstrike surgically with a well written and sourced explanation on why their browser is a safety risk for the entire company and that the problem should be escalated quickly to IT because that’s much more worrying than a simple website bug most people’s browsers won’t display. Attach a couple of links to layman-friendly articles about Explorer not being considered a browser anymore even by Microsoft (it’s officially a “legacy solution”) and send.

I did it a few times and each and every time I had follow ups thanking me, telling me how much they hated Explorer but they were forced to use it, and that they didn’t know about the risks of using it.

> you no longer need random time.sleep()

you never needed that, selenium always had multiple method available to wait for page loads or to wait for specific div to become available in the dom or visible in the viewport.

anyway, I don't understand the usefulness of a mobile web render into a browser: a tall, narrow frame is no substitute of a mobile device. for one the rendering engine is not the same, secondly you don't get touch events generated for it, thirdly hover and pixel density media queries straight up won't work

Selenium can use Chromedriver's device emulation mode (eg "add_experimental_option("mobileEmulation", {"deviceName": "iPhone X"})") to enable touch events, pixel density, etc. It's not the same as testing on a real device but it's still useful to have as part of a test pipeline if you don't have the budget for every device you need to test on.

https://chromedriver.chromium.org/mobile-emulation

Interesting. It breaks on my site. https://seleniumbase.io/devices/?url=www.narrator.ai

Tried again and now it doesn't load. Maybe I'll try later. Looks cool though

I tried opening my test site and it was displayed without CSS styles or images. Could this be because I have a restrictive content security policy set?