Skip to content

Regressions in Dismiss Alert and Confirm Action compared to 1.8 #934

Closed

Description

@pekkaklarck

At the moment (SL 3.0 beta 3) there are some regressions compared to version 1.8:

  1. Dismiss Alert accept=${FALSE} leaves the alert open but it in 1.8 it closes it regardless the value of accept. It's behavior to accept by default and require configuration to dismiss is strange, but we already have Clean up keywords related to alerts #933 about that and other alert related oddities.

  2. Dismiss Alert always returns the message of the alert but in 1.8 it returns true or false depending was the alert close or not. This is strange behavior too.

  3. Confirm Action accepts the first alert but subsequent alerts are dismissed by default. In 1.8 all alerts were accepted by default.

Activity

  1. added this to the v3.0.0 milestone on Sep 28, 2017
  2. pekkaklarck commented on Sep 28, 2017

    @pekkaklarck
    MemberAuthor

    Added new regression label. The idea is to use that label so that issues labeled with it will be seen in release notes of preview releases but not anymore in the final release notes.

  3. added a commit that references this issue on Sep 28, 2017
    d17e3f5
  4. added a commit that references this issue on Oct 5, 2017
    65d9957
  5. pekkaklarck commented on Dec 1, 2017

    @pekkaklarck
    MemberAuthor

    Regressions compared to 1.8 that are already fixed don't belong to 3.0 release notes.

  6. removed this from the v3.0.0 milestone on Dec 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions