用于 Intranet 应用程序的 Chrome 或 Firefox（或与浏览器无关）？
如果您正在为一家小型企业设计一个核心业务 Intranet 应用程序，并希望它尽可能具有响应式的感觉，而员工对被某种浏览器困住不感兴趣，那么您会为 Firefox、Chrome 进行设计，还是测试更多比为了避免锁定而需要的范围更广？ 在将所有鸡蛋放入一个浏览器篮子之前，您是否会考虑其他因素？
例如，Chrome 是否具有其他浏览器所缺乏的任何与速度相关的功能，这些功能需要以跨浏览器不友好的方式定位 Chrome，如果有，是否值得围绕这些功能进行设计？
If you were designing a core business intranet app for a small business, and wanted it to be as responsive-feeling as possible, where the staff are indifferent to being stuck with a certain browser, would you design for Firefox, Chrome, or test more widely than you need to just to avoid lock-in? Are there other factors you'd consider before placing all your eggs in one browser basket or not?
For instance, does Chrome have any speed-related features that other browsers lack that would need Chrome to be targeted in a cross-browser-unfriendly way, and if it did, would it be worth designing around them?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（10）
与浏览器无关。 不知道什么时候有人会强制使用某个浏览器，并且您将不得不重做某个模块，因为它使用了仅适用于现在过时的浏览器的特殊插件或功能。
从技术上讲，我们是一家 IE 商店，但我确保我的所有应用程序至少可以在 IE 和 Firefox 上运行，并且我也在 Chrome 中进行更多测试。
Go browser agnostic. There's no telling when somebody will mandate a certain browser, and you'll be stuck having to redo a certain module because it used a special plug or feature only available with the browser now outdated.
Technically we're an IE shop here, but I make sure all my apps function on at least IE and Firefox, and I'm doing more testing in Chrome as well.
企业对浏览器的 IT 政策是什么？ 看起来这将决定你写它的目的。 如果您客户公司的每台计算机都安装了 IE6，为什么还要为其中任何一个编写它呢？ 对于公司来说，锁定不是问题，因为他们可以规定人们在计算机上使用和必须拥有的内容的政策。
Speedwise，你不会发现选择其中一个比另一个有显着的收益，除非你正在执行发挥其优势的特定任务（例如，查看基准测试的范围，一些谷歌测试的 Chrome 速度快数百倍，而其他测试则快了数百倍） Firefox 击败了 chrome）。
理想情况下，您希望它是不可知的，但如果您必须选择一个，我会选择 Firefox，因为它是一种更成熟的浏览器。 我不太愿意将应用程序定位到仅推出几个月的浏览器，尤其是刚刚发布 1.0 的浏览器。
What is the business' IT policy on browsers? It seems like this would determine what you write it for. Why write it for either, if every computer at your client's company has IE6? Lock-in is not a problem for a company as they can dictate the policy on what people use and must have on their computers.
Speedwise you're not going to find significant gains choosing one over the other unless you're doing specific tasks that play towards their strengths (look at the range in benchmarking for instance, some google tests have chrome hundreds of times faster, where as others have firefox beating chrome).
Ideally, you'd want it to be agnostic, but if you had to choose one though, I would go with Firefox, as it's a more mature browser. I'd be reluctant to target the app for a browser that is only a couple months old, especially one that just hit 1.0.
虽然符合标准肯定有很多优势，但如果您的应用程序 UI 很重，并且您不想因缺少 HTML 小部件而苦苦挣扎，我建议使用基于 Gecko 的浏览器，您可以使用所有熟悉的功能更快地在 XUL 中构建 UI桌面应用程序比 HTML 从头开始。 由于 Gecko 是开源的并且正在积极开发，因此如果您使用专有的东西，您不会面临陷入困境的风险。
Although being standards compliant is certainly have many advantages, if your application is UI heavy and you don't want to struggle with lack HTML widgets, I suggest using a Gecko based browser which you can build UI in XUL much quicker with all the familiar functionality of a desktop application than HTML from scratch. Since Gecko is open source and actively developed, you don't risk being stuck if you were using something proprietary.
始终正确编写 - 即跨浏览器 - 因为你永远不知道新版本的浏览器何时会改变旧的行为。
然而，使用 Chrome 的网络应用程序“应用程序化”对于 Intranet 来说是一个不错的选择。
（特别是如果它有助于阻止用户说“我的浏览器坏了”）
Always write properly - i.e cross-browser - since you never know when a new version of a browser might change old behaviour.
However, using Chrome's 'applicationising' of web apps is a good choice for intranets.
(Especially if it helps stops users saying "my browser is broken")
“如果您正在为一家小型企业设计一个核心业务 Intranet 应用程序，并希望它尽可能具有响应式的感觉，而员工对于被某种浏览器困住并不在意。”
Chrome。您可以制作无 Chrome 的 Web 应用程序，这样您就可以使您的 Intranet 应用程序看起来像桌面应用程序并且运行得像桌面应用程序（快速的 Javascript 在这里很有帮助）。 您甚至可以使用 Chrome 创建应用程序快捷方式，这样就不再显示地址栏，从而获得更多的屏幕空间。
Chrome 的启动速度也比其他浏览器快一点，每次我想立即在 Stackoverflow 上阅读某些内容时，我都会使用 Chrome。
"If you were designing a core business intranet app for a small business, and wanted it to be as responsive-feeling as possible, where the staff are indifferent to being stuck with a certain browser."
Chrome. You can make chrome-less web app, so you can make your intranet app looks like and act like a desktop app(fast Javascript helps a lot here). You can even make an application shortcut with Chrome so there'll be no more address bar displayed, more screen real estate.
Chrome launch a tad faster than other browsers too, everytime I want to read something on Stackoverflow immediately, I use Chrome.
最便宜的方法是根据组织的标准定制内联网应用程序。 如果他们按小时付钱给你，那实际上是他们决定你把时间花在什么事情上。 如果他们说仅适用于 FireFox，那么就应该这样做。 如果是固定出价，那么你可能有一些回旋余地，但最终这是他们的决定。 他们可能有理由不希望它与 Chrome 一起使用（我想不出原因，但这并不意味着没有原因。）
The cheapest way to go would be to tailor the intranet app to the standards of the organization. If they are paying you by the hour, really it is their decision as to what you spend your time on. If they say it is FireFox only, then that is the way it should be done. If it is a fixed bid, then you might have some leeway, but ultimately it is their decision. They may have reasons why they don't want it to work with chrome (I can't think of a reason, but that doesn't mean there aren't some.)
与浏览器无关。
我的经验是，虽然技术社区对浏览器（类似的）有强烈的偏好，但实际的用户群体并不真正打扰......或者换句话说，现代浏览器之间没有显着差异对于最终用户来说很重要。
我认为 IE 和 Firefox（尤其是 IE）是为符合标准而设计的，而 Chrome 可能比较宽松，尤其是可以与 Google 应用程序很好地配合，而 Google 应用程序本身并不真正符合 w3c 规范。
一个安全的选择是按照 w3c 标准设计您的应用程序，并确保它在大多数浏览器中都能正常工作。
Be browser agnostic.
My experience is that while there is a strong preference for a browser (of their like) in tech communities, the actual user population does not really bother...or to put in other way, there is no significant difference between the modern browsers that would matter for the end-user.
I think IE and Firefox (IE especially) are designed for standards conformance where as Chrome might be lenient, especially to work great with Google apps which themselves are not really w3c spec conformant.
A safe bet is to design your app per w3c standards and be assured it would work the same in most of the browsers.
为了在政治上正确，在网络标准方面，您必须使其能够在主要浏览器中以及现有公司配置的所有爵士乐中呈现。 但是，将 Chrome 与 Gears 结合使用有什么优势呢？
To be politically correct, web standrards-wise, you'd have to make it presentable in the major browsers, and all that jazz about existing company config. However, what about the advantages of using Chrome with Gears?
“并希望它尽可能具有响应式的感觉，让员工对被某种浏览器困住不感兴趣”
听起来您需要一个智能客户端应用程序。
编辑：我所说的智能客户端是指独立于浏览器运行并使用 Web 服务与服务器通信的应用程序。
"and wanted it to be as responsive-feeling as possible, where the staff are indifferent to being stuck with a certain browser"
Sounds like you need a smart client application.
EDIT: By smart client I mean an application that runs seperatly from a browser and uses web services to talk to the server.
我会尽可能与浏览器无关。 我们有几个这样的系统，技术上它们只支持一种浏览器，但我们确实确保它们至少可以在 IE - Gecko - WebKit 上运行（即使它们不太漂亮）宇宙。
（另一方面，如果我今天要从头开始其中一个，那么针对 Chrome 而不是 IE 进行优化将非常非常诱人。）
I'd go as browser-agnostic as possible. We've got a couple systems like this, where technically they only support one browser, but we make really sure they at least function (even if they're not pretty) across the IE - Gecko - WebKit universe.
(On the other hand, if I was going to be starting one of those from scratch today, optimizing for Chrome rather than IE would be really, really tempting.)