Open Bug 1370959 Opened 4 years ago Updated 2 years ago
Hardening proxy capability parsing
There are a couple of issues with parsing the proxy capabilities. Mostly because some parts of the webdriver spec are still not that clear about, and we don't know how people are actually using the proxy settings. So what we want to do first is to get an impression how current tests as written for Selenium are using the proxy settings. If it turns out that the spec is offering to many different ways to specify the settings, and some are not used at all, we would like to strip them off. Here a raw query for proxy tests for different Selenium bindings: https://github.com/SeleniumHQ/selenium/search?utf8=%E2%9C%93&q=proxy%2Btest&type= Based on the outcome it would be good to get started in creating wdspec tests first. Once a good set of tests have been put together we will be able to see which changes for geckodriver and Marionette are necessary.
Depends on: 1387092
Depends on: 1387094
Depends on: 1391016
We are actually pretty good in parsing the proxy capabilities in Marionette now. But we need more tests for webdriver-rust, and especially for the wdspec tests in web-platform-tests. I will start working on that bug once geckodriver 0.19 is out and webdriver-rust is part of the tree.
Depends on: 1395886
Depends on: 1397306
Depends on: 1418055
Depends on: 1420577
More tests would be nice to have, but as far as I can tell this does not align with conformance work unless we believe we have bugs in that area?
Priority: P1 → P3
Also the webdriver crate is now in central, so that unblocks this.
You need to log in before you can comment on or make changes to this bug.