-
Notifications
You must be signed in to change notification settings - Fork 8
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
MapTable doesn't work in IE11 #7
Comments
I just tried it on BrowserStack: I get this error: Will dive more on this later |
Never mind! No rush on this now. We'll need it some day, but not just yet. Thanks! |
The link that you provided is very specific to his use case. There's no onLoad attribute in MapTable. |
Hey again! PCH has prioritized deploying maptable on our IXP Dir home page. There's no rush on this! We'll be spinning up an Windows VM with IE to dive into this henceforth. |
progress! i ran ie11 against the non-minified version. The line it's having problems with function extendRecursive() {
var dst = {};
var src = void 0;
var p = void 0;
var args = [].splice.call(arguments, 0);
while (args.length > 0) {
src = args.splice(0, 1)[0];
if (toString.call(src) === '[object Object]') {
for (p in src) {
if (src.hasOwnProperty(p)) {
if (toString.call(src[p]) === '[object Object]') {
dst[p] = extendRecursive(dst[p] || {}, src[p]);
} else {
dst[p] = src[p];
}
}
}
}
}
return dst;
} so, armed with that detail, it looks like this stack exchange post might be the answer:
i'll dive in and see if there's not a fix somewhere in here! |
Change this line:
to:
|
yay! adding However now, see the filters don't work :( . The error is in
I'm diving into it now! |
Same here, replace |
yay! that did it. now if I can just figure how to commit the changes. see my comment on #11 |
next up! Clicking "remove filter" results in an error on line 99 of
Line 98 is:
|
you can use this: |
Heya! I think we decided that <IE11 won't be supported. However, none of the demos hosted on blocks.org (eg Basic Map - Custom markers) work in modern.ie's latest IE11 VM.
The text was updated successfully, but these errors were encountered: