[Webkit-unassigned] [Bug 175181] New: Web Automation: clear element should fire onchange event

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Aug 4 01:56:57 PDT 2017


https://bugs.webkit.org/show_bug.cgi?id=175181

            Bug ID: 175181
           Summary: Web Automation: clear element should fire onchange
                    event
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebKit2
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: cgarcia at igalia.com
                CC: bburg at apple.com, joepeck at webkit.org

There's a test in selenium to check this that all other browsers pass:

FAIL test/selenium/webdriver/common/correct_event_firing_tests.py::testClearingAnElementShouldCauseTheOnChangeHandlerToFire[WebKitGTK]

========================================================================================== FAILURES ==========================================================================================
____________________________________________________________ testClearingAnElementShouldCauseTheOnChangeHandlerToFire[WebKitGTK] _____________________________________________________________

driver = <selenium.webdriver.webkitgtk.webdriver.WebDriver (session="d04a47a2-3c83-41c8-8acf-848523af1ea5")>, pages = <conftest.Pages object at 0x7fe9772acd10>

    def testClearingAnElementShouldCauseTheOnChangeHandlerToFire(driver, pages):
        pages.load("javascriptPage.html")
        element = driver.find_element_by_id("clearMe")
        element.clear()
        result = driver.find_element_by_id("result")
>       assert result.text == "Cleared"
E       AssertionError: assert ' ' == 'Cleared'
E         -  
E         + Cleared

test/selenium/webdriver/common/correct_event_firing_tests.py:97: AssertionError

The spec doesn't say anything about change event, it says that when clearing a resettable element the element reset algorithm should be run. And the HTML spec says that input events shouldn't be fired when resetting but doesn't mention change events. I guess that in these cases it's better to be consistent with all other implementations and what selenium expects.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170804/90aa260c/attachment.html>


More information about the webkit-unassigned mailing list