Cells with Cell Edit Template Losing Input After Tab

Posted by: johnny.su on 5 February 2018, 11:23 am EST

    • Post Options:
    • Link

    Posted 5 February 2018, 11:23 am EST

    Hi,

    We’re seeing a bug where if you type a character and immediately hit tab (has to be really fast) into a cell with a Cell Edit Template that the character isn’t being committed. I’m also able to reproduce the issue with the demo you have here: http://demos.wijmo.com/5/angular2/explorer/explorer/#/grid/celledittempl

    To reproduce: Click on a Amount cell. Then hit a number and tab out really fast. The number isn’t being committed to the cell.

    Regards,

    Johnny

  • Posted 5 February 2018, 4:13 pm EST

    Hi Johnny,

    We tried to replicate the issue and we were able to replicate the issue if tab key is pressed within second.

    This should not be breaking change for you.

    However, we have forwarded this issue to the concerned team for furhter investigation with tracking id 307599.

    We will let you know as we get any update on this.

    ~Manish

  • Posted 20 February 2018, 9:29 am EST

    Hi Manish,

    Any updates on this? This issue is affecting the efficiency of a lot of our users. They’re not able to quickly get their data into the table.

    Regards,

    Johnny

  • Posted 20 February 2018, 2:43 pm EST

    Hi Johnny,

    We are sorry, this issue is still with the development team. We will let you know as we get any update on this.

    ~Manish

  • Posted 23 February 2018, 3:25 am EST

    Hi Johnny

    The problem occurs only for the very first time you begin cell editing. I don’t see the issue on the second and subsequent attempts.

    You may notice that after you started editing for the first time, the height of the grid rows increases a bit to accommodate InputNumber editor which is a bit taller. When this happens, the grid has to recreate a cell editor, which in conjunction with the asynchronous nature of the focus/blur events produces the discussing effect.

    To get rid of this, you can increase the default rows height to make it enough to accommodate cell editor in height, so that to prevent grid from a necessity to do it when first cell editing is starting. For example, in the discussing sample the following setting on the wj-flex-grid element will resolve the problem:

    <wj-flex-grid #flex1 (initialized)="flex1.rows.defaultSize = 32" ...>
    

    The other way is to disable the rows auto-sizing performed by the cell edit template. For this, you can set the autoSizeRows property to false on the corresponding template element:

    <ng-template wjFlexGridCellTemplate [autoSizeRows]="false" ...>
    

    But in this case the cell editor can be clipped a bit, so the first way with rows.defaultSize looks like more preferred.

    Thanks,

    Alex

  • Posted 25 February 2018, 5:58 pm EST

    Hi,

    Setting a higher defaultSize didn’t fix the issue for me. I think the issue I’m having is a little different.

    When entering a value and tabbing out quickly, the value isn’t reflected to the display cell template. Then when I put the cell into edit mode (hit space) the value is there. Wait for the cell to be fully in edit mode and tab out then the value is reflected in the display cell template.

    Does this sound familiar?

    Regards,

    Johnny

  • Posted 7 March 2018, 4:17 am EST

    One thing I noticed today is that the first key does not get directly sent to the input field in the CellEdit template because I had a keydown listener on it and it only captured the ‘Tab’ key.

    For example, if I typed in ‘T’ and then ‘Tab’, the keydown listener on the input in the CellEdit template would only capture the ‘Tab’.

                 <wj-flex-grid-column
                        name="unitQtyUom"
                        is-required="false"
                        binding="unitQtyUom.value">
                    <wj-flex-grid-cell-template cell-type="Cell">
                        <bolt-wj-ca-display-cell></bolt-wj-ca-display-cell>
                    </wj-flex-grid-cell-template>
                    <wj-flex-grid-cell-template cell-type="CellEdit">
                        <bolt-wj-ca-edit-cell></bolt-wj-ca-edit-cell>
                    </wj-flex-grid-cell-template>
                </wj-flex-grid-column>
    

    The template for the element directive (bolt-wj-ca-edit-cell) looks like this:

  • Posted 7 March 2018, 5:24 am EST

    I was able to still recreate the issue with a Fiddle that Manish created: http://jsfiddle.net/dj5gpynp/5/. I modified the ‘id’ column to have a custom editor. If you type in a character and hit tab really fast the issue is still there. The issue is still there in subsequent attempts too.

    This is more representative of what we have compared to the first example. The suggestions from Alex didn’t work for us. Maybe if you could help us solve the issue with this Fiddle, the fix might work on what we have.

    Thanks,

    Johnny

  • Posted 8 March 2018, 1:08 am EST

    Hi Johnny,

    I have reported this issue as bug [ID: 312150]

    ~nilay

  • Posted 21 March 2018, 10:28 am EST

    Hi,

    Any updates on this? Or possible workarounds for now?

    Regards,

    Johnny

  • Posted 21 March 2018, 2:08 pm EST

    Hi,

    Sorry we are unable to provide any workaround for the case,. However, I have requested the development to prioritize the case. I will update you once I have further updates.

  • Posted 22 March 2018, 3:05 am EST

    Thank you! Looking forward to hearing back from you soon!

  • Posted 27 March 2018, 8:59 am EST

    The fix works great. Thank you and the development team! I’ll be on a lookout for the next release.

  • Posted 12 April 2018, 6:44 am EST

    Hi,

    The fix doesn’t seem to be in the latest version 5.20181.436. The issue is fixed in the pre release build above but not in the latest version that just got released. Could you verify that the fix is in the latest version?

    Thanks,

    Johnny

  • Posted 12 April 2018, 7:04 pm EST

    Hi,

    We have fixed the issue in our latest Pre-release build

    http://prerelease.componentone.com/wijmo5/wijmo-5.20181.436-nightly.d20180326.t2300.zip

    Please this out here

    http://jsfiddle.net/gr8j5fr5/

    Let me know if you are still facing any issue with the Fix.

    Please note that Pre-release builds are not recommended to be used in Production Environments and they are have not gone through the QA cycle that our Release builds must pass through. This fix will be made available in the next release of Wijmo ( tentatively mid week of April)

  • Posted 13 April 2018, 3:17 am EST

    Hi Abhishek,

    The post said you replied on April 13th but I’m not seeing it. Were you able to confirm that the fix is in Wijmo version 5.20181.436 that recently got release?

    Regards,

    Johnny

  • Posted 16 April 2018, 9:34 pm EST

    Hi johnny,

    We are really sorry for the inconvenience. The fix for this case was excluded in the release version as it led to regressions and was hence was rolled back.

    This case is currently assigned to our dev team , but we unable to provide an ETA as this time.

  • Posted 24 April 2018, 7:01 am EST

    Hi,

    Any updates? Can this be expedited in any way? We’ve been waiting for this fix for awhile now. Our users are less efficient when they have to do fast data entry. They’re having to double check their data fearing inputs are lost.

    Regards,

    Johnny

  • Posted 25 April 2018, 3:31 pm EST

    Johnny,

    I am sorry but we are unable to provide any ETA due to complexity of the fix and the regressions that can be caused. We will notify you if there are any further updates

  • Posted 2 July 2018, 6:12 am EST

    Hi,

    Will the fix be included in the next release?

    Regards,

    Johnny

  • Posted 4 July 2018, 4:15 pm EST

    Hi,

    Our Dev Team has investigated this fix and we found that fixing this case results in multiple regressions which affects product stability. Fixing this issue would require to run through multiple QA cycles and this will take us some considerable time. We are unable to provide an ETA but we will update you when this case has any updates.

Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels