Re: [WebDriver] getPageSource - Does it need to be a remote end call?

On 10 Apr 2015, at 00:22, Seva Lo <vlotoshnikov@gmail.com> wrote:
> Current implementations are inconsistent, and selenium documentation for the API method includes sentence "Think of it as an artist's impression."

Selenium API requirements and documentation can change.

> If it *is* in the scope and within the authority of the spec to require (MUST) that local ends implement certain functionality, then I think specifying that local end MUST implement [get]PageSource API method would suffice.

We decided in the past that local end is explicitly out of scope.

But how local ends would implement a shim routine could be governed by Selenium, i.e. that it would be considered a bug if it didn't return document.documentElement.outerHTML (if that's the most sensible thing to return).

> If otherwise it is beyond the authority/outside of the scope, then I think keeping the remote end endpoint would help insure the functionality is preserved. (still more specification than "artist's impression" would help)

Yes, I think if it's a mobile requirement I have no problem leaving this in the spec.

Received on Friday, 10 April 2015 11:13:17 UTC