1. 6

  2. 6

    Nice visually, but switching the order of “ok” and “cancel” left-to-right is at least a misdemeanor.

    1. 3

      It depends on your host platform. Windows puts OK first, macOS puts OK last. If they’d switch places, then a different part of users would have a problem with it. Most important thing is that OK is visually different than Cancel.

      1. 3

        I think this highlights why replacing system controls should be avoided where possible. By using built in alert and friends it follows the system conventions with no extra code needed.

        1. 2

          This is a weird stance upon any examination. The native alert/confirmation dialogs have a ton of problems (eg being modal and preventing tab switching) and there is no user expectation of website UI feeling native to your OS because that’s literally impossible as there are no other native UI controls. Using a browser alert dialog would just be bad ux.

          1. 1

            There is no user expectation of website UI feeling native to your OS because that’s literally impossible as there are no other native UI controls.

            I personally see a raising expectation from users for a unified (let’s call it “system”) UI feeling inside interactive (let’s call them “with form elements”) web pages.

            In the population of users I’m familiar with (office workers in EU) I’ve never heard anybody praising a website because it was “beautiful” nor criticizing it because it was “ugly”. At the same time I heard many complains due to non standard (or “non system looking”) controls and UI designs.

      2. 2

        Thans for feedback. I’ve just published a new version which provides an option for reversing button positon.

      3. 3

        I think these alerts would look better if the grow-in animation were shorter. The bounce effect is so slow and large (compared to other UI animations) that the movement distracts me for a moment from the content of the alert. This makes the alert feel slow and unsteady instead of fluid.

        1. 4

          Can we stop describing software as “beautiful” already?

          1. 2

            Yeah, every time I see a headline like this, I kind of don’t want to click, because I will be like “meh, nice, but beautiful??”..

            Went through and had a look on these. The popups look nice. Author did a good job.

            1. 1

              I’ve never heard any other software describe itself as beautiful before, but I don’t think calling software beautiful is always bad. For example, I like to think that the code of my Bad Code Rocks contest entry is beautiful in how convoluted it manages to be. However, I agree that when trying the demo of this alerts library, I don’t find the alerts beautiful compared to other modal dialog libraries. Maybe “beautiful” is supposed to be relative to the browser’s built-in alert dialogs?

              1. 0

                Every 2nd app on AppStore says it does the same thing as all other apps in its category, but THIS one is beautiful.

                edit: OK, maybe not exactly every 2nd, but there are a lot of those apps.

              2. 1

                I agree with you. So I changed to “Cool”. Cool is cool? ^^

              3. 2

                Small issue: if you click on the grey area and then press Esc, the box doesn’t close.

                1. 2

                  Problem fixed on v1.0.2 which is I just published. Thank you for reporting this.

                2. 1

                  For the confirmation dialogues, you should make it so that the initial focus is on the cancel button, or else when you tab through you could potentially accidentally confirm the action.

                  Someday, someone will have an enter key that fails (sticky keys get turned on or whatever) and accidentally deletes/confirms payment/etc and someone on your Support team will have a bad day.

                  But it looks nice. :) thanks for sharing.