xml – 为什么不推荐使用E4X并从某些浏览器中删除？

发布时间：2020-12-16 23:12:30 所属栏目：百科来源：网络整理

导读：为什么E4X已被弃用并从某些浏览器中删除？ Warning: E4X is obselete. It’s been disabled by default for chrome in Firefox 17,and completely removed in Firefox 21. Use DOMParser/DOMSerializer or a non-native JXON algorithm instead. https://dev

为什么E4X已被弃用并从某些浏览器中删除？

Warning: E4X is obselete. It’s been disabled by default for chrome in
Firefox 17,and completely removed in Firefox 21. Use
DOMParser/DOMSerializer or a non-native JXON algorithm instead.

https://developer.mozilla.org/en-US/docs/Archive/Web/E4X/Processing_XML_with_E4X

解决方法

它被弃用并从唯一支持它的浏览器中删除,因为它是一个执行不佳的语言功能,导致各种问题.

As Brendan said somewhere “E4X is crazyland”,and FF’s implementation of E4X deviates from the spec in ways that are not written down anywhere.

— Mark S. Miller

The only way for it to come back would be via a new edition of ECMA-357,which Adobe and Mozilla were going to work on. Until then,it’s out.

— Brendan Eich

The idea behind it wasn’t bad,but the way it was integrated into the language was. SpiderMonkey was the only JS engine that ever implemented it,and there were endless problems caused by that and severe complications of the engine’s implementation required for this support.

— Till Schneidereit

从Bug 695577起

（编辑：李大同）

【声明】本站内容均来自网络，其相关言论仅代表作者个人观点，不代表本站立场。若无意侵犯到您的权利，请及时与联系站长删除相关内容!