Your coding agent proposes a new CSS feature. The preview looks right in your browser, but a teammate opens it in an older browser and the layout breaks. Before approving the change, tell the agent which browsers your project supports and ask it to explain what happens when the new feature is unavailable.

Google’s November 10 announcement introduced the stable release of Modern Web Guidance 1.0, a collection of guidance for coding agents that uses Baseline browser compatibility data. The most useful place to start is a single change with a clear support target and a short list of behaviors a reviewer can check.
Choose the support target before requesting code
Start with the project’s existing browser support policy. For a public website, that might include an older browser that still accounts for meaningful use. For an internal tool, the target might come from the company’s managed browser versions. If the project already uses a Baseline target, give that target to the agent explicitly. The Modern Web Guidance setup guide says the tool defaults to Baseline Widely available when you leave the target unspecified. Keep any specific browser requirements alongside that target so they survive the handoff.
Ask for one change with a usable fallback
Suppose a fictional account settings page uses a fixed layout that crowds its Save button on narrow screens. Ask the agent to improve that layout within the existing support policy. Tell it to keep every field and action reachable if its preferred CSS feature is unavailable. Ask it to identify the feature, the fallback and the checks a reviewer should run.
Update the account settings form for narrow viewports. Follow the browser support policy in this repository. Keep every field and the Save button reachable without horizontal scrolling. If you use a newer CSS feature, explain what users see without it. Preserve the form’s keyboard order and visible focus. Report the checks you ran and the checks still pending.
This leaves the implementation open while defining a result you can verify. If the agent cannot find a support policy, settle that question before accepting a new dependency.
Test the part a screenshot cannot prove
Check the change in the browsers covered by your policy, including one near the oldest version you support. Try a narrow viewport and longer field labels. Then use the keyboard to reach each input and the Save button. Check that focus remains visible and that an invalid submission gives the user a clear way to find and correct the problem. These checks answer different questions. A layout can fit the screen while leaving keyboard users unsure where they are.
Use a preview to inspect the change quickly, then record which browsers you actually checked. If your development server runs on another machine, see TechPulse’s guide to previewing remote apps in VS Code.
Leave a review note the next maintainer can use
Record the support target, the feature introduced, the fallback behavior and the verified browser versions. If a check is pending, say who will run it and what result they should look for. Keep that note with the change. When the browser support policy moves forward, the next maintainer can decide whether the fallback still serves a purpose.
Prepared with AI assistance using Chrome’s announcement and documentation. The form example is illustrative. Read the TechPulse editorial policy.
✍️ Leave a Comment