◆ HTML

Hide a DIV when user clicks outside

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 HTML tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskMake sure this 'share' dropdown menu disappears when the user clicks anywhere outside of it, so…+
Make sure this 'share' dropdown menu disappears when the user clicks anywhere outside of it, so it doesn't stay open indefinitely.
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 we push this new notification panel live, ensure it closes automatically if the user…+
Before we push this new notification panel live, ensure it closes automatically if the user clicks anywhere outside of it, but not if they click inside it. Also, make sure it stays open if they scroll, so they can interact with its content without it vanishing unexpectedly.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe new 'user settings' pop-up I just implemented is staying open on the screen even when I…+
The new 'user settings' pop-up stays open even after I click away from it.
The new 'user settings' pop-up I just implemented is staying open on the screen even when I click outside of it. This is really distracting and makes the interface feel clunky. I'm afraid users will get frustrated and think the site is broken. What's the most common reason a 'click outside to close' function fails, and what's the most robust way to implement it so it reliably closes when it should, but not when interacting with 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 frequently struggle with getting overlay elements like dropdowns or modals to close reliably…+
My interactive elements often don't close when users click outside them, creating a messy interface.
I frequently struggle with getting overlay elements like dropdowns or modals to close reliably when a user clicks outside them. This leads to a cluttered interface and a poor user experience. What habit should I change in my approach to handling outside clicks for interactive components to ensure they always behave as expected and keep the UI clean?
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 HTML'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.