W3C home > Mailing lists > Public > public-browser-tools-testing@w3.org > July to September 2014

[Bug 26743] New: 14.3.3 - Clarify behavior when typing into non-interactable elements

From: <bugzilla@jessica.w3.org>
Date: Sat, 06 Sep 2014 03:33:23 +0000
To: public-browser-tools-testing@w3.org
Message-ID: <bug-26743-5015@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26743

            Bug ID: 26743
           Summary: 14.3.3 - Clarify behavior when typing into
                    non-interactable elements
           Product: Browser Test/Tools WG
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: WebDriver
          Assignee: public-browser-tools-testing@w3.org
          Reporter: juangj@gmail.com
        QA Contact: public-browser-tools-testing@w3.org
                CC: mike@w3.org
            Blocks: 20860

Section 14.3.3 says:
"A requirement for key-based interaction with an element is that it is
interactable. Typing into an element is permitted if one of the following
conditions is met:"
(and then a list of conditions)

No behavior is specified when the element is not interactable. I think the
language implies that an error should be thrown (because the "requirement" is
not fulfilled), but the spec should specify which error.


Different drivers currently behave differently in this case. For example:
* ChromeDriver (2.10) throws an error ("unknown error: cannot focus element")
* FirefoxDriver (as of
https://code.google.com/p/selenium/source/detail?r=afde40cbbf5c5cd71aa2bdf20c5ded55fae9e786)
seems to type into some other element entirely -- the <BODY> element, in my
testing
* IEDriver seems to do the same thing as FirefoxDriver

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Saturday, 6 September 2014 03:33:24 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 12 February 2015 15:39:03 UTC