Canmove, confirm
1,567
edits
Changes
→Blocklist syntax
<match name="description" exp="1[.]2[.]3"/>
<match name="filename" exp=".*\.exe"/>
</pluginItem>
<pluginItem os="Linux" xpcomabi="x86_64-gcc3">
<!-- All match tags must match a plugin to blocklist a plugin -->
<match name="name" exp="some other luginplugin"/>
<match name="description" exp="5[.]6[.]7"/>
<match name="filename" exp="npplugin\.dll"/>
</pluginItem>
<pluginItem os="Linux" xpcomabi="x86_64-gcc3">
<!-- All match tags must match a plugin to blocklist a plugin -->
<match name="name" exp="some bad plugin"/>
<versionRange>
<targetApplication id="{ec8030f7-c20a-464f-9b0e-13a3a9e97384}">
<versionRange minVersion="3.0" maxVersion="3.0.*"/>
</targetApplication>
</versionRange>
</pluginItem>
</pluginItems>
* The second <tt>pluginItem</tt> is blocked on Linux with x86_64-gcc3 architecture. Like os, xpcomabi is a comma separated list and matches against the [http://developer.mozilla.org/en/docs/XPCOM_ABI XPCOM ABI] of the application.
* The third <tt>pluginItem</tt> is blocked only on Firefox versions 3-3.0.*
As can be seen it is possible to blocklist all version of an extension for all versions of an application as well as any combination of application id's along with version ranges for both the extension id and application id. Also, by not specifying a value and instead using the default value it is possible to lessen the size of the blocklist xml file. This is possible by using the following defaults:
