Unhandled JS exception in main.js:1068 in IE11

[michaelklishin]

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]

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]

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.

[Michael-Ekkert]

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" <[email protected]mailto:[email protected]> 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]

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

[michaelklishin]

Fixed in #99, will be in 3.6.1.