- From: James Graham <james@hoppipolla.co.uk>
- Date: Wed, 25 Feb 2015 12:31:59 +0000
- To: "public-browser-tools-testing@w3.org" <public-browser-tools-testing@w3.org>
AIUI it is currently expected that using webdriver to navigate relative URLs (like "foo/bar.html") fails. Is there any particular reason for this limitation? It seems like it is a helpful feature; e.g. it makes things Just Work if you read the href attribute (not property) of an <a> element and use that as the input to get() (except in rare cases involving xml:base). >From a spec point of view it seems rather easy to support; in the algorithm (which doesn't really exist yet) for get add a step like: * Resolve url relative to the API base url of the entry settings object. (that doesn't sound very easy, but it's specese for "do exactly what window.location.assign(url) or window.location.href=url does")
Received on Wednesday, 25 February 2015 12:32:27 UTC