Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

    Tahoe Skin - editByCell: clears and loses focus

    Hi there,

    we've noticed that there is a bug when using the ListGrid's editByCell in combination with the Tahoe skin. When editing a field and hovering over another field, the editor is cleared and loses focus.
    If the editor is re-selected, you can input another value. When the field is submitted with enter, the value from when it was first cleared reappears. Also not all input to the field is saved when editing is ended without hovering over another field. This seems to only be the case when pulling the cursor out of the ListGrid quickly and is shown in the attached animation.

    The bug does not appear when editByCell is false, or when the Enterprise skin is used.
    Click image for larger version

Name:	editByCell.gif
Views:	48
Size:	37.3 KB
ID:	248782

    Version: SmartClient_v11.1p_2017-08-27
    Browser: Current Firefox, Chome and IE
    Skin: Tahoe

    Code for reproduction
    Code:
    <script>
    isc.VLayout.create(
        {
        "ID":"rootVLayout",
        "width":"100%",
        "height":"100%",
        "members":
        [
        isc.ListGrid.create({
            ID: "ListGrid1",
            width:500,
            height:120,
            alternateRecordStyles:true,
            editEvent: "click",
            editByCell: true,
            canEdit: true,
            fields:[
                {name:"name"},
                {name:"value"},
            ],
            data:[
            {id:1, name:"One", value:"1"},
            {id:2, name:"Two", value:"2"},
            {id:3, name:"Three", value:"3"},
            {id:4, name:"Four", value:"4"},
            ]
        }),
        isc.IButton.create({
            title: "End Editing",
            click: "ListGrid1.endEditing()"
    })
    ]
    }
    )
    </script>
    Best regards

    #2
    Hi Isomorphic,

    this might be related to this issue.

    Best regards
    Blama

    Comment


      #3
      This is fixed in builds of Aug 30 or later.

      Comment


        #4
        Thanks.
        Fix confirmed for build of 30 Aug.

        Comment

        Working...
        X