[Deprecation] Listener added for a synchronous 'DOMNodeInserted' DOM Mutation Event.

Question

[Deprecation] Listener added for a synchronous 'DOMNodeInserted' DOM Mutation Event.

Aaronliu2016 opened this issue a year ago · 56 comments

Aaronliu2016 commented a year ago

Chrome console shows this warning information:

[Deprecation] Listener added for a synchronous 'DOMNodeInserted' DOM Mutation Event. This event type is deprecated () and work is underway to remove it from this browser. Usage of this event listener will cause performance issues today, and represents a risk of future incompatibility. Consider using MutationObserver instead.

Is this caused by the quill.js version?

noxsii commented 6 months ago

push...

Answer 1 · 2023-08-03T06:12:33.000Z

slab/quill#3806
update quill to 2.0.0

Answer 2 · 2023-08-04T18:14:00.000Z

hello, any predictions for an update to version 2.0?

Answer 3 · 2023-08-16T15:31:21.000Z

Hello, same problem here, any news ?

Answer 4 · 2023-08-18T14:34:07.000Z

Facing performance issues because of this! An update would be helpful

Answer 5 · 2023-08-21T18:49:39.000Z

Any update on this?

Answer 6 · 2023-08-29T04:45:01.000Z

got the same issue.

Answer 7 · 2023-08-29T09:20:53.000Z

Have to switch to tiptap instead of quill. Not as easy as vue-quill but the vue3 sample of tiptap is really clear.
guess what, its performance is way much better.

Answer 8 · 2023-08-30T07:21:46.000Z

I got the same issue on vue-quill, can someone recommend rich text editor that can embed video from youtube or any other media sites which will be compatible to vue js 3

Answer 9 · 2023-09-01T12:59:49.000Z

