Расширенные разрешения

Welcome! In this lesson, we'll dive into advanced browser extension permissions. These permissions grant powerful capabilities, allowing your extension to interact more deeply with web content and user data.

Understanding them is crucial for building robust extensions while maintaining user trust and security.

We'll cover:

• Host Permissions
• activeTab Permission
• scripting Permission

Host permissions are fundamental. They define which websites your extension can interact with. This includes reading data, modifying content, or making network requests on those specific sites.

Think of them as "keys" that unlock access to certain web domains.

You declare host permissions in your manifest.json file under the host_permissions key. Each string is a URL pattern.

For instance, to allow access to all pages on google.com, you'd specify:

You can use wildcards (*) for broader access. For example, "<all_urls>" (or "*://*/*") grants access to all URLs, on all schemes (HTTP, HTTPS).

While powerful, using broad wildcards should be done with extreme caution, as it grants your extension significant control over the user's browsing experience on any site.

The activeTab permission is a safer alternative to broad host permissions for one-off actions on the current page.

When the user invokes your extension (e.g., clicks its icon), activeTab grants your extension temporary host permissions to the currently active tab. These permissions last until the user navigates away or closes the tab.

With activeTab, your extension can access information about the current tab, like its URL or title, without needing permanent host permissions.

Try running this example. Imagine this code is in your extension's popup script:

The scripting permission allows your extension to programmatically inject JavaScript and CSS into web pages. This is how you modify a page's content or behavior.

It's an essential permission for content scripts, replacing the Manifest V2 tabs.executeScript API.

Once you have scripting permission (and host permission for the target tab), you can inject code. This example injects a simple script to change the background color of the active tab.

Imagine this running in your background script or popup:

Always follow the Principle of Least Privilege: request only the permissions your extension absolutely needs.

• Required Permissions: Declared in manifest.json and requested at install.
• Optional Permissions: Can be requested at runtime using chrome.permissions.request() only when the user needs that specific feature. This gives users more control and builds trust.

Which permission(s) would you need for an extension that, when its icon is clicked, reads the current page's title and then injects a custom CSS file into that same page?

Great job! You've learned about powerful advanced permissions:

• Host Permissions: Grant access to specific websites.
• activeTab: Provides temporary host permissions to the active tab upon user invocation, ideal for one-off actions.
• scripting: Enables programmatic injection of JavaScript and CSS.

Always use the least privileged approach to ensure security and user trust. Next, we'll explore secure coding practices!