[Bug 28968] New: Add algorithm for handling the "unexpected modal dialog" to "Processing model" section


            Bug ID: 28968
           Summary: Add algorithm for handling the "unexpected modal
                    dialog" to "Processing model" section
           Product: Browser Test/Tools WG
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: WebDriver
          Assignee: public-browser-tools-testing@w3.org
          Reporter: vlotoshnikov@gmail.com
        QA Contact: public-browser-tools-testing@w3.org
                CC: mike@w3.org
            Blocks: 20860

The way remote end handles unexpected modal dialogs[1] is currently defined in
section Interactions >> ... >> sendKeys().

It really should be defined elsewhere, probably as part of the main algorithm
of handling a command by the remote end, the Processing model section:

That is because not only sendKeys() but many other commands will have to "send
an error" if a modal dialog is active.

[1] "Unexpected" modal dialog is any modal dialog that is active when remote
end receives a command that doesn't handle that modal dialog and that [the
command] should fail because of that dialog being active.

You are receiving this mail because:
You are the QA Contact for the bug.

Received on Monday, 20 July 2015 09:19:35 UTC