Inline editing invoked by double click throwing error in console

My app is webassembly build on .Net5 RC2 I am using Syncfusion version 18.3.0.44 .
I am trying to implement grid with inline editing.
When user start editing by double click browser control throws error.

Uncaught (in promise) Error: System.ArgumentException: There is no event handler associated with this event. EventId: '568'. (Parameter 'eventHandlerId')
   at Microsoft.AspNetCore.Components.RenderTree.Renderer.DispatchEventAsync(:5001/UInt64 eventHandlerId, EventFieldInfo fieldInfo, EventArgs eventArgs)
   at Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer.DispatchEventAsync(:5001/UInt64 eventHandlerId, EventFieldInfo eventFieldInfo, EventArgs eventArgs)
   at :5001/Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer.ProcessNextDeferredEventAsync()
    at Object.endInvokeDotNetFromJS (blazor.webassembly.js:1)
    at Object.invokeJSFromDotNet (blazor.webassembly.js:1)
    at Object.w [as invokeJSFromDotNet] (blazor.webassembly.js:1)
    at _mono_wasm_invoke_js_blazor (dotnet.5.0.0-rc.2.20475.5.js:1)
    at do_icall (:5001/<anonymous>:wasm-function[10593]:0x194db2)
    at do_icall_wrapper (:5001/<anonymous>:wasm-function[3305]:0x79dee)
    at interp_exec_method (:5001/<anonymous>:wasm-function[2155]:0x44ac8)
    at interp_runtime_invoke (:5001/<anonymous>:wasm-function[7859]:0x12ef59)
    at mono_jit_runtime_invoke (:5001/<anonymous>:wasm-function[7344]:0x118db9)
    at do_runtime_invoke (:5001/<anonymous>:wasm-function[3304]:0x79d37)

I did try to disable AllowEditOnDblClick in GridEditSettings but this works only on until first edit. After first update user is able again to begin edit with double click and then again grid throws error.

Any idea what is wrong with my grid ?
Why does  double click for edit crashing my app?





3 Replies 1 reply marked as answer

RN Rahul Narayanasamy Syncfusion Team October 29, 2020 02:47 PM UTC

Hi Admir, 

Greetings from Syncfusion. 

Query: Inline Editing throws Exception on Console 

We have validated the reported issue and it occur due to @onblur event of Blazor for elements inside the EditForm. Inside the GridEdit Form (inline editing), we have used the textbox controls and other editor controls. They have used @onblur event for certain actions. It is not related to Syncfusion components alone, it is a Framework issue.   
  
Please find the below Github issue which is reported by Blazor team. Once below issue resolved, this error will not be thrown.  
  
  
Also above error will not affect the default functionality of Grid Editing. Please get back to us if you have further queries. 
 
Regards, 
Rahul 



AH Admir Hodžic October 30, 2020 08:45 AM UTC

Thank you on your response.
Bug you mentioned on GitHub is closed on Preview7 .NET5 my app is on version RC2 which is after Preview7, but we still hitting this error.
After i get few  errors in console my app crash and calls for realod.

May I please you to check this error:

ncaught (in promise) Error: System.ArgumentException: There is no event handler associated with this event. EventId: '9802'. (Parameter 'eventHandlerId')
   at Microsoft.AspNetCore.Components.RenderTree.Renderer.DispatchEventAsync(UInt64 eventHandlerId, EventFieldInfo fieldInfo, EventArgs eventArgs)
   at Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer.DispatchEventAsync(UInt64 eventHandlerId, EventFieldInfo eventFieldInfo, EventArgs eventArgs)
   at Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer.ProcessNextDeferredEventAsync()
    at Object.endInvokeDotNetFromJS (blazor.webassembly.js:1)
    at Object.invokeJSFromDotNet (blazor.webassembly.js:1)
    at Object.w [as invokeJSFromDotNet] (blazor.webassembly.js:1)
    at _mono_wasm_invoke_js_blazor (dotnet.5.0.0-rc.2.20475.5.js:1)
    at do_icall (<anonymous>:wasm-function[10593]:0x194db2)
    at do_icall_wrapper (<anonymous>:wasm-function[3305]:0x79dee)
    at interp_exec_method (<anonymous>:wasm-function[2155]:0x44ac8)
    at interp_runtime_invoke (<anonymous>:wasm-function[7859]:0x12ef59)
    at mono_jit_runtime_invoke (<anonymous>:wasm-function[7344]:0x118db9)
    at do_runtime_invoke (<anonymous>:wasm-function[3304]:0x79d37)
