◆ HTML

Hide HTML5 number input spin box

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 taskOn the quantity input field for product XYZ, remove the up and down arrows that appear inside…+
On the quantity input field for product XYZ, remove the up and down arrows that appear inside the box. I just want users to type numbers.
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 pricing calculator, make sure the number input fields for 'Quantity'…+
Before we launch the new pricing calculator, make sure the number input fields for 'Quantity' and 'Discount Percentage' look clean and professional. Hide the default spin box arrows so they don't distract from the user's input.
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 design team just reviewed the new checkout page and is complaining that the quantity input…+
The design team is complaining that the number input fields look ugly on their Macs.
The design team just reviewed the new checkout page and is complaining that the quantity input fields have ugly up/down arrows, especially on their Macs. I thought I removed them, but they're still showing for some users, and I'm afraid this is making the site look unprofessional. I can't tell if it's a browser-specific issue or if my previous fix wasn't robust enough. What's the likely diagnosis, and what's the best next move to universally hide these arrows?
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 lose time and credibility trying to hide the spin box arrows in number input…+
I keep struggling to consistently hide the spin box arrows in number input fields across browsers.
I frequently lose time and credibility trying to hide the spin box arrows in number input fields, as they often reappear in different browsers or after updates. This makes my work look inconsistent to the design team. What habit should I change to reliably ensure these arrows are hidden everywhere, 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 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.