Re:Prototype: Puppeteer for Firefox
by danShumway on Tuesday July 23, 2019 @10:53AM
(#20507183)
That still doesn't explain to me design decisions like how WebDriver's file upload works.
If I'm remote-controlling a browser over a network, wouldn't I occasionally want to send it an arbitrary file upload? Why do I need to separately transfer the file using a different service, and then refer to it with the disk path?
The only reason I can think of is, "normal users couldn't do that." But normal users also can't control a browser over a network. There's no reason to restrict a control protocol to only things that normal users can do.
>There's no reason to restrict a control protocol to only things that normal users can do.
The selenium maintainers seem to have a very strong opposite opinion.
That is just further reason why it ought to support scenarios that the grandparent was describing, like modifying request data, even if that functionality is not useful for automated testing
Selenium/WebDriver isn't a testing tool. It's a a W3C protocol for remote control of web browsers. I think once you get over that misconception, selenium starts to make a lot more sense.