endInvokeDotNetFromJS @ blazor.webassembly.js:1
invokeJSFromDotNet @ blazor.webassembly.js:1
w @ blazor.webassembly.js:1
_mono_wasm_invoke_js_blazor @ dotnet.5.0.0-rc.2.20475.5.js:1
do_icall @ 00ab9d9a:0x194db2
do_icall_wrapper @ 00ab9d9a:0x79dee
interp_exec_method @ 00ab9d9a:0x44ac8
interp_runtime_invoke @ 00ab9d9a:0x12ef59
mono_jit_runtime_invoke @ 00ab9d9a:0x118db9
do_runtime_invoke @ 00ab9d9a:0x79d37
mono_runtime_try_invoke @ 00ab9d9a:0x12977
tp_cb @ 00ab9d9a:0xf7d7d
mono_background_exec @ 00ab9d9a:0x9a68b
Module._mono_background_exec @ dotnet.5.0.0-rc.2.20475.5.js:1
pump_message @ dotnet.5.0.0-rc.2.20475.5.js:1
setTimeout (async)
_schedule_background_exec @ dotnet.5.0.0-rc.2.20475.5.js:1
mono_threads_schedule_background_job @ 00ab9d9a:0x26e9d
sgen_perform_collection @ 00ab9d9a:0x21edb
sgen_ensure_free_space @ 00ab9d9a:0x2fdc8
sgen_alloc_obj_nolock @ 00ab9d9a:0x3be9a
mono_gc_alloc_vector @ 00ab9d9a:0x66f58
mono_array_new_specific_internal @ 00ab9d9a:0x9b3c7
mono_array_new_specific_checked @ 00ab9d9a:0x3347a
interp_exec_method @ 00ab9d9a:0x4c569
interp_runtime_invoke @ 00ab9d9a:0x12ef59
mono_jit_runtime_invoke @ 00ab9d9a:0x118db9
do_runtime_invoke @ 00ab9d9a:0x79d37
mono_runtime_invoke_checked @ 00ab9d9a:0xf652
mono_runtime_try_invoke_array @ 00ab9d9a:0x10e78b
ves_icall_InternalInvoke @ 00ab9d9a:0xed487
ves_icall_InternalInvoke_raw @ 00ab9d9a:0xecf4c
do_icall @ 00ab9d9a:0x194d3f
do_icall_wrapper @ 00ab9d9a:0x79dee
interp_exec_method @ 00ab9d9a:0x44ac8
interp_runtime_invoke @ 00ab9d9a:0x12ef59
mono_jit_runtime_invoke @ 00ab9d9a:0x118db9
do_runtime_invoke @ 00ab9d9a:0x79d37
mono_runtime_invoke_checked @ 00ab9d9a:0xf652
mono_runtime_try_invoke_array @ 00ab9d9a:0x10e78b
ves_icall_InternalInvoke @ 00ab9d9a:0xed487
ves_icall_InternalInvoke_raw @ 00ab9d9a:0xecf4c
do_icall @ 00ab9d9a:0x194d3f
do_icall_wrapper @ 00ab9d9a:0x79dee
interp_exec_method @ 00ab9d9a:0x44ac8
interp_runtime_invoke @ 00ab9d9a:0x12ef59
mono_jit_runtime_invoke @ 00ab9d9a:0x118db9
do_runtime_invoke @ 00ab9d9a:0x79d37
mono_runtime_invoke_checked @ 00ab9d9a:0xf652
mono_runtime_try_invoke_array @ 00ab9d9a:0x10e78b
ves_icall_InternalInvoke @ 00ab9d9a:0xed487
ves_icall_InternalInvoke_raw @ 00ab9d9a:0xecf4c
do_icall @ 00ab9d9a:0x194d3f
do_icall_wrapper @ 00ab9d9a:0x79dee
interp_exec_method @ 00ab9d9a:0x44ac8
interp_runtime_invoke @ 00ab9d9a:0x12ef59
mono_jit_runtime_invoke @ 00ab9d9a:0x118db9
do_runtime_invoke @ 00ab9d9a:0x79d37
mono_runtime_try_invoke @ 00ab9d9a:0x12977
mono_runtime_invoke @ 00ab9d9a:0x10eb85
mono_wasm_invoke_method @ 00ab9d9a:0x108e03
Module._mono_wasm_invoke_method @ dotnet.5.0.0-rc.2.20475.5.js:1
call_method @ dotnet.5.0.0-rc.2.20475.5.js:1
(anonymous) @ dotnet.5.0.0-rc.2.20475.5.js:1
beginInvokeDotNetFromJS @ blazor.webassembly.js:1
h @ blazor.webassembly.js:1
e.invokeMethodAsync @ blazor.webassembly.js:1
(anonymous) @ blazor.webassembly.js:1
invokeWhenHeapUnlocked @ blazor.webassembly.js:1
(anonymous) @ blazor.webassembly.js:1
t.dispatchEvent @ blazor.webassembly.js:1
(anonymous) @ blazor.webassembly.js:1
(anonymous) @ blazor.webassembly.js:1
e.onGlobalEvent @ blazor.webassembly.js:1
Show 43 more frames

This error occurs on same grid (editing is disabled) when user using keyboard to navigate to upper rows and select header row (filtering) after that when user click down line to select rows again console throws error like this.
So when user using keyboard navigation and selecting rows in up direction, and when hit once again up on first row, grid control get focused in filter row.
After leaving filter row with keyboard key down this occurs.
My page has form on it but grid does not have editing enabled.
Is this the same case with blur or it is something different


RN Rahul Narayanasamy Syncfusion Team November 4, 2020 12:35 PM UTC

Hi Admir, 

Query: Inline editing invoked by double click throwing error in console - After i get few  errors in console my app crash and calls for realod. 
 
We have validated your query and we can able to reproduce the console error while doble clicking the row to editing the record. But the application will not crashed at our end. The default functionalities of the editing is working fine. Please find the below sample for your reference. 


The console error was thrown in the console. But it does not crash the application. 

If you are still facing the problem, then could you please share the below details. it will be helpful to validate and provide a better solution. 

  • Reproduce the problem(application crashed after getting few errors) in the provided sample and revert back to us.
  • Video demonstration of the problem.
  • Share a simple sample to reproduce the problem.

Regards, 
Rahul 


Marked as answer
Loader.
Up arrow icon