I am getting this warning on Firefox Use of Mutation Events is deprecated. Use MutationObserver instead.
On google Chrome Warning is
[Deprecation] Listener added for a synchronous 'DOMNodeInserted' DOM Mutation Event. This event type is deprecated (https://w3c.github.io/uievents/#legacy-event-types) and work is underway to remove it from this browser. Usage of this event listener will cause performance issues today, and represents a risk of future incompatibility. Consider using MutationObserver instead.

Where exactly we need to use MutationObserver Or quick fix update will be great. We urgently need to fix this people are moving to other editor due to this warning.

Answer 10 · 2023-09-06T18:19:24.000Z

Also having this issue with vanilla js quil. Really need to fix this quick plz, or I'll have to move to a different editor.

Error is coming from this line in the following code:

_this.domNode.addEventListener('DOMNodeInserted', function() {});

var Scroll = function(_Parchment$Scroll) {
                    _inherits(Scroll, _Parchment$Scroll);

                    function Scroll(domNode, config) {
                        _classCallCheck(this, Scroll);

                        var _this = _possibleConstructorReturn(this, (Scroll.__proto__ || Object.getPrototypeOf(Scroll)).call(this, domNode));

                        _this.emitter = config.emitter;
                        if (Array.isArray(config.whitelist)) {
                            _this.whitelist = config.whitelist.reduce(function(whitelist, format) {
                                whitelist[format] = true;
                                return whitelist;
                            }, {});
                        }
                        // Some reason fixes composition issues with character languages in Windows/Chrome, Safari
                        _this.domNode.addEventListener('DOMNodeInserted', function() {});
                        _this.optimize();
                        _this.enable();
                        return _this;
                    }

Answer 11 · 2023-09-15T13:12:44.000Z

The line _this.domNode.addEventListener('DOMNodeInserted', function () {}); appears to be a workaround to trigger some internal logic in response to changes in the DOM when new nodes are inserted into _this.domNode. However, the empty function doesn't actually perform any meaningful action.

An equivalent using MutationObserver will be something like this:

var observer = new MutationObserver(function () {});
observer.observe(_this.domNode, { childList: true });

childList when set to true, indicates that the observer should monitor changes to the direct children (added or removed nodes) of the target node.

I tried this and the warning is gone. Apparently all works as expected.

Answer 12 · 2023-10-03T01:40:31.000Z

same problem

Answer 13 · 2023-10-13T07:51:32.000Z

Hello. Tell me, is there a plan to fix this error?

Answer 14 · 2023-10-13T08:33:05.000Z

The solution would be to upgrade to version 2 of quill, but it hasn't been released yet slab/quill#3806

Answer 15 · 2023-10-16T08:35:34.000Z

The problem is we have no updates on the promised version 2 of Quill. Just use Tiptap instead

Answer 16 · 2023-10-16T15:51:39.000Z

The problem is we have no updates on the promised version 2 of Quill. Just use Tiptap instead

Your suggestion is to replace quill throughout the project?

Answer 17 · 2023-11-04T18:29:01.000Z

There should be an update soon, the developer hoping to release a beta before December.
slab/quill#3896

Answer 18 · 2023-11-23T06:15:11.000Z

[Deprecation] Listener added for a synchronous DC" Mutation Event. This event type is deprecated quill..
and work is underway to remove it from this browser. usage of this event listener will cause performance issues today, and represents a risk of future incompatibility. consider using
MutationObserver instead ......Unable to perform some functionality because of this! An update or help would be helpful

Answer 19 · 2023-12-03T09:38:09.000Z

quilljs/quill#3806 update quill to 2.0.0

只能等待了……

Answer 20 · 2023-12-25T14:03:32.000Z

still no update to quill. I'm using tiptap but you have to import almost everything.

Answer 21 · 2023-12-29T21:55:55.000Z

Hello guys, any update on when is the new version release going to happen and is this issue with the mutation going to be fixed?

Answer 22 · 2023-12-30T04:30:06.000Z

Hey guys also waiting for the update.

Answer 23 · 2024-01-04T02:21:39.000Z

The line _this.domNode.addEventListener('DOMNodeInserted', function () {}); appears to be a workaround to trigger some internal logic in response to changes in the DOM when new nodes are inserted into _this.domNode. However, the empty function doesn't actually perform any meaningful action.

An equivalent using MutationObserver will be something like this:
var observer = new MutationObserver(function () {});
observer.observe(_this.domNode, { childList: true });
childList when set to true, indicates that the observer should monitor changes to the direct children (added or removed nodes) of the target node.

I tried this and the warning is gone. Apparently all works as expected.

This method works. Thank you!

Answer 24 · 2024-01-04T13:27:23.000Z

Hey everyone, still waiting for fixes in the new version of react-quill.. is there any updates.. on when this error is going to be fixed "[Deprecation] Listener added for a synchronous 'DOMNodeInserted' DOM Mutation Event."

Answer 25 · 2024-01-09T12:03:05.000Z

Hey everyone, still waiting for fixes in the new version of react-quill.. is there any updates.. on when this error is going to be fixed "[Deprecation] Listener added for a synchronous 'DOMNodeInserted' DOM Mutation Event."

I thought you found the solution?

Answer 26 · 2024-01-09T13:37:50.000Z

Hey I am also facing this error let us know if someone find the solution for this.

Answer 27 · 2024-01-11T23:08:19.000Z

same here, standing in line and waiting.

Answer 28 · 2024-01-16T06:55:42.000Z

iListener added for a synchronous 'DOMNodeInserted' DOM Mutation Event. This event type is deprecated (https://w3c.github.io/uievents/#legacy-event-types) and work is underway to remove it from this browser. Usage of this event listener will cause performance issues today, and represents a risk of future incompatibility. Consider using MutationObserver instead.

i have the same problem
Any solution now？

Answer 29 · 2024-01-19T09:17:24.000Z

I met the same prompt. Not sure what the impact is.

Answer 30 · 2024-01-22T08:30:29.000Z

me too i have same issue

Answer 31 · 2024-01-22T12:00:44.000Z

Hi 👋

I'm the maintainer of Quill, and we just released the second beta version of Quill 2.0. This version is considered feature-complete, and I wanted to know if there's anything I can do to help the transition to Quill 2.0.

There are many performance improvements made in Quill 2.0 and the dev/beta version has already been running on Slab for more than one year without any major issues. The version also avoids Mutation Event at all so should solve the issue.

We are still working on the documentation and examples, but https://v2.quilljs.com/ already contains useful info for upgrading to 2.0.

Answer 32 · 2024-01-23T07:49:25.000Z

@luin i want to know this plugin vue-quill is maintained by you This plugin doesn't seem to introduce quill 2.0 . How to solve it？

Answer 33 · 2024-01-24T23:41:13.000Z

i'm using react-quill v2.0 warning message still appear

Answer 34 · 2024-01-25T01:25:18.000Z

@GisungJung react-quill v2.0 uses Quill v1 so that's the reason you still saw the warning.

Answer 35 · 2024-01-29T04:14:23.000Z

@GisungJungReact-quill v2.0 使用 Quill v1，所以这就是您仍然看到警告的原因。

When to upgrade React Quill built-in Quill to Quill2？

Answer 36 · 2024-02-04T19:56:13.000Z

Find this line

_this.domNode.addEventListener('DOMNodeInserted', function () {});

Select it and replace with

    let observer = new MutationObserver(function (mutations) {
        //mutations.forEach(function (mutation) {
        // Обработка изменений в DOM
        //console.log(mutation);
        //});
    });

    // Настройка на отслеживание изменений в документе
    let observerConfig = {childList: true, subtree: true};
    observer.observe(_this.domNode, observerConfig);

Answer 37 · 2024-02-24T02:08:36.000Z

Any updates here?

Answer 38 · 2024-02-25T00:13:04.000Z

I'm facing the same problem, even with quill updated to version 2.0.0, I tried a few things, but without success

Answer 39 · 2024-02-27T02:20:42.000Z

Solution:

Find this line: _this.domNode.addEventListener('DOMNodeInserted', function () {}); let observerConfig = {childList: true, subtree: true};
Select it and replace with:
observer.observe(_this.domNode, observerConfig);
_this.optimize();
_this.enable();
return _this;
}

Answer 40 · 2024-02-27T10:45:39.000Z

Solution:

Find this line: _this.domNode.addEventListener('DOMNodeInserted', function () {}); let observerConfig = {childList: true, subtree: true};

Select it and replace with:
observer.observe(_this.domNode, observerConfig);
_this.optimize();
_this.enable();
return _this;
}

It's working for me, Thanks!

Answer 41 · 2024-02-27T11:06:53.000Z

Solution:

Find this line: _this.domNode.addEventListener('DOMNodeInserted', function () {}); let observerConfig = {childList: true, subtree: true};

Select it and replace with:
observer.observe(_this.domNode, observerConfig);
_this.optimize();
_this.enable();
return _this;
}

