- From: Luke Inman-Semerau <luke.semerau@gmail.com>
- Date: Mon, 9 Mar 2015 09:01:23 -0700
- To: public-browser-tools-testing <public-browser-tools-testing@w3.org>
I know mobile isn't explicitly in the first draft of the spec, but
it's slightly more complicated for the current ios and android
implementations that I know about. There is no equivalent trivial
execute script method that could generate the 'Native' source / tree.
Although since it's not really a Page, I could see the addition of a
new end point to handle mobile's case.
On Mon, Mar 9, 2015 at 7:11 AM, David Burns <dburns@mozilla.com> wrote:
> Hi All,
>
> Do we want to keep getPageSource a server side call or are we ok with moving
> this into the client. The JS required to create it is rather trivial[1].
> This could easily be moved into the local end with little disruption to
> people's tests.
>
> David
>
> [1] driver.execute_script('return document.documentElement.outerHTML')
>
>
Received on Monday, 9 March 2015 16:01:55 UTC