If you have extra questions about this answer, please click " If the answer is the right solution, please click "
This is a known problem.įor more javascript questions, please add such tags for more expert help. So, you will need to adjust your Javascript in such a manner that it will have a fallback logic for the data that will no longer be available and will apply the changes necessary where the data will be available even after the change. That means that lots of stuff that you use now will no longer be available after a certain update. Basically there will be limitations in the user agent string. The article is likely covering most (or all) the problems you need to solve. Read some articles about the issue, like this one: Search for all of these in the entire codebase and detect all lines that refer to any of these. The warning message tells you that you use some deprecated resources, namely "If your site, service, library or application relies on certain bits of information being present in the User Agent string such as Chrome minor version, OS version number, or Android device model, you will need to begin the migration to use the User Agent Client Hints API instead."
"Beginning in M92, we plan to start sending deprecation notices for the erAgent, navigator.appVersion, and atform getters in the DevTools Issues tab." It's one of the libraries that is using navigator features that Chrome is deprecating. What version of Google Chrome are you using? For some newer versions, there are these warnings. To fix this issue, replace the usage of erAgent, navigator.appVersion, and atform with feature detection, progressive enhancement, or migrate to erAgentData. In a future version of Chrome, the amount of information available in the User Agent string will be reduced. A page or script is accessing at least one of erAgent, navigator.appversion, and atform.
0 kommentar(er)
