Mirrors
/
uBlock
mirror of https://github.com/gorhill/uBlock.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
uBlock/platform/chromium/manifest.json

119 lines
2.7 KiB
JSON
Raw Normal View History

first commit
2014-06-23 16:42:43 -06:00
{
Rephrase `author` entry in manifest
2020-01-30 10:46:54 -07:00
"author": "Raymond Hill & contributors",
complete "debian" as a target platform
2018-04-27 09:43:35 -06:00
"background": {
"page": "background.html"
},
"browser_action": {
"default_icon": {
use image data instead of paths for browser icons When using paths, platform implementations of setIcon typically will fetch the resource then convert to image data internally. It is preferable for uBO to do this conversion itself as it can be done only once at launch time. With chromium-based browsers, using image data eliminate the incessant network traffic to fetch browser icons as reported in the extension's dev tool, meaning a good chunk of overhead is eliminated. Also, use optimal icon sizes, as of now both chromium and firefox prefers 16px instead of 19px, and 32px instead of 38px.
2018-05-07 17:03:50 -06:00
"16": "img/icon_16.png",
Add 64px toolbar icon for 4K displays Related issue: - https://github.com/uBlockOrigin/uBlock-issues/issues/2477
2023-03-27 10:59:39 -06:00
"32": "img/icon_32.png",
"64": "img/icon_64.png"
new feature: element zapper
2017-05-27 09:51:24 -06:00
},
complete "debian" as a target platform
2018-04-27 09:43:35 -06:00
"default_title": "uBlock Origin",
Make the new "fenix" popup panel the default one The old "classic" popup panel will still be used when at least one of the following is true: - advanced setting `uiFlavor` is set to `classic`; or - the browser is Chromium 65 or older; or - the browser is Firefox 67 or older The default configuration of the new popup panel at installation time is to show the power button, statistics and the basic tool icons, i.e. access to dashboard, logger, pickers. For existing installations, the new popup panel will be configured by respecting the existing configuration of the classic one. The new popup panel is currently already in use on Firefox for Android, and the visual redesign was made according to suggestions and feedback from <https://github.com/brampitoyo> to be optimal for Firefox for Android. The new popup panel will allow closing the following pending issues: - https://github.com/uBlockOrigin/uBlock-issues/issues/255 - https://github.com/uBlockOrigin/uBlock-issues/issues/178
2020-04-30 04:54:51 -06:00
"default_popup": "popup-fenix.html"
complete "debian" as a target platform
2018-04-27 09:43:35 -06:00
},
"commands": {
"launch-element-zapper": {
"description": "__MSG_popupTipZapper__"
first commit
2014-06-23 16:42:43 -06:00
},
complete "debian" as a target platform
2018-04-27 09:43:35 -06:00
"launch-element-picker": {
"description": "__MSG_popupTipPicker__"
continued: corralling platform-specific stuff into their meta folder
2014-11-15 19:21:13 -07:00
},
complete "debian" as a target platform
2018-04-27 09:43:35 -06:00
"launch-logger": {
"description": "__MSG_popupTipLog__"
Add keyboard support for toggling down blocking profile Related issue: - https://github.com/uBlockOrigin/uBlock-issues/issues/371 By default, no specific keyboard shortcut is predefined, this will have to be assigned by the user. The command name in English is "Toggle blocking profile". The default behavior is to toggle down according to one of the following scenarios. a) If script execution is disabled through the no-scripting switch, the no-scripting switch will be locally toggled so as to allow script execution. The page will be automatically reloaded. b) If script execution is not blocked but the 3rd-party script and/or frame cells are blocked, local no-op rules will be set so as to no longer block 3rd-party scripts and/or frames. The page will be automatically reloaded. Given this, it may take more than one toggle down command to reach the lowest blocking profile, which is one where JavaScript execution is not blocked and 3rd-party scripts and frames resources block rules, if any, are bypassed with local no-op rules. TODO: At this point, I haven't yet decided whether toggling from the lowest profile should restore the original highest blocking profile.
2019-06-26 05:47:14 -06:00
},
Add ability to open the dashboard with a keyboard shortcut Related feedback: - https://github.com/gorhill/uBlock/commit/9a6feb34d546#commitcomment-38852663
2020-04-30 08:31:23 -06:00
"open-dashboard": {
"description": "__MSG_popupTipDashboard__"
},
Use "relax" instead of "toggle" Related issue: - https://github.com/uBlockOrigin/uBlock-issues/issues/371
2019-06-27 06:16:18 -06:00
"relax-blocking-mode": {
"description": "__MSG_relaxBlockingMode__"
Add command to toggle cosmetic filtering Related issue: - https://github.com/uBlockOrigin/uBlock-issues/issues/2000
2022-02-22 06:44:09 -07:00
},
"toggle-cosmetic-filtering": {
"description": "__MSG_toggleCosmeticFiltering__"
Add support to toggle no-scripting switch with keyboard shortcut Related issue: https://github.com/uBlockOrigin/uBlock-issues/issues/692
2024-01-12 10:01:23 -07:00
},
"toggle-javascript": {
"description": "__MSG_toggleJavascript__"
complete "debian" as a target platform
2018-04-27 09:43:35 -06:00
}
},
"content_scripts": [
{
"matches": [
"http://*/*",
"https://*/*"
],
"js": [
"/js/vapi.js",
"/js/vapi-client.js",
"/js/contentscript.js"
],
Injects user styles and content scripts in `about:blank` frames Related issues: - https://github.com/uBlockOrigin/uBlock-issues/issues/688 - https://github.com/uBlockOrigin/uBlock-issues/issues/1164 `match_about_blank` is now used for content scripts and user styles.
2020-07-19 07:06:19 -06:00
"all_frames": true,
"match_about_blank": true,
"run_at": "document_start"
Work on vendor API abstraction, and near complete Safari support
2014-10-17 13:44:19 -06:00
},
complete "debian" as a target platform
2018-04-27 09:43:35 -06:00
{
"matches": [
Add easylist.to as a valid target for subscriber content script
2020-09-14 06:43:51 -06:00
"https://easylist.to/*",
Add `fanboy.co.nz` as valid location for subscription links
2020-09-14 13:46:24 -06:00
"https://*.fanboy.co.nz/*",
Revisit the behavior of the click-to-subscribe content script Related issue: - https://github.com/uBlockOrigin/uBlock-issues/issues/763 Changes: From now on, uBO will allow click-to-subscribe on only a few select domains, currently: - https://filterlists.com/ - https://github.com/ - https://github.io/ More domains can be added if and only the demonstration is made that more than a marginal number of filter lists can be subscribed from those domains. The browser alert box is no longer used to confirm subscription to a filter list. Instead, the asset viewer has been expanded to serve that purpose. This way, users can peruse at the content of a filter list before subscribing to it.
2020-09-13 06:01:53 -06:00
"https://filterlists.com/*",
Add `forums.lanik.us` as a valid location for subscription links Related issue: - https://github.com/uBlockOrigin/uBlock-issues/issues/1246
2020-09-14 13:37:53 -06:00
"https://forums.lanik.us/*",
Revisit the behavior of the click-to-subscribe content script Related issue: - https://github.com/uBlockOrigin/uBlock-issues/issues/763 Changes: From now on, uBO will allow click-to-subscribe on only a few select domains, currently: - https://filterlists.com/ - https://github.com/ - https://github.io/ More domains can be added if and only the demonstration is made that more than a marginal number of filter lists can be subscribed from those domains. The browser alert box is no longer used to confirm subscription to a filter list. Instead, the asset viewer has been expanded to serve that purpose. This way, users can peruse at the content of a filter list before subscribing to it.
2020-09-13 06:01:53 -06:00
"https://github.com/*",
Remove `letsblock.it` as target for `subscribe.js` content script Related discussion: https://github.com/uBlockOrigin/uBlock-issues/discussions/3194
2024-04-03 08:51:39 -06:00
"https://*.github.io/*"
complete "debian" as a target platform
2018-04-27 09:43:35 -06:00
],
"js": [
"/js/scriptlets/subscriber.js"
],
"run_at": "document_idle",
"all_frames": false
Add ability to update lists through links with specifically crafted URLs As per discussion with uBO volunteers. Volunteers offering support for uBO will be able to craft links with specially formed URLs, which once clicked will cause uBO to automatically force an update of specified filter lists. The URL must be crafted as shown in the example below: https://ublockorigin.github.io/uAssets/update-lists.html?listkeys=ublock-filters,easylist Where the `listkeys` parameter is a comma-separated list of tokens corresponding to filter lists. If a token does not match an enabled filter list, it will be ignored. The ability to update filter lists through a specially crafted link is available only on uBO's own support sites: - https://github.com/uBlockOrigin/ - https://reddit.com/r/uBlockOrigin/ - https://ublockorigin.github.io/ Additionally, a visual cue has been added in the "Filter lists" pane to easily spot the filter lists which have been recently updated, where "recently" is currently defined as less than an hour ago.
2023-10-14 11:41:49 -06:00
},
{
"matches": [
"https://github.com/uBlockOrigin/*",
"https://ublockorigin.github.io/*",
"https://*.reddit.com/r/uBlockOrigin/*"
],
"js": [
"/js/scriptlets/updater.js"
],
"run_at": "document_idle",
"all_frames": false
complete "debian" as a target platform
2018-04-27 09:43:35 -06:00
}
],
Add virtuous signal that remote code execution is not possible Related Chromium issue: - https://bugs.chromium.org/p/chromium/issues/detail?id=985759 By expressly restricting JavaScript execution to only code from the extension package, this explicitly tells code reviewer that uBO can't execute remote code. I also had to add `object-src 'self'`, otherwise Chromium refused to load the extension with the following error message: > 'content_security_policy': CSP directive 'object-src' must be specified `object-src 'self'` is the default value.
2019-07-21 08:37:58 -06:00
"content_security_policy": "script-src 'self'; object-src 'self'",
complete "debian" as a target platform
2018-04-27 09:43:35 -06:00
"default_locale": "en",
"description": "__MSG_extShortDesc__",
"icons": {
"16": "img/icon_16.png",
"32": "img/icon_32.png",
"64": "img/icon_64.png",
"128": "img/icon_128.png"
},
"incognito": "split",
"manifest_version": 2,
Rewrite cname uncloaking code to account for new `ipaddress=` option This commit makes the DNS resolution code better suited for both filtering on cname and ip address. The change allows early availability of ip address so that `ipaddress=` option can be matched at onBeforeRequest time. As a result, it is now possible to block root document using `ipaddress=` option -- so long as an ip address can be extracted before first onBeforeRequest() call. Related issue: https://github.com/uBlockOrigin/uBlock-issues/issues/2792 Caveat ------ the ip address used is the first one among the list of ip addresses returned by dns.resolve() method. There is no way for uBO to know which exact ip address will be used by the browser when sending the request, so this is at most a best guess. The exact IP address used by the browser is available at onHeadersReceived time, and uBO will also filter according to this value, but by then the network request has already been sent to the remote server. Possibly a future improvement would make available the whole list of ip addresses to the filtering engine, but even then it's impossible to know with certainty which ip address will ultimately be used by the browser -- it is entirely possible that the ip address used by the browser might not be in the list received through dns.resolve().
2024-09-12 09:19:57 -06:00
"minimum_chrome_version": "80.0",
complete "debian" as a target platform
2018-04-27 09:43:35 -06:00
"name": "uBlock Origin",
"options_ui": {
fix https://www.reddit.com/r/uBlockOrigin/comments/9gwrna/when_you_right_click_and_go_to_options_it_keeps/
2018-09-18 18:14:09 -06:00
"page": "dashboard.html",
"open_in_tab": true
complete "debian" as a target platform
2018-04-27 09:43:35 -06:00
},
"permissions": [
Forgot to declarare "alarms" permmission in manifest for Chromium Related commit: https://github.com/gorhill/uBlock/commit/059e4e5e28
2024-02-29 11:18:33 -07:00
"alarms",
complete "debian" as a target platform
2018-04-27 09:43:35 -06:00
"contextMenus",
"privacy",
"storage",
"tabs",
"unlimitedStorage",
"webNavigation",
"webRequest",
"webRequestBlocking",
"<all_urls>"
],
"short_name": "uBlock₀",
"storage": {
"managed_schema": "managed_storage.json"
},
"version": "1.15.11.0",
"web_accessible_resources": [
"/web_accessible_resources/*"
]
Fix version typo
2015-02-05 17:34:53 -07:00
}