Web Standards Programmers Reference HTML, CSS, JavaScript, Perl, Python, and PHP (Steven M. Schafer) (Z-Library)

# Web Standards Programmer's Reference: HTML, CSS, JavaScript, Perl, Python, and PHP ## 【One-Line Pitch】 A comprehensive technical reference covering the full stack of early-2000s web development—from XHTML markup and CSS styling to client-side JavaScript and server-side CGI scripting with Perl, Python, and PHP—best suited for programmers with prior web experience who need a structured reference rather than a beginner tutorial. ## 【Book Arc】 - **Opening (~0%–10%)**: Establishes the book's scope and prerequisites, covering XHTML document fundamentals including the DOCTYPE tag, basic document structure, and core markup elements like headings and horizontal rules. The introduction also outlines the required development environment (Apache server, text editor, browser) and points readers to the WROX website for source code. - **Early (~10%–29%)**: Dives into HTML/XHTML elements in detail—lists with CSS counter tricks, image creation and editing tools, URL structures (absolute vs. relative paths), anchor tags, text formatting (monospaced, superscript, subscript), and table construction with row/column attributes. - **Middle (~29%–48%)**: Covers forms and form handling (GET vs. POST methods, security concerns with formmail vulnerabilities), then transitions into CSS fundamentals—style definition syntax, selectors, generated content, shorthand expressions, and text styling properties including line-height and font embedding technologies (OpenType vs. TrueDoc). - **Late (~48%–75%)**: Moves into client-side scripting with JavaScript, covering built-in objects (Window, Document, Form, Location, History), Dynamic HTML techniques, and practical examples for writing text, manipulating images, working with forms, and creating DHTML effects. - **Ending (~75%–100%)**: Introduces Common Gateway Interface (CGI) basics—HTTP request/response mechanics, data encapsulation, and how CGI scripts operate—followed by the Perl language chapter covering its history and resources. The book's structure suggests additional chapters on Python and PHP follow, though the excerpts do not cover these in detail. ## 【Key Takeaways】 - **DOCTYPE is a document identifier, not an HTML tag** (Early): The DOCTYPE declaration tells validation tools and browsers which standards the document follows, making it critical for proper rendering and validation—yet it's frequently overlooked by developers. - **CSS counters enable custom list numbering** (Early): Using counter-reset, counter-increment, and the :before pseudoelement, you can create numbered lists starting at any value—though browser support was limited (only Opera at time of writing), demonstrating the gap between CSS2 spec and implementation. - **Relative vs. absolute URLs have distinct use cases** (Early): Relative paths work only within the same server and are best for stable site sections, while absolute paths are generally preferred—and omitting the protocol makes the browser use its default. - **GET is inherently insecure for form data** (Early): GET passes data as plain text in the URL, visible to users and sniffable by hackers, while POST encodes data in the HTTP stream—making POST the required choice for confidential information, despite being slightly harder to implement. - **CSS style definitions follow a consistent selector-property-value format** (Middle): The pattern `selector { property: value; }` scales from simple element matching to complex relationship-based selectors, with some properties like border combining multiple sub-properties into shorthand declarations. - **Generated content breaks the content/presentation separation** (Middle): CSS can inject quote marks, counters, and other presentation content into documents—powerful but philosophically at odds with the strict separation of content from styling. - **Font embedding was fragmented across browsers** (Middle): OpenType (Microsoft/Adobe) worked only in Internet Explorer while TrueDoc (Bitstream) worked natively only in Netscape—a reminder that web font technology was far from standardized, and licensing rights must be verified before embedding. - **Form handlers carry security risks** (Early): The infamous formmail.cgi vulnerability allowed spammers to abuse unsecured scripts for anonymous email—highlighting that generic form handlers need careful security consideration or third-party services. ## 【Reading Tips】 - **Skim the HTML/XHTML chapters if you have basic markup experience**: Chapters 2–9 cover familiar ground (headings, lists, images, links, text formatting, tables); focus instead on the less-common details like CSS counters, character alignment in tables, and the security implications of form methods. - **Deep-read the CSS chapters (13–16)**: The style definition syntax, selector expressions, generated content, and font embedding sections contain the most conceptually dense material—these are worth careful study, especially the shorthand property patterns. - **Treat JavaScript chapters (22–23) as practical reference**: The object listings (Window, Document, Form, etc.) are reference material to consult as needed, while the examples section (writing text, images, forms, DHTML tricks) provides ready-to-adapt code patterns. - **Watch for dated browser support notes**: The book repeatedly notes which browsers support which features (Opera for counters, IE for OpenType, Netscape for TrueDoc)—treat these as historical context rather than current guidance, and verify against modern standards. - **Use the companion website for source code**: The introduction directs readers to WROX.com for downloadable code examples—retrieving these will save you from transcription errors and let you test examples directly. ## 【Coverage Limits】 This guide covers the book's structure and key concepts from the opening through the CGI/Perl chapters (~75% of the book). The excerpts do not include detailed content on the Python and PHP chapters, nor the later JavaScript examples in full—readers should expect those sections to follow the same reference-style pattern established earlier. ##