通过DATATIME查看FIREFOX 1.0.7和IE6：摘要报告 [英] FIREFOX 1.0.7 AND IE6 viewed through DATATIME: a summary REPORT
问题描述
好的！为了避免混淆，我将开始一个新的论点。
谢谢！
FIREFOX 1.0.7和IE6通过DATATIME查看：摘要报告
============================================== ==== =============
由Pamela
Datatime团队
----- ------------
好的伙计们。我回来了。
我一直在努力实施你的所有建议，并且
包含了你提供的有关Datatime web的所有建议
出口。特别是要提取不同的样式并制作
的初级课程，以避免重复相同的
描述符。
- 致谢-------------------------------------------------- -
我特别感谢贡献者：
PretLetters
Spartanicus
比尔
kchayka
Beauregard
Antoine
Robi
Arne
Niek
Rincewind
Blinky the Shark
Matt
Udo
....
（希望不要错过任何人。虽然有人应该列入黑名单
列表： - ））
这是我最新的结果。这是2页。第一个包含一个
SCREENSHOT来显示DATATIME中的原始内容。
另一个是相应的WEB OUTPUT。
比较Firefox和IE可以看到差异。
显示的布局并不是没有任何意义。
这只是一个使用了几种格式化效果的测试。 />
ORIGINAL SCREENSHOT（位图）：
http://cam70.sta.uniroma1.it/Technic...screenshot.htm
WEB OUTPUT（用CSS2渲染）：
http://cam70.sta.uniroma1.it/Technic...tatimedemo.htm
只是为了记录你的CSS已经过验证
http： //www.google.com/url?sa=D&q=htt...ss-validator/v ...
你得到5000多个错误，那是'这不是一个错误的5000和超过10,000警告，令我惊讶的是，任何浏览器都可以渲染如此可怜的编码，特别是因为它必须处理3385 html编码错误。 / blockquote>
我丢失了以前的记录。但我还是应该得到奖金
什么
Matt Silberstein说...... :-)
有一些奇怪的警告关于颜色和字体。请告诉我
知道代码更改
消除它们。
您的建议对我的工作非常重要。
当然，如果您愿意，所有人都会被邀请加入
支持Datatime专家的董事会
---------- -------------------------------------------------- ----------
这次我一直在使用并行FIREFOX结束IE
来仔细检查报告的呈现。
在重新编程网络输出的过程中，我做了一些
的发现（我主观上使用了这个词），我想分享。
有些是只是假设。所以，如果我错了，请纠正我。
IE有一个众所周知的问题，它本身不支持PNG
透明度。要修改此行为，必须使用
脚本。对于网站管理员来说，就是在< style>中插入一行，例如
img {behavior：url（" pngbehavior.htc"）;}
;部分。这项工作正常，是IE团队建议的官方
解决方案。 （IE7 beta纠正了这种行为）。
警告！我注意到这是非常重要的*在哪里*你放置这一行。
事实上虽然IE并不在乎。如果你把它放在
类定义之前，FIREFOX就不能再正确地渲染
了。
为了安全起见，放置它超过类定义。
关于doctypes，我注意到如果你使用<！DOCTYPE html PUBLIC" - // W3C // DTD HTML 4.01 // EN" ;>
而不是<！DOCTYPE html PUBLIC" - // W3C // DTD HTML 4.01
Transitional // EN">
块的计算存在明显的差异。
实际上我使用HTML 4.01绘制框的算法
Transitional不会
使用HTML 4.01，需要稍微不同的算法。
这表明盒子模型不同。
一般来说，似乎FIREFOX更严格那IE。一个例子是
行为
它调用了pngbehavior.htc。以下是其他两个例子。
1.
HTML 4.01过渡似乎有不同的呈现方式
IE6和Firefox。我的印象是，当使用此doctype
时，Firefox使用与IE6相关的较新的盒子模型，
而不会渲染一些最新的属性。
因此，使用Transitional doctype的最后一个版本的Firefox似乎无法获得与IE6相同的结果和
作为方框
model
使用的是不同的。
使用DTD HTML 4.01你可以获得几乎完全相同的
渲染，除了下面解释的一些小细节。
2.
关于编码。如果您的网页实际编码为UTF-8并且您偶然指定了另一种编码，例如charset = iso-8859-1
IE似乎无论如何能够理解编码是UTF-8，
FIREFOX改为使用指定的内容。这可能是
在一开始就会出现一些奇怪的字符
页面。
总的来说，我有这样的印象远远就是Firefox是
的候选人对于用户来说更可爱，特别是那些面向开源的用户，因为有些人b $ b
不错的功能和标签界面。 FIREFOX在某种程度上更适合用于最终用户的
confortable
。 （IE可能看起来更好看。）
Firefox对css是不可原谅和严格的。
Firefox渲染INSET / OUTSET有些奇怪。
实际上如果边框尺寸是1，它用于边框的前景色。
这很奇怪，因为边框宽度不会发生> 1. IE6确实
没有
有这个问题。
中心我使用了VALIGN，因为我找不到用css的方法。
（帮助!!!!!!!!!!!!）
这对维护非常不舒服，需要一些关注
由TD生成的单元格自动向下移动2个像素并向右移动到它的
容器。
所以要纠正这种行为容器的绝对位置必须是
转移
左上角2个像素。浏览器中单元格的大小不同。
这里
IE似乎更加一致。
< table>< ; td bgcolor =蓝色宽度= 127px高度= 139px valign = mid>奥地利
< / td>< / table>
此指令生成以下是物理盒子：
IE6中129x141像素
Firefox中129x139像素
进一步的Firefox和IE如果TD盒子的行为略有不同/>
il大于
容器，IE也扩大了容器。 Firefox没有。但是这个
不会影响我们，除非小区的内容小于其内容。
--------- -------------------------------------------------- -------
感谢您的帮助，Datatime Web EXPORT到目前为止已经合理地改进了
。
特别是那些大的页面已经通过
初步
提取样式类明智地减少了。
因为我觉得解决方案我还需要垂直对齐的帮助
有用
是不优雅和笨拙（虽然它有效）。
毕竟，它也证明了Datatime也可以用作有效
工具测试和
过度支持浏览器!! :-)
-Pamela
解决方案
ex ******** @ libero.it 写道：IE有一个众所周知的问题，它本身不支持PNG
透明度。要修改此行为，必须使用
脚本。对于网站管理员来说，就是在< style>中插入一行，例如
img {behavior：url（" pngbehavior.htc"）;}
部分。这项工作正常，是IE团队建议的官方解决方案。 （IE7 beta纠正了这种行为）。
IE确实支持PNG中的一种透明色。
警告！我注意到这一点非常重要*你在哪里放置这条线。
实际上虽然IE并不在乎。如果你把它放在类定义之前，FIREFOX就不能再正确地呈现页面。
为了安全起见，将它放在类定义之外。
这是因为浏览器应该忽略
错误之后的CSS，而''behavior''是一个错误。
关于doctypes，我注意到如果你使用<！DOCTYPE html PUBLIC" - // W3C // DTD HTML 4.01 // EN">
而不是<！DOCTYPE html PUBLIC" - // W3C // DTD HTML 4.01
Transitional // EN">
块的计算存在明显的差异。
实际上我用来绘制的算法带有HTML 4.01的方框
Transitional不支持HTML 4.01，需要稍微不同的算法。
这表明盒子模型不同。
您引用的DOCTYPE将触发怪癖模式。您应该使用
<！DOCTYPE HTML PUBLIC" - // W3C // DTD HTML 4.01 Transitional // EN"
" http：//www.w3 .ORG / TR / HTML4 / loose.dtd">相反，这将触发
标准模式。这将消除各种IE6特性。
中心我使用了VALIGN，因为我找不到用css的方法。
（HELP !!!!!!!!!!!! ）
尝试CSS vertical-align属性。
>IE确实支持PNG中的一种透明色。
你在说什么？
你引用的DOCTYPE将触发怪癖模式。您应该使用
<！DOCTYPE HTML PUBLIC" - // W3C // DTD HTML 4.01 Transitional // EN"
显然你还没有去过在上周的讨论之后
贡献了很多人，这个doctype被丢弃了。
实际上正如我所说，没有办法让firefox 1.0.7到如果使用过渡，则表现为像IE6一样的b $ b。相信我。
为了居中我使用了VALIGN，因为我找不到用css的方法。
（帮助!!!! !!!!!!!!）
尝试CSS vertical-align属性。
这与Valign不同。尊重线路
不是盒子。
所以你认为我过去四天一直在玩吗？ :-)
-pamela
ex ******** @ libero.it 写道：IE确实支持ONE透明色PNG。
你在说什么？
正如我所说。 IE支持PNG中的一种透明色，没有
诉诸行为黑客，就像GIF支持一种透明的
颜色一样。 IE不支持的是ALPHA透明度。
您引用的DOCTYPE将触发怪癖模式。您应该使用
<！DOCTYPE HTML PUBLIC" - // W3C // DTD HTML 4.01 Transitional // EN"
显然您没有关注过上周
贡献了很多人，这个doctype被丢弃了。
实际上正如我所说，如果使用过渡，没有办法让firefox 1.0.7像IE6一样表现得很好。相信我。
显然你不明白DOCTYPE在触发
怪癖模式或标准模式中的作用。特别是，你没有理解省略URL的后果：
<！DOCTYPE HTML PUBLIC" - // W3C // DTD HTML 4.01 Transitional // EN">
与以下内容不同：
<！DOCTYPE HTML PUBLIC" - // W3C // DTD HTML 4.01 Transitional // EN"
" http：//www.w3.org/TR/html4/loose.dtd">
后者触发IE6中的标准模式;前者没有。
您在帖子中抱怨IE和FF盒子的差异
型号，但您观察到的差异是因为您未能
使用在IE中触发标准模式的DOCTYPE。
以我用的为中心VALIGN，因为我找不到用css的方法。
（HELP !!!!!!!!!!!!）
尝试CSS vertical-align财产。
这与Valign不同。它是对线条的尊重而不是框。
当应用于TD时，vertical-align适用于框。参见CSS
2.1规范，第17.5.3节。
所以你认为我过去四天一直在玩这个游戏吗？ ： - ）
这种态度不会鼓励人们帮助你。
Ok! to avoid confusion I will start a new argument.
Thanks!!
FIREFOX 1.0.7 AND IE6 viewed through DATATIME: a summary REPORT
================================================== =============
by Pamela
Datatime Team
-----------------
Ok guys. I am back.
I have been working hard to implement all your suggestions and to
incorporate all the advice you kindly provided concerning Datatime web
export. And in particular to extract the different styles and to make
preliminary classes, in order to avoid repetitions of the same
descriptors.
- acknowledgements ----------------------------------------------------
In particular I am very grateful to the contributors:
PretLetters
Spartanicus
Bill
kchayka
Beauregard
Antoine
Robi
Arne
Niek
Rincewind
Blinky the Shark
Matt
Udo
....
(hope didn''t miss anyone. Althought someone should be listed in a black
list :-))
Here is my latest result. These are 2 pages. The first one contains a
SCREENSHOT to show the original as it is in DATATIME.
And the other is the corresponding WEB OUTPUT.
Compare Firefox and IE to see differences.
The layout shown it is not intended to not make any sense.
It is just a TEST where several formatting effects are used.
ORIGINAL SCREENSHOT (bitmap):
http://cam70.sta.uniroma1.it/Technic...screenshot.htm
WEB OUTPUT (rendered with CSS2):
http://cam70.sta.uniroma1.it/Technic...tatimedemo.htm
Just for the record when your css is
validated
http://www.google.com/url?sa=D&q=htt...ss-validator/v...
you get over 5000 errors, that''s not a typo that''s 5000 and over 10,000
warnings, It amazes me that any browser can render such a pitifully poor
piece of coding, especially as it has to cope with 3385 html coding errors.
I have lost my previous record. But I still deserve a prize according
what
Matt Silberstein says... :-)
There are some strange warning about colors and font. Please let me
know the code changes
to eliminate them.
Your suggestions are very important for my work.
Of course, all of you are invited, if you wish, to join the board of
supporting experts of Datatime
----------------------------------------------------------------------
This time I have been working using in parallel FIREFOX end IE
to double check the rendering of the report.
In the process of reprogramming the web ouput I have made some
discoveries (i use the word subjectively), which I wish to share.
Some are just hypotheses. So, please, correct me if am wrong.
IE has the well-known issue it does not support natively the PNG
transparency. To modify this behavior it is necessary to use
a script. For the webmaster, it is matter of inserting 1 line, such as
img {behavior:url("pngbehavior.htc");}
within the <style> section. This work fine and is the official
solution suggested by IE Team. (IE7 beta corrects this behavior).
WARNING! I noticed it is very important *where* you place this line.
In fact while IE doensn''t care. If you place it before
the class definitions, FIREFOX is no more able to render
the page correctly.
To be safe, place it past the class definitions.
About doctypes, I noticed that if you
use <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
instead of <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01
Transitional//EN">
there are sensible differences in the computation of the blocks.
Infact the algorithm I used to draw the boxes with HTML 4.01
Transitional does NOT
work with HTML 4.01, and a slightly different algorithm is needed.
This would suggest the box model is different.
In general, it seems FIREFOX is more strict that IE. An example was the
behavior
it has with the call to "pngbehavior.htc". Here are other 2 examples.
1.
HTML 4.01 Transitional seems to be rendered differently by
IE6 and Firefox. I have the impression that when this doctype
is used, Firefox uses a newer box model with respect to IE6,
while just some of the latest properties are not rendered.
Hence, there seems to be no way to get the same result with IE6 and
the last version of Firefox using the Transitional doctype, as the box
model
used is different.
Using DTD HTML 4.01 you can get almost exactly the same
rendering, apart some small details explained below.
2.
About encoding. If your web page is actually encoded UTF-8 and you
by chance specify another encoding, such as charset=iso-8859-1
IE seems anyway able to understand that the encoding is UTF-8,
FIREFOX instead uses what is specified. This might
cause the appearance of some strange chars at the very beginning
of the page.
In general, the impression I have got so far is that Firefox is
candidate to
be more lovable by users, especially those open source oriented, due to
some
nice features and the tabbed interface. FIREFOX is somehow more
confortable
to use for the final user. (IE is perhaps sligtly better good looking).
Firefox is unforgiven and strict as to css.
There is something strange with Firefox rendering of INSET/OUTSET.
In fact if the border size is 1 it uses for the borders the forecolor.
This is strange as it does not happen with border width > 1. IE6 does
not
have this problem.
To center I used the VALIGN, because I could not find a way with css.
(HELP!!!!!!!!!!!!)
This is very uncomfortable to maintain and requires some attention as
the cell generated by TD
automatically is shifted 2 pixels below and to the righ respect to its
container.
So to correct this behavior the absolute location of container must be
shifted
2 pixels top left. The size of the cell is different in the browsers.
Here
IE seems to be a little more consistent.
<table><td bgcolor=blue width=127px height=139px valign=middle>Austria
</td></table>
this instruction generates the following phisical box:
129x141 pixels in IE6
129x139 pixels in Firefox
Further Firefox anf IE have slightly different behavior if the TD box
il larger than
the container, IE enlarges the container also. Firefox no. But this
will not
affect us, except when the cell il smaller than its content.
------------------------------------------------------------------
So thanks to your help the Datatime web EXPORT has so far improved
sensibly.
In particular those big pages have been reduced sensibly by a
preliminary
extraction of style classes.
I still need help with vertical alignent since I feel the solution I
have use
is unelegant and ackward (althought it works).
After all, it also turns out Datatime can also be used as an effective
tool to test and
overstress browsers!! :-)
-Pamela
解决方案ex********@libero.it wrote:IE has the well-known issue it does not support natively the PNG
transparency. To modify this behavior it is necessary to use
a script. For the webmaster, it is matter of inserting 1 line, such as
img {behavior:url("pngbehavior.htc");}
within the <style> section. This work fine and is the official
solution suggested by IE Team. (IE7 beta corrects this behavior).
IE does support ONE transparent colour in PNGs.
WARNING! I noticed it is very important *where* you place this line.
In fact while IE doensn''t care. If you place it before
the class definitions, FIREFOX is no more able to render
the page correctly.
To be safe, place it past the class definitions.
That is because the browser is supposed to ignore CSS that follows an
error, and ''behavior'' is an error.
About doctypes, I noticed that if you
use <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
instead of <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01
Transitional//EN">
there are sensible differences in the computation of the blocks.
Infact the algorithm I used to draw the boxes with HTML 4.01
Transitional does NOT
work with HTML 4.01, and a slightly different algorithm is needed.
This would suggest the box model is different.
The DOCTYPEs you have cited will trigger quirks mode. You should use
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd"> instead, which will trigger
standards mode. This will eliminate various IE6 idiosyncracies.
To center I used the VALIGN, because I could not find a way with css.
(HELP!!!!!!!!!!!!)
Try the CSS vertical-align property.
>IE does support ONE transparent colour in PNGs.
what are you talking about?
The DOCTYPEs you have cited will trigger quirks mode. You should use
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
Evidently you have not been following the discussion of last week
where contributed a lot of people and this doctype was discarded.
Actually as I said, there is no way to make firefox 1.0.7 to behave
exacly like IE6 if transitional is used. Trust me.
To center I used the VALIGN, because I could not find a way with css.
(HELP!!!!!!!!!!!!)
Try the CSS vertical-align property.
This is NOT the same thing as Valign. It is respect to the line
not the box.
So do you think I have been playing the last four days? :-)
-pamela
ex********@libero.it wrote:IE does support ONE transparent colour in PNGs.
what are you talking about?
Just what I said. IE supports one transparent colour in PNGs, without
resorting to the behavior hack, just like GIFs support one transparent
colour. What IE does not support (yet) is ALPHA-transparency.
The DOCTYPEs you have cited will trigger quirks mode. You should use
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
Evidently you have not been following the discussion of last week
where contributed a lot of people and this doctype was discarded.
Actually as I said, there is no way to make firefox 1.0.7 to behave
exacly like IE6 if transitional is used. Trust me.
Evidently you do not understand the role of DOCTYPEs in triggering
either quirks mode or standards mode. In particular, you do not
understand the consequences of omitting the URL:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
is not the same as:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
The later triggers standards mode in IE6; the former does not.
You complained in your post about differences in the IE and FF box
models, but the differences you observed happened because you failed to
use a DOCTYPE that triggers standards mode in IE.
To center I used the VALIGN, because I could not find a way with css.
(HELP!!!!!!!!!!!!)
Try the CSS vertical-align property.
This is NOT the same thing as Valign. It is respect to the line
not the box.
When applied to a TD, vertical-align applies to the box. See the CSS
2.1 specification, section 17.5.3.
So do you think I have been playing the last four days? :-)
This kind of attitude will not encourage people to help you.
这篇关于通过DATATIME查看FIREFOX 1.0.7和IE6：摘要报告的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
