“TypeError: Illegal invocation” when trying to upgrade from v1.2

后端 未结 1 2023
天涯浪人
天涯浪人 2021-02-07 06:26

Edit: It seems that this could be related to Chrome v43, I downgraded to v42 and everything works fine.

Edit: I\'ve submitted an issue

1条回答
  •  名媛妹妹
    2021-02-07 06:50

    Between the angular-issue, the chromium-bug, the webkit-bug and the (I dont even know what this is) something-Webkit-issue it would appear as if everyone (well, mostly everyone) is throwing their hands in the air. Perhaps I'm being judgemental/plain wrong in saying that.

    Anyway, I wasn't able to get the window.history.back case to log without causing an Illegal Invocation but I was able to do console.log.call(window, 'x') with the following 'snippet:'

    (function() { console.log = console.log.bind(console); }());
    

    (taken straight off of the last link there, thanks Brian!)

    Just slap that out in the top of your HTML document/wherever you want (I guess).


    I'm super curious as to what would happen if you were to run that @Ignas. I cannot seem to replicate the issue you are presenting with a Factory binding to $scope and running that $interval of yours.

    Would love to see if it holds any effect (albeit, not a functional one but more so a decorative one, I suppose).

    Sidenote; Me being the newbie I am, I was just informed by my peers that console.log.call(window) shall indeed throw an Illegal Invocation error, so that is a non-issue afaic. Still curious as to if this would hold effect on the logFn inside Angular.

    0 讨论(0)
提交回复
热议问题