Announcement

Collapse
No announcement yet.

error on samsung device

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • error on samsung device

    Good morning.
    When I create a field of type array or multi enum, the closing of the record using the X , does not work on some Samsung devices. I have tried the demo and encounter the same error.

  • #2
    Hi,

    I saw the topic in General. We ask to be as detail as possible in bug report rules.

    What exactly devices? What browsers?

    Comment


    • AlessioMa
      AlessioMa commented
      Editing a comment
      I apologise.
      I have tested on some samsung devices, a 52, samsung s21, samsung s22, samsung galaxi tablet, on these devices I find the erroe.
      when i create a field of array type, in order to insert custom values, i have the possibility to inexrire with the + key. however, when i try to delete with the X key, the created element is not deleted.
      This problem is not encountered on other android devices and on iPhone devices.

  • #3
    as you can see in the photo, the green button works the red button does not work

    Comment


    • #4
      It happens on Chrome browser?

      Did it start to happen recently?

      Comment


      • #5
        The multi-enum field utilizes a library which utilizes Jquery UI sortable. The issue might happen widely then, not only in Espo as Jquery UI is still widely used. Maybe it started after some recent Chrome update?

        Comment


        • AlessioMa
          AlessioMa commented
          Editing a comment
          the problem occurs using google crome and samsung browser, i have also tested on a windows tablet, using edge, but i do not find the error.
          Below is the number and date of the crome update
          s-10 agg aug24
          s-21 agg n 129.066881

      • #6
        this is the link to the demo. here I created the multi enum and array fields

        Comment


        • #7
          Thanks for input. We will try to reproduce.

          Maybe someone here have ides what it could be?

          Comment


          • #8
            We could not reproduce on a Samsung tablet on Chrome 129.

            Comment

            Working...
            X