◆ HTML

Hide scroll bar while still scrolling

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

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskFor the new product page, make sure the content still scrolls, but hide the scrollbar so it…+
For the new product page, make sure the content still scrolls, but hide the scrollbar so it looks cleaner on desktop browsers for the launch on Tuesday.
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 the new product page live, hide the scrollbar while keeping the content…+
Before we push the new product page live, hide the scrollbar while keeping the content scrollable. It needs to look seamless on all browsers and not confuse users trying to scroll.
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 client loves the new landing page design, but it shows a hidden scrollbar on a section that…+
The client just approved the design for the new landing page, but the design has a hidden scrollbar on a scrollable section.
The client loves the new landing page design, but it shows a hidden scrollbar on a section that needs to scroll. I'm worried it will break on different browsers or confuse users who can't see the scroll indicator. What's the most robust way to hide the scrollbar while ensuring smooth scrolling across all devices, and what should I tell the client about potential usability issues before Friday's launch?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm constantly asked to hide scrollbars for 'cleaner' designs, but it often leads to…+
I keep getting requests for 'cleaner' designs that involve hiding standard UI elements like scrollbars.
I'm constantly asked to hide scrollbars for 'cleaner' designs, but it often leads to cross-browser headaches or user confusion. I waste too much time trying to make these hacks robust. What habit should I change to better manage these design requests and push back effectively on risky aesthetic choices without alienating the design team?
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.