118
edits
Community:SummerOfCode17/AndroidWebExtensions: Difference between revisions
Jump to navigation
Jump to search
Community:SummerOfCode17/AndroidWebExtensions (view source)
Revision as of 19:30, 10 March 2017
, 10 March 2017→APIs
(→APIs) |
|||
| Line 30: | Line 30: | ||
|- | |- | ||
! API | ! API | ||
! Description / Hints | |||
|- | |- | ||
| [https://developer.mozilla.org/en-US/Add-ons/WebExtensions/API/contextMenus contextMenus] | | [https://developer.mozilla.org/en-US/Add-ons/WebExtensions/API/contextMenus contextMenus] | ||
| An API for adding items to the browser's context menu. Fennec already has a legacy API for context menus ([https://developer.mozilla.org/en-US/Add-ons/Firefox_for_Android/API/NativeWindow#contextmenus See MDN]). Hooking up the web extension API to the legacy API should be a good first step. Depending on differences in the APIs additional functionality needs to be implemented. | |||
|- | |- | ||
| [https://developer.chrome.com/extensions/browsingData browsingData] | | [https://developer.chrome.com/extensions/browsingData browsingData] | ||
| API to remove browsing data from a user's profile. Most of the browsing data of Firefox for Android is handled by the Java / Android layer. Implementing this API will require notifying the Java layer via events and then removing the specified data from the profile. | |||
|- | |- | ||
| [https://developer. | | [https://developer.chrome.com/apps/identity identity] | ||
| (See API docs) | |||
|- | |- | ||
| [https://developer.mozilla.org/en-US/ | | [https://developer.chrome.com/extensions/proxy proxy] | ||
| Implementing this API can be tricky: Most requests are performed by [https://developer.mozilla.org/en-US/docs/Mozilla/Gecko Gecko]. But there are some requests done by Java / Android. Not all of them honor the proxy settings. Besides implementing this API it might be required to identify requests not using proxies and adding support for that. | |||
|} | |} | ||