微软的JavaScript文档的新问题 [英] Microsoft's JavaScript doc's newfangled problem
问题描述
有时在过去的几个月里，显然微软对他们的JavaScript文档网站进行了更改：
http://msdn.microsoft .com / library / de ... bfe2330aa9.asp
所以，一个人必须该死的按下扩展。按钮查看
文档，每个该死的页面。
他妈的是怎么回事？
并且，更改之前的好URL现在已经被破坏（给出HTTP错误404）。
许多新奇的按钮，例如复制代码等。在Safari，FireFox，iCab，Mac IE中没有该死的工作
。
而且，在任何这些浏览器中，代码示例都变为单个
拥挤的块没有任何换行符。例如
?? Circle.prototype.pi = Math.PI;函数ACirclesArea（）{return
this.pi * this.r * this.r; //圆圈区域的公式为
r< SUP> 2< / SUP>。 } Circle.prototype.area = ACirclesArea; //计算圆的面积的函数
现在是Circle
Prototype对象的一种方法。 var a = ACircle.area（）; //这就是你怎么用
调用Circle对象上的区域函数。??
他妈的是什么？
答案：母亲的无能已经活跃起来。
-------------
关于OpenSource文档问题的论文集，请参阅
底部：
http://xahlee.org/perl-python/python.html
Xah
xa*@xahlee.org
a ?? http://xahlee.org/
sometimes in the last few months, apparently Microsoft made changes to
their JavaScript documentation website:
http://msdn.microsoft.com/library/de...bfe2330aa9.asp
so that, one has to goddamn press the "expand" button to view the
documentation, for every goddamn page.
What the fuck is going on?
And, good url before the change are now broken (giving HTTP error 404).
Many of the newfangled buttons such as "Copy Code" doesn''t goddamn work
in Safari, FireFox, iCab, Mac IE.
And, in any of these browsers, the code examples becomes single
congested block without any line breaks. e.g.
??Circle.prototype.pi = Math.PI; function ACirclesArea () { return
this.pi * this.r * this.r; // The formula for the area of a circle is
r<SUP>2</SUP>. } Circle.prototype.area = ACirclesArea; // The function
that calculates the area of a circle is now a method of the Circle
Prototype object. var a = ACircle.area(); // This is how you would
invoke the area function on a Circle object.??
WHAT THE FUCK is going on?
Answer: Motherfucking incompetence has come alive.
-------------
For a collection of essays on OpenSource documentation problems, see
bottom of:
http://xahlee.org/perl-python/python.html
Xah
xa*@xahlee.org
a?? http://xahlee.org/
推荐答案
Xah Lee写道：
Xah Lee wrote:
有时在过去的几个月里，显然微软改变了他们的JavaScript文档网站：
sometimes in the last few months, apparently Microsoft made changes to
their JavaScript documentation website:
他们的* JScript *文档网站 - 这里是关键字。
请参阅：
< http://groups.google.com/group/comp.lang.javascript/browse_frm/thread/a4a1e9736dc8fa11/9f41a436cf9d8f44>
正式分手后IE for Mac OS：
< http://groups.google.com/group/comp.lang.javascript/browse_frm/thread/e85ccf55553d8da2/5dddd18b0949b792#5dddd18b0949b792>
JScript站点现在仅适用于Windows 98 SE及更高版本的Internet Explorer 5.5和
更高。
其他任何访问者都在外面微软的支持和兴趣 - 在
JScript域中最少
。这是坏事和粗鲁，但它是，我很害怕
它将是。
Their *JScript* documentation website - here''s the keyword.
See:
<http://groups.google.com/group/comp.lang.javascript/browse_frm/thread/a4a1e9736dc8fa11/9f41a436cf9d8f44>
After the official breakup with IE for Mac OS:
<http://groups.google.com/group/comp.lang.javascript/browse_frm/thread/e85ccf55553d8da2/5dddd18b0949b792#5dddd18b0949b792>
JScript site is now only and exclusively for Internet Explorer 5.5 and
higher under Windows 98 SE and higher.
Any other visitors are out of support and interest of Microsoft - at
least in JScript domain. It is bad and rude, but it is and I''m affraid
it will be.
Xah Lee写道：
Xah Lee wrote:
有时候在过去的几个月里，显然微软改变了他们的JavaScript文档网站：
http：// msdn。 microsoft.com/library/de...bfe2330aa9.asp
所以，一个人必须该死的按扩展按钮查看
文档，每个该死的页面。
他妈的是怎么回事？
他们仍在使用浏览器嗅探来确定要发送到CSS的什么CSS浏览器（IE 5.2获取''ie4.css''' ，Safari获得了''n6.css''。尽管它们提供了
，但它们可以向浏览器提供数百（甚至数千）行的js文件
代码执行它们。为什么要打扰嗅探？
他们仍然在他们的风格和脚本元素中使用''<！ - - >''
- ya gotta想知道谁会使用
a浏览器浏览一个关于浏览器脚本的页面，该浏览器不知道脚本元素是什么（并且可能是超过10年的
）。 br />
在一个名为''whidbey / script.js'的文件中，他们仍然使用document.all
而没有任何回退到getElementById。不是代码名称<对于Visual Studio .NET 2005，是否为
？它是否仅使用document.all？
帧页面会产生大量错误，包括非常基本的内容
比如假装是XML的文档中没有doctype和unclosed标签。
[...]
他妈的是什么？
答：母亲的无能已经活跃起来。
sometimes in the last few months, apparently Microsoft made changes to
their JavaScript documentation website:
http://msdn.microsoft.com/library/de...bfe2330aa9.asp
so that, one has to goddamn press the "expand" button to view the
documentation, for every goddamn page.
What the fuck is going on?
They are still using browser sniffing to determine what CSS to send to
the browser (IE 5.2 gets ''ie4.css'', Safari gets ''n6.css''. Despite
that, they deliver js files with hundreds (maybe thousands) of lines
of code to browsers that can''t execute them. Why bother sniffing?
They are still using ''<!-- -->'' inside their style and script elements
- ya gotta wonder who would visit a page about browser scripting using
a browser that doesn''t know what a script element is (and is probably
more than 10 years old).
In a file called ''whidbey/script.js'' they still use document.all
without any fall back to getElementById. Isn''t whidbey the code name
for Visual Studio .NET 2005? Does it use document.all exclusively?
The frame pages generate lots of errors, including really basic things
like no doctype and unclosed tags in documents that pretend to be XML.
[...]
WHAT THE FUCK is going on?
Answer: Motherfucking incompetence has come alive.
是的。他们的Office XML标准文档运行到1,900
页面。他们的流媒体服务器和媒体
播放器界面和格式的文档在给予18个月后才被视为完全没用。
你有什么期望？
[...]
-
Zif
Yes. Their documentation for the Office XML standard runs to 1,900
pages. The documentation of their streaming media server and media
player interfaces and formats was deemed utterly useless after being
given 18 months to deliver same.
What did you expect?
[...]
--
Zif
Zif写道：
Zif wrote:
在一个名为''whidbey / script.js'的文件中，他们仍然使用document.all
回到getElementById。对于Visual Studio .NET 2005，不是代码名称吗？ ？*它是否仅使用document.all？
In a file called ''whidbey/script.js'' they still use document.all
without any fall back to getElementById. Isn''t whidbey the code name
for Visual Studio .NET 2005? ?*Does it use document.all exclusively?
我想知道他们是否有意在VS 2005中阅读该文档？
I''m wondering if they meant for that documentation to be read in VS 2005?
这篇关于微软的JavaScript文档的新问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
