Firefox 3 vs Firefox 4 开发差异?
我正在考虑更新到 Firefox 4(当前运行的是 Firefox 3.6.15——等等,这不是一个具体的软件问题!),并且在 Web 开发方面有一些担忧。
我唯一关心的是两者之间是否存在任何兼容性问题(CSS / HTML)或怪癖。我不愿意看到在一个网站上使用 Firefox 4 时的 3px 间距,而在 Firefox 3 上使用 0px 的间距(几乎就像 IE6 vs IE7 vs IE8 的惨败,如果你明白我的意思的话)。
最后,我只是检查 Firefox 4 是否正常,显示带有更新“引擎”的网站/网络应用程序(这是我所期望的)。
想法?这个级别有人比较过吗?我不仅仅是在谈论 CSS 重置级别之类的事情,尽管我正在沿着这些兼容性思路进行思考。
希望我能够清楚地表达我的担忧。除了与 FF4(超过 FF3)的增强列表之外,我似乎找不到任何比较,我并不是想将此作为一个软件问题,而是我是否应该意识到升级时缺少的任何输出更改。我不想错过客户开发和浏览器兼容性方面的关键差异。
谢谢。
I was thinking of updating to Firefox 4 (currently running Firefox 3.6.15 -- hold on not a software question specifically!) and had some concerns when it comes to web development.
My only concern is if there are any compatibility issues (CSS / HTML) or quirks between the two. I would hate to see something like a 3px spacing while using Firefox 4 on one website vs 0px using Firefox 3 (almost like an IE6 vs IE7 vs IE8 fiasco, if you get my drift).
Ultimately I am just checking if Firefox 4 is business as usual with the display of a website / web app with an updated 'engine' (which is what I expect).
Thoughts? Has anyone compare at this level? And I'm not just talking things like on the CSS Reset level, altho I am thinking along those lines of compatibility.
Hopefully I am making my concern somewhat clear. I couldn't seem to find any comparisons other than enhancement list to FF4 (over FF3), I don't mean to make this a software question but rather, should I be aware of any output changes that I am missing by upgrading. I don't want to miss critical differences when it comes to development and browser compatibility for the customer.
Thanks.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(5)
https://developer.mozilla.org/en/Firefox_4_for_developers
https://developer.mozilla.org/en/Firefox_4_for_developers
即使 IE6 / IE7 / IE8 与其他浏览器相比也没有你想象的那么惨败;旧 IE 版本中存在奇怪间距差异的错误主要是由于网站强制浏览器进入 Quirks 模式(名副其实)而不是标准模式造成的。如果您处于标准模式,所有浏览器几乎都遵循相同的规则,尽管旧版本中的功能较少(IE6 的功能要少得多)。
考虑到这一点,从 FF3.6 升级到 FF4.0 不会给使用 FF3.6(以及一般标准模式)编写的现有网站带来任何问题。
我所知道的 FF4 的唯一主要警告是他们删除了
-moz-binding
CSS 功能。这是(或者更确切地说,曾经是)Firefox 特定的(即非标准)CSS 功能,它允许您使用 CSS 将 XUL 模板绑定到 HTML 元素。 XUL 是 Firefox 用户界面(以及 Mozilla 的其他应用程序)编写的 XML UI 定义语言。出于安全考虑,他们取消了直接从网页引用它的功能。这个问题一般不应该引起任何人的关注——如果你一直坚持标准,你就永远不会使用它。
然而,它有一种被广泛使用的方式:作为一种浏览器黑客手段,让 Firefox 支持省略号。所有其他浏览器都支持 CSS
text-overflow:ellipsis;
,但 Firefox 不支持。连FF4都不支持。有人设法使用-moz-binding
破解了一种方法,从那时起许多网站就一直在使用它。这个 hack 在 FF4 中将不再起作用。请参阅我关于此主题的问题:text-overflow:ellipsis in Firefox 4? (和 FF5)
但除此之外,Firefox 4 中的几乎所有其他新功能(当然从渲染引擎的角度来看)都是 FF3.6 的增量升级,因此现有网站应该可以继续工作不变。
Even IE6 / IE7 / IE8 vs other browsers isn't as big a fiasco as you make out; the bugs in old IE versions with weird spacing differences were mainly caused by web sites forcing the browser into Quirks mode (which lives up to its name) rather than standards mode. If you're in standards mode, the browsers all pretty much live up to the same rules, albeit with fewer features in older versions (much fewer features in the case of IE6).
With that in mind, the upgrade from FF3.6 to FF4.0 shouldn't present you with any issues for existing sites written with FF3.6 in mind (and standards mode in general).
The only major caveat that I'm aware of with FF4 is that they've removed the
-moz-binding
CSS feature. This is (or rather, was) a Firefox-specific (ie non-standard) CSS feature which allowed you to bind an XUL template to an HTML element using CSS. XUL is the XML UI definition language which the Firefox user interface is written in (as well as other apps from Mozilla). They've removed the ability to reference it directly from a web page due to security considerations.This one issue shouldn't generally concern anyone -- if you'd been sticking to standards anyway, you'd never have used it.
However, there is one way in which it has been used quite widely: as a browser hack to get Firefox to support an ellipsis. All other browsers support CSS
text-overflow:ellipsis;
, but Firefox does not. Even FF4 won't support it. Someone managed to hack a way to do it using-moz-binding
, and many sites have been using it since then. This hack will cease to work in FF4.See my question on this topic here: text-overflow:ellipsis in Firefox 4? (and FF5)
But other than that one thing, pretty much everything else new in Firefox 4 - certainly from the perspective of the rendering engine -- is an incremental upgrade from FF3.6, so existing sites should continue to work unchanged.
您可以在同一个盒子中运行两个版本,至少用于测试。
http://www.thewindowsclub .com/how-to-run-firefox-3-and-firefox-4-simultaneously-in-windows
我想您无法使用其他浏览器非常有效地做到这一点。 (例如具有自动更新功能的 IE 或 Chrome)
You could run both versions in the same box, at least for testing.
http://www.thewindowsclub.com/how-to-run-firefox-3-and-firefox-4-simultaneously-in-windows
I guess you can't do this very effectively with other browsers. (like IE, or Chrome with auto-updates)
两者之间的主要区别将更多地体现在新元素、属性和 API 方面,而不是您提到的基本属性。任何较小的设计或布局问题很久以前就得到了解决,或者如果要修复的话,也可能很少见。它不像 IE 那样不仅存在版本之间的问题,而且存在版本内部的问题。
The major differences between the two are going to be more along the lines of new elements, properties and APIs and not basic properties as you mention. Any smaller design or layout problems were solved long ago or, if one were to be fixed, probably rare. It's not like IE where there are issues not only between versions but within versions.
无论到目前为止发布了什么,请务必小心,因为我已经注意到渲染方面的一些差异 - 特别是垂直间距和内联列表元素。就我而言,差异实际上相当巨大,因为这会影响顶部菜单元素的外观。以前IE8、Chrome10/11和FF4都将其呈现为相同的,但现在FF4是一个明显的异常值。我也在使用 html5/html4-strict 文档类型。只是需要考虑的事情;这种转变并不像之前的帖子可能让你相信的那样乐观......
Regardless of what's been posted thus far, be careful because I've already noticed several differences in rendering -- specifically with vertical spacing and inline list elements. In my case, the difference is actually quite huge since this impacts the look of the top menu element. Previously IE8,Chrome10/11 and FF4 all rendered it identical, but now FF4 is a definite outlier. I am using the html5/html4-strict doctype too. Just something to consider; the transition isn't quite as rosy as the prior posts would perhaps lead you to believe...