RE: WebDriver spec - Where we are and were we are going

> Currently all the major parts of the specification have been done*. However,
> we have diverged the specification on some parts. Some of that was intended
> and some of that was not intended and we need to fix these things up. The
> more people, who are looking at this from either a local end implementation
> or remote end implementation, who can report issues the better.

I was looking at Section 13.1[1] and would love it if the algorithm were modified to match the bug you and Jim were discussing a couple years ago[2].

> Test Suite:
> This month, Mozilla will hopefully start the work to supply the necessary parts
> to Web-Platform-Tests and start work on auditing the test suite that is there.
> This is being driven both by Gecko engineers and Servo engineers who would
> like this supported.

At Microsoft we have been doing this at a high level (very high level so far). Would love to do this work together. You may remember the tool I showed briefly at TPAC that helps map tests to sections of the spec based on the Web Annotations[3] spec. Maybe if you guys take the time to vet the tests themselves and we take the time to match sections to those tests we can get it done more quickly.

> Charter:
> Our current extension to the charter ends at the end of March. I would like to
> get this extended so we can do the "to recommendation" process, which
> requires work, mentioned above in this email, to have been done.

Happy to help here as well. I don't think we will be allowed to publish a new draft at the w3c if we are not under Charter, but Mike can correct me if I'm wrong.

-John
[1] https://w3c.github.io/webdriver/webdriver-spec.html#element-click

[2] https://www.w3.org/Bugs/Public/show_bug.cgi?id=21184

[3] https://www.w3.org/annotation/

Received on Thursday, 3 March 2016 18:48:10 UTC