Skip to content
This repository has been archived by the owner on Nov 17, 2020. It is now read-only.

Unhandled JS exception in main.js:1068 in IE11 #98

Closed
michaelklishin opened this issue Dec 30, 2015 · 5 comments
Closed

Unhandled JS exception in main.js:1068 in IE11 #98

michaelklishin opened this issue Dec 30, 2015 · 5 comments
Assignees
@michaelklishin
Labels
bug effort-tiny
Milestone
3.6.1

Comments

@michaelklishin
Copy link
Member

JS code around that line:

                 if (matches != null && matches.length > 1) {
                     for (item of contexts) {
                         if (matches[1].indexOf(item) == 0) {update_pages(item, 1)};
                     }
                 }

I'm not a JS exprt but the for(i of items) construct does look non-standard to me.
@michaelklishin michaelklishin added this to the 3.6.x milestone Dec 30, 2015
@michaelklishin michaelklishin mentioned this issue Dec 30, 2015
Closed
@michaelklishin
Copy link
Member Author

Reported by @Michael-Ekkert.

Does the same happen in Chrome on Windows?

for … of does seem to be fairly recent. Perhaps Array.prototype.forEach should be used instead.

@michaelklishin
Copy link
Member Author

Mozilla's docs don't even mention IE in the for … of compatibility table. Looks like Edge is the first browser to support it. So a workaround is to use Chrome or Edge.

@michaelklishin michaelklishin self-assigned this Dec 30, 2015
@Michael-Ekkert
Copy link

It works in chrome, just not IE11 which is company standard.

Thanks

Sent from my iPhone

On Dec 29, 2015, at 6:25 PM, "Michael Klishin" <notifications@github.commailto:notifications@github.com> wrote:

Mozilla's docs don't even mention EI for for … of. Looks like Edge is the first browser to support it. So a workaround is to use Chrome or Edge.

—
Reply to this email directly or view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_rabbitmq_rabbitmq-2Dmanagement_issues_98-23issuecomment-2D167904307&d=AwMFaQ&c=4aA2H3GyBw6it6SRFhMbbIJGKZA51o1h2BweFpsEY5k&r=r4TdAGcGHG4CylHqiq049JZSALSTkxt7aMFgrbgvlmM&m=4JEi6ogoL0u9V3rNGNqY1oZ4XNx5bYdFQFiEkgPEzD8&s=ZTkVoGZpif98zNZrEhMOvH7hBuVU29jkSFHtScFERow&e=.

@michaelklishin
Copy link
Member Author

Sure, we didn't intend to break IE compatibility.

@michaelklishin michaelklishin modified the milestones: 3.6.1, 3.6.x Dec 30, 2015
@michaelklishin michaelklishin mentioned this issue Dec 30, 2015
Merged
@michaelklishin
Copy link
Member Author

Fixed in #99, will be in 3.6.1.

This was referenced Jan 13, 2016
Closed
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@michaelklishin michaelklishin

Labels
bug effort-tiny
Projects
None yet
Milestone
3.6.1
Development

No branches or pull requests
2 participants
@michaelklishin @Michael-Ekkert