"this.boundedEvents is undefined" in Firefox / "Cannot read property 'hasOwnProperty' of undefined" in Chrome

[Steffen Harbich]

Hi,

in my nextjs 10 application, I have code like (the only place where a toolbar is applied):

import { RichTextEditorComponent, Inject, Toolbar, Image, Link, HtmlEditor, QuickToolbar } from "@syncfusion/ej2-react-richtexteditor"

<RichTextEditorComponent value={model?.body} name="body" toolbarSettings={toolbarSettings}>

   <Inject services={[Toolbar, Link, HtmlEditor, QuickToolbar, Image]} />

</RichTextEditorComponent>

But as soon as I navigate to any other page, the following error occurs in Firefox:

In Chrome, the error looks a bit different:

Unfortunately, I cannot reproduce this in a small example. I hope you can find the problem with these error details.

Syncfusion version 19.1.69.

Maybe related to https://www.syncfusion.com/forums/158868 although there is no grid involved.

Best regards, Steffen Harbich

[Revanth Krishnan]

Hi Steffen, 

 

 

Greetings from Syncfusion support. 

 

 

We have validated your query “When I navigate to other pages from the Rich Text Editor page, console error "this.boundedEvents is undefined" occurs in Firefox and "Cannot read property 'hasOwnProperty' of undefined" in Chrome.” 

 

We have analyzed the shared code snippet and we tried to reproduce the issue in the following ways, 

• Ensure the issue by rendering the Rich Text Editor with ‘toolbarSettings’ enabled
• Navigating to other pages from Rich Text Editor.
• Also, ensured by disabling the toolbar and navigating to other pages.
• Ensured in both the chrome, Firefox browser.

 

But we couldn’t reproduce the issue from our end. We have prepared a sample in nextjs for your reference, 

Sample: https://www.syncfusion.com/downloads/support/directtrac/general/ze/nextjs-blog-15935274 

 

Can you please share the following details? 

• The full code snippet of the Rich Text Editor page with its properties.
• The video illustration of the issue reproducing scenario.
• Please share with the issue reproducible sample or please modify the shared sample with the issue reproducing code.

 

The above details will be helpful for us to validate and reproduce the issue from our end and assist you at the earliest. 

 

Regards, 

Revanth 

[Steffen Harbich]

Hi,

renewing the node_modules directory fixed it. I was upgrading from 18.2.x and for some reason it made a difference to remove the node_modules directory completly and install dependencies again. So this is no longer an issue.

Regards, Steffen

[Revanth Krishnan]

Hi Steffen, 

 

Thanks for the update. 

We are glad that the issue has been resolve on your end. Please let us know if you need further assistance. 

 

Regards, 

Revanth