forked from ParinVachhani/todo-webextension
-
Notifications
You must be signed in to change notification settings - Fork 0
/
manifest.json
65 lines (65 loc) · 3.14 KB
/
manifest.json
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
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
{
// The first three keys: manifest_version, name, and version, are mandatory and contain basic metadata for the add-on.
"manifest_version": 2,
"name": "Do It First",
"version": "1.0",
// description and homepage_url are optional
"description": "Adds a todo cum reminders list to new tab and also in place of your social media feeds in Deep Work Mode. Finish the tasks to regain access to your social media feeds.",
"homepage_url": "https://github.com/ParinVachhani/todo-webextension",
// icons is optional, but recommended: it allows you to specify an icon for the add-on, that will be shown in the Add-ons Manager.
"icons": {
"48": "icons/icon-48x48.png",
"96": "icons/icon-96x96.png"
},
// Background scripts run in the context of special pages called background pages.
// This gives them a window global, along with all the standard DOM APIs that provides.
// Background scripts can use any of the WebExtension APIs in the script, as long as their extension has the necessary permissions.
// Background scripts can make XHR requests to any hosts for which they have host permissions.
"background": {
"scripts": ["background.js"]
},
// permissions lists permissions the add-on needs. We're just asking for the activeTab permission here.
// "permissions": [
// "activeTab"
// ],
"permissions": ["storage", "tabs", "activeTab"],
// Content scripts can see and manipulate the page's DOM, just like normal scripts loaded by the page.
// Unlike normal page scripts, they can:
// > Make cross-domain XHR requests.
// > Use a small subset of the WebExtension APIs.
// > Exchange messages with their background scripts and can in this way indirectly access all the WebExtension APIs.
// Content scripts cannot directly access normal page scripts but can exchange messages with them using the standard window.postMessage() API.
"content_scripts": [
{
"matches": ["://www.facebook.com/"],
"js": ["facebook.js"]
},
{
"matches": ["https://twitter.com/"],
"js": ["twitter.js"]
}
],
// browser_action specifies the toolbar button. We're supplying three pieces of information here:
// > default_icon is mandatory, and points to the icon for the button
// > default_title is optional, and will be shown in a tooltip
// > default_popup is used if you want a popup to be shown when the user clicks the button. We do, so we've included this key and made it point to an HTML file included with the add-on.
"browser_action": {
"default_icon": "icons/icon-36x36.png",
"default_title": "Do It First"
// "default_popup": "popup/popup.html"
},
// Web accessible resources are resources such as images, HTML, CSS, and JavaScript that you include in the extension and want to make accessible to content scripts and page scripts. Resources which are made web-accessible can be referenced by page scripts and content scripts using a special URI scheme.
"web_accessible_resources": [
],
// Commands
"commands": {
"_execute_browser_action": {
"suggested_key": {
"default": "Ctrl+Shift+D"
}
}
},
"chrome_url_overrides" : {
"newtab": "popup/index.html"
}
}