◆ HTML

Check if DOM element is visible in viewport

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 taskWrite the JavaScript function 'checkVisibility' that returns true if the 'cookie-banner' div is…+
Write the JavaScript function 'checkVisibility' that returns true if the 'cookie-banner' div is currently visible within the user's browser viewport.
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 launch the new product tour, create a function that checks if each step's modal is…+
Before we launch the new product tour, create a function that checks if each step's modal is fully visible. The marketing team needs to confirm users are seeing the entire message, not just part of it, especially on smaller screens.
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 'add-to-cart' button is sometimes not triggering its animation, even when it should be on…+
The 'add-to-cart' button is sometimes not triggering its animation, even when it should be on screen.
The 'add-to-cart' button is sometimes not triggering its animation, even when it should be on screen, according to user reports. This is directly impacting conversion rates. I'm using an Intersection Observer, but I suspect it's misfiring or the threshold is off. What's the most likely diagnosis for this intermittent failure, and what's the best next step to reliably detect when the button is truly visible for the buyer?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI often struggle to reliably detect when elements are truly visible to the user, leading to…+
I often struggle to reliably detect when elements are truly visible to the user.
I often struggle to reliably detect when elements are truly visible to the user, leading to inconsistent UX for animations or lazy loading. It's frustrating when features don't behave as expected across different devices. What habit should I change in my approach to checking DOM element visibility to ensure consistent and reliable behavior for our users?
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.