Re: Next publication of the WebDriver Specification.

I think it would be better to have this in a future version. This is not to
say that it is not important but if I can limit the scope to what is there
we can get the cogs working. For the most part implementors are working off
the Living Spec version and this to make sure we are doing our deliverables
for the working group.

Though if others thought we needed it sooner I am happy to go with that
approach too.

David

On Sat, 20 Jul 2019 at 05:00, Mike Pennisi <mike@bocoup.com> wrote:

> Hi David!
>
> [1] is a second attempt to make the "Execute Script" algorithm sound
> from a normative perspective. Do you think we could work that out for
> the new version?
>
> In addition to increasing confidence that the spec text can be
> implemented as written, I'm also motivated by the possibility of
> supporting `await` expressions. I'd love to help with that, but I don't
> know if you and the other editors are interested in adding new features
> to this release. If you are, it probably influences how we proceed with
> that "cleanup" patch. I've opened [2] to discuss some technical
> considerations for supporting `await`.
>
> [1] https://github.com/w3c/webdriver/pull/1431
> [2] https://github.com/w3c/webdriver/issues/1436
>
> On 7/18/19 3:42 AM, David Burns wrote:
> > Hi All,
> >
> > It is time that we see about publishing a newer version of the
> > WebDriver specification. I have got a list of changes[1]. Most of it
> > is corrections as people have been doing implementations.
> >
> > The new command is `New Window`.
> >
> > If I don't hear anything by 30 July 2019 I will start the process with
> > Mike to get it published.
> >
> > David
> >
> > [1]
> > https://gist.github.com/AutomatedTester/828a76d853dd4b4c5383b8ae2bdfd327
>
>