and do you want to update this manually every time you clone a project?

Answer 42 · 2024-02-28T16:05:56.000Z

Solution:

Find this line: _this.domNode.addEventListener('DOMNodeInserted', function () {}); let observerConfig = {childList: true, subtree: true};

Select it and replace with:
observer.observe(_this.domNode, observerConfig);
_this.optimize();
_this.enable();
return _this;
}

and do you want to update this manually every time you clone a project?

you could possibly make a patch but that's really not the right way to do it. The package author should include this fix!

Answer 43 · 2024-02-28T17:27:39.000Z

I ended up using quill core library and creating my own component. I know is not the best thing around, but at least works.

If someone uses, remember to copy the quill css styles and snow theme to laravel webpack/vite css compiler.

TextEditor.txt

Answer 44 · 2024-03-07T06:14:02.000Z

[Deprecation] Listener added for a synchronous 'DOMNodeInserted' DOM Mutation Event. This event type is deprecated () and work is underway to remove it from this browser. Usage of this event listener will cause performance issues today, and represents a risk of future incompatibility. Consider using MutationObserver instead. Any solution for this I am using it in NextJS

Answer 45 · 2024-04-03T02:27:05.000Z

the message disappears now after using 2.0.0

<!-- <script defer src="https://cdn.quilljs.com/1.3.6/quill.js"></script> -->
<script defer src="https://cdn.jsdelivr.net/npm/quill@2.0.0-rc.4/dist/quill.js"></script>

Answer 46 · 2024-04-18T14:22:09.000Z

With the release of Quill 2.0 (https://github.com/quilljs/quill/releases/tag/v2.0.0), will this library be updated to support it?

Answer 47 · 2024-04-29T18:59:52.000Z

I'm facing this same warning in my React application. Any expected fix for this problem?

Answer 48 · 2024-04-30T00:25:56.000Z

@Wellitonzs For React you can use Quill without a library/framework: https://quilljs.com/playground/react

Answer 49 · 2024-05-13T12:25:37.000Z

For Vue 3 and Quill 2 you could try this simple wrapper component: https://github.com/alekswebnet/vue-quilly

Answer 50 · 2024-05-14T09:27:03.000Z

Исправьте это говно 💩

Answer 51 · 2024-06-09T11:24:44.000Z

Just go to your terminal and install the latest version of quill
Then go to your package.json and add:
"overrides": {
"quill": "^2.0.2"
}

Then uninstall @vueup/vue-quill package
Then install it again.
The error will be resolved

Answer 52 · 2024-06-09T15:43:39.000Z

@Sky-Breaker07 : Thanks for the tip. It worked as expected! Saved me a lot of work forking and changing vue-quill.

Answer 53 · 2024-07-03T21:47:00.000Z

I would like to update to quill 2 but It's too buggy. :/

Answer 54 · 2024-07-06T05:03:50.000Z

Just go to your terminal and install the latest version of quill Then go to your package.json and add: "overrides": { "quill": "^2.0.2" }

Then uninstall @vueup/vue-quill package Then install it again. The error will be resolved

didnt work

added to npm/package.json overrides block does error on audit fix

# npm audit
npm error code EOVERRIDE
npm error Override for quill@2.0.2 conflicts with direct dependency
npm error A complete log of this run can be found in: /_logs/2024-07-06T04_54_41_286Z-debug-0.log

even with "overrides": { "quill": "2.0.2" } or edit dependencies block to "quill": "^2.0.2" didnt do the trick

after fresh install vue-quill error is still here (damn) and in dependencies we see quill 1.3.7

Answer 55 · 2024-09-04T12:14:13.000Z

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.