You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
On a new bare-bones Ember app, if the user uses the Chrome "Translate to " option on the page and then does something that renders an FA icon, a console error is shown and the icon isn't rendered.
Reproducible test case
ember new translate-test
Modify package.json and add "@fortawesome/ember-fontawesome": "^0.2.1" and "@fortawesome/free-brands-svg-icons" as devDependencies.
Modify environment.js to include fontawesome: {icons: {'free-brands-svg-icons': ['google']}} in the ENV hash.
Expected behavior
The expected behavior is that the icon shows without error. If you load the page without translating, it works fine. It's only an issue if you translate the page first.
Desktop (please complete the following information):
Windows 10, Chrome, 85.0.4183.83 Browser
Additional context
Using the latest Ember 3.20 build.
The text was updated successfully, but these errors were encountered:
Describe the bug
On a new bare-bones Ember app, if the user uses the Chrome "Translate to " option on the page and then does something that renders an FA icon, a console error is shown and the icon isn't rendered.
Reproducible test case
ember new translate-test
package.json
and add"@fortawesome/ember-fontawesome": "^0.2.1"
and"@fortawesome/free-brands-svg-icons"
as devDependencies.environment.js
to includefontawesome: {icons: {'free-brands-svg-icons': ['google']}}
in theENV
hash.application.hbs
to include the following:Here's a video of the steps in the browser: https://recordit.co/tDCGmmOQJn
Expected behavior
The expected behavior is that the icon shows without error. If you load the page without translating, it works fine. It's only an issue if you translate the page first.
Desktop (please complete the following information):
Additional context
Using the latest Ember 3.20 build.
The text was updated successfully, but these errors were encountered: