When someone interacts with a webpage, the browser sends events to the relevant JavaScript code. The cut event happens when selected content is cut.
When cut happens
Selected content is cut.
You can listen for it using addEventListener(). That keeps event handling separate from HTML attributes such as onclick and works well with modern code organization.
A small working example
<label for="demo-target">Try the input</label>
<input id="demo-target" name="sample" type="text" required>
<p id="event-status" role="status">Waiting for cut...</p>
<script>
const eventTarget = document.getElementById("demo-target");
const eventStatus = document.getElementById("event-status");
if (eventTarget) {
eventTarget.addEventListener("cut", (eventDetails) => {
eventStatus.textContent = "cut event received";
console.log(eventDetails.type, eventDetails.target);
});
}
</script>
Reading the code
The browser listens for cut on the relevant target. When the event occurs, the callback receives eventDetails, updates the status message and logs the event name and target in Developer Tools.
Select field content and use the system cut shortcut.
The form example is for learning. HTML constraint validation is helpful feedback, but the server must still validate submitted values and handle requests safely.
Try it in your browser
Open the page, show the Console panel, and follow this test: Select field content and use the system cut shortcut. Then change one thing in the example and observe whether the event still fires.
Common Beginner Mistakes
- Expecting
cutto fire without its required user action or browser condition. - Select field content and use the system cut shortcut.
- Adding repeated event listeners without considering cleanup or unwanted side effects.
Key Takeaways
cutreports selected content is cut.addEventListener("cut", ...)listens for the event on the appropriate target.- Select field content and use the system cut shortcut.