Experimental: This is an experimental technology
Check the Browser compatibility table carefully before using this in production.
The source read-only property of the ToggleEvent interface is an Element object instance representing the HTML popover control element that initiated the toggle.
An Element object instance, or null if the popover was not activated by a control element.
A <button> element can be set as a popover control by specifying the id of the popover element in its commandfor or popovertarget attribute (if the button is specified using <input type="button">, only the popovertarget attribute works).
When the toggle event fires on the popover, the ToggleEvent event object's source property will then contain a reference to the popover control button that initiated the toggle. This is useful for running different code in response to the toggle event depending on which control initiated it (see an example).
Before the source property was available, developers would have to reimplement the command attribute functionality from scratch to provide a similar identifier and then monitor it with JavaScript to know which button invoked the popover. In addition, there was a danger of such JavaScript tasks blocking the showing or hiding of the popover. The toggle event is asynchronous, and therefore avoids this problem.
If the popover was not activated by a control button â for example, if the popover is being controlled using a JavaScript method such as HTMLElement.togglePopover() â the source property returns null.
source usage
This demo shows how to use the source property to perform a different action depending on which control button was used to close a popover.
Our markup contains a <button>, a <p>, and a <div> element. The <div> is designated as an auto popover, and the button is designated as a control for showing the popover using the commandfor and command attributes.
The popover contains a heading asking the user if they would like a cookie, and two buttons allowing them to select an answer of "yes" or "no". Each one of these buttons is designated as a control for hiding the popover.
<button commandfor="popover" command="show-popover">
Select cookie preference
</button>
<p id="output"></p>
<div id="popover" popover="auto">
<h3>Would you like a cookie?</h3>
<button id="yes" commandfor="popover" command="hide-popover">Yes</button>
<button id="no" commandfor="popover" command="hide-popover">No</button>
</div>
html {
font-family: sans-serif;
}
[popover] {
border: 1px solid grey;
padding: 10px 20px;
border-radius: 5px;
}
[popover] h3 {
margin: 0 0 10px;
}
In our script, we start off by grabbing references to the "yes" and "no" buttons, the popover, and the output <p>.
const yesBtn = document.getElementById("yes");
const noBtn = document.getElementById("no");
const popover = document.getElementById("popover");
const output = document.getElementById("output");
We then add some feature detection to detect whether the HTML command attribute is supported, and whether the source property is supported. If either are not supported, we output an appropriate message to the output <p>. If both are supported, we add a toggle event listener to the popover. When fired, it checks if the "yes" or the "no" button was used to toggle (hide) the popover; an appropriate message is printed to the output <p> in each case.
if (yesBtn.command === undefined) {
output.textContent = "Popover control command attribute not supported.";
} else {
popover.addEventListener("toggle", (event) => {
if (event.source === undefined) {
output.textContent = "ToggleEvent.source not supported.";
} else if (event.source === yesBtn) {
output.textContent = "Cookie set!";
} else if (event.source === noBtn) {
output.textContent = "No cookie set.";
}
});
}
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4