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
IE 11 testing/serving fails with i18n in es5 JIT mode with 9.0.0-rc.4 #34246
Labels
regression
Indicates than the issue relates to something that worked in a previous version
type: bug/fix
Milestone
Comments
12 tasks
I suspect the problem is this line here
In JIT mode this is being output for evaluation. |
petebacondarwin
added a commit
to petebacondarwin/angular
that referenced
this issue
Dec 6, 2019
Previously the JIT evaluated code for ivy localized strings included backtick tagged template strings, which are not compatible with ES5 in legacy browsers such as IE 11. Now the generated code is ES5 compatible. Fixes angular#34246
petebacondarwin
added a commit
to petebacondarwin/angular
that referenced
this issue
Dec 6, 2019
Previously the JIT evaluated code for ivy localized strings included backtick tagged template strings, which are not compatible with ES5 in legacy browsers such as IE 11. Now the generated code is ES5 compatible. Fixes angular#34246
gkalpak
pushed a commit
to gkalpak/angular
that referenced
this issue
Dec 6, 2019
Previously the JIT evaluated code for ivy localized strings included backtick tagged template strings, which are not compatible with ES5 in legacy browsers such as IE 11. Now the generated code is ES5 compatible. Fixes angular#34246
petebacondarwin
added a commit
to petebacondarwin/angular
that referenced
this issue
Dec 6, 2019
Previously the JIT evaluated code for ivy localized strings included backtick tagged template strings, which are not compatible with ES5 in legacy browsers such as IE 11. Now the generated code is ES5 compatible. Fixes angular#34246
petebacondarwin
added a commit
to petebacondarwin/angular
that referenced
this issue
Dec 6, 2019
Previously the JIT evaluated code for ivy localized strings included backtick tagged template strings, which are not compatible with ES5 in legacy browsers such as IE 11. Now the generated code is ES5 compatible. Fixes angular#34246
josephperrott
pushed a commit
to josephperrott/angular
that referenced
this issue
Dec 11, 2019
…de (angular#34265) Previously the JIT evaluated code for ivy localized strings included backtick tagged template strings, which are not compatible with ES5 in legacy browsers such as IE 11. Now the generated code is ES5 compatible. Fixes angular#34246 PR Close angular#34265
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
kara
added
regression
Indicates than the issue relates to something that worked in a previous version
and removed
severity5: ivy-compat
labels
Feb 11, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
regression
Indicates than the issue relates to something that worked in a previous version
type: bug/fix
🐞 bug report
Affected Package
Not sure, but looks like @angular/localization or compiler doesn't play well with JIT and
target: es5
(see below)Is this a regression?
Yes, latest Angular 8 works fine.
Description
Testing and serving fails in IE 11 with es5 target in JIT mode with i18n
🔬 Minimal Reproduction
Steps:
9.0.0-rc4
i18n
attribute anywhere in a component templateng add @angular/localize
target
toes5
ng test
orng serve
(in JIT mode withaot: 'false'
)Repo to clone with the steps above → https://github.com/maxokorokov/ie-i18n-test-fail
🔥 Exception or Error
If you dig deeper it fails here:
and component code looks like this:
To me looks like the reason is back quotes in
I18N_0 = $localize ...
callHaven't checked IE 10 and 9
🌍 Your Environment
Angular Version:
The text was updated successfully, but these errors were encountered: