W3C home > Mailing lists > Public > public-browser-tools-testing@w3.org > October to December 2013

Re: Spec Feedback - general stuff

From: Jim Evans <james.h.evans.jr@gmail.com>
Date: Tue, 29 Oct 2013 15:48:32 -0400
Message-ID: <CAMx=J=zjPMB=aDJz=B+Dn5PH3ZPF0pNWQpVz=tGLM5Lp5QZEfg@mail.gmail.com>
To: John Jansen <John.Jansen@microsoft.com>
Cc: "public-browser-tools-testing@w3.org" <public-browser-tools-testing@w3.org>
Doesn't the isSelected method (section 10.2) cover detecting form state, or
at least the ability to get the checked state of a radio button or check
box?


On Tue, Oct 29, 2013 at 2:00 PM, John Jansen <John.Jansen@microsoft.com>wrote:

> This is just some general question/feedback. Let me know if it would be
> better in separate emails...
>
> Thanks guys!
>
> Navigation is not really been called out the way users navigate the web.
> * Back
> * Forward
> * Refresh
>
> Mouse/ Keyboard input
> * Hover (css :hover as well as the various javascript mouse events
> including nested menus). Is this for v.next?
> * Web app controls are not called out. For example, custom context menus
> as well as the following functions:
> o Right click
> o Double click
> o Scroll in/ out
> o Autoscroll
> o Click and drag
> o Pinch
>
> "Keyboard input from the physical keyboard should be ignored"
> * Does this mean the physical mouse should be ignored as well?
>
> Send keys to page itself, rather than webelements...
> * Backspace for back
> * Spacebar to scroll
> * Tab to select elements
>
> Capabilities
> * Support for extensions
>
> Detecting form state
> * Checkbox and radio button IWebElements should be able to return their
> checked state
> * Radio button groups should be able to return which button (if any) is
> checked
>
>
>
Received on Tuesday, 29 October 2013 19:48:59 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:09:49 UTC