Browser Extensions Development (Chrome & Edge) · 课时

用户界面组件之间的通信

为弹出窗口、选项页面和后台脚本建立消息通道，确保数据流转顺畅

用户界面组件之间的通信 是 CoddyKit 上的免费 Browser Extensions Development (Chrome & Edge) 课时。这是第 3 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 Browser Extensions Development (Chrome & Edge) 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Browser Extensions Development (Chrome & Edge) 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

Bridge Your Extension Components

Browser extensions are made of several parts: popups, options pages, and background scripts. Each part often runs in its own isolated environment.

To build powerful extensions, these components need to talk to each other. This lesson shows you how to establish messaging channels for seamless data flow.

Isolated Environments

Think of your extension's popup, options page, and background script as separate mini-programs. They don't automatically share data or functions.

Popup: Appears when clicked, then closes.
Options Page: A dedicated settings page.
Background Script: Runs continuously, handles events.

Messaging allows them to send information and trigger actions across these boundaries.

UI Components Send Messages

To send a message from your popup or options page to the background script, you use the chrome.runtime.sendMessage() API.

This function lets you pass a JSON object (your message) to other parts of your extension. It's great for triggering actions or sending user input.

Popup to Background Example

Here's how a popup script might send a message to the background script, for instance, to toggle a feature. This JavaScript would be in your popup.js file, linked from popup.html.

// popup.js
document.getElementById('toggleButton').addEventListener('click', () => {
  chrome.runtime.sendMessage({ action: 'toggleFeature', value: true }, (response) => {
    console.log('Received response:', response);
  });
});

Background Listens for Messages

Your background script needs to listen for incoming messages. It does this using the chrome.runtime.onMessage.addListener() event.

This listener will fire whenever any part of your extension (like a popup or options page) sends a message via chrome.runtime.sendMessage().

Background Script Listener

This snippet shows a basic message listener in your background service worker (e.g., background.js). It checks the message's action and performs a task.

// background.js
chrome.runtime.onMessage.addListener((message, sender, sendResponse) => {
  if (message.action === 'toggleFeature') {
    console.log('Feature toggled:', message.value);
    // Perform background task here
    sendResponse({ status: 'success', message: 'Feature updated!' });
  }
  // Important: Return true to indicate you want to send a response asynchronously
  return true; 
});

Sending a Response Back

Often, the component that sent the message (e.g., your popup) needs to know if the action was successful or receive data back.

The sendResponse function, provided as the third argument to your onMessage listener, allows the background script to send a one-time reply to the original sender.

Handling Background Responses

The callback function in chrome.runtime.sendMessage() is where your popup or options page receives the response from the background script. This completes the two-way communication.

// popup.js (modified)
document.getElementById('toggleButton').addEventListener('click', () => {
  chrome.runtime.sendMessage({ action: 'toggleFeature', value: true }, (response) => {
    if (chrome.runtime.lastError) {
      console.error('Error sending message:', chrome.runtime.lastError.message);
      return;
    }
    console.log('Background response:', response);
    // Update popup UI based on response
    document.getElementById('status').textContent = response.message;
  });
});

Options Pages Communicate Too

The same chrome.runtime.sendMessage() and chrome.runtime.onMessage.addListener() pattern applies to communication involving your options page.

An options page can send user-defined settings to the background script for persistence, and the background can reply with confirmation or fetched data.

Messaging Concepts

Consider an extension where a popup needs to ask the background script for the current count of unread notifications.

Which API should the popup use to initiate this request?

Recap: Seamless Data Flow

You've learned how to enable communication between your extension's UI components (popups, options pages) and its background script!

Use chrome.runtime.sendMessage() to send data.
Use chrome.runtime.onMessage.addListener() to receive data and respond.

This fundamental skill allows your extension's different parts to work together effectively.

常见问题解答

「用户界面组件之间的通信」课时是免费的吗？

是的 — 「用户界面组件之间的通信」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Browser Extensions Development (Chrome & Edge) 课程的其余内容，请升级到 CoddyKit PRO。 Browser Extensions Development (Chrome & Edge) 课程共包含 4 节课。

「用户界面组件之间的通信」这节课中我会学到什么？

为弹出窗口、选项页面和后台脚本建立消息通道，确保数据流转顺畅你通过在浏览器中直接运行的动手代码来练习 Browser Extensions Development (Chrome & Edge)，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 Browser Extensions Development (Chrome & Edge) 需要有经验吗？

无需任何先前经验。CoddyKit 上的 Browser Extensions Development (Chrome & Edge) 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 3 节课，共 4 节。

「用户界面组件之间的通信」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 Browser Extensions Development (Chrome & Edge) 课中编写并运行代码吗？

能。每节 Browser Extensions Development (Chrome & Edge) 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 Browser Extensions Development (Chrome & Edge)