Skip to content
This repository has been archived by the owner on Sep 20, 2019. It is now read-only.

Object doesn't support property or method 'call' on IE11 #830

Closed
19jake68 opened this issue Aug 18, 2017 · 11 comments
Closed

Object doesn't support property or method 'call' on IE11 #830

19jake68 opened this issue Aug 18, 2017 · 11 comments
Assignees

Comments

@19jake68
Copy link

19jake68 commented Aug 18, 2017

Description:
I update my webcomponentjs from v1.0.7 to v1.0.8 then after trying to run my polymer app, I encountered the error on the screenshot below.

My app works well on IE11 with webcomponentjs 1.0.7, and I encountered this yesterday after updating to 1.0.8.

Screenshot:
image

@19jake68 19jake68 changed the title Object doesn't support property or method call on IE11 Object doesn't support property or method 'call' on IE11 Aug 18, 2017
@gigmania
Copy link

gigmania commented Sep 7, 2017

Did you find a fix for this? I am getting the same error.

@jab
Copy link

jab commented Sep 12, 2017

FWIW I recently deployed a fresh PSK2 site to https://uproxy.github.io/uproxy.org/, ended up with webcomponentsjs v1.0.10 (latest release at time of writing), and am getting a similar error (SCRIPT438: Object doesn't support property or method 'values'):

screen shot 2017-09-12 at 16 19 18

@snuggs
Copy link

snuggs commented Sep 13, 2017

FWIW We have been getting the same error as well and didn't realize it until doing some Browserstack testing recently. /cc @brandondees @robcole

@dfreedm dfreedm self-assigned this Sep 13, 2017
@dfreedm
Copy link
Contributor

dfreedm commented Sep 13, 2017

I think I need a bit more information here. Did you deploy with polymer build, and if so, at what version?

@dfreedm dfreedm added the bug label Sep 13, 2017
@notwaldorf
Copy link
Contributor

notwaldorf commented Sep 13, 2017

@azakus we're seeing it on tests too, if it helps, but with "Object doesn't support property or method 'catch'". Poor Object, so unsupportive.

(the iron-form test was green before i re-ran it as a sanity check)

@dfreedm
Copy link
Contributor

dfreedm commented Sep 13, 2017

Thanks. I couldn't get this to reproduce with a simple element, so it must be related to some element or elements use of an API.

@ernsheong
Copy link

I'm seeing this in Edge 15
image

But oddly it only happens in development environment... 🤷‍♂️ And it proceeds to load a whole bunch of development dependency stuff:

image

Oddly staging/production build is fine, but I have no idea what made the difference.

@dfreedm
Copy link
Contributor

dfreedm commented Dec 14, 2017

It looks like this can happen when the developer tools are open in IE, as it adds some sort of FunctionWrapper object as an event listener, which is neither callable nor has a handleEvent object.

The check in event handling assumes that if an object doesn't have a handleEvent method that is is a callable function.

@cwenzelg
Copy link

We experience the same Problem with Version 1.0.20. The Page also is not loading even with a closed developer tool. We also get additional 2 Syntax Errors for webcomponents-lite.js. Sometimes the IE 11 Crashed because the script keeps running. Firefix, Edge, Chrome all work fine.
IE Version is: 11.98.16299.0

@dfreedm
Copy link
Contributor

dfreedm commented Dec 14, 2017

@cwenzelg that sounds like perhaps a different issue if you're seeing syntax errors.

@cwenzelg
Copy link

The fix worked, the new Version 1.0.21 fixed that issue for me. (well not the Syntax Error) but the call error. thank you

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants