传统代码/浏览器兼容性 [英] Legacy code/browser compatibility
问题描述
这只是对你所有网络开发者的快速调查：什么
浏览器你测试/担心兼容性？
显然，你'我将测试当前的浏览器，如
IE6，IE7，Firefox 1.5 / 2，Opera 8/9，Safari 2等。
在您不再担心浏览器之前，浏览器必须有多大？任何人
这里还在测试IE4吗？
谢谢，
David
This is just a quick poll for all you web devs out there: What
browsers do you test on/are concerned about compatibility with?
Obviously, you''re going to test on current-generation browsers such as
IE6, IE7, Firefox 1.5/2, Opera 8/9, Safari 2, etc.
How old must a browser be before you stop worrying about it? Anybody
here still test on IE4?
Thanks,
David
推荐答案
David Golightly在11/10/2006 2:50 PM发表以下内容：
David Golightly said the following on 11/10/2006 2:50 PM:
对你所有网络开发人员来说只是一个简短的民意调查：什么
浏览器你测试/担心兼容性？
显然，你要去测试当前的浏览器，如
IE6，IE7，Firefox 1.5 / 2，Opera 8/9，Safari 2等。
多大年纪必须浏览器在你不再担心它之前？任何人
这里还在IE4上测试？
This is just a quick poll for all you web devs out there: What
browsers do you test on/are concerned about compatibility with?
Obviously, you''re going to test on current-generation browsers such as
IE6, IE7, Firefox 1.5/2, Opera 8/9, Safari 2, etc.
How old must a browser be before you stop worrying about it? Anybody
here still test on IE4?
John Stockton没有测试，他*使用* IE4，直到大约一个月前。
关于浏览器的年龄？谁在乎。这就是特征检测的用途。
-
兰迪
机会有利于准备好的心灵
comp.lang.javascript常见问题 - http://jibbering.com/faq
Javascript最佳实践 - http://www.JavascriptToolbox.com/bestpractices /
David Golightly写道：
David Golightly wrote:
这是对你所有网络开发人员进行快速调查：你有什么
浏览器进行测试/担心兼容性？
显然，你要测试一下在当前的浏览器上，例如
IE6，IE7，Firefox 1.5 / 2，Opera 8/9，Safari 2等。
多少岁浏览器在你不再担心它之前？任何人
这里还在IE4上测试？
This is just a quick poll for all you web devs out there: What
browsers do you test on/are concerned about compatibility with?
Obviously, you''re going to test on current-generation browsers such as
IE6, IE7, Firefox 1.5/2, Opera 8/9, Safari 2, etc.
How old must a browser be before you stop worrying about it? Anybody
here still test on IE4?
< IMHO>
IE4在几年前去世了。
IE 5.x< IE 5.5以太过焦的方式实现了未来的方式，所以死了
。
< / IMHO>
< FACTS> ;
<！ - 严格按*当前*使用优先级 - >
IE6.0
Firefox 1.5
IE7.0
Camino
Safari
其他
< / FACTS>
<IMHO>
IE4 died years ago.
IE 5.x < IE 5.5 implemented the future ways in too coorved ways so died
too.
</IMHO>
<FACTS>
<!-- Strictly by the *current* usage priority -->
IE6.0
Firefox 1.5
IE7.0
Camino
Safari
Others
</FACTS>
David Golightly写道：
David Golightly wrote:
这只是对你所有网络开发者的快速调查：
你测试什么浏览器/关心
兼容性？显然，你将测试
当前一代浏览器，如IE6，IE7，Firefox 1.5 / 2，
Opera 8/9，Safari 2等。
This is just a quick poll for all you web devs out there:
What browsers do you test on/are concerned about
compatibility with? Obviously, you''re going to test on
current-generation browsers such as IE6, IE7, Firefox 1.5/2,
Opera 8/9, Safari 2, etc.
这是一个错误的问题。一个明智的设计过程始于
，了解结果的目的是什么。因此，对于
的例子，一般公共访问电子商务（零售）
网站的目的是为了最大化利润，而专业网络应用程序
（可能在内联网上运行）实现了它的目的，当打算使用它的人们可以有效地使用它时。
第一种情况不必要地将潜在客户排除在设计之外
阶段并不是一个好主意，所以建议设计为
以容纳最大可能的客户群（请记住服务器端脚本和HTML的组合可以容纳*每个*
浏览器，可以显示HTML并提交表单）。记得;如果你不愿意从他们身上拿走他们的钱，那不是
用户的错，并且
其他人愿意这样做，这不是用户'问题也是。
在后一种情况下，可以规定那些打算使用网络应用程序的人必须运行，比方说， IE 6+或Mozilla / Gecko
浏览器，启用了javascript（因为这些很难实现限制并适用于Windows，Mac和Unix / Linux操作系统）。用户
（或更有可能，他们的雇主）将要使用网络应用程序
并愿意使用配置中规定的浏览器
需要
。
问题不在于什么是web
开发所需的最低标准，而是任何特定项目需要什么什么
才能实现它。为了以明智的方式做出这些设计决策，有必要知道帽子是否可以实现。
一位熟悉跨浏览器创作的作者设计
能够准确估算实现他们正在进行的项目目标的工作量（和相关成本）
。他们可能会确定上下文只是要求支持一些任意的
浏览器/版本，但知道可以实现什么意味着不需要
实现它是一个决定，而不是他们从来没有学过更好的后果。
That is really the wrong question. A sensible design process starts with
an appreciation of what the outcome is intended to achieve. So, for
example, the purpose of a general public access e-commerce (retailing)
web site is to maximise profits, while a specialist web application
(possibly running on an Intranet) achieves its purpose when the people
who are intended to use it can use it effectively.
In the first case needlessly excluding potential customers at the design
stage is not that good an idea, so it is advisable to design to
accommodate the largest possible customer base (baring in mind that a
combination of server-side scripting and HTML can accommodate *every*
browser that can display HTML and submit forms). Remember; it is not the
user''s fault if you are unwilling to take their money off them, and
someone else will be willing to so it is not the user''s problem either.
In the latter case it is possible to dictate that people who are going to
be using the web application must run, say, IE 6+ or a Mozilla/Gecko
browser, with javascript enabled, (as those are hardly arduous
restrictions and accommodate Windows, Mac and Unix/Linux OSs). The users
(or, more likely, their employers) will want to use the web application
and will be willing to use the browsers dictated in the configurations
required.
The question is not one of what is the minimum standard required for web
development but rather what is needed of any particular project and what
is required to achieve it. To make those design decisions in an informed
way it is necessary to know hat can be achieved.
An author conversant in the creation of genuinely cross-browser designs
is in a position to accurately estimate the effort (and associated costs)
of achieving the goals of the project they are working on. They may
decide that context only calls for support for some arbitrary set of
browsers/versions, but knowing what can be achieved means that not
achieving it is a decision rather than the consequences of their never
learning to do any better.
浏览器之前必须多大你不要担心
了吗？这里有人还在测试IE4吗？
How old must a browser be before you stop worrying
about it? Anybody here still test on IE4?
作为跨浏览器脚本设计的一个重要部分是干净的降级，
这样的代码我会一直在很多浏览器上测试我知道
无法主动支持脚本代码，否则我不确定
设计是否可以接受降级。一旦代码被设计为可接受地降低
，那么最古老的浏览器的结果将是可接受的，因为它将在最现代的浏览器上使用javascript
禁用。
Richard。
As an importune part of cross-browser script design is clean degradation,
for such code I would always test on a number of browsers that I knew
could not actively support the script code, else I would not be sure that
the design degraded acceptably. Once code is designed to degrade
acceptably then the outcome on the most ancient browsers will be as
acceptable as it will be on the most modern browser with javascript
disabled.
Richard.
这篇关于传统代码/浏览器兼容性的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
