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
Starting from Firefox 100 a deprecation warning is shown in the browser console when an Ember app is opened. The InstallTrigger global is deprecated and Ember seems to still use it for browser detection.
More information about the deprecation can be found in the bugzilla issue.
It doesn't seem like they give a clear way forward for the UA Agent detection use-case. I also haven't taken a detailed look at the code yet but it seems that these browser constants are used for working around older browser behaviors which might no longer be relevant with the new browser support policy?
@kirtan-desai hey sorry for resurrecting this thread but the same issue happens with any GO/WASM app on FireFox as well, and I don't understand what's going on here and I was hoping you might know how to fix this as well, probably the same solution?
I am seeing this in chrome, as well. Chrome Version 126.0.6478.127 (arm64) Ember v4.12.
Looking at my installation, I see that InstallTrigger is used in the latest version of 'terser', which is included in the latest version of ember-cli-terser, so it looks like there is no way to avoid this warning in Ember.
🐞 Describe the Bug
Starting from Firefox 100 a deprecation warning is shown in the browser console when an Ember app is opened. The
InstallTrigger
global is deprecated and Ember seems to still use it for browser detection.More information about the deprecation can be found in the bugzilla issue.
It doesn't seem like they give a clear way forward for the UA Agent detection use-case. I also haven't taken a detailed look at the code yet but it seems that these browser constants are used for working around older browser behaviors which might no longer be relevant with the new browser support policy?
🔬 Minimal Reproduction
🌍 Environment
➕ Additional Context
https://bugzilla.mozilla.org/show_bug.cgi?id=1754441
The text was updated successfully, but these errors were encountered: