about MutationEvent

  • Resolved ikumackarel

    (@ikumackarel)


    7 months, 3 weeks ago

    The page below describes how to deal with the abolition of Chrome’s MutationEvent, but do you know about the support status of AIOSEO?
    When I searched the latest source, it seems that MutationEvent remains, but what do you think?

    https://developer.chrome.com/blog/mutation-events-deprecation

    (by Google Translate)

    一応日本語でも聞いておきますが、
    下記のページにて、ChromeのMutationEventの廃止における対応方法が記載されていますが、AIOSEOの対応状況についてご存知でしょうか？
    最新のソースを検索したところMutationEventが残っているようですがどうでしょうか???？

    https://developer.chrome.com/blog/mutation-events-deprecation

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author arnaudbroes

    (@arnaudbroes)

    Hey @ikumackarel,

    Thank you for reaching out.

    I don’t think we’re using MutationEvents anywhere in our code. As far as I know, we exclusively use MutationObservers.

    Can you tell me where you saw this is in our source code? It could be part of one of our dependencies.

    Thread Starter ikumackarel

    (@ikumackarel)

    Hi, Arnaud.
    Thank you for answering.

    Can you tell me where you saw this is in our source code? It could be part of one of our dependencies.

    of course.
    all-in-one-seo-pack/dist/Lite/assets/js/Editor.js
    It seems to be mentioned in the above file.
    I don’t know the details, but does this file have nothing to do with the behavior of the plugin?

    Plugin Author arnaudbroes

    (@arnaudbroes)

    Thanks for getting back to me!

    I just had a look, that file seems to me. It contains one instance of MutationObserver and none of MutationEvent. It also uses some object properties that are called mutations. I think we should be good but I’ll take another closer look at the plugin later just to make sure.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘about MutationEvent’ is closed to new replies.