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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
[馃悰 Bug]: Intercepting network response produces exception #10574
Comments
@dokisha, thank you for creating this issue. We will troubleshoot it as soon as we can. Info for maintainersTriage this issue by using labels.
If information is missing, add a helpful comment and then
If the issue is a question, add the
If the issue is valid but there is no time to troubleshoot it, consider adding the
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable
After troubleshooting the issue, please add the Thank you! |
@titusfortner I'm facing the similar. If it works for you we can safeguard that (using a PR). replacing this
|
PRs very appreciated, ideally with a spec. Do we know when the response header won't be present? |
* fixes #10574 Co-authored-by: Virendra Negi <virendra.negi@sugarboxnetworks.com>
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
* fixes SeleniumHQ#10574 Co-authored-by: Virendra Negi <virendra.negi@sugarboxnetworks.com>
What happened?
Intercepting network response crashes the browser.
@titusfortner said:
the code is assuming responseHeaders will be there, but that's optional according to chromedevtools.github.io/devtools-protocol/tot/Fetch
How can we reproduce the issue?
Relevant log output
Operating System
Ubuntu
Selenium version
ruby 2.6.5p114 (2019-10-01 revision 67812) [x86_64-linux]
What are the browser(s) and version(s) where you see this issue?
Chrome 99.0.4844.84
What are the browser driver(s) and version(s) where you see this issue?
ChromeDriver99.0.4844.51
Are you using Selenium Grid?
No
The text was updated successfully, but these errors were encountered: