IE7和Web标准 [英] IE7 and Web Standards
问题描述
Paul Thurrott：
Wilson'（IE首席项目经理）的帖子令人失望，因为微软
并不打算完全支持IE 7.0中的最新CSS标准......
http://www.windowsitpro.com/Article/...7208.html?Ad=1
Roy
Roy Schestowitz写道：Paul Thurrott：
Wilson（IE领导计划）经理）帖子令人失望，因为微软并不打算完全支持IE 7.0中最新的CSS标准......
IE7与我们完全无关将至少再花5年b $ b。b年。 MS继续以最具创新性的方式开拓前沿技术。
-
jmm dash list（at）sohnen- moe（dot）com
（删除.AXSPAMGN电子邮件）
Roy Schestowitz：Paul Thurrott：
无论那个人是谁。从这篇文章来看，他并不认真对待（关于网页设计）。
http://www.windowsitpro.com/Article/...7208.html?Ad=1
我不明白为什么网页设计师会对他们不在IE7b1测试组中包含的
感到失望，因为我只知道这一个
无论如何都没有为他们改变那么多。如果IE7b2以相同的方式限制在
，我可以理解失望，如果它确实包含了承诺的错误修复和改进。在那之前让系统管理员等等。
检查所谓的安全性改进。
当然很遗憾，但没什么新鲜的，MS不遵守行业
标准，其中beta版本几乎是功能固定的---但是，某些
属性只能释放候选版本（RC）。因此beta1
必须被视为alpha版本，或者用Opera的术语来说，是一个
技术预览版（TP）。
Chris Wilson的博客文章
< http://blogs.msdn.com/ie/archive/2005/07/29/445242.aspx>今天列出了很多与IE有关的主要烦恼，所以，如果他们确实被带走了，我们应该感到高兴，而不是要求抵制。没有严肃的
预计微软将成为五年内首次发布的标准符合标准的领导者（不包括IE / Mac）。
关于Acid2，很高兴实现这一点，Firefox和Opera
不是，但是（仍然不完整的）CSS 2.1测试套件更重要。
对于MS和其他浏览器开发人员而言，现在将目标定为CSS 2.1
一致，而不是2.0。
一CSS 2.1的功能我们可能在IE7中看不到表格相关
值的''display''值，因为那可能需要一个
完全重写渲染引擎的一个主要部分。
也许他们应该检查移植的可能性和改进IE5 / Mac的渲染引擎Tasman的b
那些没有b $ b的传统镇流器 - 我知道什么，也许他们做了。
Backwards com对于MS来说，适应性并不是一个问题：在怪癖模式中我完全不期待任何
的变化。在标准模式下，他们可以使所有
标准符合他们想要的变化，尽管打破了一些网站
愚蠢地依赖于CSS黑客攻击。任何人总是气馁黑客，而且心灵理智（不过DTD切换也是如此）。尽管如此，我担心他们再次认为错误兼容性非常重要，即使在
标准模式中也是如此。
此外，如果GUI被固定在第一个屏幕截图所示的位置，对于用户而言，这比用CSS整合更糟糕。
Christoph P？ per写道：Roy Schestowitz：
Paul Thurrott：
无论那个人是谁。
他多年来一直在写关于Windows内容的书籍。我有一张
早期的Visual Interdev他的书，并与他对话
然后。他非常乐于助人。
http://www.winsupersite.com/
注意我只是指向你的问题的一些参考，而不是
他是否是专家。 < g>
-
-bts
-这个空间故意留空。
Paul Thurrott:
"Wilson''s (IE Lead Program Manager) post is disappointing because Microsoft
doesn''t plan to fully support the latest CSS standard in IE 7.0..."
http://www.windowsitpro.com/Article/...7208.html?Ad=1
Roy
Roy Schestowitz wrote:Paul Thurrott:
"Wilson''s (IE Lead Program Manager) post is disappointing because Microsoft
doesn''t plan to fully support the latest CSS standard in IE 7.0..."
IE7 is completely irrelevant to us and will be for at least another 5
years. MS continues to pioneer trailing edge technology in most innovative
ways.
--
jmm dash list (at) sohnen-moe (dot) com
(Remove .AXSPAMGN for email)
Roy Schestowitz:Paul Thurrott:
Whoever that guy is. Judging by this one article, he is no?ne to be
taken serious (regarding webdesign).
http://www.windowsitpro.com/Article/...7208.html?Ad=1
I don''t understand why webdesigners are disappointed that they are not
included in the IE7b1 testing group, because for all I know this one
doesn''t change that much for them anyway. If IE7b2 was restricted in the
same way, I could understand the disappointment, if it indeed included
the promised bug-fixes and improvements. Until then let sysadmins etc.
check out the alleged security improvements.
Of course it''s sad, but nothing new, that MS doesn''t comply to industry
standards, where beta versions are pretty much feature-fixed---some
attribute that to release candidates (RC) only, though. Therefore beta1
would have to be considered an alpha release or, in Opera''s terms, a
technical preview (TP).
Chris Wilson''s blog post
<http://blogs.msdn.com/ie/archive/2005/07/29/445242.aspx> lists many of
the main annoyances with IE today, so, if they''re indeed being taken
care of, we should be glad, instead of calling for boycot. No?ne serious
expects Microsoft to become the leader in standards compliance with
their first release in five years (not counting IE/Mac).
Regarding Acid2, it''s nice to fulfill that, which Firefox and Opera
don''t, but the (still incomplete) CSS 2.1 test suite is more important.
It''s reasonable for MS and other browser developers to target CSS 2.1
conformance now, instead of 2.0.
One CSS 2.1 feature we likely won''t see in IE7 are the table related
values of the ''display'' value, because that would probably require a
complete rewrite of one of the major parts of the rendering engine.
Maybe they should have checked out the possibility of porting and
improving Tasman, the rendering engine of IE5/Mac, because that doesn''t
have as much legacy ballast---what do I know, maybe they did.
Backwards compatibility isn''t really an issue for MS: I don''t expect any
changes at all in Quirks Mode. In Standards Mode they can make all the
standards conforming changes they want, despite breaking a few sites
stupidly relying on CSS hacks. Hacks were always discouraged by anyone
with a sane mind (so was DTD switching, though). My fear is nevertheless
that they once again think bug compatibility was important even in
Standards Mode.
Besides, if the GUI was fixed to what first screenshots indicate, that''d
be a far worse problem for users than CSS conformity.
Christoph P?per wrote:Roy Schestowitz:Paul Thurrott:
Whoever that guy is.
He''s been writing books about Windows stuff for many years. I have an
early Visual Interdev book of his, and corresponded with him back
then. He was very helpful.
http://www.winsupersite.com/
Note I am just pointing to some references for your question, not
whether he is an expert. <g>
--
-bts
-This space intentionally left blank.
这篇关于IE7和Web标准的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
