Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TypeError: Object doesn't support property or method 'next' in IE browser #461

Open
malicansoundar opened this issue Nov 22, 2019 · 10 comments

Comments

@malicansoundar
Copy link

When we try to play video content in IE we are getting the below error.
Can someone help me to close this issue?
issue-shim-git

@ljharb
Copy link
Collaborator

ljharb commented Nov 22, 2019

Can you share the code at line 438 in ima3.js, where it's presumably calling Array.from?

Even better, could you use the debugger or console.log and figure out exactly what arguments are being passed to it?

@malicansoundar
Copy link
Author

Hi @ljharb,

Thank you. I debugged the code as suggested and found the below line is causing the issue in ima3.js

bw = function () {
var a = (window.location.origin || "null").trim(), b = "null" === a, c = window == window.top, d = !1;
try {
d = null != window.top.location.hostname;
}
catch (f) {
}
var e = null != Array.from(document.body.getElementsByTagName("script")).find(function (f) {
return f.src && f.src.includes("connatix");
});
Ps.B().report(121, { location: Pv(), top_origin: Qv(), origin: a, is_null: b, is_top: c, is_friendly_to_top: d, is_vpaid_adapter: W.zb(), is_connatix_player: e });
};

@malicansoundar
Copy link
Author

Could you please help us in resolving this?
We have a production bug regarding this and our application has failed to launch.

@ljharb
Copy link
Collaborator

ljharb commented Nov 25, 2019

Specifically it looks like Array.from(document.body.getElementsByTagName("script")); can you confirm that running that code in the console reproduces the same error?

Which version of IE is this? It works fine for me in IE 10 and 11 on the es6-shim test page, for example.

Are you sure you're not loading any other polyfills, like babel-runtime/core-js?

@malicansoundar
Copy link
Author

can you confirm that running that code in the console reproduces the same error? - Yes, we are getting the same error when we use it in the console log.

Which version of IE is this? - IE11

Are you sure you're not loading any other polyfills, like babel-runtime/core-js? Yes, we are using the below dev dependency. So that it will automatically add babel-runtime/core-js.

Please help us with what has to do?

"@uirouter/angularjs": "^0.2.18",
"angular": "~1.5.0",
"angular-animate": "~1.5.0",
"angular-cookies": "~1.5.0",
"angular-messages": "~1.5.0",
"angular-resource": "~1.5.0",
"angular-route": "~1.5.0",
"angular-sanitize": "~1.5.0",
"angular-socialshare": "^2.3.11",
"angular-timer": "^1.3.4",
"angular-touch": "~1.5.0",
"es6-shim": "^0.35.1",
"humanize-duration": "^3.20.1",
"jquery": "^3.4.1",
"moment-timezone": "^0.5.11",
"ng-device-detector": "^3.0.1",
"re-tree": "^0.1.7",
"slick-carousel": "~1.4.1",
"underscore": "^1.9.1"

@malicansoundar
Copy link
Author

@ljharb
Copy link
Collaborator

ljharb commented Nov 28, 2019

core-js and es6-shim are never intended to be used together; they do the same things. If you can’t avoid using babel-runtime, you’ll need to use a bundler to omit core-js if you want to use es6-shim.

@ljharb
Copy link
Collaborator

ljharb commented Nov 28, 2019

The polyfills on MDN are not production quality and should never be used.

@adhavanUI
Copy link

Can you please share any helpful document or link to create bundler for omit core-js in angular

@ljharb
Copy link
Collaborator

ljharb commented Jan 3, 2020

It depends on what bundler you're using; webpack and browserify each have their own docs and tutorials all over the web.

Typically only the top-level app would be pulling in core-js or es6-shim tho; are you sure your own code isn't doing it?

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

No branches or pull requests

3 participants