◆ JavaScript

Detect click outside element

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts
See the prompt↓All JavaScript tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskWrite a JavaScript function that detects when a click happens outside of the 'user-menu' div…+
Write a JavaScript function that detects when a click happens outside of the 'user-menu' div and then calls the 'closeMenu' function.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I push the new dropdown menu, write a reusable hook or utility function that detects…+
Before I push the new dropdown menu, write a reusable hook or utility function that detects clicks outside of a specified DOM element. It needs to handle multiple instances of the same component on the page and prevent the click from closing other elements if the user intended to interact with a different part of the UI, so the user experience is smooth.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentMy new modal dialog is closing itself when I click a button that's part of a different…+
My new modal dialog is closing unexpectedly when the user clicks on a button that's actually inside another component.
My new modal dialog is closing itself when I click a button that's part of a different component on the page, even though that button is clearly outside the modal's boundaries. I'm afraid my 'click outside' logic is too broad or is interfering with other event listeners. I can't tell if the event is bubbling incorrectly or if my element reference is wrong. What's the most likely cause for this misbehavior, and how can I precisely ensure a click only closes the modal if it's truly outside its content?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep having issues where my 'click outside' logic for dropdowns, modals, and tooltips either…+
I consistently struggle to implement reliable 'click outside' logic for various UI components, leading to unexpected behavior.
I keep having issues where my 'click outside' logic for dropdowns, modals, and tooltips either doesn't work consistently or interferes with other UI elements, causing bugs and a poor user experience. This costs me time in debugging and refactoring. What habit should I change to implement 'click outside' detection reliably and without unintended side effects every time?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from JavaScript's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.