DiscoveryVIP / HTML & CSS AcademyHelp

91. Browser developer tools and inspection

Module 19 · About 20 minutes · Lesson 90; review earlier concepts as needed

Open Interactive Lesson

Discover

What changes when you use browser developer tools and inspection, and how can you prove it?

Predict

Record the expected structure or visual change before rendering. Name one thing that should remain unchanged.

Understand

The browser inspector shows the interpreted DOM, matched rules, computed styles, box geometry and accessibility information. The academy offers a focused equivalent inside its isolated preview. Click Inspect Element and select a rendered node; compare its relationships and measured dimensions with source. Computed values tell you what the browser applied, while the rule list explains candidate declarations without replacing full developer tools.

Important source lines

index.html:1 <section class="inspect"><h1>Inspect this element</h1><p>Select the paragraph in the preview.</p></section>
A thematic grouping, usually identified by a heading. Attribute guidance: aria-labelledby optional for an explicitly named region.
styles.css:1 .inspect { padding:24px; border:2px solid #234f9b; }
Creates internal space between content and border. Accepted grammar: <'padding-top'>{1,4}. Context: block.

The first example teaches this lesson’s primary contract. Additional examples are optional related references or applications, each with its own purpose and source; an example without an authored check requires the stated visual/manual review.

Example 1: Browser developer tools and inspection

The inspector can show a real 24px padding value and the section’s measured outer box.

index.html

<section class="inspect"><h1>Inspect this element</h1><p>Select the paragraph in the preview.</p></section>

styles.css

.inspect { padding:24px; border:2px solid #234f9b; }

script.js

Expected: The inspector can show a real 24px padding value and the section’s measured outer box.

Edit and Render This Example
Example 2: Property: padding

Creates internal space between content and border.

index.html

<section class="stage"><article class="sample"><h2>Readable content</h2><p>Longer sample text demonstrates wrapping, spacing and typography. Change a value, inspect its computed style and compare the resulting box.</p><a href="#details">Read the details</a></article><article class="peer">A second item</article></section><section id="details"><h2>Details</h2></section>

styles.css

body { font:18px/1.5 system-ui; color:#17324d; margin:1rem; }
.stage { padding:1rem; border:1px dashed #9caec0; } .sample { padding:1rem; border:2px solid #849ab1; max-width:30rem; }
.sample { padding: 24px; }

script.js

Expected: Inspect .sample in the block context. Creates internal space between content and border. The browser’s CSS.supports and computed-style report are the authority for this installed browser; a declaration can be valid but depend on additional layout or font conditions.

Edit and Render This Example
Example 3: Property: border

Combines border width, style and color.

index.html

<section class="stage"><article class="sample"><h2>Readable content</h2><p>Longer sample text demonstrates wrapping, spacing and typography. Change a value, inspect its computed style and compare the resulting box.</p><a href="#details">Read the details</a></article><article class="peer">A second item</article></section><section id="details"><h2>Details</h2></section>

styles.css

body { font:18px/1.5 system-ui; color:#17324d; margin:1rem; }
.stage { padding:1rem; border:1px dashed #9caec0; } .sample { padding:1rem; border:2px solid #849ab1; max-width:30rem; }
.sample { border: 3px solid #234f9b; }

script.js

Expected: Inspect .sample in the block context. Combines border width, style and color. The browser’s CSS.supports and computed-style report are the authority for this installed browser; a declaration can be valid but depend on additional layout or font conditions.

Edit and Render This Example
Example 4: Inline validation

Associate error text with the invalid input and focus the field on failed submit.

index.html

<section data-component aria-label="Inline validation">
<form id="form" novalidate><label>Email <input id="email" type="email" aria-describedby="error"></label><p id="error" role="status"></p><button>Validate</button></form>
</section>

styles.css

* { box-sizing: border-box; }
body { margin: 0; color: #142537; background: #eef4fa; font: 16px/1.5 system-ui, sans-serif; }
[data-component] { max-width: 44rem; margin: 1rem auto; padding: 1rem; border: 1px solid #a1b2c4; border-radius: .75rem; background: white; }
button, input, select, textarea { font: inherit; padding: .4rem .65rem; margin: .2rem; }
button { cursor: pointer; } :focus-visible { outline: 3px solid #a33e0c; outline-offset: 3px; }
label { display: block; } [hidden] { display: none !important; }
table { border-collapse: collapse; } th, td { padding: .4rem; border-bottom: 1px solid #a1b2c4; }

script.js

const root=document.querySelector("[data-component]");
root.querySelector('#form').onsubmit=e=>{e.preventDefault();const input=root.querySelector('#email'),valid=Boolean(input.value)&&input.validity.valid;input.setAttribute('aria-invalid',String(!valid));root.querySelector('#error').textContent=valid?'Valid address':'Enter an email address';if(!valid)input.focus();};

Expected: Add a success path that clears the invalid state.

Edit and Render This Example
Example 5: Element: main

The document’s principal content, normally one visible instance.

index.html

<main><h1>Principal content</h1><p>The central task belongs here.</p></main>

styles.css

body { font:18px/1.6 system-ui; margin:1.5rem; color:#17324d; } img,video,svg { max-width:100%; height:auto; } th,td { padding:.5rem; border:1px solid #a8b8c8; } :focus-visible { outline:3px solid #a44322; outline-offset:3px; }

script.js

Expected: The document’s principal content, normally one visible instance. Review its real DOM and native behavior; structural/media-only examples are labeled.

Edit and Render This Example

Build and test

The inspector can show a real 24px padding value and the section’s measured outer box. Repair the current exercise without removing necessary content. Checks inspect the stated structural/computed/stylesheet contract, not exact source text.

Starter index.html

<section class="inspect"><h1>Inspect this element</h1><p>Select the paragraph in the preview.</p></section>

Starter styles.css

.inspect { padding:0; border:2px solid #234f9b; }

Objective contract

[
  {
    "type": "style",
    "selector": ".inspect",
    "property": "padding-top",
    "value": "24px",
    "label": ".inspect computes padding-top: 24px"
  }
]
Hint 1

Locate the first difference between the intended result and the real preview. Inspect matching elements and computed styles.

Hint 2

The relevant source uses padding:24px. The exercise instead uses padding:0. Identify its effect before changing it.

Hint 3

Restore the intended padding:24px operation or implement an equivalent structure/style. Run the actual checks and explain why it works.

Complete reference solution

index.html

<section class="inspect"><h1>Inspect this element</h1><p>Select the paragraph in the preview.</p></section>

styles.css

.inspect { padding:24px; border:2px solid #234f9b; }

Explain, reflect and extend

Which part of the actual preview or inspector proves this result? Explain one boundary case and name what automated checks do not verify.

Apply this concept to a different realistic piece of content. Predict its structure or visual behavior, test narrow and wide widths where relevant, then record one invalid case and its repair.

Troubleshooting and professional practice

If nothing changes, confirm that you edited the active file and ran Run Preview, or enabled Auto Preview. Inspect the actual DOM because the browser may repair invalid nesting. For CSS, check selector matches, valid declarations, active queries and computed values. Preserve local asset paths and inspect warnings. The inspector can show a real 24px padding value and the section’s measured outer box.

Knowledge check

Explain why the stated result follows from the source. Predict a second input or width and test it independently. Automated contracts and written explanations are reviewed separately.

Optional AI prompts

  1. Explain this lesson’s source line by line using the actual objective above.
  2. Help implement one small extension and define normal, boundary and failure tests.
  3. Review/debug the source against actual preview observations; verify standards and never claim rendering without evidence.

Continue to Lesson 92: Debugging HTML and CSS

Detailed learning and editor help · Standards reference