-
Notifications
You must be signed in to change notification settings - Fork 2
/
Background-information-for-developers.html
25 lines (25 loc) · 2.04 KB
/
Background-information-for-developers.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<meta name="generator" content="pandoc">
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes">
<title></title>
<style type="text/css">code{white-space: pre;}</style>
<link rel="stylesheet" href="./github-markdown.css">
<!--[if lt IE 9]>
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
<![endif]-->
<link rel="icon" type="image/x-icon" href="favicon.ico" />
</head>
<body>
<h1 id="background-information-for-developers">Background information for developers</h1>
<p>The information provided on this page might be interesting for developers.</p>
<h2 id="extension-ids">extension IDs</h2>
<p>There are two extension IDs in use, called <em>On-AMO</em> and <em>Off-AMO</em> ID. The <strong>On-AMO</strong> ID is used for any release published on <a href="https://addons.mozilla.org/en-US/firefox/addon/requestpolicy-continued/">AMO</a>. As of the time I'm writing, only the v0.5 branch is offered on AMO, see issue <a href="https://github.com/RequestPolicyContinued/requestpolicy/issues/543">#543</a>. The <strong>Off-AMO</strong> ID is used for <a href="https://github.com/RequestPolicyContinued/requestpolicy/releases">releases on GitHub</a>. It includes an <a href="https://developer.mozilla.org/en-US/Add-ons/Install_Manifests#updateURL"><code>updateURL</code></a> which points to <a href="https://github.com/RequestPolicyContinued/RequestPolicyContinued.github.io/blob/master/xpi/update-1.x-beta.rdf"><code>update-1.x-beta.rdf</code></a>. The extra, off-AMO ID is needed due to <a href="https://wiki.mozilla.org/Addons/Extension_Signing">Extension Signing</a>.</p>
<h2 id="xpcshell">xpcshell</h2>
<ul>
<li>Mozilla's xpcshell tests are run using <code>mach</code>. In order to run custom (e.g. RequestPolicy's) xpcshell unit tests, there are two possibilities: (a) integrate the tests into <code>mozilla-central</code>; (b) use <code>runxpcshelltests.py</code>. Option (b) seemed to be much easier to me.</li>
</ul>
</body>
</html>