CSS 表达式已不再支持在 Internet Explorer 8 标准模式下

1. click Start ，click Run ，type Inetcpl.cpl ，and then click OK . 2. 在 Internet 属性 对话框框中，单击 高级 选项卡，然后单击 多媒体 部分下 始终使用 ClearType 的 HTML 。

当您从 Internet Explorer 7 具有 ClearType 启用 Internet Explorer 8 Beta 2 的一个版本升级时，ClearType 被禁用。 要重新启用 ClearType，请按照下列步骤。

javascript.options.showInConsole = true. Logs errors in chrome files to the Error Console. nglayout.debug.disable_xul_cache = true. Disables the XUL cache so that changes to windows and dialogs do not require a restart. This assumes you're using directories rather than JARs. Changes to XUL overlays will still require reloading of the document overlaid. browser.dom.window.dump.enabled = true. Enables the use of the dump() statement to print to the standard console. See window.dump for more info. You can also use nsIConsoleService from privileged script. javascript.options.strict = true. Enables strict JavaScript warnings in the Error Console. Note that since many people have this setting turned off when developing, you will see lots of warnings for problems with their code in addition to warnings for your own extension. You can filter those with Console2. extensions.logging.enabled = true. This will send more detailed information about installation and update problems to the Error Console.

Once you have a key you need to add its public part to your add-on's install.rdf file. The simplest way to do this is to select the key then click the Install toolbar button. You must then locate your install.rdf for McCoy and the public part of the key will be added directly to the file. The file will be overwritten so take a backup if you need to.

You need to use McCoy to sign this file so that the application can verify that it really came from you. Simply select the key you originally added to the add-on's install.rdf, then click the "Sign" toolbar button, select your update.rdf file and the data in it will be signed. It's important to note that if you change any information in the update file then it must be signed again.

The updateURL uses https, or there is no updateURL at all (which defaults to addons.mozilla.org which is https) The updateURL uses http and the updateKey entry is specified which will be used to verify the data in the update manifest.

In the update manifest delivered from the updateURL the updateLink must be specified in one of the following ways: The updateLink to the XPI file must use https The updateLink can use http and you must include an updateHash for the XPI file using sha1, sha256, sha384 or sha512 hash algorithms.

Your server should serve OpenSearch plugins using the MIME type application/opensearchdescription+xml. Be sure that your Search Plugin XML is well formed. You can check by loading the file directly into Firefox. Ampersands in the template URL need to be escaped with & and tags need to be closed with a trailing slash or matching end tag. The xmlns attribute is important, without it you could get an error message indicating that "Firefox could not download the search plugin from: (URL)". Note that you must include a text/html URL — search plugins including only Atom or RSS URL types (which is valid, but Firefox doesn't support) will also generate the "could not download the search plugin" error. Remotely fetched favicons must not be larger than 10KB