Browser Extensions Development (Chrome & Edge) · Pelajaran

Memahami Izin Lanjutan

Pelajari izin sensitif seperti `activeTab`, `scripting`, dan izin host, serta pahami kapan dan bagaimana cara memintanya.

Pelajaran 1 dari 411 langkah

Memahami Izin Lanjutan adalah pelajaran Browser Extensions Development (Chrome & Edge) gratis di CoddyKit. Ini adalah pelajaran 1 dari 4. Kamu bisa membaca pelajaran lengkapnya di bawah secara gratis — lalu praktikkan langsung di browser dengan editor kode bawaan dan tutor AI 24/7. Ini adalah bagian dari jalur belajar Browser Extensions Development (Chrome & Edge), dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus Browser Extensions Development (Chrome & Edge) mencakup 4 pelajaran total.

Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.

Beyond Basic Permissions

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

Granting Web Access

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.

Manifesting Host Access

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:

{
  "name": "My Extension",
  "version": "1.0",
  "manifest_version": 3,
  "host_permissions": [
    "https://www.google.com/*"
  ]
}

Broad Access with Wildcards

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.

{
  "name": "My Extension",
  "version": "1.0",
  "manifest_version": 3,
  "host_permissions": [
    "<all_urls>"
  ]
}

Temporary Tab Privileges

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.

{
  "name": "My Extension",
  "version": "1.0",
  "manifest_version": 3,
  "permissions": [
    "activeTab"
  ]
}

Getting Current Tab URL

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:

// This script runs when the extension popup opens.
document.addEventListener('DOMContentLoaded', function() {
  chrome.tabs.query({ active: true, currentWindow: true }, function(tabs) {
    if (tabs.length > 0) {
      const activeTab = tabs[0];
      console.log('Active tab URL:', activeTab.url);
      // Display in popup for demonstration
      document.body.innerHTML = `<p>Current URL: ${activeTab.url}</p>`;
    } else {
      document.body.innerHTML = `<p>No active tab.</p>`;
    }
  });
});

Programmatic Code Injection

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.

{
  "name": "My Extension",
  "version": "1.0",
  "manifest_version": 3,
  "permissions": [
    "scripting"
  ],
  "host_permissions": [
    "https://www.example.com/*"
  ]
}

Modifying a Page

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:

// This code would typically run from a background script
// or popup after a user action.
chrome.tabs.query({ active: true, currentWindow: true }, function(tabs) {
  if (tabs.length > 0) {
    const activeTabId = tabs[0].id;
    chrome.scripting.executeScript({
      target: { tabId: activeTabId },
      function: () => {
        // This function runs in the context of the web page
        document.body.style.backgroundColor = 'lightblue';
        console.log('CoddyKit: Page background changed!');
      }
    });
  }
});

Least Privilege Principle

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.

Permission Scenarios

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?

Advanced Permissions Summary

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!

Gratis untuk memulai

Belajar JavaScript dengan tutor AI — gratis

Tulis dan jalankan kode asli di browser kamu, dapatkan bantuan instan dari tutor AI 24/7, dan lanjutkan di mana kamu tinggalkan di web atau aplikasi.

Kursus
12
Pelajaran
48

Pertanyaan yang Sering Diajukan

Apakah pelajaran “Memahami Izin Lanjutan” gratis?

Ya — teks lengkap “Memahami Izin Lanjutan” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus Browser Extensions Development (Chrome & Edge), upgrade ke CoddyKit PRO. Kursus Browser Extensions Development (Chrome & Edge) mencakup 4 pelajaran total.

Apa yang akan aku pelajari di “Memahami Izin Lanjutan”?

Pelajari izin sensitif seperti `activeTab`, `scripting`, dan izin host, serta pahami kapan dan bagaimana cara memintanya. Kamu berlatih Browser Extensions Development (Chrome & Edge) dengan kode praktik yang langsung kamu jalankan di browser, dan tutor AI 24/7 menjawab pertanyaanmu saat kamu mengerjakan pelajaran ini.

Apakah aku perlu pengalaman untuk memulai Browser Extensions Development (Chrome & Edge)?

Tidak diperlukan pengalaman sebelumnya. Browser Extensions Development (Chrome & Edge) di CoddyKit dirancang untuk pemula hingga pelajar tingkat lanjut, jadi kamu bisa memulai di sini atau dari awal dan belajar sesuai kecepatan kamu sendiri. Ini adalah pelajaran 1 dari 4.

Berapa lama pelajaran “Memahami Izin Lanjutan” memakan waktu?

Sebagian besar pelajaran CoddyKit memakan waktu sekitar 5–10 menit. Setiap pelajaran ringkas dan interaktif, jadi kamu membuat kemajuan stabil dan melanjutkan dari tempat kamu tinggalkan di web dan aplikasi.

Bisakah aku menulis dan menjalankan kode dalam pelajaran Browser Extensions Development (Chrome & Edge) ini?

Ya. Setiap pelajaran Browser Extensions Development (Chrome & Edge) menyertakan editor kode bawaan, jadi kamu menulis dan menjalankan kode nyata langsung di browser dan mendapatkan umpan balik AI instan — tidak diperlukan penyiapan lokal.

Semua pelajaran dalam kursus ini

  1. Memahami Izin Lanjutan
  2. Praktik Pemrograman Aman
  3. Kebijakan Keamanan Konten (CSP)
  4. Izin Opsional dan Permintaan Saat Berjalan
← Kembali ke Browser Extensions Development (Chrome & Edge)