Possible Bug in March 13, 1.5.3 Release

  • Resolved recveri

    (@recveri)


    2 years, 11 months ago

    For the keyboard navigation by letter/number for the SELECT type, thank you for incorporating it in this newest release.

    However, this could be a bug. Please confirm if this could be fixed as soon as possible.

    There is an issue when label is different from the actual field values. Let’s say the items are entered in the alphabetical order of the labels (not the differing/real input values):

    Input Value=DZ (Label: Algeria)
    Input Value=AU (Label: Australia)
    Input Value=UK (Label: United Kingdom)

    On pressing “A”, it should take to first item in the list “Algeria”, but it selects “Australia”. Pressing “D” jumps to “Algeria” (following its real input value, which a user can’t even see).

    So we see that it is following in order of the values (hidden from user doing the selection) than by the actual labels.

    Please confirm if this is how it was meant to be, or this is a bug?

    Thank you.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Michele Giorgi

    (@michelegiorgi)

    Hey @recveri
    Thanks for your support. I have just published a new Formality version (v1.5.4) with this bug/behaviour fixed.

    Cheers,
    Michele

    Thread Starter recveri

    (@recveri)

    Thanks for fixing this in the new version. However, there is one more thing that is apparently different from normal SELECT/dropdown behavior. On desktops, one still has to resort to pressing ENTER on a keyboard to select an option. Selection with a MOUSE CLICK does not work. Most people while using laptops or desktops by default select with a mouse, and then when it does not work in this case, one starts to wonder what will work (and then finally ENTER key on the keyboard selects/or changes an option). It feels for a moment, one is stuck in that SELECT field.

    Please confirm if this could be treated as a bug and an updated version provided for this at your earliest convenience.

    Thank you.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Possible Bug in March 13, 1.5.3 Release’ is closed to new replies.