DiscoveryVIP / HTML & CSS AcademyHelp

89. Forms, buttons and interface states

Module 18 · About 20 minutes · Lesson 88; review earlier concepts as needed

Open Interactive Lesson

Discover

What changes when you use forms, buttons and interface states, and how can you prove it?

Predict

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

Understand

Controls need default, hover, focus, disabled, invalid and busy behavior as appropriate. A visual disabled style does not disable an element; use native state or actual application logic. A form’s status should explain what happened. HTML/CSS can express many native states, but tasks such as search or saving require implemented JavaScript or a backend.

Important source lines

index.html:1 <form><label>Work email <input type="email" required></label><button type="submit">Preview submission</button><button type="button" disabled>Unavailable action</button></form>
A group of named controls for a submitted task. Attribute guidance: action/method for real delivery; local preview intercepts submission.
styles.css:1 button { padding:.75rem 1rem; } button:disabled { opacity:.6; } input:invalid { border:2px solid #a52a24; }
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: Forms, buttons and interface states

The second control is truly disabled, while the form retains native validation and a submit action.

index.html

<form><label>Work email <input type="email" required></label><button type="submit">Preview submission</button><button type="button" disabled>Unavailable action</button></form>

styles.css

button { padding:.75rem 1rem; } button:disabled { opacity:.6; } input:invalid { border:2px solid #a52a24; }

script.js

Expected: The second control is truly disabled, while the form retains native validation and a submit action.

Edit and Render This Example
Example 2: Property: opacity

Makes the entire composited element translucent, including its content.

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 { opacity: 0.7; }

script.js

Expected: Inspect .sample in the block context. Makes the entire composited element translucent, including its content. 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: 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 4: 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 5: Focus tooltip

A tooltip supplements an accessible name with a description. Show it on keyboard focus and permit dismissal.

index.html

<section data-component aria-label="Focus tooltip">
<button id="help" aria-describedby="tip">Export format</button><span id="tip" role="tooltip" hidden>CSV contains plain text columns.</span>
</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]");
const help=root.querySelector('#help'),tip=root.querySelector('#tip');help.onfocus=help.onmouseenter=()=>{tip.hidden=false;};help.onblur=()=>{tip.hidden=true;};help.onmouseleave=()=>{if(document.activeElement!==help)tip.hidden=true;};help.onkeydown=e=>{if(e.key==='Escape')tip.hidden=true;};

Expected: Move essential instructions into visible inline text.

Edit and Render This Example

Build and test

The second control is truly disabled, while the form retains native validation and a submit action. Repair the current exercise without removing necessary content. Checks inspect the stated structural/computed/stylesheet contract, not exact source text.

Starter index.html

<form><label>Work email <input type="email" required></label><button type="submit">Preview submission</button><button type="button">Unavailable action</button></form>

Starter styles.css

button { padding:.75rem 1rem; } button:disabled { opacity:.6; } input:invalid { border:2px solid #a52a24; }

Objective contract

[
  {
    "type": "count",
    "selector": "button[disabled]",
    "value": 1,
    "label": "Include 1 matching button[disabled] element(s)"
  }
]
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 disabled. The exercise instead uses an omitted operation. Identify its effect before changing it.

Hint 3

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

Complete reference solution

index.html

<form><label>Work email <input type="email" required></label><button type="submit">Preview submission</button><button type="button" disabled>Unavailable action</button></form>

styles.css

button { padding:.75rem 1rem; } button:disabled { opacity:.6; } input:invalid { border:2px solid #a52a24; }

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 second control is truly disabled, while the form retains native validation and a submit action.

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 90: Combining components into templates

Detailed learning and editor help · Standards reference