This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 28968 - Add algorithm for handling the "unexpected modal dialog" to "Processing model" section
Summary: Add algorithm for handling the "unexpected modal dialog" to "Processing model...
Status: RESOLVED DUPLICATE of bug 24816
Alias: None
Product: Browser Test/Tools WG
Classification: Unclassified
Component: WebDriver (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Browser Testing and Tools WG
QA Contact: Browser Testing and Tools WG
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 20860
  Show dependency treegraph
 
Reported: 2015-07-20 09:19 UTC by seva
Modified: 2015-10-26 05:55 UTC (History)
2 users (show)

See Also:


Attachments

Description seva 2015-07-20 09:19:31 UTC
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.
Comment 1 Andreas Tolfsen 2015-10-26 05:55:11 UTC

*** This bug has been marked as a duplicate of bug 24816 ***