You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Chrome runtime update in #39912 seems to have introduced several new test flakes. Those tests were disabled in that PR, and should be fixed are reactivated
The text was updated successfully, but these errors were encountered:
In Chrome 119, creating an <a> element inside the FakeWindow's Document, then setting its anchor.href to a schema-agnostic URL (e.g., anchor.href = '//a.com/';, ancho.href = 'a.com';) correctly changes the anchor.hostname field as well.
In Chrome 120, these URLs result in an empty string in anchor.hostname.
This issue only manifests itself inside the FakeWindow, it works as expected in a real window.
The one thing I noticed is that win.document.baseURI is set to http://localhost:6789/path/to/test/file.html in 119, and to about:blank in 120. I'm not sure if this is relevant, or how to continue this investigation
@erwinmombay you had additional context to add here about Chrome, right?
The Chrome runtime update in #39912 seems to have introduced several new test flakes. Those tests were disabled in that PR, and should be fixed are reactivated
The text was updated successfully, but these errors were encountered: