Skip to content
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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unexpected "Cannot parse URL: relative URL with a cannot-be-a-base base" in two WPT tests #25064

Open
pshaughn opened this issue Dec 3, 2019 · 2 comments
Labels
A-content/dom Interacting with the DOM from web content

Comments

@pshaughn
Copy link
Member

pshaughn commented Dec 3, 2019

In html/browsers/browsing-the-web/navigating-across-documents/005/html, .click() is called on an anchor with href="href.html".
In html/browsers/browsing-the-web/navigating-across-documents/source/navigate-child-function-parent.html, an iframe's contentWindow.location is assigned "support/dummy/html".
In both cases we end up with "Cannot parse URL: relative URL with a cannot-be-a-base base". This message is probably coming from the url crate; either we're passing garbage in as the base URL, or (probably less likely) the url crate's broken.

@jdm jdm added the A-content/dom Interacting with the DOM from web content label Dec 3, 2019
@jdm jdm added this to To do in web-platform-test failures via automation Dec 3, 2019
@jdm
Copy link
Member

jdm commented Dec 3, 2019

I suspect the documents are about:blank documents, which is not a valid base URL.

@pshaughn
Copy link
Member Author

pshaughn commented Dec 3, 2019

In 005.html the anchor being clicked is on the main 005.html page itself; an iframe is present as the target of the anchor, however, so it could be the URL is being computed relative to that instead of the main page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-content/dom Interacting with the DOM from web content
Projects
Development

No branches or pull requests

2 participants