28968 2015-07-20 09:19:31 +0000 Add algorithm for handling the "unexpected modal dialog" to "Processing model" section 2015-10-26 05:55:11 +0000 1 1 1 Unclassified Browser Test/Tools WG WebDriver unspecified All All RESOLVED DUPLICATE 24816 P2 normal --- 20860 1 vlotoshnikov public-browser-tools-testing ato mike public-browser-tools-testing oldest_to_newest 122216 0 vlotoshnikov 2015-07-20 09:19:31 +0000 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: http://w3c.github.io/webdriver/webdriver-spec.html#processing-model 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. 123938 1 ato 2015-10-26 05:55:11 +0000 *** This bug has been marked as a duplicate of bug 24816 ***