blocks|key|2932286|text|看看这个：http://www.w3schools.com/js/js_browser.asp|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2932287|使用javascript检测用户浏览器的-Easy方式。在那里，我只需使用switch语句或其他语句来显示尚未测试的浏览器的消息。如果你想要确切的浏览器版本，你必须从"navigator.userAgent“字段中解析它。|2932288|entityMap|0|LINK|mutability|MUTABLE|url|http://www.w3schools.com/js/js_browser.asp^0|5|16|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

Check out this: <a href="http://www.w3schools.com/js/js_browser.asp" rel="nofollow">http://www.w3schools.com/js/js_browser.asp</a>

-Easy way of detecting the user's browser with javascript. From there I'd just use a switch statement or something to display the messages for browsers that aren't tested yet. If you want the exact browser version you'll have to parse it from the "navigator.userAgent" field.

blocks|key|2932339|text|如果目标是完全验证，则需要更具体地说明版本。请记住，一些浏览器升级并不是100%25向后兼容以前的版本。(例如，看看IE9中的IE8模式与原生IE8呈现是如何不同的。)你将不得不重新测试每个新的浏览器版本，迟早会有一个“在浏览器版本X上完全测试，而没有在昨天发布的版本X%2B1上测试”的问题。功能检测、优雅降级以及在用户体验显著降级时以非侵入性方式向用户显示警告是一种更好的方式。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2932340|要直接回答您的问题，如果您必须实现所要求的内容，只需解析用户代理即可。这可能是很有用的，特别是你知道浏览器不能正常工作并发出警告，或者作为一个糟糕的内部网应用程序的创可贴，它对运行它的确切浏览器版本非常挑剔。对于一个新开发的应用程序，你可以控制需求，我不建议在浏览器版本上警告，因为有更好的方法来做到这一点。|2932341|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

If the goal is full validation, you need to be even more specific about versions. Keep in mind that some browser upgrades are not 100% backwards compatible with previous versions. (Look at how IE8 mode in IE9 is not the same as native IE8 rendering, for instance.) You're going to have to retest with every new browser version, and sooner or later there's going to be a "Fully tested with browser version X, not tested with version X+1 that was released yesterday" problem. Feature detection, graceful degradation, and a warning non-intrusively displayed to the user if their experience is being significantly downgraded is a better way to go.

To directly answer your question, if you must implement what you are asking for just parse the user agent. This could be useful specifically watching out for a browser you know doesn't work right and warning, or as a bandaid for a badly written intranet app that is very picky about the exact browser version it will run on. For a newly developed app where you have control over the requirements, I would not recommend warning on browser version since there are better ways to do it.

blocks|key|4548358|text|几乎在任何情况下，浏览器检测都是“有点怪异”。jQuery路径可能和您能得到的一样好，但正如您所说的，它并不好。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4548359|更好的解决方案通常是进行功能检测，特别是在您所描述的网站依赖于特定功能的情况下。|4548360|最好的特征检测库是Modernizr。这将为您提供一组Javascript标志，这些标志根据浏览器是否支持给定功能而设置为true或false。它检测对一大堆东西的支持，包括Web+Workers。|offset|length|4548361|entityMap|0|LINK|mutability|MUTABLE|url|http://www.modernizr.com/^0|0|0|9|9|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@$F|S|G|T|1|U]]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

Browser detection is indeed "a bit quirky", in pretty much any scenario. The jQuery route is probably as good as you're going to get, but as you say it's not great.

A better solution is generally to do feature detection, especially in cases like the one you describe where your site relies on specific features.

The best feature detection library is <a href="http://www.modernizr.com/" rel="nofollow">Modernizr</a>. This will give you an bunch of Javascript flags which are set to true or false according to whether the browser supports a given feature. It detects support for a whole bunch of stuff, including Web Workers.

I have an app that I have fully tested in Safari 5, IE 9, FF6, and Chrome 14. I'm not looking to block or exclude any browsers from the experience. But I want to warn/inform users that there may be a better experience in another browser, and if they choose to continue, there may be features not working or broken. 

I have looked at jQuery browser detection, but it seems to be a bit quirky. I know the best solution would be to warn based on feature detection, but we are currently in beta and I am not completely sure what features make or break. Such as web workers, its known that web workers not working breaks our app, but it works in IE lower versions. But then there is an issue with Opera that web workers is available, but not functioning correctly. 

Ultimately I am looking for an easy way to say Browser X Version y and up don't show warning, and those and under show warning.

What is the best way to approach this?

Best way to display warning message to "untested" browsers?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我有一个已经在Safari5、IE9、FF6和Chrome14上进行了全面测试的应用程序，我并不打算阻止或排除任何浏览器的体验。但我想警告/通知用户，在另一个浏览器中可能会有更好的体验，如果他们选择继续，可能会有一些功能无法工作或损坏。我看过jQuery浏览器检测，但它似乎有点奇怪。我知道最好的解决方案是基于功能检测的...

问向“未经测试”的浏览器显示警告消息的最佳方式？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问向“未经测试”的浏览器显示警告消息的最佳方式？EN