fang5566
管理员
管理员
  • UID3719
  • 注册日期2005-03-07
  • 最后登录2024-03-21
  • 发帖数18482
  • 经验4836枚
  • 威望5点
  • 贡献值4316点
  • 好评度1115点
  • 社区居民
  • 最爱沙发
  • 忠实会员
  • 终身成就
阅读:8130回复:0

Firefox 32 附加组件兼容性

楼主#
更多 发布于:2014-08-18 14:46
Firefox 32 will be released on September 2nd. Here’s the list of changes that went into this
version that can affect add-on compatibility. There is more information
available in Firefox 32 for Developers, so you should read that too.

General



Content scripts


Implement Xrays to Object objects, Implement Xrays to Array objects. This extends an important security barrier between privileged and unprivileged code, called Xray Vision.
 In a nutshell, it protects privileged scripts from running unexpected
code when calling familiar functions in content code, like window.alert, which can be replaced by page scripts. It ensures that you always call the original function.
For better separation between privileged and unprivileged code, we recommend that you start looking into the Message Manager.
 We will be writing more about it soon, because using the Message
Manager will be necessary when Firefox moves to a multi-process
architecture (known as Electrolysis or e10s for short). The sooner you
start using it in your add-on, the better.

XPCOM



New!

  • Provide add-ons a standard directory to store data, settings.
     Most add-on devs know that they should store their data somewhere in
    the profile directory (preferences should only store small configuration
     values), but we don’t have a clear standard for this, or a good storage
     API. This first step establishes a standard directory:
    [profile]/extension-data/[add-on ID]. The follow-up bug will implement an API to make it easier to store data in that folder.
    For now, you should consider migrating your data to the new location.
    Kudos to Alex Vincent for the great work!



http://blog.mozilla.org/addons/2014/08/14/compatibility-for-firefox-32/
Firefox More than meets your experience
游客

返回顶部