SCRIPT1014: Invalid character cart, line 57 character 29 - IE 10

[sma09sjb]

Preconditions

1. Windows 7 IE 10, Magento 2.1.1

Steps to reproduce

1. Add a product to cart and try and expand the shipping section
2. Multiple js errors being thrown in totals.js and cart.js

Expected result

1. Shipping area should be expanded

Actual result

1. 

1. loading gif never disappears

[veloraven]

@sma09sjb thank you for your feedback.
Magento does not support the operating system you've listed. Please confirm that you can reproduce this issue on a supported platform. For an overview of supported technologies, see System Requirements.

[sma09sjb]

Where can i find a complete list of your supported OS? By that do you mean you don't support IE 10 or Windows 7?

I've tried the same in WIndows 8 IE 10 and i'm getting the same results.

[JDavidVR]

@veloraven uhmm but this is on browser side (is not development environment), I don't think is a valid argument say magento doesn't support windows, because many (potential) client use windows as theirs desktop OS.

[sma09sjb]

@veloraven i'm also slightly confused by your comment, can you clarify your meaning.

[veloraven]

@sma09sjb I was sure I had added the link to requirements, sorry for inconvenience. Here you are: System Requirements.
I also thought that you mentioned OS of the server (as it usually happens), and did not realize that it was about customer's system.
@JDavidVR thank you for noting this point.

[sma09sjb]

Hi @veloraven unfortunately that link isn't working for me, i'm assuming it's purely for internal use.

This error occurred on a customer environment we were using to test our site.

Can you confirm this is a Magento bug and if so when i can expect some resolution?

Thanks,

Sophie

[odubovyk]

Supported browsers can be found here , and we support IE9-10-11 on Storefront.
On current develop this issue is fixed.

[veloraven]

@sma09sjb sorry once more - my mistake, there was a wrong link. I have updated it, it should open normally now.
And yes, we took it as an issue, internal ticket for Magento 2.1 - MAGETWO-60293

[debuysserk]

Hi guys, is this effectively fixed? Could you point us to the correct commit in the develop branch so we can try to cherry pick it to our project?

Thanks.

[veloraven]

@debuysserk you can find reference for the fixing commit for develop branch in #5358.

[korostii]

you can find reference for the fixing commit for develop branch

@veloraven Is there any chance we can get these releases on a separate stable branch other than develop? IMHO that's quite simple to implement and would effectively allow to get these fixes in a timely manner using composer.
Both using develop branch on production and forking the magento2 repository in order to be able to cherry-pick the selected bugfix commits seem like risky and hacky workarounds. If there is any other cleaner solution I would also be happy to try it out.

That is, if the current turtle pace of releasing bugfix versions once per 6 months continues (my frustration from which I have already expressed on a different issue)
Additionally, seeing some bugfixes to somehow miss even this slow schedule and get pushed back to the next release, like in this very case (see f3d7952 ) is just jaw-dropping.

An even more dramatic example can be seen here: #7985. That bug, it seems, was earlier reported in #5352, same day "fixed on develop", later on reported again in duplicate issues at least 5 times by different people, still not released to 2.1 branch and now it's " targeted against the 2.1.5 release for early next year". Like, seriously? Seriously?
I'd like to quote a related comment from one of those threads:

It's disappointing. If anyone on the Magento team is reading this, please take some time to fix all know issues/bugs before releasing 2.1.3 or 2.2. It's just common sense to do so

Months later, seems as if nobody is reading this :(
See also another bug with a similar story: #3789
I understand that all the merging and QA stuff going on which might slow it down, I really do, but I am beginning to wonder whether such a workflow is really any good for the actual quality of the product.

[magento-engcom-team]

@sma09sjb, thank you for your report.
We were not able to reproduce this issue by following the steps you provided. If you'd like to update it, please reopen the issue.
We tested the issue on 2.3.0-dev, 2.2.0, 2.1.9