我们应该为 Intranet 应用程序部署 Webkit 浏览器吗？
在我工作的地方，我们越来越发现为 IE 进行开发很困难，从 Intranet 应用程序的角度来看，IE 历来是最容易瞄准的浏览器。
- 它已经部署了。
- 它已经理解 NTLM 身份验证，因此与我们的域级安全性完美集成。
- 它具有简洁但非标准的功能，例如 XMLDOM 和 XmlHTTP。
现在，我们对 IE 提出的问题越来越恼火：
- 有几个版本：IE 7、8 和即将推出的 9 beta，它们在性能、功能（尤其是 re:security 和区域）和美观方面都有稍微不同的问题。
- IE 7 和 8 比基于 Webkit 的浏览器慢。时期。
- 由于存在技术限制，例如缺少
canvas元素、CSS 错误等，因此很难使用第 3 方包，甚至很难在 IE 版本之间一致地编写代码。 - 用户越来越多地使用 Firefox 或 Chrome，甚至用于 Intranet 使用。
有人有过转型的经验吗？
欢迎任何建议。
At my place of employment, we are increasingly finding it difficult to develop for IE, which was historically the easiest browser to target, from an intranet-app point of view.
- It was already deployed.
- It already understood NTLM authentication, thus well integrated with our domain-level security.
- It had neat, albeit non-standard features such as XMLDOM and XmlHTTP.
Now, we are increasingly irritated by issues presented by IE:
- There are several versions: IE 7, 8, and soon 9 beta, which all have slightly different issues related to performance, functionality (especially re:security and zones), and aesthetics.
- IE 7 and 8 are slower than Webkit-based browsers. Period.
- There are technology limitations such as missing
canvaselement, CSS bugs, etc. that make it hard to use 3rd party packages or even consistently write code across IE versions. - Users are increasingly using Firefox or Chrome, even for intranet use.
Does anyone have experience with making a transition?
Any advice would be welcome.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
首先，使用基于Webkit的浏览器检查当前所有内网应用程序。如果您要创建一个在 IE 上会损坏的 Intranet 站点（例如，使用画布），那么您最好确保修复在现代基于 Webkit 的浏览器上损坏的所有旧版 Intranet 应用程序，然后再强制每个人都需要这样做运行非 IE 浏览器。
确保浏览器在您的公司网络上也能正常运行。例如：Chrome 仍然存在 NTLM/Kerberos 方面的一些突出问题。虽然这是一个小问题，但如果这意味着您可以放弃 IE。然而，根据您的用户群，永远不要低估那些只使用过 IE 的用户所需要的注意力。
我在工作中使用基于 Webkit 的浏览器，尽管我们有大量蹩脚/损坏的 IE 网站。我有时必须打开 IE 才能完成这些网站上的任务。现在，我对此感到满意，因为我已经习惯了它，并且更喜欢能够将 Chrome 与其他所有功能一起使用而带来的轻微痛苦。然而，非技术员工则不会，而且更愿意只坐在 IE 中（因为在他们眼中，网站无法运行是 Chrome 的错{因为它已经运行了好几年了（这一点对于企业来说很难反驳）观点（不要引入他们驳回的“技术上的胡言乱语”）]}）
所以，当然，去做吧。只要确保你做好计划，以便第一次就尽可能顺利地进行。你想要的是用户的认同，而不是强烈的反对。
Firstly, check all current intranet apps with a Webkit-based browser. If you are going to make an intranet site that will be broken on IE (eg, using canvas), then you better make sure that you fix any legacy intranet apps that are broken on modern Webkit-based browsers before you force everyone to need to run a non-IE browser.
Make sure the browsers function correctly on your corporate network as well. For example: Chrome still has some outstanding issues with NTLM/Kerberos. Although this is a small issue if it means you can drop IE. Depending on your user base however, never underestimate the user attention that will be needed for those who have used nothing but IE.
I use a Webkit-based browser at work, even though we have a ton of crappy/broken IE only sites. I have to occasionally open IE to complete tasks on those sites. Now, I'm okay with it because I'm use to it and prefer the minor pain to be able to use Chrome with everything else. Non-technical employees however are not and would prefer to just sit in IE (since in their eyes, it is Chrome's fault the site doesn't work {since it has worked fine for several years [a point hard to argue with from a business perspective (without bringing in 'technically mumbo-jumbo' that they dismiss)]})
So, sure, do it. Just make sure you plan it out so that it goes as smoothly as possible first time around. User buy-in is what you want, not backlash.
我的开发方法一直是为 Firefox 或 Chrome 编写，而且它只适用于 IE。我知道，这是违反直觉的，但它对我来说往往是有效的。
My method of development has always been to write for Firefox or Chrome and it kind of just works in IE. I know, it's counter-intuitive, but it worked out for me more often than not.