◆ HTML

Retrieve element's actual width and height

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 taskGet the exact width and height of the main banner image on the homepage, so I can update the…+
Get the exact width and height of the main banner image on the homepage, so I can update the design spec for the new campaign assets.
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 finalize the layout for the new dashboard, I need to know the true rendered width and…+
Before I finalize the layout for the new dashboard, I need to know the true rendered width and height of the user profile widget after all CSS has been applied. I need these precise dimensions to ensure the surrounding elements align perfectly and don't overlap, creating a clean interface for the user.
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 'Latest News' content block is overflowing horizontally on mobile, but when I inspect it,…+
A critical content block is overflowing on mobile, but its reported dimensions are wrong.
The 'Latest News' content block is overflowing horizontally on mobile, but when I inspect it, the reported width seems fine. I'm afraid it's going to look broken for half our audience. I suspect some padding or border isn't being accounted for in the dimensions I'm seeing. What's the actual rendered width and height of that block, including all its box model properties, and what's the best way to get that precise measurement to fix the overflow?
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 run into layout problems where elements overlap or create unwanted scrollbars…+
Layout issues often stem from not knowing an element's true rendered size.
I frequently run into layout problems where elements overlap or create unwanted scrollbars because I misjudge their true rendered size, especially with dynamic content or complex CSS. I waste time tweaking values. What's the key habit I need to cultivate to accurately determine an element's actual width and height, including all its box model properties, to prevent these recurring layout mishaps?
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.