Skip to content

Clean up keywords related to alerts #933

@pekkaklarck

Description

@pekkaklarck

The current alert related keywords are a mess. Biggest problems:

  1. Selecting should the alert be dismissed by pressing Ok or Cancel needs to be done using separate Choose Ok/Cancel On Next Confirmation keywords. I think there used to be a technical reason to do it this way, but looking at the current code this doesn't seem to be the case. Much better to just pass this information as a normal argument to keywords dismissing alerts.

  2. There are several keywords with same/similar functionality. In practice Confirm Action, Dismiss Alert an Get Alert Message all close the alert by default.

  3. Strange configuration options and default values. For example, Dismiss Alert actually accepts the alert by default and needs to be separately configured to dismiss it.


If I've understood it correctly, there can be three kind of Javascript alerts:

  1. An alert with a message and Ok button (window.alert).
  2. An alert with a message and Ok/Cancel buttons (window.confirm)
  3. An alert with a message, text input field, and Ok/Cancel buttons (window.prompt)

We need to think what kind of a set of keywords are needed to handle these different alerts. The more we can keep backwards compatibility (i.e. keyword names) the better, but the most important goal is making the set of keywords consistent and easy to use.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions