73. HTML, CSS and client JavaScript
Module 15 · 20 minutes · Lesson 72; earlier service and JavaScript fundamentals
Open Interactive LessonDiscover
How can you use html, css and client javascript without changing the wrong data?
- Explain html, css and client javascript in your own words
- Trace the actual console result from the source
- Repair the supplied failing operation and verify the result
Predict
Which values or resources will change, and which should stay unchanged? Write your prediction before execution.
Understand
HTML defines structure, CSS presentation and client JavaScript interaction. These files do not run as Apps Script services in the browser. Use textContent for untrusted text rather than innerHTML. The server can supply a prepared HTML file through HtmlService; the studio exports complete client and server source.
Example 1: Working automation
The markup contains a labeled field and live output region; actual client events are tested in the studio.
function main() {
const output = HtmlService.createHtmlOutput("<label>Name <input id='name'></label><button type='button'>Preview</button><output aria-live='polite'></output>");
console.log(output.getContent());
}Important line explanations
- Line 1: function main() {
- Define a named block of instructions. Run Script calls main; helpers run only when called.
- Line 2: const output = HtmlService.createHtmlOutput("<label>Name <input id='name'></label><button type='button'>Preview</button><output aria-live='polite'></output>");
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 3: console.log(output.getContent());
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 4: }
- Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
"logs": [
"<label>Name <input id='name'></label><button type='button'>Preview</button><output aria-live='polite'></output>"
],
"error": null,
"resource": "logs",
"value": null
}Example 2: Investigate a reproducible failure
Predict the effect of aria-live='off' and identify the first mismatch. This example is intentionally faulty.
function main() {
const output = HtmlService.createHtmlOutput("<label>Name <input id='name'></label><button type='button'>Preview</button><output aria-live='off'></output>");
console.log(output.getContent());
}Important line explanations
- Line 1: function main() {
- Define a named block of instructions. Run Script calls main; helpers run only when called.
- Line 2: const output = HtmlService.createHtmlOutput("<label>Name <input id='name'></label><button type='button'>Preview</button><output aria-live='off'></output>");
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 3: console.log(output.getContent());
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 4: }
- Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
"logs": [
"<label>Name <input id='name'></label><button type='button'>Preview</button><output aria-live='off'></output>"
],
"error": null,
"resource": "logs",
"value": null
}Example 3: Separate setup from execution and inspect repeat behavior
Call the same named operation twice. Compare outputs and resource counts to learn whether this operation is idempotent. Repeated creation is deliberately visible; real exports require a rerun policy.
function lessonAction() {
const output = HtmlService.createHtmlOutput("<label>Name <input id='name'></label><button type='button'>Preview</button><output aria-live='polite'></output>");
console.log(output.getContent());
}
function main() {
lessonAction();
lessonAction();
}Important line explanations
- Line 1: function lessonAction() {
- Define a named block of instructions. Run Script calls main; helpers run only when called.
- Line 2: const output = HtmlService.createHtmlOutput("<label>Name <input id='name'></label><button type='button'>Preview</button><output aria-live='polite'></output>");
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 3: console.log(output.getContent());
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 4: }
- Close the current block. Indentation makes scope and the function boundary visible.
- Line 5: function main() {
- Define a named block of instructions. Run Script calls main; helpers run only when called.
- Line 6: lessonAction();
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 7: lessonAction();
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 8: }
- Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
"logs": [
"<label>Name <input id='name'></label><button type='button'>Preview</button><output aria-live='polite'></output>",
"<label>Name <input id='name'></label><button type='button'>Preview</button><output aria-live='polite'></output>"
],
"error": null,
"resource": "logs",
"value": null
}Example 4: Add a diagnostic boundary around the operation
Observe start, successful completion or a rethrown failure. This optional professional pattern adds error context without swallowing the error or rolling back changes.
function lessonAction() {
const output = HtmlService.createHtmlOutput("<label>Name <input id='name'></label><button type='button'>Preview</button><output aria-live='polite'></output>");
console.log(output.getContent());
}
function main() {
console.log("Start: HTML, CSS and client JavaScript");
try { lessonAction(); console.log("Completed operation"); }
catch(error) { console.error("Failed operation: " + error.message); throw error; }
}Important line explanations
- Line 1: function lessonAction() {
- Define a named block of instructions. Run Script calls main; helpers run only when called.
- Line 2: const output = HtmlService.createHtmlOutput("<label>Name <input id='name'></label><button type='button'>Preview</button><output aria-live='polite'></output>");
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 3: console.log(output.getContent());
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 4: }
- Close the current block. Indentation makes scope and the function boundary visible.
- Line 5: function main() {
- Define a named block of instructions. Run Script calls main; helpers run only when called.
- Line 6: console.log("Start: HTML, CSS and client JavaScript");
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 7: try { lessonAction(); console.log("Completed operation"); }
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 8: catch(error) { console.error("Failed operation: " + error.message); throw error; }
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 9: }
- Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
"logs": [
"Start: HTML, CSS and client JavaScript",
"<label>Name <input id='name'></label><button type='button'>Preview</button><output aria-live='polite'></output>",
"Completed operation"
],
"error": null,
"resource": "logs",
"value": null
}Build and test
Repair the supplied script so that: The markup contains a labeled field and live output region; actual client events are tested in the studio. Preserve other source data. Checks compare observable output and the named resource, not exact source text.
function main() {
const output = HtmlService.createHtmlOutput("<label>Name <input id='name'></label><button type='button'>Preview</button><output aria-live='off'></output>");
console.log(output.getContent());
}Graduated hints
Hint 1
Inspect the operation containing aria-live='off'. Compare it with the stated rule and the first mismatch.
Hint 2
The repair concerns aria-live='polite'. Change only the relevant argument, operator or method; rerun with fresh input.
Hint 3
The reference uses aria-live='polite' where the broken source uses aria-live='off'. Explain why before applying it.
Reference solution
function main() {
const output = HtmlService.createHtmlOutput("<label>Name <input id='name'></label><button type='button'>Preview</button><output aria-live='polite'></output>");
console.log(output.getContent());
}Explain and reflect
Which operation proves the intended result in html, css and client javascript? Which wrong input would expose a weakness, and what would remain unchanged?
Adapt the calculation or validation to a second realistic case. Write its expected result before running. Demonstrate one invalid case and explain whether the side effects should be rolled back or retried.
Troubleshooting
If the console is empty, inspect the logs preview: this script may work through state changes. If the function is missing, select main. For a service error inspect the first failed timeline entry and its arguments. Use Manual unless investigating a trigger. Changing input data also changes the expected result; restore sample data before the authored checks.
Knowledge check
Explain the key method or operator. Give an exact output for a second input, plus one invalid case. Verify the result in the interactive lesson; written explanations need self or educator review.
Optional AI practice
Explain this concept using the source above. Help implement one small extension and define its tests. Review/debug the source using its actual expected output; cite real method references and never claim execution.