blob: 84a7210eef56f8c0a83c0eaf9eeb5705e6a440a8 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
|
---
title: 사용자 행동
slug: Mozilla/Add-ons/WebExtensions/User_actions
translation_of: Mozilla/Add-ons/WebExtensions/User_actions
---
<div>{{AddonSidebar}}</div>
<p>Some WebExtension APIs perform functions that are generally performed as a result of a user action. For example:</p>
<ul>
<li>a browser action with a popup will display the popup when the user clicks it, but there's also a {{WebExtAPIRef("browserAction.openPopup")}} API enabling an extension to open the popup programmatically.</li>
<li>if an extension adds a sidebar, it is typically opened by the user via some part of the browser's built-in user interface, such as the View/Sidebar menu. But there's also a {{WebExtAPIRef("sidebarAction.open")}} API enabling an extension to open their sidebar programmatically.</li>
</ul>
<p>To follow the principle of "no surprises", APIs like this can only be called from inside the handler for a user action. User actions include the following:</p>
<ul>
<li>Clicking the extension's browser action or page action.</li>
<li>Selecting a context menu item defined by the extension.</li>
<li>Activating a keyboard shortcut defined by the extension (this only treated as a user action from Firefox 63 onwards).</li>
<li>Clicking a button in a page bundled with the extension.</li>
</ul>
<p>For example:</p>
<pre class="brush: js">function handleClick() {
browser.sidebarAction.open();
}
browser.browserAction.onClicked.addListener(handleClick);</pre>
<p>Note that user actions in normal web pages are not treated as user actions for this purpose. For example, if a user clicks a button in a normal web page, and a content script has added a click handler for that button and in that handler sends a message to the extension's background page, then the background page message handler is not considered to be handling a user action.</p>
<p>Also, if a user input handler waits on a <a href="/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise">promise</a>, then its status as a user input handler is lost. For example:</p>
<pre class="brush: js">async function handleClick() {
let result = await someAsyncFunction();
// this will fail, because the handler lost its "user action handler" status
browser.sidebarAction.open();
}
browser.browserAction.onClicked.addListener(handleClick);</pre>
|
