- From: David Burns <dburns@mozilla.com>
- Date: Mon, 15 Oct 2012 18:15:58 +0100
- To: Simon Stewart <simon.m.stewart@gmail.com>
- CC: Arthur Barstow <art.barstow@nokia.com>, w@wja.no, shs@google.com, public-browser-tools-testing@w3.org, "public-webevents@w3.org" <public-webevents@w3.org>
Arthur, Simon also forgot about the Mozilla implementation[1]. One thing to note is that only Opera and Google(Chrome for Desktop only at the moment) have official implementations with Marionette[1] catching up on all platforms. The rest of the implementations have been done by the open source project. Representatives from Opera, Google and Mozilla, including Simon and myself, will be there to discuss anything further with you. I am hoping that other companies will come along and discuss things with us at TPAC. Thanks for the email and feel free to ask us more questions as they come up. David [1] https://developer.mozilla.org/en-US/docs/Marionette On 15/10/2012 12:27, Simon Stewart wrote: > Hi Arthur, > > The WebDriver spec is formalising the APIs and workings of the > existing webdriver implementations[1][2][3]. That means that the > implementations are actually further along than the specification > would make them appear. > > We have two mobile implementations right now: one for Android and one > for iOS. Both of these have some level of support for touch events, > either through the main "WebElement" API[4] or through the Advanced > User Interactions API, the entry point to which is the Actions[5] and > TouchActions[6] classes in Java. The test suite for the webdriver spec > will be in Python, so we should be surfacing these APIs there. > > I'd be happy to focus on the parts of the spec that you feel would be > most advantageous to your group, so please feel free to ask us to > flesh out any sections that you feel are missing. If it would help, > I'll be at TPAC from Monday to Wednesday and would be happy to chat at > any point (and you'd also be welcome to attend the browser test tools > sessions on Monday and/or Tuesday) > > Regards, > > Simon > > [1] http://selenium.googlecode.com/ > [2] http://chromedriver.googlecode.com/ > [3] http://www.opera.com/developer/tools/operadriver/ > [4] http://selenium.googlecode.com/svn/trunk/docs/api/java/org/openqa/selenium/interactions/Actions.html > [5] http://selenium.googlecode.com/svn/trunk/docs/api/java/org/openqa/selenium/interactions/touch/TouchActions.html > > On Sun, Oct 14, 2012 at 3:02 PM, Arthur Barstow <art.barstow@nokia.com> wrote: >> Hi All, >> >> The Web Events WG is working on a test suite for the Touch Events spec [1] >> and during a recent meeting, someone asked [2] about the status of the Web >> Driver [3] work by the Browser Testing and Tools WG and I agreed to >> followup. >> >> I would appreciate it, if you would please provide a short status and plan >> for Web Driver including the implementation status of the spec (or a pointer >> to such info). >> >> -Thanks, Art Barstow >> >> [1] http://w3c-test.org/webevents/tests/touch-events-v1/submissions/ >> [2] http://www.w3.org/2012/09/11-webevents-minutes.html#item03 >> [3] http://dvcs.w3.org/hg/webdriver/raw-file/default/webdriver-spec.html >> >> -------- Original Message -------- >> Subject: ACTION-97: Report on the status of WebDriver work by the >> Browser Test Tools WG (Web Events Working Group) >> Date: Tue, 11 Sep 2012 15:26:22 +0000 >> From: ext Web Events Working Group Issue Tracker <sysbot+tracker@w3.org> >> Reply-To: Web Events Working Group <public-webevents@w3.org> >> To: <art.barstow@nokia.com> >> >> >> >> ACTION-97: Report on the status of WebDriver work by the Browser Test Tools >> WG (Web Events Working Group) >> >> http://www.w3.org/2010/webevents/track/actions/97 >> >> On: Arthur Barstow >> Due: 2012-09-18 >> >> If you do not want to be notified on new action items for this group, please >> update your settings at: >> http://www.w3.org/2010/webevents/track/users/7672#settings >> >> >> >> >> >
Received on Monday, 15 October 2012 17:16:34 UTC