Use the clarativeContent API to take actions depending on the content of a page, without requiring permission to read the page's content. Use the Debuggee tabId to target tabs with sendCommand and route events by tabId from onEvent callbacks. Use bugger to attach to one or more tabs to instrument network interaction, debug JavaScript, mutate the DOM and CSS, etc. The bugger API serves as an alternate transport for Chrome's remote debugging protocol.
Use the okies API to query and modify cookies, and to be notified when they change. You can choose what types of objects your context menu additions apply to, such as images, hyperlinks, and pages. Use the ntextMenus API to add items to Google Chrome's context menu. More generally speaking, content settings allow you to customize Chrome's behavior on a per-site basis instead of globally.
Use the ntentSettings API to change settings that control whether websites can use features such as cookies, JavaScript, and plugins. Use the commands API to add keyboard shortcuts that trigger actions in your extension, for example, an action to open the browser action or send a command to the extension. Use this API to expose certificates to the platform which can use these certificates for TLS authentications. Note that accessibilityFeatures.modify does not imply accessibilityFeatures.read permission. For modifying feature state, the extension needs accessibilityFeatures.modify permission. In order to get feature states the extension must request accessibilityFeatures.read permission. This API relies on the ChromeSetting prototype of the type API for getting and setting individual accessibility features. Use the chrome.accessibilityFeatures API to manage Chrome's accessibility features. Release information is not available for APIs before Chrome 42, which was released in early 2015. If you need to know the outcome of an operation, then you pass a callback function into the method. Unless the doc says otherwise, methods in the chrome.* APIs are asynchronous: they return immediately, without waiting for the operation to finish. Meanwhile, we kindly suggest using Google Chrome or Microsoft Edge to get the best out of Wordmark.Chrome provides extensions with many special-purpose APIs like ntime and chrome.alarms. We are eagerly waiting for the new Local Font Access API to be implemented by all the browsers. Unfortunately there are no methods currently available to detect your installed fonts within these browsers. Brave users need to turn off Brave Shield from the address bar.You will need to restart your browser after installing new fonts.You should only prefer this option if Local Font Access feature is not available.This extension is a very simple add-on that shares the list of your fonts with Wordmark. Until the new Local Font Access feature is supported, these Chromium based browsers can use our extension available on Chrome Web Store. Opera, Yandex, Brave and other Chromium browsers Meanwhile you can consider using Google Chrome or Microsoft Edge to see all your fonts on Wordmark. We are following its developement and will add it once Unfortunately this feature is not supported by your browser yet.
We will be gradually prompting the extension users to switch to Local Font Access. If you are currently using our browser extension, your Local Font Acesss permission will be the prefered methodįor showing your fonts. You can read more about site permissions on Google's help documents. Great! Your browser supports this feature but needs your permission to show all your fonts on Wordmark.Ĭlick the padlock icon on the left of the address bar and toggle Fonts on.
0 kommentar(er)
