Problem with IE11 - JS error Expected ':'

Getting help Issues
1

Hi,
we implemented your library for one of our client ( looks like : Handsontable example - JSFiddle - Code Playground ). They reported an issue, that its not working properly on IE11 (table is not shown and it throws JS error) . We tested it in IE11 and we also tried change to same version of IE11 but everything works fine on ours computers. Error is shown below, but note that I had to change document mode in IE11 to IE8 to simulate an issue. It is similar problem as this one : javascript - What does it do when a method definition inside an object literal is prefixed by the `get` keyword? - Stack Overflow . What can causing this issue?

error.PNG1662×219 15.8 KB

Martin

2

Thanks for sharing @matho285
I tried IE11 and the table successfully loaded.
I’ll mark this issue to be checked by our programmers.

3

HI @matho285, Handsontable doesn’t support IE 8 and below. That is why error occurs. We support all IE versions greater or equal than 9, see our compatibility page.

4

I tried it too in IE11 and it worked. But our client have this problem on their computers with IE11. Could it be some browser settings?

5

Hi @budnix,

i know that it doesn’t support IE8. I just showed the problem in IE8 (because I can’t get that error on our computers in IE11), but for our client it occurs in IE11. That’s mystery I am trying to solve.

6

Hi @matho285 IE seems to be always following its own path.

If your customer should share any additional details about the system version/custom settings etc. it would be very helpful.

Like you rightly noted before - it’s hard to fix or even track something that you can’t reproduce in the same browser that it was spotted.

7

Maybe try to run this updated fiddle (unminified version of Handsontable) on client browser. If error still occurs it will be easier to compare with error line in unminified code.

8

Hi @aleksandra_budnik,

I’ll try to get some additional information.

9

Okay, I’ll send them link and we will see what happen. I’ll let you know.

10

Hi @matho285
Is the any progress? Did you maybe had a time to check @budnix solution?

11

Hi, it seems that it is our client configuration problem. The page was viewed in IE document mode using IE11 as browser. We don’t know why they have this setting, but we also figured out missing meta-tag “X-UA-Compatible”. After that we don’t have an opportunity to send them repair build, so I did’nt reply here. But it seems like browser configuration problem, so this topic can be closed.

Thanks for yor help.

Martin

12

Thank you for update @matho285
I’m closing this issue.