◆ JavaScript

Handle cross-browser issues

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 taskUsers report the date picker crashes in Safari 14. Reproduce the bug in Safari on macOS,…+
Users report the date picker crashes in Safari 14. Reproduce the bug in Safari on macOS, localize the offending code in date-picker.js where Intl.DateTimeFormat is used, add a feature detection fallback for the Safari behavior, test in Chrome and Firefox, and push 'fix: date picker Safari fallback' by Thursday so marketing's demo works.
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 change the date picker to handle Safari, make the fix easy to approve: show the Safari…+
Before I change the date picker to handle Safari, make the fix easy to approve: show the Safari stack trace and the Intl call suspected, propose a minimal feature-detection fallback with a short comment explaining why it's needed, and list the browsers/versions tested so the reviewer can focus on the compatibility risk rather than re-reading the code.
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 date picker works in Chrome but throws in Safari 14. I suspect Intl.DateTimeFormat…+
The date picker fails only in Safari and I don't know why.
The date picker works in Chrome but throws in Safari 14. I suspect Intl.DateTimeFormat differences but I'm unsure which behavior to rely on. I am the release owner for the demo and can't delay. Which quick diagnostic confirms whether Intl is the issue, and what is the safest fallback to implement instantly that won't break Firefox or Edge?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWe keep shipping features that work in Chrome but fail in other browsers, causing late QA…+
Cross-browser bugs keep appearing late in QA.
We keep shipping features that work in Chrome but fail in other browsers, causing late QA fire-drills. Root causes seem to be missing cross-browser testing, implicit reliance on modern APIs, and no feature-detection patterns. Which single process change will reduce these late failures the most: adding a Safari VM to CI, requiring feature detection for all new APIs, or a compatibility checklist during PR? Which is fastest to adopt for our small 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 JavaScript'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.