[Question/Bug] grapesjs throws a DOMException if you import HTML contents with invalid (numbered) attributes

Just to keep you informed, I applied the try/catch fix suggested by @ankx06 and @artf to our code, but in a generic way.

I wanted to ensure that the exception would be catched in all cases when setComponents() is being called. Either from our code, or, more importantly (and not covered by @ankx06 's example, as far as I know) from the Import Code window.

So, I used a JavaScript closure technique to wrap the original setComponents() function within a new one, in which I put the try/catch: https://stackoverflow.com/a/10427757

var myGrapesJsObject = grapesjs.init(...);
myGrapesJsObject.setComponents = (function (originalFct) {
		  return function (components) {
			try {
				originalFct(components);
			}
			catch (ex) {
                                window.alert('Parse error: ' + ex);
				}
		  }
		})(myGrapesJsObject.setComponents);

And it works perfectly. No more blocking DOMExceptions.

Thank you all for your suggestions!

@jmchaves this is not called from any event. This is the function to update component's inner components/html.

I have also faced this issue while setting an invalid attribute/style for image height/width.

Currently, I have handled using a try-catch block

  static updateInnerHTMLofComponent(component, newContent) {
    // Set inner content empty               // this is optional
    component.set("content", "");

    // Add new content in component. This will remove existing child components and create new child components
    try {
      component.components(newContent);
    } catch (error) {
      // Handling component render failed when user set invalid attributes to one of the component
      this.hendleComponentRenderFailed(component, error.message);
    }
  }

If the newContent has multiple components and only one component have the error, due to exception none of the components renders, at least the components which are not in error should render correctly and the component in error can render after ignoring invalid such attribute?

Thanks, Ankit