devtools: Uncaught ReferenceError: o is not defined

When simulating mobile devices…Long press a button, tools report error about a second later.

Edit: Or right click and it immediately report the error

    document.addEventListener("contextmenu", t=>{
        const n = t.target;
        if (n) {
            const t = Object(o.a)(n); // here
            if (t)
                return e.__VUE_DEVTOOLS_CONTEXT_MENU_HAS_TARGET__ = !0,
                void (e.__VUE_DEVTOOLS_CONTEXT_MENU_TARGET__ = t)
        }
        e.__VUE_DEVTOOLS_CONTEXT_MENU_HAS_TARGET__ = null,
        e.__VUE_DEVTOOLS_CONTEXT_MENU_TARGET__ = null
    }
    )

Version

4.0.0

Browser and OS info

Chrome 63/ Win 10 FCU

Steps to reproduce

1.Long press a button 2.report error

What is expected?

No mistake

What is actually happening?

report error

About this issue

Original URL
State: closed
Created 6 years ago
Reactions: 12
Comments: 31 (12 by maintainers)

Most upvoted comments

4.1.1 has been pushed to chrome web store, it should be live any time.

+16

yyx990803 on Jan 25, 2018

@f3l1x, the fix should come in the next version.

+16

anteriovieira on Jan 24, 2018

Thanks for the fix @Akryum! This issue also affected the extension on Firefox and it is now fixed as well.

Please ignore the complainers. Users need to understand that any time they install an extension and grant permission to inject javascript on any page, they are opening 3rd party sites up to breakage. That’s not on you at all. Developers should know better.

hackel on Jan 25, 2018

I cannot send an email to all my users and tell them about the plugin. I don’t even have their contact data.

Why don’t you have any mean of supporting your users?

Akryum on Jan 25, 2018

@Akryum After your fix in #528, I’ve also seen this, the first time Vue-Devtools is run.

This can now be seen in the same sample here (the same url sample in #528). This seems to happen only the first time Vue-Devtools is initialized.

Steps to reproduce

Install Vue-Devtools from this branch https://github.com/Akryum/vue-devtools/tree/types-improvements
Closed all developer tools windows (where vue-devtools is in)
Click this url to open the sample project in CodeSandbox

Sometimes this error pops right away on the page. Sometimes you need to click on the page a few times and it will display the error instead of the rendered content. In one of my project, it displays in the developer tools’ console window.

When reloading the page the second time (without closing Vue-devtools), the error is gone.

ratiw on Jan 20, 2018

4.1.1 is out, not experiencing this bug anymore on my end (user agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36). Thanks for fixing this!

candu on Jan 25, 2018

@anteriovieira This can happen even if the devtools are not open.

Akryum on Jan 25, 2018

I have this issue on pages where Vue isn’t loaded at all, so not sure why the plugin is listening.

TheDutchCoder on Jan 24, 2018

Confirm, it’s fixed for my and NW.js environment.

f3l1x on Jan 28, 2018

Seems to be related to the contextual menu that displays the “inspect vue component” with latest Vue.js, I’m installing it and it’s fresh, also having the issue.

tribakzero on Jan 24, 2018

@Akryum After revisit it again, it actually happens when I “right-click” the window.

Please see the attached gif.

vue-devtools-error

ratiw on Jan 21, 2018