![]() The last four browsers in the previous table use the same code package and minimize the need to maintain parallel versions. For example, Safari extensions can use both web and native code to communicate with counterpart native applications. If your goal is to publish your extension in the extensions store for each browser, your extension must be modified for each version to target and run in each distinct browser environment. Links to the tutorials are in the See also section, below. Some less-common APIs might be browser-specific. In most cases, a Chromium extension works as-is in different Chromium browsers and the APIs work as expected. ![]() Many of the tutorials on these sites use browser-specific APIs that might not match the browser for the app you are developing. It is just a starting point for your research. The following table isn't exhaustive or definitive. Some of the popular browsers to build extensions for include Microsoft Edge, Safari, Firefox, Chrome, Opera, and Brave. Great places to begin your extension development tutorials and documentation research are sites hosted by the browser organizations. To work directly with a specific part of the browser, such as a window or tab, you must send API requests and must often reference the browser by name.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |