Answers and explanations · Debug and prepare a static release

Compare the reasoning, not just the final appearance. Other correct solutions can satisfy the same requirements.

1. Loading failure

The HTML remains readable with browser defaults because the stylesheet cannot be found at the requested path. Either restore the filename or update the link to the intended new name. Changing selectors cannot fix a file that never loaded.

2. Width failure

The late matching width declaration is a real rule the browser can apply. Removing it lets the grid and card sizing work again. Hiding horizontal overflow at body would mask the content that no longer fits, so it is not an adequate repair.

3. Honest release note

A useful example is: “Checked local links and image loading in Chromium at 320px and 1280px, keyboard navigation through the form, and valid/invalid invented entries. No response data is included in the local result URL. Not yet tested on a physical phone, Safari, or a screen reader. No public deployment performed.” Replace this example with your actual observations. Do not claim these tests just because this paragraph lists them.

Return to practice · Return to lesson