After the recent row between developers of the AdBlock Plus and NoScript add-ons for Firefox, Mozilla is considering creating an add-on policy. Mozilla’s proposal follows.

Changes to default home page and search preferences, as well as settings of other installed add-ons, must be related to the core functionality of the add-on. If this relation can be established, you must adhere to the following requirements when making changes to these settings:

• The add-on description must clearly state what changes the add-on makes.
• All changes must be ‘opt-in’, meaning the user must take non-default action to enact the change.
• Uninstalling the add-on restores the user’s original settings if they were changed.

These are minimum requirements and not a guarantee that your add-on will be approved.

NoScripts developer has already agreed to this policy and has released an update to its extension.

A war has broken out between two of Firefox’s most used plug-ins, AdBlock Plus and NoScript, with both scripts trying to out do each other by disabling the others features.

The war started as a result of AdBlock Plus blocking ads in NoScript’s change log window. The change log window is displayed every time NoScript is updated, which as of late has been rather frequent, and is NoScript’s only source of income.

AdBlock is of course doing what it does best, blocking ads, regardless of the source. The AdBlock blog has a full list of events as they see the current situation.