This content was uploaded by our users and we assume good faith they have the permission to share this book. If you own the copyright to this book and it is wrongfully on our website, we offer a simple DMCA procedure to remove your content from our site. Start by pressing the button below!
Praise for Javascript Bible ‘‘JavaScript Bible is the definitive resource in JavaScript programming. I am never more than three feet from my copy.’’ — Steve Reich, CEO, PageCoders ‘‘This book is a must-have for any web developer or programmer.’’ — Thoma Lile, President, Kanis Technologies, Inc. ‘‘Outstanding book. I would recommend this book to anyone interested in learning to develop advanced Web sites. Mr. Goodman did an excellent job of organizing this book and writing it so that even a beginning programmer can understand it.’’ — Jason Hensley, Director of Internet Services, NetVoice, Inc. ‘‘Goodman is always great at delivering clear and concise technical books!’’ — Dwayne King, Chief Technology Officer, White Horse ‘‘JavaScript Bible is well worth the money spent!’’ — Yen C.Y. Leong, IT Director, Moo Mooltimedia, a member of SmartTransact Group ‘‘A must-have book for any internet developer.’’ — Uri Fremder, Senior Consultant, TopTier Software ‘‘I love this book! I use it all the time, and it always delivers. It’s the only JavaScript book I use!’’ — Jason Badger, Web Developer ‘‘Whether you are a professional or a beginner, this is a great book to get.’’ — Brant Mutch, Web Application Developer, Wells Fargo Card Services, Inc. ‘‘I never thought I’d ever teach programming before reading your book [JavaScript Bible]. It’s so simple to use — the Programming Fundamentals section brought it all back! Thank you for such a wonderful book, and for breaking through my programming block!’’ — Susan Sann Mahon, Certified Lotus Instructor, TechNet Training ‘‘Danny Goodman is very good at leading the reader into the subject. JavaScript Bible has everything we could possibly need.’’ — Philip Gurdon ‘‘An excellent book that builds solidly from whatever level the reader is at. A book that is both witty and educational.’’ — Dave Vane ‘‘I continue to use the book on a daily basis and would be lost without it.’’ — Mike Warner, Founder, Oak Place Productions ‘‘JavaScript Bible is by far the best JavaScript resource I’ve ever seen (and I’ve seen quite a few).’’ — Robert J. Mirro, Independent Consultant, RJM Consulting
JavaScript Bible Seventh Edition
JavaScript Bible Seventh Edition
Danny Goodman Michael Morrison Paul Novitski Tia Gustaff Rayl
Wiley Publishing, Inc.
Disclaimer: This eBook does not include ancillary media that was packaged with the printed version of the book. JavaScript Bible, Seventh Edition Published by Wiley Publishing, Inc. 10475 Crosspoint Boulevard Indianapolis, IN 46256 www.wiley.com Copyright 2010 by Wiley Publishing, Inc., Indianapolis, Indiana Published simultaneously in Canada ISBN: 978-0-470-52691-0 Manufactured in the United States of America 10 9 8 7 6 5 4 3 2 1 No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning or otherwise, except as permitted under Sections 107 or 108 of the 1976 United States Copyright Act, without either the prior written permission of the Publisher, or authorization through payment of the appropriate per-copy fee to the Copyright Clearance Center, 222 Rosewood Drive, Danvers, MA 01923, (978) 750-8400, fax (978) 646-8600. Requests to the Publisher for permission should be addressed to the Permissions Department, John Wiley & Sons, Inc., 111 River Street, Hoboken, NJ 07030, (201) 748-6011, fax (201) 748-6008, or online at http://www.wiley.com/go/permissions. Limit of Liability/Disclaimer of Warranty: The publisher and the author make no representations or warranties with respect to the accuracy or completeness of the contents of this work and specifically disclaim all warranties, including without limitation warranties of fitness for a particular purpose. No warranty may be created or extended by sales or promotional materials. The advice and strategies contained herein may not be suitable for every situation. This work is sold with the understanding that the publisher is not engaged in rendering legal, accounting, or other professional services. If professional assistance is required, the services of a competent professional person should be sought. Neither the publisher nor the author shall be liable for damages arising herefrom. The fact that an organization or web site is referred to in this work as a citation and/or a potential source of further information does not mean that the author or the publisher endorses the information the organization or web site may provide or recommendations it may make. Further, readers should be aware that Internet web sites listed in this work may have changed or disappeared between when this work was written and when it is read. For general information on our other products and services please contact our Customer Care Department within the United States at (877) 762-2974, outside the United States at (317) 572-3993 or fax (317) 572-4002. Wiley also publishes its books in a variety of electronic formats. Some content that appears in print may not be available in electronic books. Library of Congress Control Number: 2010923547 Trademarks: Wiley and the Wiley logo are trademarks or registered trademarks of John Wiley & Sons, Inc. and/or its affiliates, in the United States and other countries, and may not be used without written permission. JavaScript is a registered trademark of Oracle America, Inc. All other trademarks are the property of their respective owners. Wiley Publishing, Inc. is not associated with any product or vendor mentioned in this book.
To Tanya, with whom I share this loving orbit with Briar and Callum in our own cozy Klemperer rosette. — Paul Novitski To my husband, Edward, whose love, support, and encouragement kept me going through this and all my adventures, and to the memory of my parents who inspired me to step out in faith. — Tia Gustaff Rayl
About the Authors Danny Goodman is the author of numerous critically acclaimed and best-selling books, including The Complete HyperCard Handbook, Danny Goodman’s AppleScript Handbook, Dynamic HTML: The Definitive Reference, and JavaScript & DHTML Cookbook. He is a renowned authority on and expert teacher of computer scripting languages. His writing style and pedagogy continue to earn praise from readers and teachers around the world. Michael Morrison is a writer, developer, toy inventor, and author of a variety of books covering topics such as Java, C++, Web scripting, XML, game development, and mobile devices. Some of Michael’s notable writing projects include Faster Smarter HTML and XML, Teach Yourself HTML & CSS in 24 Hours, and Beginning Game Programming. Michael is also the founder of Stalefish Labs (www.stalefishlabs.com), an entertainment company specializing in unusual games, toys, and interactive products. Paul Novitski has been writing software as a freelance programmer since 1981. He once taught himself BASIC in order to write a machine language disassembler so that he could lovingly hack Wang’s OIS microcode. He has focused on internet programming since the late ’90s. His company, Juniper Webcraft, produces HTML-strict websites featuring accessible, semantic markup, separation of development layers, and intuitive user interfaces. He knows the righteousness of elegant code, the poignancy of living on the bleeding edge of wilderness, the sweet melancholy of mbira music, and the scorching joy of raising twin boys. Tia Gustaff Rayl is a consultant who does development and training in database and Web technologies. Most recently she has published courseware for XHTML, CSS, JavaScript, and SQL. It comes as no surprise to those who know her that she began her software career with degrees in English and Education from the University of Florida. As is usual for most newcomers to the field, her introduction to computing was maintaining software. She went on to a long-standing career in the software industry in full life cycle system, application, and database development; project management; and training for PC and mainframe environments. In the mid-nineties she worked on early Web-enabled database applications, adding JavaScript to her repertoire. She continues to take on development projects to maintain her code-slinging skills. If she had any spare time (and money) she would go on an around-the-world cruise with her husband and two dogs.
About the Technical Editor Benjamin Schupak holds a master’s degree in computer science and has more than 11 years of professional programming experience for large corporations and U.S. federal departments. He lives in the New York metro area and enjoys traveling.
Credits Executive Editor Carol Long
Vice President and Executive Publisher Barry Pruett
Project Editor John Sleeva
Associate Publisher Jim Minatel
Technical Editor Benjamin Schupack Production Editor Rebecca Anderson
Project Coordinator, Cover Lynsey Stanford
Editorial Director Robyn B. Siesky
Proofreaders Maraya Cornell, Word One New York Sheilah Ledwidge, Word One New York
Editorial Manager Mary Beth Wakefield
Indexer Robert Swanson
Marketing Manager Ashley Zurcher
Cover Designer Michael E. Trent
Production Manager Tim Tate
Cover Image Joyce Haughey
Vice President and Executive Group Publisher Richard Swadley
My gratitude for being given the opportunity and the latitude to work on this immense tome extends to Carol Long of Wiley, editor John Sleeva, Carole Jelen at Waterside Productions, Julian Hall, my partner in crime at Juniper Webcraft, and, above all, my sweet, loving, supportive, and nearly homicidal spouse Tanya Wright, all of them long-suffering and all to be commended for not actually throttling me in the course of this overlong birthing. The solid foundation of research and explication established by Danny Goodman and his past collaborators in previous editions is awesome and I am humbled to have been able to help move this great body of knowledge forward to the next step. Tia Gustaff Rayl, who with wings spread and sparks flying rode in to the rescue, has been a kick in the pants to work with; she’s smart and funny, but more than that she is gifted with the precise serendipity and good taste to share a birthday with me. –Paul Novitski I have been blessed with the support of many people who have reviewed my work and encouraged me along the way. I could never have done any of this without the devoted support of my husband, Edward. I love him without cease and thank God for bringing him into my life. I have been blessed by the remarkable patience of an incredibly tolerant immediate and extended family, as well as amused friends, who put up with my ‘‘Hi, I love you. Don’t talk to me right now.’’ way of answering the phone and greeting visitors at the door. My husband, family and friends are the ones who sacrificed the most for this book. Thank you all. I want to thank Paul for being great to work with and for his wry sense of humor which left me on the floor laughing just when I most needed a lift. I want to thank my editor, John Sleeva, who with great patience and humor guided me through the maze of the publishing world. I also want to thank Rebecca Anderson and Maraya Cornell for forcing me to be a better writer. Finally, I want to thank Miss Bigelow, my 11th and 12th grade English teacher, who instilled within me a great respect and love for the written word. –Tia Gustaff Rayl
JavaScript’s Role in the World Wide Web and Beyond .........................................................3 Developing a Scripting Strategy ............................................................................................15 Selecting and Using Your Tools ............................................................................................27 JavaScript Essentials ...............................................................................................................37
5: Your First JavaScript Script ...................................................................................................61 6: Browser and Document Objects ........................................................................................... 77 7: Scripts and HTML Documents ..............................................................................................95 8: Programming Fundamentals, Part I ....................................................................................109 9: Programming Fundamentals, Part II ...................................................................................121 10: Window and Document Objects ...................................................................................... 135 11: Forms and Form Elements ................................................................................................153 12: Strings, Math, and Dates ...................................................................................................179 13: Scripting Frames and Multiple Windows .........................................................................191 14: Images and Dynamic HTML .............................................................................................207
The String Object ..............................................................................................................225 The Math, Number, and Boolean Objects ........................................................................269 The Date Object ................................................................................................................ 285 The Array Object ...............................................................................................................311 JSON — Native JavaScript Object Notation .................................................................... 357 E4X — Native XML Processing ........................................................................................363 Control Structures and Exception Handling ....................................................................373 JavaScript Operators ..........................................................................................................411 Function Objects and Custom Objects ............................................................................ 437 Global Functions and Statements .....................................................................................481
Document Object Model Essentials ..................................................................................503 Generic HTML Element Objects .......................................................................................537 Window and Frame Objects .............................................................................................739 Location and History Objects ........................................................................................... 881 Document and Body Objects ............................................................................................907 Link and Anchor Objects ..................................................................................................995 Image, Area, Map, and Canvas Objects ..........................................................................1003 Event Objects ...................................................................................................................1043
Body Text Objects .............................................................................................................BC2 The Form and Related Objects ....................................................................................BC103 Button Objects ..............................................................................................................BC128 Text-Related Form Objects ...........................................................................................BC153 Select, Option, and FileUpload Objects ...................................................................... BC177 Style Sheet and Style Objects .......................................................................................BC207 Ajax, E4X, and XML .....................................................................................................BC272 HTML Directive Objects ...............................................................................................BC289 Table and List Objects ..................................................................................................BC303 The Navigator and Other Environment Objects ......................................................... BC360 Positioned Objects ........................................................................................................BC411 Embedded Objects ........................................................................................................BC448 The Regular Expression and RegExp Objects ..............................................................BC465
Data-Entry Validation ...................................................................................................BC492 Scripting Java Applets and Plug-Ins .............................................................................BC524 Debugging Scripts .........................................................................................................BC564 Security and Netscape Signed Scripts ..........................................................................BC590 Cross-Browser Dynamic HTML Issues .........................................................................BC608 Internet Explorer Behaviors ..........................................................................................BC623
Tables and Calendars ...............................................................................BC637 A Lookup Table .......................................................................................BC652 A Poor Man’s Order Form .......................................................................BC665 Outline-Style Table of Contents ..............................................................BC674 Calculations and Graphics .......................................................................BC695 Intelligent ‘‘Updated’’ Flags ......................................................................BC705 Decision Helper ....................................................................................... BC715 Cross-Browser DHTML Map Puzzle ....................................................... BC747 Transforming XML Data ..........................................................................BC764 Creating Custom Google Maps ............................................................... BC782
Part IX: Appendixes (continued) . . . . . . . . . . . . . . . . . . . . . . BC799 Appendix C: JavaScript Reserved Words ..........................................................................................BC800 Appendix D: Answers to Tutorial Exercises .....................................................................................BC801 Appendix E: JavaScript and DOM Internet Resources .....................................................................BC818
Chapter 1: JavaScript’s Role in the World Wide Web and Beyond . . . . . . 3 Competing for Web Traffic .............................................................................................................4 Other Web Technologies .................................................................................................................4 JavaScript: A Language for All ...................................................................................................... 10 JavaScript: The Right Tool for the Right Job ................................................................................12
Chapter 5: Your First JavaScript Script . . . . . . . . . . . . . . . . . . . . . . . . . . 61 What Your First Script Will Do ....................................................................................................61 Entering Your First Script .............................................................................................................62 Have Some Fun .............................................................................................................................74 Exercises .........................................................................................................................................75
Chapter 6: Browser and Document Objects . . . . . . . . . . . . . . . . . . . . . 77 Scripts Run the Show ....................................................................................................................77 When to Use JavaScript .................................................................................................................78 The Document Object Model ........................................................................................................79 When a Document Loads ..............................................................................................................82
xvii
Contents
Object References .......................................................................................................................... 85 Node Terminology .........................................................................................................................87 What Defines an Object? ...............................................................................................................88 Exercises .........................................................................................................................................93
Chapter 8: Programming Fundamentals, Part I . . . . . . . . . . . . . . . . . . 109 What Language Is This? ..............................................................................................................109 Working with Information ..........................................................................................................109 Variables .......................................................................................................................................110 Expressions and Evaluation .........................................................................................................112 Data Type Conversions ............................................................................................................... 115 Operators .....................................................................................................................................116 Exercises .......................................................................................................................................118
Chapter 10: Window and Document Objects . . . . . . . . . . . . . . . . . . . 135 Top-Level Objects ........................................................................................................................135 The window Object .....................................................................................................................135 window Properties and Methods ................................................................................................139 The location Object .....................................................................................................................142 The navigator Object ...................................................................................................................143 The document Object ..................................................................................................................143 Exercises .......................................................................................................................................152
Chapter 11: Forms and Form Elements . . . . . . . . . . . . . . . . . . . . . . . . 153 The Form object ..........................................................................................................................153 Form Controls as Objects ........................................................................................................... 158 Passing Elements to Functions with this ....................................................................................170 Submitting and Prevalidating Forms .......................................................................................... 173 Exercises .......................................................................................................................................177
Chapter 12: Strings, Math, and Dates . . . . . . . . . . . . . . . . . . . . . . . . . 179 Core Language Objects ................................................................................................................179 String Objects ..............................................................................................................................180 The Math Object ......................................................................................................................... 183 The Date Object .......................................................................................................................... 184
xviii
Contents
Date Calculations .........................................................................................................................186 Exercises .......................................................................................................................................189
Chapter 13: Scripting Frames and Multiple Windows . . . . . . . . . . . . . . 191 Frames: Parents and Children .....................................................................................................191 References Among Family Members ...........................................................................................194 Frame-Scripting Tips ...................................................................................................................195 About iframe Elements ................................................................................................................196 Highlighting Footnotes: A Frameset Scripting Example ............................................................196 References for Multiple Windows ...............................................................................................202 Exercises .......................................................................................................................................206
Chapter 14: Images and Dynamic HTML . . . . . . . . . . . . . . . . . . . . . . . 207 The Image Object ........................................................................................................................207 Rollovers Without Scripts ........................................................................................................... 216 The javascript: Pseudo-URL ........................................................................................................219 Popular Dynamic HTML Techniques ......................................................................................... 220 Exercises .......................................................................................................................................222
Chapter 25: Document Object Model Essentials . . . . . . . . . . . . . . . . . 503 The Object Model Hierarchy ...................................................................................................... 503 How Document Objects Are Born ..............................................................................................505 Object Properties .........................................................................................................................506 Object Methods ........................................................................................................................... 507 Object Event Handlers ................................................................................................................ 508 Object Model Smorgasbord .........................................................................................................509 Basic Object Model ......................................................................................................................510 Basic Object Model Plus Images .................................................................................................511 Navigator 4–Only Extensions .....................................................................................................511 Internet Explorer 4+ Extensions ................................................................................................512 Internet Explorer 5+ Extensions ................................................................................................515 The W3C DOM ...........................................................................................................................516 Scripting Trends .......................................................................................................................... 532 Standards Compatibility Modes (DOCTYPE Switching) ............................................................534 Where to Go from Here ..............................................................................................................535
his seventh edition of the JavaScript Bible represents knowledge and experience accumulated over fifteen years of daily work in JavaScript and a constant monitoring of newsgroups for questions, problems, and challenges facing scripters at all levels. Our goal is to help you avoid the same frustration and head-scratching we and others have experienced through multiple generations of scriptable browsers. While the earliest editions of this book focused on the then-predominant Netscape Navigator browser, the browser market share landscape has changed through the years. For many years, Microsoft took a strong lead with its Internet Explorer, but more recently, other browsers that support industry standards are finding homes on users’ computers. The situation still leaves an age-old dilemma for content developers: designing scripted content that functions equally well in both standards-compliant and proprietary environments. The job of a book claiming to be the ‘‘bible’’ is not only to present both the standard and proprietary details when they diverge, but also to show you how to write scripts that blend the two so that they work on the wide array of browsers visiting your sites or web applications. Empowering you to design and write good scripts is our passion, regardless of browser. It’s true that our bias is toward industry standards, but not to the exclusion of proprietary features that may be necessary to get your content and scripting ideas flowing equally well on today’s and tomorrow’s browsers.
Organization and Features of This Edition Like the previous three editions of the JavaScript Bible, this seventh edition contains far more information than can be printed and bound into a single volume. The complete contents can be found in the electronic version of this book (in PDF form) on the CD-ROM that accompanies the book. This edition is structured in such a way as to supply the most commonly needed information in its entirety in the printed portion of the book. Content that you use to learn the fundamentals of JavaScript and reference frequently are at your fingertips in the printed version, while chapters with more advanced content are in the searchable electronic version on the CD-ROM. Here are some details about the book’s structure.
Part I: Getting Started with JavaScript Part I of the book begins with a chapter that shows how JavaScript compares with Java and discusses its role within the rest of the World Wide Web. The web browser and scripting world have undergone significant changes since JavaScript first arrived on the scene. That’s why Chapter 2 is devoted to addressing challenges facing scripters who must develop applications for both single- and cross-platform browser audiences amid rapidly changing standards efforts. Chapter 3 introduces some tools you can use to compose your pages and scripts, while Chapter 4 delves into the nitty-gritty of how to use JavaScript to run in a wide variety of browsers.
xxv
Introduction
Part II: JavaScript Tutorial All of Part II is handed over to a tutorial for newcomers to JavaScript. Ten lessons provide you with a gradual path through browser internals, basic programming skills, and genuine browser scripting, with an emphasis on industry standards as supported by most of the scriptable browsers in use today. Exercises follow at the end of each lesson to help reinforce what you just learned and challenge you to use your new knowledge (you’ll find answers to the exercises in Appendix D, on the CD-ROM). The goal of the tutorial is to equip you with sufficient experience to start scripting simple pages right away while making it easier for you to understand the in-depth discussions and examples in the rest of the book.
Part III: JavaScript Core Language Reference Reference information for the core JavaScript language fills Part III. In all reference chapters, a compatibility chart indicates the browser version that supports each object and object feature. Guide words near the tops of pages help you find a particular term quickly.
Part IV: Document Objects Reference Part IV, the largest section of the book, provides in-depth coverage of the document object models as implemented in today’s browsers, including the object used for modern Ajax applications. As with the core JavaScript reference chapters of Part III, these DOM chapters display browser compatibility charts for every object and object feature. One chapter in particular, Chapter 26, contains reference material that is shared by most of the remaining chapters of Part IV. To help you refer back to Chapter 26 from other chapters, a shaded tab along the outside edge of the page shows you at a glance where the chapter is located. Additional navigation aids include guide words near the tops of most pages to indicate which object and object feature is covered on the page. Note that the Objects Reference begun in Part IV of the book continues in Part VI on the CD, with an additional 13 chapters of reference material.
Part V: Appendixes Appendix A offers a JavaScript and Browser Objects Quick Reference. Appendix B provides information about using the CD-ROM that comes with this book, which includes numerous bonus chapters and examples.
Part VI: Document Objects Reference (continued) Beginning the portion of the book that resides only the accompanying CD, Part VI continues the document objects reference discussions that begin in Part IV by providing an additional 13 chapters of reference material.
Part VII: More JavaScript Programming Chapters 46–51 discuss advanced JavaScript programming techniques, including data-entry validation, debugging, and security issues.
Part VIII: Applications The final ten chapters of the book, available only on the CD-ROM, feature sample applications that cover the gamut from calendars to puzzles.
xxvi
Introduction
Part IX: Appendixes (continued) The final three appendixes provide helpful reference information. These resources include a list of JavaScript reserved words in Appendix C, answers to Part II’s tutorial exercises in Appendix D, and Internet resources in Appendix E.
CD-ROM The CD-ROM is a gold mine of information. It begins with a PDF version of the entire contents of this seventh edition of the JavaScript Bible. This version includes bonus chapters covering:
Dynamic HTML, data validation, plug-ins, and security
Techniques for developing and debugging professional web-based applications
Ten full-fledged JavaScript real-world applications
Another treasure trove on the CD-ROM is the Listings folder where you’ll find over 300 ready-to-run HTML documents that serve as examples of most of the document object model and JavaScript vocabulary words in Parts III and IV. All of the bonus chapter example listings are also included. You can run these examples with your JavaScript-enabled browser, but be sure to use the index.html page in the Listings folder as a gateway to running the listings. We could have provided you with humorous little sample code fragments out of context, but we think that seeing full-fledged HTML documents (simple though they may be) for employing these concepts is important. We encourage you to manually type the script listings from the tutorial (Part II) of this book. We believe you learn a lot, even by aping listings from the book, as you get used to the rhythms of typing scripts in documents. Be sure to check out the Chapter 4 listing file called evaluator.html. Many segments of Parts III and IV invite you to try out an object model or language feature with the help of an interactive workbench, called The Evaluator — a JavaScript Bible exclusive! You see instant results and will quickly learn how the feature works. The Quick Reference from Appendix A is in PDF format on the CD-ROM for you to print out and assemble as a handy reference, if desired. Adobe Reader is also included on the CD-ROM, in case you don’t already have it.
Prerequisites to Learning JavaScript Although this book doesn’t demand that you have a great deal of programming experience behind you, the more web pages you’ve created with HTML, the easier you will find it to understand how JavaScript interacts with the familiar elements you normally place in your pages. Occasionally, you will need to modify HTML tags to take advantage of scripting. If you are familiar with those tags already, the JavaScript enhancements will be simple to digest. To learn JavaScript, you won’t need to know server scripting or how to pass information from a form to a server. The focus here is on client-side scripting, which operates independently of the server after the JavaScript-enhanced HTML page is fully loaded into the browser. However, we strongly believe that a public web page should be operational in the absence of JavaScript, so any dynamic functionality that looks up results or modifies the content of a page should interact with a server-side script fundamentally. After that foundation is laid, we add JavaScript to make a page faster, easier, or more
xxvii
Introduction
fun. So although you don’t need to know server-side scripting in order to learn JavaScript, for serious web work you should either learn a server-side scripting language such as PHP in addition to JavaScript or look for server-side programmers to complement your client-side scripting abilities. The basic vocabulary of the current HTML standard should be part of your working knowledge. You should also be familiar with some of the latest document markup standards, such as XHTML and Cascading Style Sheets (CSS). Web searches for these terms will uncover numerous tutorials on the subjects.
If you’ve never programmed before Don’t be put off by the size of this book. JavaScript may not be the easiest language in the world to learn, but believe us, it’s a far cry from having to learn a full programming language such as Java or C. Unlike developing a full-fledged monolithic application (such as the productivity programs you buy in stores), JavaScript lets you experiment by writing small snippets of program code to accomplish big things. The JavaScript interpreter built into every scriptable browser does a great deal of the technical work for you. Programming, at its most basic level, consists of nothing more than writing a series of instructions for the computer to follow. We humans follow instructions all the time, even if we don’t realize it. Traveling to a friend’s house is a sequence of small instructions: Go three blocks that way; turn left here; turn right there. Amid these instructions are some decisions that we have to make: If the stoplight is red, then stop; if the light is green, then go; if the light is yellow, then floor it! (Just kidding.) Occasionally, we must repeat some operations several times (kind of like having to go around the block until a parking space opens up). A computer program not only contains the main sequence of steps, but it also anticipates what decisions or repetitions may be needed to accomplish the program’s goal (such as how to handle the various states of a stoplight or what to do if someone just stole the parking spot you were aiming for). The initial hurdle of learning to program is becoming comfortable with the way a programming language wants its words and numbers organized in these instructions. Such rules are called syntax, the same as in a living language. Computers aren’t very forgiving if you don’t communicate with them in the specific language they understand. When speaking to another human, you can flub a sentence’s syntax and still have a good chance that the other person will understand you. Not so with computer programming languages. If the syntax isn’t perfect (or at least within the language’s range of knowledge), the computer has the brazenness to tell you that you have made a syntax error. The best thing you can do is just accept the syntax errors you receive as learning experiences. Even experienced programmers make mistakes. Every syntax error you get — and every resolution of that error made by rewriting the wayward statement — adds to your knowledge of the language.
If you’ve done a little programming before Programming experience in a procedural language, such as BASIC, may actually be a hindrance rather than a help to learning JavaScript. Although you may have an appreciation for precision in syntax, the overall concept of how a program fits into the world is probably radically different from JavaScript’s role. Part of this has to do with the typical tasks a script performs (carrying out a very specific task in response to user action within a web page), but a large part also has to do with the nature of object-oriented programming.
xxviii
Introduction
If you’ve programmed in C before In a typical procedural program, the programmer is responsible for everything that appears on the screen and everything that happens under the hood. When the program first runs, a great deal of code is dedicated to setting up the visual environment. Perhaps the screen contains several text entry fields or clickable buttons. To determine which button a user clicks, the program examines the coordinates of the click and compares those coordinates against a list of all button coordinates on the screen. Program execution then branches out to perform the instructions reserved for clicking in that space. Object-oriented programming is almost the inverse of that process. A button is considered an object — something tangible. An object has properties, such as its label, size, alignment, and so on. An object may also contain a script. At the same time, the system software and browser, working together, can send a message to an object — depending on what the user does — to trigger the script. For example, if a user clicks in a text entry field, the system/browser tells the field that somebody has clicked there (that is, has set the focus to that field), giving the field the task of deciding what to do about it. That’s where the script comes in. The script is connected to the field, and it contains the instructions that the field carries out after the user activates it. Another set of instructions may control what happens when the user types an entry and tabs or clicks out of the field, thereby changing the content of the field. Some of the scripts you write may seem to be procedural in construction: They contain a simple list of instructions that are carried out in order. But when dealing with data from form elements, these instructions work with the object-based nature of JavaScript. The form is an object; each radio button or text field is an object as well. The script then acts on the properties of those objects to get some work done. Making the transition from procedural to object-oriented programming may be the most difficult challenge for you. But when the concept clicks — a long, pensive walk might help — so many light bulbs will go on inside your head that you’ll think you might glow in the dark. From then on, object orientation will seem to be the only sensible way to program. By borrowing syntax from Java (which, in turn, is derived from C and C++), JavaScript shares many syntactical characteristics with C. Programmers familiar with C will feel right at home. Operator symbols, conditional structures, and repeat loops follow very much in the C tradition. You will be less concerned about data types in JavaScript than you are in C. In JavaScript, a variable is not restricted to any particular data type. With so much of JavaScript’s syntax familiar to you, you will be able to concentrate on document object model concepts, which may be entirely new to you. You will still need a good grounding in HTML to put your expertise to work in JavaScript.
If you’ve programmed in Java before Despite the similarity in their names, the two languages share only surface aspects: loop and conditional constructions, C-like ‘‘dot’’ object references, curly braces for grouping statements, several keywords, and a few other attributes. Variable declarations, however, are quite different, because JavaScript is a loosely typed language. A variable can contain an integer value in one statement and a string in the next (though we’re not saying that this is good style). What Java refers to as methods, JavaScript calls methods (when associated with a predefined object) or functions (for scripter-defined actions). JavaScript methods and functions may return values of any type without having to state the data type ahead of time.
xxix
Introduction
Perhaps the most important Java concepts to suppress when writing JavaScript are the object-oriented notions of classes, inheritance, instantiation, and message passing. These aspects are simply non-issues when scripting. At the same time, however, JavaScript’s designers knew that you’d have some hard-to-break habits. For example, although JavaScript does not require a semicolon at the end of each statement line, if you type one in your JavaScript source code, the JavaScript interpreter won’t balk.
If you’ve written scripts (or macros) before Experience with writing scripts in other authoring tools or macros in productivity programs is helpful for grasping a number of JavaScript’s concepts. Perhaps the most important concept is the idea of combining a handful of statements to perform a specific task on some data. For example, you can write a macro in Microsoft Excel that performs a data transformation on daily figures that come in from a corporate financial report on another computer. The macro is built into the Macro menu, and you run it by choosing that menu item whenever a new set of figures arrives. Some modern programming environments, such as Visual Basic, resemble scripting environments in some ways. They present the programmer with an interface builder, which does most of the work of displaying screen objects with which the user will interact. A big part of the programmer’s job is to write little bits of code that are executed when a user interacts with those objects. A great deal of the scripting you will do with JavaScript matches that pattern exactly. In fact, those environments resemble the scriptable browser environment in another way: They provide a finite set of predefined objects that have fixed sets of properties and behaviors. This predictability makes learning the entire environment and planning an application easier to accomplish.
Formatting and Naming Conventions The script listings and words in this book are presented in a monospace font to set them apart from the rest of the text. Because of restrictions in page width, lines of script listings may, from time to time, break unnaturally. In such cases, the remainder of the script appears in the following line, flush with the left margin of the listing, just as it would appear in a text editor with word wrapping turned on. If these line breaks cause you problems when you type a script listing into a document yourself, we encourage you to access the corresponding listing on the CD-ROM to see how it should look when you type it. As soon as you reach Part III of this book, you won’t likely go for more than a page before reading about an object model or language feature that requires a specific minimum version of one browser or another. To make it easier to spot in the text when a particular browser and browser version is required, most browser references consist of an abbreviation and a version number. For example, WinIE5 means Internet Explorer 5 for Windows; NN4 means Netscape Navigator 4 for any operating system; Moz stands for the modern Mozilla browser (from which Firefox, Netscape 6 or later, and Camino are derived); and Safari is Apple’s own browser for Mac OS X. If a feature is introduced with a particular version of browser and is supported in subsequent versions, a plus symbol (+) follows the number. For example, a feature marked WinIE5.5+ indicates that Internet Explorer 5.5 for Windows is required at a minimum, but the feature is also available in WinIE8 and probably future WinIE versions. If a feature was implemented in the first release of a modern browser, a plus symbol immediately follows the browser family name, such as Moz+ for all Mozilla-based browsers. Occasionally, a feature or some highlighted behavior applies to only one browser. For example, a feature marked
xxx
Introduction
NN4 means that it works only in Netscape Navigator 4.x. A minus sign (e.g., WinIE-) means that the browser does not support the item being discussed. The format of HTML markup in this edition follows HTML5 coding conventions, but also adheres to many XHTML standards such as all-lowercase tag and attribute names.
Note
Tip
Caution
Cross Reference
Note, Tip, Caution, and Cross-Reference icons occasionally appear in the book to flag important points or suggest where to find more information.
xxxi
JavaScript Bible Seventh Edition
Part I Getting Started with JavaScript IN THIS PART Chapter 1 JavaScript’s Role in the World Wide Web and Beyond Chapter 2 Developing a Scripting Strategy Chapter 3 Selecting and Using Your Tools Chapter 4 JavaScript Essentials
JavaScript’s Role in the World Wide Web and Beyond
M
any of the technologies that make the World Wide Web possible have far exceeded their original goals. Envisioned at the outset as a medium for publishing static text and image content across a network, the Web is forever being probed, pushed, and pulled by content authors. By taking for granted so much of the ‘‘dirty work’’ of conveying the bits between server and client computers, content developers and programmers dream of exploiting that connection to generate new user experiences and practical applications. It’s not uncommon for a developer community to take ownership of a technology and mold it to do new and exciting things. But with so many web technologies — especially browser programming with JavaScript — within reach of everyday folks, we have witnessed an unprecedented explosion in turning the World Wide Web from a bland publishing medium into a highly interactive, operating system– agnostic authoring platform. The JavaScript language, working in tandem with related browser features, is a web-enhancing technology. When employed on the client computer, the language can help turn a static page of content into an engaging, interactive, and intelligent experience. Applications can be as subtle as welcoming a site’s visitor with the greeting ‘‘Good morning!’’ when it is morning in the client computer’s time zone — even though it is dinnertime where the server is located. Or, applications can be much more obvious, such as delivering the content of a slide show in a one-page download while JavaScript controls the sequence of hiding, showing, and ‘‘flying slide’’ transitions as we navigate through the presentation. Of course, JavaScript is not the only technology that can give life to drab web content. Therefore, it is important to understand where JavaScript fits within the array of standards, tools, and other technologies at your disposal. The alternative technologies described in this chapter are HTML, Cascading Style Sheets (CSS), server programs, and plug-ins. In most cases, JavaScript can work side by side with these other technologies, even though the hype can make them sound like one-stop shopping places for all your interactive needs. (That’s rarely the case.) Finally, you learn about the origins of JavaScript and what role it plays in today’s advanced web browsers.
3
IN THIS CHAPTER How JavaScript blends with other web-authoring technologies The history of JavaScript What kinds of jobs you should and should not entrust to JavaScript
Part I: Getting Started with JavaScript
Competing for Web Traffic Web page publishers revel in logging as many visits to their sites as possible. Regardless of the questionable accuracy of web page hit counts, a site consistently logging 10,000 dubious hits per week is clearly far more popular than one with 1,000 dubious hits per week. Even if the precise number is unknown, relative popularity is a valuable measure. Another useful number is how many links from outside pages lead to a site. A popular site will have many other sites pointing to it — a key to earning high visibility in web searches. Encouraging people to visit a site frequently is the Holy Grail of web publishing. Competition for viewers is enormous. Not only is the Web like a 50 million–channel television, but also, the Web competes for viewers’ attention with all kinds of computer-generated information. That includes anything that appears onscreen as interactive multimedia. Users of entertainment programs, multimedia encyclopedias, and other colorful, engaging, and mouse-finger-numbing actions are accustomed to high-quality presentations. Frequently, these programs sport first-rate graphics, animation, live-action video, and synchronized sound. By contrast, the lowest-common-denominator web page has little in the way of razzle-dazzle. Even with the help of Dynamic HTML and style sheets, the layout of pictures and text is highly constrained compared with the kinds of desktop publishing documents you see all the time. Regardless of the quality of its content, an unscripted, vanilla HTML document is flat. At best, interaction is limited to whatever navigation the author offers in the way of hypertext links or forms whose filled-in content magically disappears into the web site’s server.
Other Web Technologies With so many ways to spice up web sites and pages, you can count on competitors for your site’s visitors to do their darnedest to make their sites more engaging than yours. Unless you are the sole purveyor of information that is in high demand, you continually must devise ways to keep your visitors coming back and entice new ones. If you design for an intranet, your competition is the drive for improved productivity by colleagues who use the internal web sites for getting their jobs done. These are all excellent reasons why you should care about using one or more web technologies to raise your pages above the noise. Let’s look at the major technologies you should know about. Figure 1-1 illustrates the components that make up a typical dynamic web site. The core is a dialog between the server (the web host) and the client (the browser); the client requests data and the server responds. The simplest model would consist of just the server, a document, and a browser, but in practice web sites use the other components shown here, and more. The process begins when the browser requests a page from the server. The server delivers static HTML pages directly from its hard drive; dynamic pages are generated on-the-fly by scripts executed in a language interpreter, such as PHP, but likewise delivered by the server to the client, usually in the form of HTML markup. For example, a server-side database can store the items of a catalog, and a PHP script can look up those data records and mark them up as HTML when requested by the browser. The downloaded page may contain the addresses of other components: style sheets, JavaScript files, images, and other assets. The browser requests each of these, in turn, from the server, combining them into the final rendering of the page. A JavaScript program is inert — just another hunk of downloaded bits — until it’s received by the browser, which validates its syntax and compiles it, ready for execution when called upon by the
4
Chapter 1: JavaScript’s Role in the World Wide Web and Beyond
HTML page or the human user. It’s then part of the web page and confined to the client side of the sever-client dialog. JavaScript can make requests of servers, as we’ll see later, but it cannot directly access anything outside of the page it’s part of and the browser that’s running it. FIGURE 1-1
The components of a typical dynamic web site. server-side scripting (e.g., PHP)
server
marked-up content (HTML, XHTML, XML)
client-side scripting (e.g., JavaScript)
style sheets (CSS)
database (e.g., MySQL)
images & objects (e.g., JPEG, Flash)
user agent (e.g., browser)
the user
Hypertext Markup Language (HTML and XHTML) As an outgrowth of SGML (Standard Generalized Markup Language), HTML brings structure to the content of a page. This structure gives us handles on the content in several important ways:
Markup transforms a sea of undifferentiated text into discrete parts, such as headlines, paragraphs, lists, data tables, images, and input controls. Structure augments the meaning of the content by establishing relationships between different parts: between headline and subhead; between items in a list; between divisions of the page such as header, footer, and content columns. The semantics of a page are important to every reader: visual browsers for the sighted, vocal and Braille browsers for the visually impaired, search engines, and other software that parses the page, looking for a comprehensible structure.
The browser transforms some marked-up structures into objects with particular behaviors. An image spills out rows of pixels in visually meaningful patterns. A form control accepts input from the user, while a button submits those form control values to the server. A hyperlink can load a new page into the browser window. These different types of objects would not be possible without some form of markup.
5
Part I: Getting Started with JavaScript
The way a page is presented on screen, in Braille, or in speech, is determined by a style sheet that points to elements on the page and assigns appearance, emphasis, and other attributes. Every browser comes with a default style sheet that makes headlines, body text, hyperlinks, and form controls look a particular way. As web developers, we create our own style sheets to override the browser defaults and make our pages look the way we want. A style sheet tells the browser how to render the HTML page by referring to the document’s markup elements and their attributes.
Most importantly for the topic at hand, HTML markup gives JavaScript ways to locate and operate on portions of a page. A script can collect all the images in a gallery, or jump to a particular paragraph, because of the way the document is marked up.
Clearly, HTML markup and the way we handle it are critical to a document’s structure and meaning, its presentation, and its successful interaction with JavaScript. While all the details of how best to use HTML are outside the scope of this book, it’s clear that you’ll want to hone your markup skills while you’re learning JavaScript. Even the best script in the world can fail if launched on faulty, sloppy, or unplanned markup. In the early years of web development, back before the turn of the century, in that medieval era now known as ‘‘the 90s,’’ web designers didn’t have much consciousness about markup semantics and accessibility. Pages were marked up in any way that would produce a desired visual presentation, relying on the default styling of the browser and without regard for the sensibility of the markup. A developer might choose an h4 tag simply in order to produce a certain size and style of font, regardless of the document’s outline structure, or use data table markup for non-tabular content, simply to force the page layout to align. Required spaces and faux spacer images were mashed into the real content merely to tweak the appearance of the page: how things looked took complete precedence over what things meant. Fortunately, today that perspective seems quaintly old-fashioned, but unfortunately, there are still thousands of people producing pages that way and millions of pages left over from that dark era, their finger bones clutching at our sleeves and urging us to join them in their morbid pastime. It is one goal of this book to encourage you to code like a modern, living mammal, and not like a fossil. Relegating HTML to the category of a tagging language does disservice not only to the effort that goes into fashioning a first-rate web page, but also to the way users interact with the pages. To our way of thinking, any collection of commands and other syntax that directs the way users interact with digital information is programming. With HTML, a web-page author controls the user experience with the content just as the engineers who program Microsoft Excel craft the way users interact with spreadsheet content and functions. Version 4.0 and later of the published HTML standards endeavor to define the purpose of HTML as assigning context to content, leaving the appearance to a separate standard for style sheets. In other words, it’s not HTML’s role to signify that some text is italic but rather to signify why we might choose to italicize it. For example, you would tag a chunk of text that conveys emphasis (via the tag) or to mark its purpose () separately from the decision of how to format it with the style sheet. This separation between HTML markup and CSS presentation is an extremely powerful concept that makes the tweaking and redesign of web sites much faster than in the old days of inline styling and tags. XHTML is a more recent adaptation of HTML that adheres to stylistic conventions established by the XML (eXtensible Markup Language) standard. No new tags come with XHTML, but it reinforces the notion of tagging to denote a document’s structure and content. While for several years XHTML was seen as the next stage of evolution of HTML toward the holy grail of a universal XML markup for documents, that promise has failed to deliver, in part because Microsoft, with its enormous share of the browser market, has consistently declined to accommodate XHTML served correctly as application/xhtml+xml. Nearly all XHTML documents
6
Chapter 1: JavaScript’s Role in the World Wide Web and Beyond
today are served as text/html, which means that browsers treat them as just more HTML ‘‘tag soup.’’ Perhaps the only advantage gained by using XHTML markup is the stricter set of rules used by the W3C HTML Validator (http://validator.w3.org), which checks to make sure that all tags are closed in XHTML documents, but isn’t so fussy with HTML with its looser definitions. For convincing arguments against the use of XHTML served as text/html, read ‘‘Sending XHTML as text/html Considered Harmful,’’ by Ian Hickson (http://hixie.ch/advocacy /xhtml) and ‘‘Beware of XHTML,’’ by David Hammond (http://www.webdevout.net /articles/beware-of-xhtml). More recently, HTML5 has been growing in the Petri dishes of the World Wide Web Consortium (W3C). While modern browsers have only just begun to implement some of its features, HTML5 is considered by many to offer a more promising future than the seemingly abandoned XHTML. HTML5 offers an enriched vocabulary of markup tags compared to version 4, the better to align the markup language with the uses to which HTML is put in the real world. Because HTML 4.01 is the prevailing markup language for the web today, the HTML samples in this book are compatible with HTML 4.01, except for those that illustrate newer HTML5 elements such as canvas. With the proper DOCTYPE, the samples should validate as HTML5. They are easily convertible to XHTML1.0 with a few simple transforms: change the DOCTYPE, add lang attributes to the HTML element, and close empty elements such as input and link with />. It’s our hope that this will make the samples useful to folks heading up either HTML or XHTML paths, and also make the book more future-friendly as HTML5 comes into its own.
Cascading Style Sheets (CSS) Specifying the look and feel and speech of a web page is the job of Cascading Style Sheets (CSS). Given a document’s structure as spelled out by its HTML markup, a style sheet defines the layout, colors, fonts, voices, and other visual and aural characteristics to present the content. Applying a different set of CSS definitions to the same document can make it look and sound entirely different, even though the words and images are the same. (CSS 2.1 is the version of the W3C style sheet specification most widely supported by today’s user agents. Aural style sheets that let us assign voices and other sounds to the markup of a web page are a module of the CSS 3 specification and, at this writing, are supported only by Opera and the FireVox extension to Firefox, although other browsers are sure to follow.) Mastery of the fine points of CSS takes time and experimentation, but the results are worth the effort. The days of using HTML tables and transparent ‘‘spacer’’ images to generate elaborate multicolumn layouts are very much on the wane. Every web developer should have a solid grounding in CSS. The learning curve for CSS can be steep because of the inconsistent support for its many features from one browser to the next. You can make your life much easier by triggering standards mode in the browser, whereby it adheres more closely to the W3C CSS specification. We recommend triggering standards mode by using a correct DOCTYPE at the top of your markup, such as one of these: HTML 4.01 Strict: HTML 5:
7
Part I: Getting Started with JavaScript
XHTML 1.0 Strict:
For a clear explanation of DOCTYPE switching, read Eric Meyer’s essay ‘‘Picking a Rendering Mode’’ (http://www.ericmeyeroncss.com/bonus/render-mode.html).
Server-side programming Web sites that rely on database access, or change their content very frequently, incorporate programming on the server that generates the HTML output for browsers and/or processes forms that site visitors fill out on the page. Even submissions from a simple login or search form ultimately trigger some server process that sends the results to your browser. Server programming takes on many guises, the names of which you may recognize from your surfing through web development sites. PHP, ASP, .NET, JSP, and ColdFusion are among the most popular. Associated programming languages include Perl, Python, Java, C++, C#, Visual Basic, and even server-side JavaScript in some environments. Whatever language you use, the job definitely requires the web-page author to be in control of the server, including whatever back-end programs (such as databases) are needed to supply results or massage the information coming from the user. Even with the new, server-based web site design tools available, server scripting is often a task that a content-oriented HTML author will need to hand off to a more experienced programmer. Client-side JavaScript is not a replacement for server-side scripting. Any web site that reacts dynamically to user actions or that saves data must be driven by server-side scripting, even if JavaScript is used in the browser to enhance the user’s experience. The reasons are simple: First, JavaScript itself cannot write to files on the server. It can help the user make choices and prepare data for upload, but after that it can only hand off data to a sever-side script for database updating. Second, not all user agents run JavaScript. Screen readers, mobile devices, search engines, and browsers installed in certain corporate contexts are among those that don’t invoke JavaScript, or that receive web pages with the JavaScript stripped out. Therefore, your web site should be fully functional with JavaScript turned off. Use JavaScript to make the browsing experience faster, cooler, or more fun when it’s present, but don’t let your site be broken if JavaScript isn’t running. As powerful and useful as server-side scripting can be, its speed of interaction with the user is limited by the speed of the Internet connection between server and user agent. Obviously, any process that results in updating data on the server must include some client-server dialog, but there are many aspects of user interaction that, with the help of JavaScript, can take place entirely within the browser — form validation and drag-&-drop are two examples — then update the server when the response-sensitive process is complete. One way that server programming and browser scripting work together is with what has become known as Ajax — Asynchronous JavaScript and XML. The ‘‘asynchronous’’ part runs in the browser, requesting XML data from, or posting data to, the server-side script entirely in the background. XML data returned by the server can then be examined by JavaScript in the browser to update portions of the web page. That’s how many popular web-based email user interfaces work, as well as the draggable satellite-photo closeups of Google Maps (http://maps.google.com). Working together, server programming and browser scripting can make beautiful applications together. You’ll want to write in a server-side language such as PHP, or team up with someone who does, to lay the foundations for the JavaScript-enhanced pages you’ll be creating.
8
Chapter 1: JavaScript’s Role in the World Wide Web and Beyond
Of helpers and plug-ins In the early days of the World Wide Web, a browser needed to present only a few kinds of data before a user’s eyes. The power to render text (tagged with HTML) and images (in popular formats such as GIF and JPEG) was built into browsers intended for desktop operating systems. Not wanting to be limited by those data types, developers worked hard to extend browsers so that data in other formats could be rendered on the client computer. It was unlikely, however, that a browser would ever be built that could download and render, say, any of several soundfile formats. One way to solve the problem was to allow the browser, upon recognizing an incoming file of a particular type, to launch a separate application on the client machine to render the content. As long as this helper application was installed on the client computer (and the association with the helper program was set in the browser’s preferences), the browser would launch the program and send the incoming file to that program. Thus, you might have one helper application for a MIDI sound file and another for an animation file. Beginning with Netscape Navigator 2 in early 1996, software plug-ins for browsers enabled developers to extend the capabilities of the browser without having to modify the browser. Unlike a helper application, a plug-in can enable external content to blend into the document seamlessly. The most common plug-ins are those that facilitate the playback of audio and video from the server. Audio may include music tracks that play in the background while visiting a page, or live (streaming) audio, similar to a radio station. Video and animation can operate in a space on the page when played through a plug-in that knows how to process such data. Today’s browsers tend to ship with plug-ins that decode the most common sound-file types. Developers of plug-ins for Internet Explorer for the Windows operating system commonly implement plug-ins as ActiveX controls — a distinction that is important to the underpinnings of the operating system, but not to the user. Plug-ins and helpers are valuable for more than just audio and video playback. A popular helper application is Adobe Acrobat Reader, which displays Acrobat files that are formatted just as though they were being printed. But for interactivity, developers today frequently rely on the Flash plug-in by Macromedia (now owned by Adobe). Created using the Flash authoring environment, a Flash application can have active clickable areas and draggable elements, animation, and embedded video. Some authors simulate artistic video games and animated stories in Flash. A browser equipped with the Flash plug-in displays the content in a rectangular area embedded within the browser page. A variant of JavaScript called ActionScript enables Flash to interact with the user and components of the HTML page. Like JavaScript, ActionScript gets access to outside resources by making data-read and -write requests of the server. YouTube.com is a popular example of a web site with richly integrated Flash. One potential downside for authoring interactive content in Flash or similar environments is that if the user does not have the correct plug-in version installed, it can take some time to download the plug-in (if the user even wants to bother). Moreover, once the plug-in is installed, highly graphic and interactive content can take longer to download to the client (especially on a dial-up connection) than some users are willing to wait. This is one of those situations in which you must balance your creative palette with the user’s desire for your interactive content. Another client-side technology — the Java applet — was popular for a while in the late 1990s, but has fallen out of favor for a variety of reasons (some technical, some corporate-political). But this has not diminished the use of Java as a language for server and even cellular telephone programming, extending well beyond the scope of the language’s founding company, Sun Microsystems.
9
Part I: Getting Started with JavaScript
JavaScript: A Language for All Sun’s Java language is derived from C and C++, but it is a distinct language. Its main audience is the experienced programmer. That leaves out many web-page authors. Java’s preliminary specifications in 1995 were dismaying. How much more preferable would have been a language that casual programmers and scripters who were comfortable with authoring tools such as Apple’s once-formidable HyperCard and Microsoft’s Visual Basic could adopt quickly. As these accessible development platforms have shown, nonprofessional authors can dream up many creative applications, often for very specific tasks that no professional programmer would have the inclination to work on. Personal needs often drive development in the classroom, office, den, or garage. But Java was not going to be that kind of inclusive language. Spirits lifted several months later, in November 1995, when we heard of a scripting language project brewing at Netscape Communications, Inc. Born under the name LiveScript, this language was developed in parallel with a new version of Netscape’s web server software. The language was to serve two purposes with the same syntax. One purpose was as a scripting language that web server administrators could use to manage the server and connect its pages to other services, such as back-end databases and search engines for users looking up information. Extending the ‘‘Live’’ brand name further, Netscape assigned the name LiveWire to the database connectivity usage of LiveScript on the server. On the client side — in HTML documents — authors could employ scripts written in this new language to enhance web pages in a number of ways. For example, an author could use LiveScript to make sure that the user had filled in a required text field with an e-mail address or credit card number. Instead of forcing the server or database to do the data validation (requiring data exchanges between the client browser and the server), the user’s computer handles all the calculation work — putting some of that otherwise-wasted computing horsepower to work. In essence, LiveScript could provide HTML-level interaction for the user.
LiveScript becomes JavaScript In early December 1995, just prior to the formal release of Navigator 2, Netscape and Sun Microsystems jointly announced that the scripting language thereafter would be known as JavaScript. Though Netscape had several good marketing reasons for adopting this name, the changeover may have contributed more confusion to both the Java programming world and HTML scripting world than anyone expected. Before the announcement, the language was already related to Java in some ways. Many of the basic syntax elements of the scripting language were reminiscent of the Java style. However, for client-side scripting, the language was intended for very different purposes than Java — essentially to function as a programming language integrated into HTML documents rather than as a language for writing applets that occupy a fixed rectangular area on the page (and that are oblivious to anything else on the page). Instead of Java’s full-blown programming language vocabulary (and conceptually more difficult-to-learn object-oriented approach), JavaScript had a small vocabulary and a more easily digestible programming model. The true difficulty, it turned out, was making the distinction between Java and JavaScript clear to the world. Many computer journalists made major blunders when they said or implied that JavaScript provided a simpler way of building Java applets. To this day, some new programmers believe JavaScript is synonymous with the Java language: They post Java queries to JavaScript-specific Internet newsgroups and mailing lists.
10
Chapter 1: JavaScript’s Role in the World Wide Web and Beyond
The fact remains that client-side Java and JavaScript are more different than they are similar. The two languages employ entirely different interpreter engines to execute their code.
Enter Microsoft and others Although the JavaScript language originated at Netscape, Microsoft acknowledged the potential power and popularity of the language by implementing it (under the JScript name) in Internet Explorer 3. Even if Microsoft might prefer that the world use the VBScript (Visual Basic Script) language that it provides in the Windows versions of IE, the fact that JavaScript is available on more browsers and operating systems makes it the client-side scripter’s choice for anyone who must design for a broad range of users. With scripting firmly entrenched in the mainstream browsers from Microsoft and Netscape, newer browser makers automatically provided support for JavaScript. Therefore, you can count on fundamental scripting services in browsers such as Opera or the Apple Safari browser (the latter built upon an Open Source browser called KHTML). Not that all browsers work the same way in every detail — a significant challenge for client-side scripting that is addressed throughout this book.
JavaScript versions The JavaScript language has its own numbering system, which is completely independent of the version numbers assigned to browsers. The Mozilla Foundation, successor to the Netscape browser development group that created the language, continues its role as the driving force behind the JavaScript version numbering system. The first version, logically enough, was JavaScript 1.0. This was the version implemented in Navigator 2, and the first release of Internet Explorer 3. As the language evolved with succeeding browser versions, the JavaScript version number incremented in small steps. JavaScript 1.2 is the version that has been the most long lived and stable, currently supported by Internet Explorer 7. Mozilla-based browsers and others have inched forward with some new features in JavaScript 1.5 (Mozilla 1.0 and Safari), JavaScript 1.6 (Mozilla 1.8 browsers), and JavaScript 1.7 (Mozilla 1.8.1 and later). Each successive generation of JavaScript employs additional language features. For example, in JavaScript 1.0, arrays were not developed fully, causing scripted arrays not to track the number of items in the array. JavaScript 1.1 filled that hole by providing a constructor function for generating arrays and an inherent length property for any generated array. The JavaScript version implemented in a browser is not always a good predictor of core language features available for that browser. For example, although JavaScript 1.2 (as implemented by Netscape in Netscape Navigator 4) included broad support for regular expressions, not all of those features appeared in Microsoft’s corresponding JScript implementation in Internet Explorer 4. By the same token, Microsoft implemented try-catch error handling in its JScript in Internet Explorer 5, but Netscape didn’t include that feature until the Mozilla-based Netscape Navigator 6 implementation of JavaScript 1.5. Therefore, the language version number is an unreliable predictor in determining which language features are available for you to use.
Core language standard: ECMAScript Although Netscape first developed the JavaScript language, Microsoft incorporated the language in Internet Explorer 3. Microsoft did not want to license the Java name from its trademark owner (Sun Microsystems), which is why the language became known in the Internet Explorer environment as
11
Part I: Getting Started with JavaScript
JScript. Except for some very esoteric exceptions and the pace of newly introduced features, the two languages are essentially identical. The levels of compatibility between browser brands for a comparable generation are remarkably high for the core language (unlike the vast disparities in object model implementations discussed in Chapter 25, ‘‘Document Object Model Essentials’’). As mentioned, standards efforts have been under way to create industry-wide recommendations for browser makers to follow (to make developers’ lives easier). The core language was among the first components to achieve standard status. Through the European standards body called ECMA, a formal standard for the language was agreed to and published. The first specification for the language, dubbed ECMAScript by the standards group, was roughly the same as JavaScript 1.1 in Netscape Navigator 3. The standard (ECMA-262) defines how various data types are treated, how operators work, what a particular data-specific syntax looks like, and other language characteristics. A newer version (called version 3) added many enhancements to the core language (version 2 was just version 1 with errata fixed). The current version of the ECMAScript specification is known as ECMAScript, Fifth Edition, published online at www.ecma-international.org. To quote the ECMA, ‘‘The Fifth Edition codifies de facto interpretations of the language specification that have become common among browser implementations and adds support for new features that have emerged since the publication of the Third Edition. Such features include accessor properties, reflective creation and inspection of objects, program control of property attributes, additional array manipulation functions, support for the JSON object encoding format, and a strict mode that provides enhanced error checking and program security.’’ If you are a student of programming languages, you will find the document fascinating; if you simply want to script your pages, you might find the minutia mind-boggling. All mainstream browser developers have pledged to make their browsers compliant with the ECMA standard. The vast majority of the ECMAScript standard has appeared in Navigator since version 3 and Internet Explorer since version 4, and as new features are added to the ECMA standard, they tend to find their way into newer browsers as well. The latest version of ECMAScript is version 5. The previous edition, the 3rd, has been supported in all mainstream browsers for the past few years.
Note Even as ECMAScript, Fifth Edition was in the works, The Mozilla Foundation and Microsoft were implementing comparable versions of JavaScript 2.0 and JScript, respectively. An extension to ECMAScript called E4X (ECMAScript for XML) was finalized in late 2005 and is implemented in browsers based on Mozilla 1.8.1 or later (for example, Firefox 2.0). The Adobe ActionScript 3 language, which is used in the development of Flash animations, fully supports E4X. E4X is a significant addition to JavaScript because it makes XML (Extensible Markup Language) a native data type within the syntax of the language, making the processing of data in XML format much easier. XML is the data format used by many data exchange processes, including Ajax (see Chapter 39).
JavaScript: The Right Tool for the Right Job Knowing how to match an authoring tool to a solution-building task is an important part of being a well-rounded web site author. A web designer who ignores JavaScript is akin to a plumber who bruises his knuckles by using pliers instead of the wrench from the bottom of the toolbox.
12
Chapter 1: JavaScript’s Role in the World Wide Web and Beyond
By the same token, JavaScript won’t fulfill every dream. The more you understand about JavaScript’s intentions and limitations, the more likely you will be to turn to it immediately when it is the proper tool. In particular, look to JavaScript for the following kinds of solutions:
Getting your web page to respond or react directly to user interaction with form elements (input fields, text areas, buttons, radio buttons, checkboxes, selection lists) and hypertext links
Distributing small collections of database-like information and providing a friendly interface to that data
Controlling multiple-frame navigation, plug-ins, or Java applets based on user choices in the HTML document
Preprocessing data on the client before submission to a server
Changing content and styles in modern browsers dynamically and instantly, in response to user interaction
Requesting files from the server, and making read and write requests of server-side scripts
At the same time, it is equally important to understand what JavaScript is not capable of doing. Scripters waste many hours looking for ways of carrying out tasks for which JavaScript was not designed. Most of the limitations are intentional, to protect visitors from invasions of privacy or unauthorized access to their desktop computers. Therefore, unless a visitor uses a modern browser and explicitly gives you permission to access protected parts of his or her computer, JavaScript cannot surreptitiously perform any of the following actions:
Setting or retrieving the browser’s preferences settings, main window appearance features, action buttons, and printing capability
Launching an application on the client computer
Reading or writing files or directories on the client computer (with one exception: cookies)
Writing directly to files on the server
Capturing live data streams from the server for retransmission
Sending secret e-mails from web site visitors to you (although it can send data to a server-side script capable of sending email)
Web site authors are constantly seeking tools that will make their sites engaging (if not cool) with the least amount of effort. This is particularly true when the task of creating a web site is in the hands of people more comfortable with writing, graphic design, and page layout than with hard-core programming. Not every webmaster has legions of experienced programmers on hand to whip up some special, custom enhancement for the site. Neither does every web author have control over the web server that physically houses the collection of HTML and graphics files. JavaScript brings programming power within reach of anyone familiar with HTML, even when the server is a black box at the other end of a telephone line.
13
Developing a Scripting Strategy
I
f you are starting to learn JavaScript at this point in the history of scriptable browsers, you have both a distinct advantage and a disadvantage. The advantage is that you have the wonderful capabilities of mature browser offerings from Microsoft, The Mozilla Foundation (under brand names such as Firefox, Netscape, and Camino), Apple, and others at your bidding. The disadvantage is that you have not experienced the painful history of authoring for older browser versions that were buggy and at times incompatible with one another due to a lack of standards. You have yet to learn the anguish of carefully devising a scripted application for the browser version you use, only to have site visitors send you voluminous email messages about how the page triggers all kinds of script errors when run on a different browser brand, generation, or operating system platform. Welcome to the real world of scripting web pages with JavaScript. Several dynamics are at work to help make an author’s life difficult if the audience for the application uses more than a single type of browser. This chapter introduces you to these challenges before you type your first word of JavaScript code. Our fear is that the subjects we raise may dissuade you from progressing further into JavaScript and its powers. But as developers ourselves — and some of us have been using JavaScript since the earliest days of its public prerelease availability — we dare not sugar-coat the issues facing scripters today. Instead, we want to make sure you have an appreciation for what lies ahead to assist you in learning the language. We believe that if you understand the big picture of the browser-scripting world as it stands today, you will find it easier to target JavaScript usage in your web application development and be successful at it.
Browser Leapfrog Browser compatibility has been an issue for authors since the earliest days of the web gold rush — long before JavaScript. Despite the fact that browser developers and other interested parties voiced their opinions during formative stages of standards development, HTML authors could not produce a document that appeared
15
IN THIS CHAPTER How leapfrogging browser developments help and hurt web developers Separating the core JavaScript language from document objects The importance of developing a cross-browser strategy
Part I: Getting Started with JavaScript
the same, pixel by pixel, on all client machines. It may have been one thing to establish a set of standard tags for defining heading levels and line breaks, but it was rare for the actual rendering of content inside those tags to look identical on different brands of browsers on different operating systems. Then, as the competitive world heated up — and web browser development transformed itself from a volunteer undertaking into profit-seeking businesses — creative people defined new features and new tags that helped authors develop more flexible and interesting-looking pages. As happens a lot in any computer-related industry, the pace of commercial development easily surpassed the studied progress of standards. A browser maker would build a new HTML feature into a browser and only then propose that feature to the relevant standards body. Web authors were using these features (sometimes for prerelease browser versions) before the proposals were published for review. When the deployment of content depends almost entirely on an interpretive engine on the client computer receiving the data — the HTML engine in a browser, for example — authors face an immediate problem. Unlike a stand-alone computer program that can extend and even invent functionality and have it run on everyone’s computer (at least for a given operating system), web content providers must rely on the functionality built into the browser. This led to questions such as, ‘‘If not all browsers coming to my site support a particular HTML feature, then should I apply newfangled HTML features for visitors only at the bleeding edge?’’ and ‘‘If I do deploy the new features, what do I do for those with older browsers?’’ Authors who developed pages in the earliest days of the Web wrestled with these questions for many HTML features that we today take for granted. Tables and frames come to mind. Eventually, the standards caught up with the proposed HTML extensions — but not without a lot of author woe along the way. Despite the current dominance of the Microsoft Internet Explorer browser on the dominant Windows operating system, the number of browsers that people use is not shrinking. Several recent browsers, including the modern Netscape, Firefox, and Camino browsers, are based on an Open Source browser called Mozilla. The Macintosh operating system includes its own Apple-branded browser, Safari (released in 2003). And the independent Opera browser also has a home on some users’ computers. All of these non-Microsoft browser makers obviously believe that they bring improvements to the world to justify their development — building better mousetraps, you might say.
Duck and Cover Today’s browser wars are fought on different battlegrounds than in the early days of the Web. The breadth and depth of established web standards have substantially fattened the browser applications — and the books developers read to exploit those standards for their content. On one hand, most developers clamor for deeper standards support in new browser versions. On the other hand, everyday users care little about standards. All they want is to have an enjoyable time finding the information they seek on the Web. Most users are slow to upgrade, holding out until their favorite sites start breaking in their ancient browsers. Industry standards don’t necessarily make the web developer’s job any easier. For one thing, the standards are unevenly implemented across the latest browsers. Some browsers go further in their support than others. Then, there are occasional differences in interpretation of vague standards details. Sometimes the standards don’t provide any guidance in areas that are vital to content developers. At times, we are left to the whims of browser makers who fill the gaps with proprietary features in the hope that those features will become de facto standards.
16
Chapter 2: Developing a Scripting Strategy
As happens in war, civilian casualties mount when the big guns start shooting. The browser battle lines shifted dramatically in only a few years. The huge market-share territory once under Netscape’s command came under Microsoft’s sway. More recently, however, concerns about privacy and security on the Windows platform have driven many users to seek less vulnerable browsers. Mozilla Firefox has so far been the biggest beneficiary in the search for alternatives. Although a fair amount of authoring common ground exists between the latest versions of today’s browsers, uneven implementation of the newest features causes the biggest problems for authors wishing to deploy on all browsers. Trying to define the common denominator may be the toughest part of the authoring job.
Compatibility Issues Today Allow us to describe the current status of the compatibility situation among the top three browser families: Microsoft Internet Explorer, browsers based on Mozilla, and Apple Safari. The discussion in the next few sections intentionally does not get into specific scripting technology very deeply; some of you may know very little about programming at this point. In many chapters throughout this book, we offer scripting suggestions to accommodate a variety of browsers.
Separating the core JavaScript language from document objects Although early JavaScript authors initially treated client-side scripting as one environment that permitted the programming of page elements, the scene has changed as the browsers have matured. Today, a clear distinction exists between specifications for the core JavaScript language and for the elements you script in a document — for example, buttons and fields in a form (see Figure 2-1). FIGURE 2-1
The document object model is the programming interface between the HTML or XML document and the JavaScript programming language. HTML or XML document (marked-up text)
Document Object Model (DOM) (nodes, properties, methods, & event handlers)
On one level, this separation is a good thing. It means that one specification exists for basic programming concepts and syntax that could become the programming language in any number of other environments. You can think of the core language as basic wiring. When you know how electric
17
Part I: Getting Started with JavaScript
wires work, you can connect them to all kinds of electrical devices. Similarly, JavaScript today is used to wire together elements in an HTML document. Tomorrow, operating systems could use the core language to enable users to wire together desktop applications that need to exchange information automatically. At the ends of today’s JavaScript wires inside browsers are the elements on the page such as paragraphs (p), images (img), and input fields (input). In programming jargon, these items are known as document objects. By keeping the specifications for document objects separate from the wires that connect them, you can use other kinds of wires (other languages) to connect them. It’s like designing telephones that can work with any kind of wire, including a type of wire that hasn’t been invented yet. Today, the devices can work with copper wire or fiber-optic cable. You get a good picture of this separation in Internet Explorer, whose set of document objects can be scripted with either JavaScript or VBScript. The same objects can be connected with either of those two different sets of wiring. The separation of core language from document objects enables each concept to have its own standards effort and development pace. But even with recommended standards for each factor, each browser maker is free to extend the standards. Furthermore, authors may have to expend more effort to devise one version of a page or script that plays on multiple browsers, unless the script adheres to a common denominator (or uses some other branching techniques to let each browser run its own way).
Core language standard Keeping track of JavaScript language versions requires a brief history lesson. The first version of JavaScript (in Netscape Navigator 2) was version 1, although that numbering was not part of the language usage. JavaScript was JavaScript. Version numbering became an issue when Navigator 3 was released. The version of JavaScript associated with that Navigator version was JavaScript 1.1. The first appearance of the Navigator 4 generation increased the language version one more notch with JavaScript 1.2. Microsoft’s scripting effort contributes confusion for scripting newcomers. The first version of Internet Explorer to include scripting was Internet Explorer 3. The timing of Internet Explorer 3 was roughly coincidental to Navigator 3. But as scripters soon discovered, Microsoft’s scripting effort was one generation behind. Microsoft did not license the JavaScript name. As a result, the company called its language JScript. Even so, the HTML tag attribute that lets you name the language of the script inside the tags could be either JScript or JavaScript for Internet Explorer. Internet Explorer 3 could understand a JavaScript script written for Navigator 2. During this period of dominance by Navigator 3 and Internet Explorer 3, scripting newcomers were often confused because they expected the scripting languages to be the same. Unfortunately for the scripters, there were language features in JavaScript 1.1 that were not available in the older JavaScript version in Internet Explorer 3. Microsoft improved JavaScript in IE3 with an upgrade to the .dll file that gives IE its JavaScript syntax. However, it was hard to know which .dll is installed in any given visitor’s IE3. The situation smoothed out for Internet Explorer 4. Its core language was essentially up to the level of JavaScript 1.2, as in early releases of Navigator 4. Almost all language features that were new in Navigator 4 were understood when you loaded the scripts into Internet Explorer 4. Microsoft still officially called the language JScript. While all of this jockeying for JavaScript versions was happening, Netscape, Microsoft, and other concerned parties met to establish a core language standard. The standards body is a Switzerland-based organization originally called the European Computer Manufacturer’s Association and now known simply as ECMA (commonly pronounced ‘‘ECK-ma’’). In mid-1997, the first formal language specification was agreed on and published (ECMA-262). Due to licensing issues with the JavaScript name, the body created a new name for the language: ECMAScript.
18
Chapter 2: Developing a Scripting Strategy
With only minor and esoteric differences, this first version of ECMAScript was essentially the same as JavaScript 1.1, used in Navigator 3. Both Navigator 4 and Internet Explorer 4 officially supported the ECMAScript standard. Moreover, as happens so often when commerce meets standards bodies, both browsers went beyond the ECMAScript standard. Fortunately, the common denominator of this extended core language is broad, lessening authoring headaches on this front. JavaScript version 1.3 was implemented in Netscape Navigator 4.06 through 4.7x. This language version is also the one supported in IE5, 5.5, and 6. A few new language features are incorporated in JavaScript 1.5, as implemented in Mozilla-based browsers (including Navigator 6 and later). A few more core language features were added to JavaScript 1.6, first implemented in Mozilla 1.8 (Firefox 1.5, and yet more to JavaScript 1.8 in Firefox 3). In practice, so many browsers in use today support all but a few leading-edge features of the Mozilla browsers, that JavaScript version numbers are mostly irrelevant. Other compatibility issues with older browsers will likely get in your way before core language problems do. The time has come to forget about elaborate workarounds for the inadequacies of the oldest browsers.
Document object model If prevalent browsers have been close to one another in core JavaScript language compatibility, nothing could be further from the truth when it comes to the document objects. Internet Explorer 3 based its document object model (DOM) on that of Netscape Navigator 2, the same browser level it used as a model for the core language. When Netscape added a couple of new objects to the model in Navigator 3, the addition caused further headaches for neophyte scripters who expected those objects to appear in Internet Explorer 3. Probably the most commonly missed object in Internet Explorer 3 was the image object, which lets scripts swap the image when a user rolls the cursor atop a graphic — mouse rollovers, they’re commonly called. In the level 4 browsers, however, Internet Explorer’s DOM jumped way ahead of the object model that Netscape implemented in Navigator 4. The two most revolutionary aspects of IE4 were the ability to script virtually every element in an HTML document and the instant reflow of a page when the content changed. This opened the way for HTML content to be genuinely dynamic without requiring the browser to fetch a rearranged page from the server. NN4 implemented only a small portion of this dynamism, without exposing all elements to scripts or reflowing the page. It introduced a proprietary layering concept that was abandoned at the end of the Navigator 4.x lifetime. Inline content could not change in NN4 as it could in IE4. Suffice it to say that IE4 was an enviable implementation. At the same time, a DOM standard was being negotiated under the auspices of the World Wide Web Consortium (W3C). The hope among scripters was that after a standard was in place, it would be easier to develop dynamic content for all browsers that supported the standard. The resulting standard — the W3C DOM — formalized the notion of being able to script every element on the page, as in IE4. But it also invented an entirely new object syntax that no browser had used. The race was on for browsers to support the W3C DOM standards. An arm of the Netscape company called Mozilla.org was formed to create an all-new browser dedicated to supporting industry standards. The engine for the Mozilla browser became the basis for the all-new Navigator 6. It incorporated all of the W3C DOM Level 1 and a good chunk of Level 2. Mozilla 1.01 became the basis for the Netscape 7 browser, whereas Netscape 7.1 was built on the Mozilla 1.4 generation. In the summer of 2003, Netscape’s parent company, AOL Time Warner, decided to end further Netscape-branded browser development. The work on the underlying Mozilla browser, however, continues under an independent organization called The Mozilla Foundation.
19
Part I: Getting Started with JavaScript
Mozilla-based browsers, and others using the same engine (such as Firefox and Camino), continue to be upgraded and released to the public. The Mozilla engine arguably offers the most in-depth support for the W3C DOM standards. Even though Microsoft participated in W3C DOM standards development, IE5 and 5.5 implemented only some of the W3C DOM standard — in some cases, just enough to allow simple cross-browser scripting that adheres to the standard. Microsoft further filled out W3C DOM support in IE6, but chose to omit several important parts. Despite the long time gap between releases of IE6 and IE7, the latter included no additional W3C DOM support — much to the chagrin of web developers. IE8 finally did some significant catching up with the W3C DOM specification, with a switch to put IE8 back into IE7-compatibility mode for support of legacy scripts. The Apple Safari browser has raced forward in its comparatively short life to offer substantial W3C DOM support. This is especially true of version 2, which was first released as part of Mac OS X version 10.4. With this seemingly tortuous history of DOM development and browser support leading to the present day, you may wonder how anyone can approach DOM scripting with hope of success. Yet you’d be amazed by how much you can accomplish with today’s browsers. You’ll certainly encounter compatibility issues along the way, but this book will guide you through the most common problems and equip you to tackle others.
Laying a good foundation with markup When the HTML markup on a page conforms to uniform public standards, browsers from different manufacturers tend to treat it similarly. However, in order to support the millions of web pages from past years, browsers also take a stab at guessing the author’s intent when the markup differs from the specs. Because this sort of ‘‘guessing,’’ for the most part, isn’t prescribed in the HTML standards, the various browser manufacturers have come up with their own very different solutions. Therefore, you will get more consistent results and build more bullet-proof sites if your markup is easily parsable and error-free. We encourage you produce markup that conforms to the W3C specification — for example, the HTML 4.01 spec at http://www.w3.org/TR/html4/. It’s a good idea to rely on tools such as the W3C HTML Validator (http://validator.w3.org/) to check your markup against the standard. Beyond that, be consistent in your own work even when the spec is loose — for example, we suggest that you close all tags such as td and li even if the spec and the Validator don’t require it. Examine and mimic the kind of markup produced by JavaScript using DOM methods, and you’ll be doing fine.
Cascading Style Sheets Navigator 4 and Internet Explorer 4 were the first browsers to claim compatibility with a W3C recommendation called Cascading Style Sheets Level 1 (CSS1). This specification provided designers an organized way to customize the look and feel of a document (and thus minimized the HTML in each tag). As implementations go, NN4’s had a lot of rough edges, especially when trying to mix style sheets and tables. But IE4 was no angel, either, especially when one compared the results of style sheet assignments as rendered in the Windows and Macintosh versions of the browser (developed by two separate teams). CSS Level 2 adds more style functionality to the standard; IE6, Mozilla-based browsers, and Safari support a good deal of Level 2 (albeit unevenly) with the latest versions, such as Mozilla 1.8+ and
20
Chapter 2: Developing a Scripting Strategy
Safari 2+, and they are beginning to support CSS Level 3 features. Rendering of styled content is more harmonious among browsers, largely thanks to guidelines about how styles should render. Complex layouts, however, still need careful tweaking from time to time because of different interpretations of the standard. JavaScript plays a role in style sheets in IE4+, Mozilla, and Safari because those browsers’ object models permit dynamic modification to styles associated with any content on the page. Style sheet information is part of the object model and therefore is accessible and modifiable from JavaScript.
Standards compatibility modes (DOCTYPE switching) Both Microsoft and Netscape/Mozilla discovered that they had, over time, implemented CSS features in ways that ultimately differed from the published standards that came later (usually after much wrangling among working-group members). To compensate for these differences and make a clean break to be compatible with the standards, the major browser makers decided to let the page author’s choice of header element details determine whether the document was designed to follow the old way (sometimes called quirks mode) or the standards-compatible way. The tactic, known informally as DOCTYPE switching, is implemented in Internet Explorer 6 and later, Internet Explorer 5 for the Mac, and all Mozilla-based browsers. Although most of the differences between the two modes are small, there are some significant differences between them in Internet Explorer 6 and later, particularly when styles or DHTML scripts rely on elements designed with borders, margins, and padding. Microsoft’s original box model measured the dimensions of elements in a way that differed from the eventual CSS standard. To place the affected browsers in CSS standards-compatible mode, you should include a element at the top of every document that specifies one of the following statements:
Be aware, however, that older versions of Internet Explorer for Windows, such as Internet Explorer 5 or Internet Explorer 5.5, are ignorant of the standards-compatible mode and
21
Part I: Getting Started with JavaScript
will use the old Microsoft quirks mode regardless of your setting. Still, using the standards-compatible mode DOCTYPE is more likely to force your content and style sheets to render similarly across the latest browsers.
Dynamic HTML and positioning Perhaps the biggest improvements to the inner workings of the Level 4 browsers from both Netscape and Microsoft revolved around a concept called Dynamic HTML (DHTML). The ultimate goal of DHTML was to enable scripts in documents to control content, content position, and content appearance in response to user actions. To that end, the W3C organization developed another standard for the precise positioning of HTML elements on a page, as an extension of the CSS standards effort. The CSS-Positioning recommendation was later incorporated into the CSS standard, and both are now part of CSS Level 2. With positioning, you can define an exact location on the page where an element should appear, whether the item should be visible, and what stacking order it should take among all the items that might overlap it. IE4+ adheres to the positioning-standard syntax and makes positionable items subject to script control. Navigator 4 followed the standard from a conceptual point of view, but it implemented an alternative methodology involving an entirely new, and eventually unsanctioned, tag for layers. Such positionable items were scriptable in Navigator 4 as well, although a lot of the script syntax differed from that used in Internet Explorer 4. Fortunately for DHTML authors, Mozilla, through its adherence to the CSS standard, is more syntactically in line with the DHTML style properties employed in IE4+. Of more interest these days is the ability to modify the inline content of a web page without reloading the entire page. Fundamental standards from the W3C DOM Level 1 are supported by a wide range of browsers, including IE5+, Mozilla, Safari, and Opera. You can accomplish quite a lot using the same basic syntax across all of these browsers. Some challenges remain, however, as you’ll see throughout this book.
Developing a Scripting Strategy How do you create web pages that work well across the board? Browsers representing the latest generation contain a hodgepodge of standards and proprietary extensions. Even if you try to script to a common denominator among today’s browsers, your code probably won’t take into account the earlier versions of both the JavaScript core language and the browser DOMs. The true challenge for authors is determining the audience for which scripted pages are intended. Each new browser generation not only brings with it new and exciting features you are probably eager to employ in your pages, but also adds to the fragmentation of the audience visiting a publicly accessible page. It can take months for the latest upgrade of a browser to supplant the previous version among its users, and some people seldom or never upgrade unless the new browser comes via a new computer or operating system upgrade. As a result, web developers are writing for an incredibly mixed audience of browser makes and models, including some of the latest mobile devices that don’t support JavaScript. Add to that all the user agents that aren’t visual browsers, such as screen readers and search engines. How to cope?
Graceful degradation and progressive enhancement At this stage in the history of scriptable browsers, most web surfers arrive at our sites with browsers equipped with support for at least simple W3C DOM and DHTML capabilities. But ‘‘most’’ isn’t everyone by a long shot, so it is our obligation to apply scripting in the additive, or value-added, manner
22
Chapter 2: Developing a Scripting Strategy
known as progressive enhancement. By this we mean that your pages should convey their primary information to nonscriptable browsers designed for users with vision or motor-skill impairments, as well as less-feature-rich browsers built into the latest cellular phones. On top of that, your scripting efforts can give visitors with recent scriptable browsers a more enjoyable experience — better interactivity, faster performance, and a more engaging presentation. You will not only be contributing to the state of the art, but also carrying on the original vision of scripting in the browser. In an early stage of the Web’s evolution, many web site developers included the fancy features of the latest browser releases without much concern for folks who hadn’t upgraded their browsers or switched from brand X to brand Y. This meant that a lot of new web sites were cosmetically — or, worse, functionally — broken for a lot of visitors. It was common to see banners explaining that ‘‘this website is viewed best in’’ such-and-such a browser, and it was left to the visitor to put up with the mess, or to install a new browser. Over the years, web site producers have acquired two exciting new features that have changed our approach to browser support: the online business model and the social conscience. Excluding potential web site visitors from both commercial and non-profit sites is recognized as fiscally unwise. Excluding users of assistive technology is regarded as unjust — not to mention actionable in an increasing number of jurisdictions. As web developers, our concern isn’t just a few obsolete browsers that can’t run JavaScript. There are many other user agents that don’t or can’t support scripting, including search engines, some mobile devices, and some screen-readers and other assistive UAs. A lot of people simply turn off JavaScript support in their browsers. Some corporate firewalls strip JavaScript out of incoming web pages so that even entirely JavaScript-capable browsers within the organization do not see it or run it. Web stats are all over the map, but some estimates of the percentage of web site visitors who run without JavaScript for all of these reasons are 10% or higher. Even if it were only 1%, it would be significant. Imagine that you’re holding the front door for customers at a physical storefront, and you choose to slam the door in the face of one out of every hundred people who approach. How long would you keep your job? Graceful degradation is an approach to system design that provides fall-backs in case of failure. In web design, this means providing a lower level of appearance or functionality if the user agent can’t handle any of the advanced technology that makes up the page. The problem with graceful degradation is the way it’s been incorporated into site production. Developers who cut their teeth in the bad old days, and those who were trained by them, continued to build sites primarily for the most advanced and well-equipped browsers and then, as a final step or retrofit, tried to accommodate the rest. This approach adds a lot of work to the final stages of a project for the sake of a minority of users, so in the real world of web design, graceful degradation is often sacrificed due to all-too-common limits on time, money, and altruism. The result is an Internet full of web sites that still fail very ungracefully for a significant number of potential visitors. Progressive enhancement is a newer approach that does justice to graceful degradation. A web site is first designed to run in all user agents, and then enhancements are added to make the user’s experience faster or richer if they’re using a more sophisticated browser. This ensures essential functionality for every reader (human or machine) and supports the fancy browsers without sacrificing the simpler ones. It puts the vegetable course before the dessert and the horse before the cart. It makes sure the car has a working engine before adding the chrome and the sound system. One way we manifest the principle of progressive enhancement in our work is by building pages that work in the absence of JavaScript. This might seem like heresy in a JavaScript ‘‘Bible,’’ but the bottom line is that JavaScript is one of many tools we use to accomplish our work. No single tool is so shiny and clever that it should upstage the real star of the show — the web site visitor.
23
Part I: Getting Started with JavaScript
Separation of development layers Another important principle in modern web design is the separation of layers of development. The main layers we work with are the content of a page (such as text and image names), its structure in HTML markup, its behavior in JavaScript, and its presentation in CSS (see Figure 2-2). The more you can keep these layers separate, the easier it will be to build, modify, and re-use your work. FIGURE 2-2
Four layers of client-side web development. behavior (JavaScript) presentation (CSS) structure (DOM / HTML markup) content (text & URIs of images etc.)
marked-up content (HTML document)
Old-school web pages are easy to spot: just look at the HTML source, and you’ll see JavaScript and styling attributes embedded in the markup. This is like a house built with the wiring and pipes embedded in cement walls. If you want to change or replace the wiring, you’ve got a real mess on your hands. These cemented pages are redundant, since identical features on different pages require the same bloated markup to be downloaded each time. For that reason, they’re also slower to download. With separated layers, each component file is fairly trim and fast to download, and if the same style sheet or JavaScript script applies to more than one page, as is often the case, the response time is even faster since the browser caches (stores) files it has already fetched from the server. Web site development and redesign are also made more efficient because several people can work on different layers without stepping on one another’s toes. It becomes possible to develop modules of markup, script, and style that can more easily be tweaked and re-used for future projects. Separate development layers aren’t unrelated. Just the opposite, in fact: the style sheet and JavaScript code refer to and depend on the HTML markup structure, tags, and attributes. They are hands whose fingers are designed to mesh perfectly, but they are still separate hands. The first step in separating layers is literally to create separate files for your HTML, JavaScript, and CSS. (The HTML files you’ll see in this book are already combinations of markup and content, which, in the everyday world of web production, are often a merger of HTML templates and database fields performed by a server-side script.) Separation of layers is also an approach we can take to our scripting logic. JavaScript has the ability to write a chunk of cemented markup and text to a document in one operation, but if we separate the new structural elements from their content in our script, we end up with code that is easier to
24
Chapter 2: Developing a Scripting Strategy
debug and re-use, and that contains fewer errors. Similarly, JavaScript can directly tweak the styling of an element on a page, changing its color or size or position, but instead, if we simply assign an id or class that is separately defined in the style sheet, then a graphic designer can change that presentation without anyone having to modify the JavaScript.
Further reading Progressive Enhancement: Paving the Way for Future Web Design, by Debra Chamra http://hesketh.com/publications/articles/progressive-enhancementpaving-the-way-for/
Graceful Degradation & Progressive Enhancement, by Tommy Olsson http://accessites.org/site/2007/02/graceful-degradation-progressiveenhancement/
Progressive enhancement, in Wikipedia http://en.wikipedia.org/wiki/Progressive_enhancement
25
Selecting and Using Your Tools
I
n this chapter, you set up a productive script writing and previewing environment on your computer and learn where to find valuable resources on the Web. We also produce sample HTML, JavaScript, and CSS files to demonstrate how to use these tools to create real web pages. Because of differences in the way various personal computing operating systems behave, we present details of environments for two popular variants: Windows (95 through XP) and Mac OS X. For the most part, your JavaScript authoring experience will be the same regardless of the operating system platform you use — including Linux or Unix. Although there may be slight differences in font designs, depending on your browser and operating system, the information remains the same. Most illustrations of browser output in this book are made from the Windows XP versions of Internet Explorer and Firefox. If you run another browser or version, don’t fret if every pixel doesn’t match the illustrations in this book.
The Software Tools The best way to learn JavaScript is to type the HTML and scripting code into documents in a text editor. Your choice of editor is up to you, although we provide some guidelines for choosing.
Choosing a text editor For the purposes of learning JavaScript in this book, avoid WYSIWYG (What You See Is What You Get) web page authoring tools such as FrontPage and Dreamweaver. These tools may come in handy later for molding your content and layout. But the examples in this book focus more on script content (which you must type anyway), so there isn’t much HTML that you have to type. Files for all complete web page listings in this book (except for the tutorial chapters) also appear on the companion CD-ROM.
27
IN THIS CHAPTER How to choose basic JavaScript authoring tools How to set up your authoring environment How to enter a simple script to create a web page
Part I: Getting Started with JavaScript
An important factor to consider in your choice of editor is how easy it is to save standard text files with an .html filename extension. In the case of Windows, any program that not only saves the file as text by default, but also enables you to set the extension to .htm or .html, prevents a great deal of problems. If you use Microsoft Word, for example, the program tries to save files as binary Word files — something that no web browser can load. To save the file initially as a .txt or .html extension file requires mucking around in the Save As dialog box. This is truly a nuisance. Perhaps more importantly, a word processor such as Microsoft Word opens with a lot of default settings that may make desktop publishing easier but can frustrate a programmer, such as inserting spaces around words and automatically replacing straight quotes with curly quotes. Setting its defaults to make it programmer-friendly will make it less useful as a word processor. Finally, we urge you not to create documents in Word and ‘‘save them as a web page.’’ This will generate an HTML document that will look much like the word processing document on which it’s based, but the actual HTML coding it produces will be bloated and redundant — a far cry from the sleek and elegant code that we hope you will be producing after you read this book. Word just isn’t the right tool for this job. Nothing’s wrong with using bare-essentials text editors. In Windows, that includes the WordPad program or a more fully featured product such as Visual Studio or the shareware editor called TextPad. For Mac OS X, the bundled TextEdit application is also fine. Favorites among Mac HTML authors and scripters include BBEdit (Bare Bones Software) and SubEthaEdit (www.codingmonkeys.de/subethaedit).
Choosing a browser The other component that is required for learning JavaScript is the browser. You don’t have to be connected to the Internet to test your scripts in the browser. You can perform all testing offline. This means you can learn JavaScript and create cool, scripted web pages with a laptop computer — even on a boat in the middle of an ocean. The browser brand and version you use are up to you. Because the tutorial chapters in this book teach the W3C DOM syntax, you should be using a recent browser. Any of the following will get you through the tutorial: Internet Explorer 5 or later (Windows or Macintosh); any Mozilla-based browser (including Firefox, Netscape 7 or later, and Camino); Apple Safari; and Opera 7 or later.
Note Many example listings in Parts III and IV of this book demonstrate language or document object model (DOM) features that work on only specific browsers and versions. Check the compatibility listing for that language or DOM feature to make sure you use the right browser to load the page.
Setting Up Your Authoring Environment To make the job of testing your scripts easier, you want to have your text editor and browser running simultaneously. You need to be able to switch quickly between editor and browser as you experiment and repair any errors that may creep into your code. The typical workflow entails the following steps:
1. Enter HTML, JavaScript, and CSS into the source documents in the text editor. 2. Save them to disk. 3. Switch to the browser.
28
Chapter 3: Selecting and Using Your Tools
4. Do one of the following:
If this is a new document, open the file through the browser’s Open menu.
If the document is already loaded, reload the file into the browser.
Steps 2 through 4 are actions you will take frequently. We call this three-step sequence the save-switch-reload sequence. You will perform this sequence so often as you script that the physical act will quickly become second nature to you. How you arrange your application windows and effect the save-switch-reload sequence varies according to your operating system. In web site production, after you tweak your markup, style sheet, and scripts to your liking on your own computer, you’ll upload them to your server using an FTP (File Transfer Protocol) program. There are also online editors, but for now let’s keep it simple. One of the advantages of doing your work off-line on your own computer is that you don’t even have to have an active Internet connection during this stage of web site development.
Windows You don’t have to have either the editor or browser window maximized (at full screen) to take advantage of them. In fact, you may find them easier to work with if you adjust the size and location of each window so that both windows are as large as possible, while still enabling you to click a sliver of the other’s window. Or, you can leave the taskbar visible so you can click the desired program’s button to switch to its window (see Figure 3-1). A monitor that displays more than 800×600 pixels certainly helps in offering more screen real estate for the windows and the taskbar. FIGURE 3-1
Editor and browser window arrangement in Windows XP.
29
Part I: Getting Started with JavaScript
In practice, however, the Windows Alt+Tab task-switching keyboard shortcut makes the job of the save-switch-reload steps outlined earlier a snap. If you run Windows and also use a Windows-compatible text editor (which more than likely has a Ctrl+S file-saving keyboard shortcut), you can effect the save-switch-reload sequence from the keyboard with your the left hand: Ctrl+S (save the source file), Alt+Tab (switch to the browser), and Ctrl+R (reload the saved source file). As long as you keep switching between the browser and the text editor via Alt+Tab task-switching, either program is always just an Alt+Tab away.
Mac OS X In Mac OS X, you can change between your text editor and browser applications via the Dock, or, more conveniently, by pressing +Tab. As long as you stay in those two applications, the other program is only one +Tab away (see Figure 3-2). With this setup, the save-switch-reload sequence is a simple affair:
1. Press 2. Press 3. Press
+S (save the source file). +Tab (switch to the browser). +R (reload the saved source file).
To return to editing the source file, press
+Tab again.
FIGURE 3-2
Editor and browser window arrangement on the Macintosh screen.
30
Chapter 3: Selecting and Using Your Tools
Reloading issues For the most part, a simple page reload is enough to let you test a revised version of a script right away. But sometimes the browser’s cache (with its default settings) can preserve parts of the previous page’s attributes when you reload, even though you have changed the source code. To perform a more thorough reload, hold down the Shift key while clicking the browser’s Reload/Refresh button. Alternatively, you can turn off the browser’s cache in the preferences area, but that setting may negatively affect the overall performance of the browser during your regular web surfing.
Validate, Validate, Validate You can save yourself hours of debugging by checking to make sure your HTML is valid. If your markup is flawed, chances are your JavaScript and CSS will not work as expected, because they both depend on HTML elements (tags) and their attributes. The more closely your markup matches the industry-standard specs, the more likely it is that you’ll get consistent results across browsers that are all approaching the holy grail of web standards conformance. You should always proofread your own code, of course, but an automated validation tool helps for large, complicated pages, and for programmers who are still learning all the rules for correct markup. The World Wide Web Consortium (W3C), which wrote the HTML specification, has developed just such a validator. It checks a page with the rules specific to the DOCTYPE that begins the page. Besides catching our typos, an added advantage of running the Validator is that it helps us learn the fine points of HTML markup. Now repeat after me: The Validator Is My Friend. The W3C Validator is at http://validator.w3.org/. It offers three ways to input your markup — by entering its online URL, by uploading the .html file from your computer, and by copying and pasting the markup into the Validator directly. Then, click the Check button and read the results. Often, a single error of markup will result in several items in the Validator error report. If it found any errors in your markup, make the necessary corrections and run your code through the Validator again until you get the green success banner. Using the Validator will probably make you curious about the HTML specifications. You can read them on the W3C web site:
HTML 4.01: http://www.w3.org/TR/html4/
HTML5: http://www.w3.org/TR/html5/
XHTML 1.0: http://www.w3.org/TR/xhtml1/
As time goes on, you’ll discover other useful specs and validators out there, such as those for CSS (Cascading Style Sheets) and web accessibility guidelines:
Web Content Accessibility Guidelines: http://www.w3.org/TR/1999/WAI-WEBCONTENT-19990505/
Web Accessibility Evaluation Tools: http://www.w3.org/WAI/ER/tools/
Creating Your First Script To demonstrate how we’ll use these tools, let’s create a classic ‘‘Hello, World’’ page in three stages: first as plain HTML, then augmented with JavaScript, and finally styled with CSS.
31
Part I: Getting Started with JavaScript
For the sake of simplicity, the kind of scripts we’re building now are the kind that run automatically, immediately after the browser loads the HTML page. Although all scripting and browsing work here is done offline, the behavior of the page is identical if you place the source file on a server and someone accesses it through the web. To begin, open your text editor and your browser. Also run Windows File Manager/Macintosh Finder to create a folder in which to save your scripts.
Stage 1: static HTML Create a new text file and enter the markup in Listing 3-1. LISTING 3-1
Source Code for hello-world.html Hello, World Hello, World
This is HTML.
Save this file to your hard drive as hello-world.html, and open it in your browser. Figure 3-3 shows the page as it appears in the browser after you’re finished. The precise appearance (or voice, if you’re using a screen-reader) may vary slightly from one browser to the next, since at this point we’re relying on the default style sheet in the browser to render the page. The head of this page contains two required elements: a meta tag that declares the MIME type and character set, and a title. The body consists of a headline and a paragraph of text, pure and simple.
Stage 2: connecting with JavaScript Now let’s add JavaScript to the page. Create a new text file on your computer and enter Listing 3-2. Be sure and spell everything exactly, including upper- and lowercase: LISTING 3-2
Source Code for hello-world.js var today = new Date(); var msg = "This is JavaScript saying it’s now " + today.toLocaleString(); alert(msg);
32
Chapter 3: Selecting and Using Your Tools
FIGURE 3-3
The static HTML file displayed in a browser.
Save this file as hello-world.js. It consists of just three JavaScript statements: the first gets the current date, the second composes a brief message, and the third displays the message. To enable this JavaScript program to act on your HTML document, add a new script tag to the head section of the HTML (shown highlighted in Listing 3-3):
LISTING 3-3
Revised Source Code for hello-world.html ... Hello, World ...
33
Part I: Getting Started with JavaScript
The HTML script element tells the browser the type and name of the script file to combine with the document. Because the src (source) attribute doesn’t include a path, the system assumes it’s in the same folder as the HTML file. Unlike the meta tag, every tag must be closed with . When you save the new JavaScript file and the modified HTML file, reload the HTML file in your browser. It should look something like Figure 3-4.
FIGURE 3-4
A JavaScript alert().
The text we passed to alert() appears in what’s called a modal dialog. ‘‘Modal’’ means that you can’t do anything more with the application (your browser) until you close the dialog. Notice that the HTML headline and paragraph seem to have disappeared! No worries; they will appear as soon as you click OK on the modal dialog. Why? The browser renders the HTML file from top to bottom. It encounters the script tag in the head and runs the named JavaScript program before it renders the HTML body. In this case, the modal dialog produced by the alert() method halts the rendering of the rest of the page until we respond.
34
Chapter 3: Selecting and Using Your Tools
Stage 3: styling with CSS Let’s add some styling to the page so that you can see how HTML and CSS interact. Create a new text file on your computer and enter Listing 3-4: LISTING 3-4
Source Code for hello-world.css h1 { font: italic 3em Arial; } p { margin-left: 2em; font-size: 1.5em; }
Save this file to your hard drive as hello-world.css. This style sheet applies a particular font and color to all the h1 elements on the page, and a left margin and font-size to all the p elements. Of course, in our document, there is only one of each. To enable this style sheet to affect your HTML document, add a link tag to the head section of the HTML (shown highlighted in Listing 3-5): LISTING 3-5
Revised Source Code for hello-world.html ... Hello, World ...
The link element tells the browser the type, relationship, and name of the style sheet to combine with the document. Note that, like the meta tag and unlike the script tag, link is an ‘‘empty’’ tag and does not take a separate closing tag. Because the src (source) attribute doesn’t include a path, the system assumes it’s in the same folder as the HTML file. Every tag must be closed with . When you save these files and reload the HTML document in your browser (and click OK on that modal dialog), it will look something like Figure 3-5.
35
Part I: Getting Started with JavaScript
FIGURE 3-5
A styled page.
36
JavaScript Essentials
W
hen first learning to use JavaScript in the context of the web browser environment, it can be easy to confuse the objects of the JavaScript language with the document objects that we control with JavaScript. It’s important to separate the language from the Document Object Model (DOM) to help you make important decisions when designing JavaScript-enhanced pages. You may come to appreciate the separation in the future if you use JavaScript for other object models, such as in server-side programming or scripting Flash animations. All the basics of the language are identical from one context to another; only the objects differ. This chapter introduces many aspects of the core JavaScript language, particularly as they relate to deploying scripts in a world in which visitors to your pages may use a wide variety of browsers. Along the way, you’ll receive additional insights into the language itself. Fortunately, browser differences, as they apply to JavaScript, have lessened considerably as modern browsers continue to inch closer to consistently supporting the JavaScript (ECMAScript) standard. You can find details about the JavaScript core language syntax in Part III.
Combining JavaScript with HTML Scriptable browsers offer several ways to include scripts or scripted elements in your HTML documents. Not all approaches are recommended in today’s best practices, but it’s useful to learn even the old-school techniques so that you can understand legacy code when you come across it on the Web.
tags We marry JavaScript code to an HTML document using a tag set that specifies the scripting language
37
IN THIS CHAPTER How to combine JavaScript with HTML How to accommodate different versions of JavaScript Language highlights for experienced programmers
Part I: Getting Started with JavaScript
through the type attribute. You can have any number of such tag sets in your document. We recommend that all your scripts be external files linked to the HTML:
However, you can also embed JavaScript directly into the HTML by wrapping it in a ... tag: // JavaScript code goes here
There are distinct advantages to linking external JavaScript to HTML rather than embedding the scripts directly in the markup. The principal of separation of development layers encourages us to keep different aspects of a document apart, typically in separate, linked files. Doing so facilitates cleaner development, faster downloads, and more modular, re-purposable code that can be much easier to modify than mixtures of technologies cemented together in a single file.
Linking to script libraries (.js files) The advantages of linking to external JavaScript files become immediately obvious when the same script needs to run on more than one page of a site. If the script were embedded in the HTML markup, each page would be bloated with redundant content, and modifying the script would necessitate repeating the same changes in more than one file. In contrast, linking to an external file adds only a single line to each HTML file, and the external JavaScript file can be modified just once to immediately affect every page that includes it. Another plus is that, by separating the script code from the HTML document, you will not have to worry about comment-hiding or CDATA section tricks (see below). Such an external script file contains nothing but JavaScript code — no tags, no HTML. The script file you create must be a text-only file. Its filename extension can be anything, but the common convention is to use .js. To instruct the browser to load the external file at a particular point in your regular HTML file, you add a src attribute to the tag as follows:
If you load more than one external library, you may include a series of these tag sets in the head of the document. Notice that the tag pair is required, even though nothing appears between them. Don’t put any script statements between the start and end tags when the start tag contains a src attribute. How you reference the source file in the src attribute depends on its physical location and your HTML coding style. In the preceding example, the .js file is assumed to reside in the same directory as the HTML file containing the tag. But you can just as easily link to JavaScript files located in other directories on your server or on other domains entirely. Just as with an HTML file, if you want to refer to an absolute URL, the protocol for the file is http://.
38
Chapter 4: JavaScript Essentials
(A critical prerequisite for using script libraries with your documents is that your web server software must know how to map files with the .js extension to a MIME type of application/x-javascript. Test your web server and, if necessary, arrange for server configuration adjustments. It is rare that a modern server will not correctly recognize .js files.) When a user views the source of a page that links in an external script library, code from the .js file does not appear in the window, even though the browser treats the loaded script as part of the current document. However, the name or URL of the .js file is plainly visible (displayed exactly as it appears in your source code). Anyone can open that file in their browser (using the http:// protocol) to view the .js file’s source code. In other words, an external JavaScript source file is no more hidden from view than JavaScript embedded directly in an HTML file. Nothing that your browser downloads to render a web page can be hidden from view.
Specifying the MIME type & language Every opening tag should specify the type attribute. script is a generic element indicating that the contained statements are to be interpreted as executable script and not rendered as HTML. The element is designed to accommodate any scripting language that the browser knows — in other words, for which it contains an interpreter. For example, Internet Explorer carries interpreters for both JScript (Microsoft’s version of JavaScript) and VBScript.
Both of these scripts will be interpreted by IE, but a non-VBScript-aware browser such as Mozilla will attempt to interpret only the JavaScript file.
Specifying the language version It is rarely necessary to specify which version of JavaScript you wish to invoke in your documents. If your script relies on the objects and methods of a recent version of JavaScript that some older browsers won’t support, it’s better to test for that support directly. For example: // if this browser isn’t DOM-aware, exit gracefully if (!document.getElementById) return; // now it’s safe to use the DOM method var oExample = document.getElementById("example");
However, it isn’t always possible to test for the existence of language features at run-time. If the new feature is built into JavaScript’s syntax, its mere presence in the script can stop the interpreter from compiling the script to the point where it can’t even execute an if-test. For example, take the E4X syntax introduced in JavaScript 1.6 (see Chapter 20, ‘‘E4X — Native XML Processing’’): var xAuthor = George Sand ;
39
Part I: Getting Started with JavaScript
If you include this syntax in a script run by a browser that doesn’t ‘‘know’’ E4X syntax, the script will simply not run, in some cases with no meaningful error message to alert the visitor or the developer. No code in the same script will run, even if it’s within the abilities of the browser. You can isolate the new syntax with a version-specific type attribute for the script element:
or: // script for all browsers goes here // script for browsers that know JavaScript 1.6 and later
Be aware, though, that specifying the version as a special flag is non-standard so not all browsers support it. In the specific case of E4X syntax, Mozilla has introduced another special flag for the type attribute: e4x=1 meaning, essentially, ‘‘E4X support = true.’’
The practical question then arises: If you have to wall off part of your script from older browsers, what alternative code do you give to those older browsers in place of the new code? And if you’re writing that work-around code, why not let that be the only code? What advantage is there in writing the same logic in two different ways in the same script? It’s a question to ponder when working with leading-edge language enhancements.
The deprecated language attribute The type attribute is required for the tag as of HTML 4, formally published in 1998. Earlier browsers recognized the language attribute instead of type. The language attribute is deprecated, which means that it’s an outdated feature of the language, has been replaced by newer constructs, and may become obsolete in future versions of HTML. Browsers continue to recognize it in order to support legacy web pages, but there’s no reason to use it in industry-standard web sites today. We include it here so that you’ll understand it when you encounter it in old markup. The language attribute allowed the scripter to write for a specific minimum version of JavaScript or, in the case of Internet Explorer, other languages such as VBScript. For example, the JavaScript interpreter built into Navigator 3 knows the JavaScript 1.1 version of the language; Navigator 4 and Internet Explorer 4 include the JavaScript 1.2 version. For versions beyond the original JavaScript, you could specify the language version by appending the version number after the language name without any spaces, as in: ... ...
The type attribute didn’t gain browser support until Internet Explorer 5, Mozilla, and W3C DOM-compatible browsers. If you need to inform even older browsers which language and
40
Chapter 4: JavaScript Essentials
version of scripting you’re using, you can specify both the type and language attributes in your tags, as older browsers will ignore the type attribute: ...
Of course, if you’re depending on features in JavaScript 1.5, you’ve forgone legacy browsers anyway. In this case, just take the forward-looking approach and test for modern methods at the beginning of the script.
The proprietary for and event attributes Internet Explorer versions 4 through 7 offered a variation on the tag that bound statements of a script to a specific object and an event generated by that object. In addition to the language attribute, the tag must include both for and event attributes (not part of the HTML specification). The value assigned to the for attribute was a reference to the desired object. Most often, this was simply the identifier assigned to the object’s id attribute. The event attribute was the event handler name that you wanted the script to respond to. For example, if you designed a script to perform some action upon a mousedown event in a paragraph whose ID was myParagraph, the script statements were enclosed in the following tag set: ...
Statements inside the tag set executed only upon the firing of the event. No function definitions were required. Because the for and event attributes were proprietary creations of Microsoft, this way of binding an object’s event to a script guaranteed that only Internet Explorer would execute the script when the named event occurred. Even in its day, the script for tag was not a winner. Its attributes constituted a lot of source code overhead for each object’s script, so it was never a very efficient technique for linking script statements to multiple objects and events. In addition, non-Internet Explorer and pre-Internet Explorer 4 browsers would execute the script statements as the page loaded, making this proprietary language feature impractical in any cross-browser script.
Old-school inline JavaScript Back in the bad old days of ‘‘tag soup’’ web development, it was common practice to insert JavaScript statements right in the HTML markup:
In that example, the change event for the control object nations is set to trigger the JavaScript statements provided: a custom function call. We’ll show you how this works elsewhere in the book to help you read legacy code, but combining markup and scripting like that today is commonly considered to be ‘‘very ’90s.’’ There are many disadvantages to inserting JavaScript into markup this way: it’s awkward and expensive to change the markup or the scripting independently when they’re this intermeshed; the downloaded markup is unnecessarily bloated and doesn’t take full advantage of the centralized
41
Part I: Getting Started with JavaScript
modularity of externally linked scripts; and user agents running versions of JavaScript that can’t handle the code are unable to avoid the script. In a modern page, this markup would be cleaned up to
with the event handler assigned entirely in JavaScript with something like AddEvent("nations", "change", doSomething);
where the AddEvent() function can cater to a variety of event models in different browsers, can be entirely separate from the markup to protect user agents that can’t handle scripting, and can be firewalled by defensive if-tests to protect it from legacy JavaScript interpreters that don’t play well with modern code.
Accommodating the JavaScript-incapable user agent There are several categories of user agent that can’t or don’t support JavaScript, representing, by some accounts, some ten to fifteen percent of all internet usage today. These user agents include search engine spiders, mobile device browsers, browsers inside government and corporate firewalls that strip out script for security reasons, assistive technologies, and browsers in which, for any of a variety of reasons, their users have turned scripting off. There is sure to be a small number of legacy browsers still in use today that cannot run JavaScript or that support very early versions, but the vast majority of non-JavaScript-using internet visitors are using contemporary hardware and software. It is our responsibility as web developers to acknowledge that JavaScript is an option, not a given, and to ensure that our pages are functional even in its absence. It’s our mission to use JavaScript to enhance the visitor’s experience and not to supply critical elements without which a page would be broken or dead in the water. We make sure that the HTML markup provides all the fundamental content, hyperlinks, and form fields, and that server-side scripting completes the dialog between client and server that is the core of the HTTP request model. Then, when JavaScript is running, it can morph the page, pretty up the user interface, and quicken the response time. That is the win-win model of modern web scripting. The question then comes, how can we add JavaScript to an HTML document in a way that leaves the page fully functional when the script interpreter is not running, not present, or packing an obsolete version? Our tactics are several:
We begin our scripts by testing for the presence of modern DOM methods such as document.getElementById in order to turn away obsolete versions of the JavaScript interpreter.
We export JavaScript to external files and link them to the HTML document with script tags. User agents not running a scripting interpreter won’t even go there.
Corollary to the above, we omit JavaScript from event attributes in HTML tags, and instead use JavaScript to assign event handlers to page elements.
If it is ever unavoidable to include JavaScript in the HTML document itself, enclose the script in HTML comments so that it won’t be rendered by not-script-savvy browsers.
Let’s take a moment to expand on that last point.
42
Chapter 4: JavaScript Essentials
Commenting out script in HTML Non-scriptable browsers do not know about the tag. Normally, browsers ignore tags that they don’t understand. That’s fine when a tag is just one line of HTML, but a ... tag pair can enclose any number of script statement lines. Old and compact browsers don’t know to expect a closing tag. Therefore, their natural inclination is to render any lines they encounter after the opening tag. Seeing JavaScript code spilling out onto a page is sure to confuse or erode the confidence of any visitor. You can, however, exercise a technique that tricks most non-scriptable browsers into ignoring the script statements: surround the script statements (inside the tag set) with HTML comment markers. An HTML comment begins with the sequence . Therefore, you should embed these comment sequences in your scripts according to the following format:
JavaScript interpreters know to ignore a line that begins with the HTML beginning comment sequence
That’s quite a mouthful and deserves a bit of explanation. XHTML parsers are intolerant of < symbols that don’t begin elements and & symbols that don’t begin HTML entities, yet these characters are commonplace JavaScript operators. The solution is to encase your script statements in what is known as a CDATA (pronounced ‘‘see-day-tah’’) section:
We can then add the HTML comment markers to stop legacy browsers from rendering the script: comment tags and an XHTML-aware browser will ignore the CDATA section and not execute the script. So, we have to close the comment tag before the CDATA begins in order to satisfy XHTML: , so we have to make the CDATA open-tag not show up. The technique we’re using is to make the HTML parsers think it’s a closed tag
but to keep XHTML from considering it closed we’ll add another comment marker
and open the block comment tag once more to stop some browsers from attempting to render the JavaScript code as plain text: comment tags, whereas scriptable browsers ignore the opening comment symbol when it appears inside a tag set. LISTING 7-4
Hiding Scripts from Most Old Browsers
The odd construction right before the ending script tag needs a brief explanation. The two forward slashes are a JavaScript comment symbol. This symbol is necessary because JavaScript otherwise tries to interpret the components of the ending HTML symbol (-->). Therefore, while the forward slashes tell JavaScript to skip the line entirely, a non-scriptable browser simply treats those slash characters as part of the entire HTML comment to be ignored. Although it’s no longer really necessary to hide JavaScript in this way from older browsers, there are instances when a different type of hiding may be required. XML is more frequently being used to feed content to the browser, and often this is done using XHTML. In the XML world, all special characters need to be enclosed in a CDATA section, or else the file may be parsed incorrectly; at the very least, it will fail validation. Again, the trick is to enclose your script, but this time it will look like
98
Chapter 7: Scripts and HTML Documents
Listing 7-5. You’ll notice again that immediately before the closing script tag the JavaScript comment hides the closing of the CDATA section from JavaScript itself. LISTING 7-5
Hiding Scripts From XML Parsers
Despite the fact that these techniques are often called script hiding, they do not conceal the scripts from human readers. All client-side JavaScript scripts are part of, or accompany, the HTML document, and they download to the browser just like all the other assets that make up the page. You can view the JavaScript source as easily as you can view the HTML document source. Do not be fooled into thinking that you can hide your scripts from prying eyes. Some developers obfuscate their scripts by removing all carriage returns and using nonsensical variable and function names, but this only slows down (and doesn’t stop) any inquisitive visitor from reading and understanding the code. Since it’s not possible to truly hide your JavaScript programming from the public, you might as well flaunt it: sign the scripts you’re proud of, include a copyright or Creative Commons notice of authorship in script comments, and encourage people who admire the script to come to you for more.
JavaScript Statements Virtually every line of code in an externally linked file or that sits within a ... tag pair is a JavaScript statement (except for HTML comment tags). To be compatible with the habits of experienced programmers, JavaScript accepts a semicolon at the end of every statement (the computer equivalent of a period at the end of a sentence). This semicolon is optional, but we strongly recommend that you use it consistently to avoid ambiguity. The carriage return at the end of a statement suffices for JavaScript to know that the statement has ended. It is possible, however, that in the future the semicolon will be required, so it’s a good idea to get into the semicolon habit now. A statement must be in the script for a purpose. Therefore, every statement does something relevant to the script. The kinds of things that statements do are
Define or initialize a variable
Assign a value to a property or variable
Change the value of a property or variable
Define or invoke an object’s method
Define or invoke a function routine
Make a decision
99
Part II: JavaScript Tutorial
If you don’t yet know what all of these things mean, don’t worry; you will, by the end of this tutorial. The point we want to stress is that each statement contributes to the scripts you write. The only statement that doesn’t perform any explicit action is the comment. A pair of forward slashes (no space between them) is the most common way to include a single-line comment in a script: // this is a one-line comment var a = b;
// this comment shares a line with an active statement
Multiple-line comments can be enclosed in slash-asterisks: /* Any number of lines are comments if they are bracketed by slash-asterisks */
You add comments to a script for the benefit of yourself and other human readers. They usually explain in plain language what a statement or group of statements does. The purpose of including comments is to remind you how your script works six months from now, or to help out another developer who needs to read your code.
When Script Statements Execute Now that you know where scripts go in a document, it’s time to look at when they run. Depending on what you need a script to do, you have four choices for determining when a script runs:
While a document loads
Immediately after a document loads
In response to user action
When called upon by other script statements
The determining factor is how the script statements are positioned in a document.
While a document loads: immediate execution Listing 7-6 is a variation of your first script from Chapter 5, ‘‘Your First JavaScript Script.’’ In this version, the script writes the current date and time to the page while the page loads. The document.write() method is a common way to write dynamic content to the page during loading. We call the kinds of statements that run as the page loads immediate statements. Care must be taken when you code scripts using document.write(). Once the page completes loading, any further document.write() statements create a new page, overwriting all the content you have carefully written. LISTING 7-6
HTML Page with Immediate Script Execution Date & Time: Immediate Execution
100
Chapter 7: Scripts and HTML Documents
Date & Time: Immediate Execution
It is currently .
In recent years, the use of document.write() has become mildly controversial. At the very least, it encourages bad structure in your document, mixing script with HTML. Good structure cleanly separates style (style sheets) and behavior (JavaScript) from the HTML markup. One issue with document.write() centers around the increased use of XML to feed content to the browser. XML documents must be well-formed. If a document.write() statement closes an element opened outside of it, or opens a new element, the XML document will fail to load because the browser will perceive it as malformed. Another issue with document.write() centers around the DOM, especially with XHTML documents (which are served as XML). The use of document.write() means that the content will not be included in the DOM. The very important short story is that you will not be able to further manipulate such content with your JavaScript programs, limiting your dynamic response to the visitor’s actions on your web page. This is an interesting conundrum because you might often choose to use document.write(), as we do in several examples in this book, to provide dynamic content, based on the browser environment, as the page loads.
Deferred scripts The other three ways that script statements run are grouped together into what we call deferred scripts. To demonstrate these deferred script situations, we must introduce you briefly to a concept covered in more depth in Chapter 9, ‘‘Programming Fundamentals, Part II’’: the function. A function defines a block of script statements summoned to run some time after those statements load into the browser. Functions are clearly visible inside a tag because each function definition begins with the word function followed by the function name (and parentheses). After a function is loaded into the browser (commonly in the head portion so that it loads early), it stands ready to run whenever called upon.
Run after loading One of the most common times a function is called on to run is immediately after a page loads. Scripts using industry-standard DOM methods would fail if we attempted to operate on page elements before they appeared in the DOM, so we ask the browser to run the script only after the page has finished loading. The window object has an event handler property called onload. Unlike most event handlers, which are triggered in response to user action (for example, clicking a button), the
101
Part II: JavaScript Tutorial
window’s onload event handler fires the instant that all of the page’s components (including images, Java applets, and embedded multimedia) are loaded into the browser. There are two cross-browser ways to connect the onload event handler to a function: via an object event property or an HTML event attribute. The object event property we prefer is shown in Listing 7-6. The assignment of the event handler is executed in immediate mode and attaches the desired function call to the load event of the window object. At this early point in page rendering, only the window object can be guaranteed to exist in the DOM. In old-school web development, the window.onload event assignment was written right into the HTML, with the element standing in to represent the window. Therefore, you can include the onload event attribute in the tag, as shown in Listing 7-7. Recall from Chapter 6, ‘‘Browser and Document Objects,’’ that an event handler can run a script statement directly. However, if the event handler must run several script statements, it is usually more convenient to put those statements in a function definition and then have the event handler invoke that function. That’s what happens in Listing 7-7: When the page completes loading, the onload event handler triggers the done() function. That function (simplified for this example) displays an alert dialog box. LISTING 7-7
Running a Script from the onload Event Handler An old-school HTML-based onload script function done() { alert("The page has finished loading."); } An old-school HTML-based onload script
Here is some body text.
Don’t worry about the curly braces or other oddities in Listing 7-7 at this point. Focus instead on the structure of the document and the flow. The entire page loads without running any script statements, although the page loads the done() function in memory so that it is ready to run at a moment’s notice. After the document loads, the browser fires the onload event handler, which causes the done() function to run. Then the user sees the alert dialog box. Although the HTML event attribute approach dates back to the earliest JavaScript browsers, the trend these days is to separate HTML markup from specifics of style (style sheets) and behavior (scripts). To the scripter’s rescue come the equivalent event handler properties of objects. To get the onload
102
Chapter 7: Scripts and HTML Documents
attribute out of the tag, you can instead assign the desired JavaScript function to the object’s event as a property, as in: window.onload = done;
Such statements typically go near the end of scripts in the head portion of the document. Note, too, that in this version, the right side of the statement is merely the function’s name, with no quotes or parentheses. Because it is easier to learn about event handlers when they’re specified as HTML attributes, most examples in this tutorial continue with that approach. We needed to show you the property version, however, because you will see a lot of real-life code using that format.
Run by user Getting a script to execute in response to a user action is very similar to the preceding example for running a deferred script right after the document loads. Commonly, a script function is defined in the head portion, and an event handler in, say, a form element calls upon that function to run. Listing 7-8 includes a script that runs when a user clicks a button. LISTING 7-8
Running a Script from User Action An onclick script function alertUser() { alert("Ouch!"); } Here is some body text.
Not every object must have an event handler defined for it, as shown in Listing 7-8 — only the ones for which scripting is needed. No script statements execute in Listing 7-8 until the user clicks the
103
Part II: JavaScript Tutorial
button. The alertUser() function is defined as the page loads, and it waits to run as long as the page remains loaded in the browser. If it is never called upon to run, there’s no harm done.
Called by another function The last scenario for when script statements run also involves functions. In this case, a function is called upon to run by another script statement. Before you see how that works, it helps to read the next lesson, Chapter 8, ‘‘Programming Fundamentals, Part I.’’ Therefore, we will hold off on this example until later in the tutorial.
Viewing Script Errors In the early days of JavaScript in browsers, script errors displayed themselves in very obvious dialog boxes. These boxes were certainly helpful for scripters who wanted to debug their scripts. However, if a bug got through to a page served up to a nontechnical user, the error alert dialog boxes were not only disruptive, but also scary. To prevent such dialog boxes from disturbing unsuspecting users, the browser makers tried to diminish the visual impact of errors in the browser window. Unfortunately for scripters, it is often easy to overlook the fact that your script contains an error because the error message is not so obvious. Not only does each browser have a different way of displaying error messages, but the display can differ from version to version. The method to display errors in each of the major browsers is covered in the section ‘‘Error Message Notification’’ in Chapter 48, ‘‘Debugging Scripts’’ on the CD-ROM. While you need to read that section before testing your code, we’ve included a sample error dialog box as it appears in IE5+ (see Figure 7-1) and one as it appears in Mozilla 1.4+ (see Figure 7-2). Keep in mind that script-error dialog boxes are not necessarily displayed by default in these and other browsers. You have to train yourself to monitor the status bar when a page loads and after each script runs. FIGURE 7-1
The expanded IE error dialog box.
Understanding error messages and doing something about them is a very large subject, the complete discussion of which is in reserved for Chapter 48. During this tutorial, however, you can use the error messages to see whether you mistyped a script from a listing in the book.
104
Chapter 7: Scripts and HTML Documents
FIGURE 7-2
The Mozilla 1.4 JavaScript console window.
Scripting versus Programming You may get the impression that scripting is easier than programming. Scripting simply sounds easier or more friendly than programming. In many respects, this is true. One of our favorite analogies is the difference between a hobbyist who builds model airplanes from scratch and a hobbyist who builds model airplanes from commercial kits. The ‘‘from scratch’’ hobbyist carefully cuts and shapes each piece of wood and metal according to very detailed plans before the model starts to take shape. The commercial kit builder starts with many prefabricated parts and assembles them into the finished product. When both builders are finished, you may not be able to tell which airplane was built from scratch and which one came out of a box of components. In the end, both builders used many of the same techniques to complete the assembly, and each can take pride in the result. Thanks to implementations of the document object model (DOM), the browser gives scripters many prefabricated components with which to work. Without the browser, you’d have to be a pretty good programmer to develop your own application from scratch that served up content and offered user interaction. In the end, both authors have working applications that look equally professional. Beyond the DOM, however, real programming nibbles its way into the scripting world. That’s because scripts (and programs) work with more than just objects. Earlier in this lesson, we said that each statement of a JavaScript script does ‘‘something’’, and that ‘‘something’’ involves data of some kind. Data is the information associated with objects or other pieces of information that a script pushes around from place to place with each statement. Data takes many forms. In JavaScript, the common incarnations of data are numbers, text (called strings), objects (derived from the object model or created with script), and true and false (called Boolean values). Each programming or scripting language determines numerous structures and limits for each kind of data. Fortunately for newcomers to JavaScript, the universe of knowledge necessary for working with data is smaller than in a language such as Java or C++. At the same time, what you learn
105
Part II: JavaScript Tutorial
about data in JavaScript is immediately applicable to future learning you may undertake in any other programming language; don’t believe for an instant that your efforts in learning scripting will be wasted. Because, deep down, scripting is programming, you need to have a basic knowledge of fundamental programming concepts to consider yourself a good JavaScript scripter. In the next two lessons, we set aside most of our discussion about the DOM and focus on the programming principles that will serve you well in JavaScript and future programming endeavors.
Exercises 1. Write the complete script tag set for a script whose lone statement is document.write("Hello, world.");
2. Build an HTML document, and include the answer to the previous question, such that the page executes the script as it loads. Open the document in your browser to test the results.
3. Add a comment to the script in the previous answer that explains what the script does. 4. Create an HTML document that displays an alert dialog box immediately after the page loads, and displays a different alert dialog box when the user clicks a form button.
5. Carefully study the document in Listing 7-9. Without entering and loading the document, predict
a. What the page looks like without further styling b. How users interact with the page c. What the script does Then type the listing as shown into a text editor. Observe all capitalization and punctuation. Do not type a carriage return after the = sign in the upperMe function statement; let the line word-wrap as it does in the following listing. It’s okay to use a carriage return between attribute name/value pairs, as shown in the first tag. Save the document as an HTML file, and load the file into your browser to see how well you did. LISTING 7-9
How Does This Page Work? Text Object Value function upperMe() { document.getElementById("output").value = document.getElementById("input").value.toUpperCase(); }
106
Chapter 7: Scripts and HTML Documents
Enter lowercase letters for conversion to uppercase:
107
Programming Fundamentals, Part I
T
he tutorial breaks away from HTML and documents for a while, as you begin to learn programming fundamentals that apply to practically every scripting and programming language you will encounter. Here, you start learning about variables, expressions, data types, and operators — things that might sound scary if you haven’t programmed before. Don’t worry. With a little practice, you will become quite comfortable with these terms and concepts.
IN THIS CHAPTER What variables are and how to use them Why you must learn how to evaluate expressions
What Language Is This?
How to convert data from one type to another
The language you’re studying is called JavaScript. But the language has some other names that you may have heard. JScript is Microsoft’s name for the language. By leaving out the ava, the company doesn’t have to license the Java name from its trademark owner: Sun Microsystems.
How to use basic operators
A standards body called ECMA (pronounced ‘‘ECK-ma’’) now governs the specifications for the language (no matter what you call it). The document that provides all of the details about the language is known as ECMA-262 (it’s the 262nd standard published by ECMA). Both JavaScript and JScript are ECMA-262 compatible. Some earlier browser versions exhibit very slight deviations from ECMA-262 (which came later than the earliest browsers). The most serious discrepancies are noted in the core language reference in Part III of this book.
Working with Information With rare exceptions, every JavaScript statement you write does something with a hunk of information — data. Data may be text information displayed onscreen by a JavaScript statement or the on/off setting of a radio button in a form. Each single piece of information in programming is also called a value. Outside of programming, the term value usually connotes a number of some kind; in the programming world, however, the term is not as restrictive.
109
Part II: JavaScript Tutorial
A string of letters is a value. A number is a value. The setting of a checkbox (whether it is checked or not) is a value. In JavaScript, a value can be one of several types. Table 8-1 lists JavaScript’s formal data types, with examples of the values you will see displayed from time to time. TABLE 8-1
JavaScript Value (Data) Types Type
Example
Description
String
"Howdy"
A series of characters inside quote marks
Number
4.5
Any number not inside quote marks
Boolean
true
A logical true or false
Null
null
Devoid of any content, but a value just the same
Object
A software thing that is defined by its properties and methods (arrays are also objects)
Function
A function definition
A language that contains these few data types simplifies programming tasks, especially those involving what other languages consider to be incompatible types of numbers (integers versus real or floating-point values). In some definitions of syntax and parts of objects later in this book, we make specific reference to the type of value accepted in placeholders. When a string is required, any text inside a set of quotes suffices. You will encounter situations, however, in which the value type may get in the way of a smooth script step. For example, if a user enters a number into a form’s text input field, the browser stores that number as a string value type. If the script is to perform some arithmetic on that number, you must convert the string to a number before you can apply the value to any math operations. You see examples of this later in this lesson.
Variables Cooking up a dish according to a recipe in the kitchen has one advantage over cooking up some data in a program. In the kitchen, you follow recipe steps and work with real things: carrots, milk, or a salmon filet. A computer, on the other hand, follows a list of instructions to work with data. Even if the data represents something that looks real, such as the text entered into a form’s input field, once the value gets into the program, you can no longer reach out and touch it. In truth, the data that a program works with is merely a collection of bits (on and off states) in your computer’s memory. More specifically, data in a JavaScript-enhanced web page occupies parts of the computer’s memory set aside for exclusive use by the browser software. In the olden days, programmers had to know the numeric address in memory (RAM) where a value was stored to retrieve a copy of it for, say, some addition. Although the innards of a program have that level of complexity, programming languages such as JavaScript shield you from it.
110
Chapter 8: Programming Fundamentals, Part I
The most convenient way to work with data in a script is to first assign the data to a variable. It’s usually easier to think of a variable as a basket that holds information. How long the variable holds the information depends on a number of factors. But the instant a web page clears the window (or frame), any variables it knows about are discarded.
Creating variables You have a couple of ways to create a variable in JavaScript, but one way covers all cases properly. Use the var keyword, followed by the name you want to give that variable. Therefore, to declare a new variable called myAge, the JavaScript statement is var myAge;
That statement lets the browser know that you can use that variable later to hold information or to modify any of the data in that variable. To assign a value to a variable, use one of the assignment operators. The most common one by far is the equal sign. For example, if you want to assign a value to the myAge variable at the same time that you declare it (a combined process known as initializing the variable), use that operator in the same statement as the var keyword: var myAge = 45;
On the other hand, if you declare a variable in one statement and later want to assign a value to it, the sequence of statements is var myAge; myAge = 45;
Use the var keyword for declaration or initialization — typically only once for the life of any variable name in a document. A JavaScript variable can hold any value type. Unlike many other languages, you don’t have to tell JavaScript during variable declaration what type of value the variable will hold. In fact, the value type of a variable can change during the execution of a program. (This flexibility drives experienced programmers crazy because they’re accustomed to assigning both a data type and a value to a variable.)
Naming variables Choose the names you assign to variables with care. You’ll often find scripts that use vague variable names, such as single letters. Other than a few specific circumstances where using letters is a common practice (for example, using i as a counting variable in repeat loops in Chapter 9), you should use names that truly describe a variable’s contents. This practice can help you follow the state of your data through a long series of statements or jumps, especially for complex scripts. A number of restrictions help instill good practice in assigning names. First, you cannot use any reserved keyword as a variable name. That includes all keywords currently used by the language and all others held in reserve for future versions of JavaScript. The designers of JavaScript, however, cannot foresee every keyword that the language may need in the future. By using the kind of single words that currently appear in the list of reserved keywords (see Appendix C, on the CD-ROM), you always run a risk of a future conflict. To complicate matters, a variable name cannot contain space characters. Therefore, one-word variable names are fine. Should your description really benefit from more than one word, you can use one of
111
Part II: JavaScript Tutorial
two conventions to join multiple words as one. One convention is to place an underscore character between the words; the other is to start the combination word with a lowercase letter and capitalize the first letter of each subsequent word within the name — referred to as CamelCase or interCap format. Both of the following examples are valid variable names: my_age myAge
Our preference is for the second version; it is easier to type and easier to read. In fact, because of the potential conflict with future one-word keywords, using multiword combinations for variable names is a good idea. Multiword combinations are less likely to appear in the list of reserved words. Variable names have a couple of other important restrictions. Avoid all punctuation symbols except for the underscore character. Also, the first character of a variable name cannot be a numeral. If these restrictions sound familiar, it’s because they’re similar to those for HTML element identifiers described in Chapter 6.
Expressions and Evaluation Another concept closely related to the value and variable is expression evaluation — perhaps the most important concept in learning how to program a computer. We use expressions in our everyday language. Remember the theme song of ‘‘The Beverly Hillbillies’’?: Then one day he was shootin’ at some food And up through the ground came a-bubblin’ crude Oil, that is. Black gold. Texas tea. At the end of the song, you find four quite different references (crude, oil, black gold, and Texas tea). They all mean oil. They’re all expressions for oil. Say any one of them, and other people know what you mean. In our minds, we evaluate those expressions to mean one thing: oil. In programming, a variable always evaluates to its contents, or value. For example, after assigning a value to a variable, such as var myAge = 45;
any time the variable is used in a statement, its value (45) is automatically applied to whatever operation that statement calls. Therefore, if you’re 15 years my junior, I can assign a value to a variable representing your age based on the evaluated value of myAge: var yourAge = myAge – 15;
The variable, yourAge, evaluates to 30 the next time the script uses it. If the myAge value changes later in the script, the change has no link to the yourAge variable because myAge evaluated to 45 when it was used to assign a value to yourAge.
Expressions in scripts You probably didn’t recognize it at the time, but you have seen how expression evaluation came in handy in several scripts in previous chapters. Let’s look at one in particular — from
112
Chapter 8: Programming Fundamentals, Part I
Listing 5-6 — where a script writes dynamic text to the page as the page loads. Recall the second document.write() statement: document.write(" of " + navigator.appName + ".");
Testing JavaScript Evaluation You can begin experimenting with the way JavaScript evaluates expressions with the help of The Evaluator Jr. (see Figure 8-1), an HTML page you can find on the companion CD-ROM. (The Senior version is introduced in Chapter 4, ‘‘JavaScript Essentials.’’) Enter any JavaScript expression into the top text box, and either press Enter/Return or click the Evaluate button. FIGURE 8-1
The Evaluator Jr. for testing expression evaluation.
The Evaluator Jr. has 26 variables (lowercase a through z) predefined for you. Therefore, you can assign values to variables, test comparison operators, and even do math here. Using the age variable examples
continued
113
Part II: JavaScript Tutorial
continued from earlier in this chapter, type each of the following statements in the upper text box, and observe how each expression evaluates in the Results field. Be sure to observe case sensitivity in your entries. The trailing semicolons are optional in The Evaluator. a = a; b = b; a – a >
45; a – 15; b; b;
To start over, click the Reload/Refresh button.
The document.write() method (remember, JavaScript uses the term method to mean command) requires a parameter in the parentheses: the text string to be displayed on the web page. The parameter here consists of one expression that joins three distinct strings: " of " navigator.appName "."
The plus symbol is one of JavaScript’s ways of joining strings. Before JavaScript can display this line, it must perform some quick evaluations. The first evaluation is the value of the navigator.appName property. This property evaluates to a string of the name of your browser. With that expression safely evaluated to a string, JavaScript can finish the job of joining the three strings in the final evaluation. The evaluated string expression is what ultimately appears on the web page.
Expressions and variables As one more demonstration of the flexibility that expression evaluation offers, this section shows you a slightly different route to the document.write() statement. Rather than join those strings as the direct parameter to the document.write() method, you can gather the strings in a variable and then apply the variable to the document.write() method. Here’s how that sequence looks, as you simultaneously declare a new variable and assign it a value: var textToWrite = " of " + navigator.appName + "."; document.write(textToWrite);
This method works because the variable, textToWrite, evaluates to the combined string. The document.write() method accepts that string value and does its display job. As you read a script or try to work through a bug, pay special attention to how each expression (variable, statement, object property) evaluates. As you learn JavaScript (or any language), you will end up scratching your head from time to time because you haven’t stopped to examine how expressions evaluate when a particular kind of value is required in a script.
114
Chapter 8: Programming Fundamentals, Part I
Data Type Conversions We mentioned earlier that the type of data in an expression can trip up some script operations if the expected components of the operation are not of the right type. JavaScript tries its best to perform internal conversions to head off such problems, but JavaScript cannot read your mind. If your intentions differ from the way JavaScript treats the values, you won’t get the results you expect. A case in point is adding numbers that may be in the form of text strings. In a simple arithmetic statement that adds two numbers, you get the expected result: 3 + 3
// result = 6
But if one of those numbers is a string, JavaScript leans toward converting the other value to a string — thus turning the plus sign’s action from arithmetic addition to joining strings. Therefore, in the statement 3 + "3"
// result = "33"
the stringness of the second value prevails over the entire operation. The first value is automatically converted to a string, and the result joins the two strings. Try this yourself in The Evaluator Jr. If you take this progression one step further, look what happens when another number is added to the statement: 3 + 3 + "3"
// result = "63"
This might seem totally illogical, but there is logic behind this result. The expression is evaluated from left to right. The first plus operation works on two numbers, yielding a value of 6. But as the 6 is about to be added to the 3, JavaScript lets the stringness of the 3 rule. The 6 is converted to a string, and two string values are joined to yield 63. Most of your concern about data types will focus on performing math operations like the ones here. However, some object methods also require one or more parameters of particular data types. Although JavaScript provides numerous ways to convert data from one type to another, it is appropriate at this stage of the tutorial to introduce you to the two most common data conversions: string to number and number to string.
Converting strings to numbers As you saw in the preceding section, if a numeric value is stored as a string — as it is when entered into a form text field — your scripts may have difficulty applying that value to a math operation. The JavaScript language provides two built-in functions to convert string representations of numbers to true numbers: parseInt() and parseFloat(). There is a difference between integers and floating-point numbers in JavaScript. Integers are always whole numbers, with no decimal point or numbers to the right of a decimal. Floating-point numbers, on the other hand, have fractional values to the right of the decimal. By and large, JavaScript math operations don’t differentiate between integers and floating-point numbers: A number is a number. The only time you need to be cognizant of the difference is when a method parameter requires an integer because it can’t handle fractional values. For example, parameters to the scroll() method of a window require integer values of the numbers of pixels vertically and horizontally that you want to scroll the window. That’s because you can’t scroll a window a fraction of a pixel onscreen.
115
Part II: JavaScript Tutorial
To use either of these conversion functions, insert the string value you wish to convert as a parameter to the function. For example, look at the results of two different string values when passed through the parseInt() function: parseInt("42") parseInt("42.33")
// result = 42 // result = 42
Even though the second expression passes the string version of a floating-point number to the function, the value returned by the function is an integer. No rounding of the value occurs here (although other math functions can help with that if necessary). The decimal and everything to its right are simply stripped off. The parseFloat() function returns an integer if it can; otherwise, it returns a floating-point number, as follows: parseFloat("42") parseFloat("42.33")
// result = 42 // result = 42.33
Because these two conversion functions evaluate to their results, you simply insert the entire function wherever you need a string value converted to a number. Therefore, modifying an earlier example in which one of three values was a string, the complete expression can evaluate to the desired result: 3 + 3 + parseInt("3")
// result = 9
Converting numbers to strings You’ll have less need for converting a number to its string equivalent than the other way around. As you saw in the previous section, JavaScript gravitates toward strings when faced with an expression containing mixed data types. Even so, it is good practice to perform data type conversions explicitly in your code to prevent any potential ambiguity. The simplest way to convert a number to a string is to take advantage of JavaScript’s string tendencies in addition operations. By adding an empty string to a number, you convert the number to its string equivalent: ("" + 2500) ("" + 2500).length
// result = "2500" // result = 4
In the second example, you can see the power of expression evaluation at work. The parentheses force the conversion of the number to a string. A string is a JavaScript object that has properties associated with it. One of those properties is the length property, which evaluates to the number of characters in the string. Therefore, the length of the string "2500" is 4. Note that the length value is a number, not a string.
Operators You will use lots of operators in expressions. Earlier, you used the equal sign (=) as an assignment operator to assign a value to a variable. In the preceding examples with strings, you used the plus symbol (+) to join two strings. An operator generally performs some kind of calculation (operation) or comparison with two values (the value on each side of an operator is called an operand) to reach a third value. This lesson briefly describes two categories of operators: arithmetic and comparison. Chapter 22, ‘‘JavaScript Operators,’’ covers many more operators, but after you understand the basics here, the others are easier to grasp.
116
Chapter 8: Programming Fundamentals, Part I
Arithmetic operators It may seem odd to talk about text strings in the context of arithmetic operators, but you have already seen the special case of the plus (+) operator when one or more of the operands is a string. The plus operator instructs JavaScript to concatenate (pronounced ‘‘kon-KAT-en-eight’’), or join, two strings together precisely where you place the operator. The string concatenation operator doesn’t know about words and spaces, so the programmer must make sure that any two strings to be joined have the proper word spacing as part of the strings, even if that means adding a space: firstName = "John"; lastName = "Doe"; fullName = firstName + " " + lastName;
JavaScript uses the same plus operator for arithmetic addition. When both operands are numbers, JavaScript knows to treat the expression as an arithmetic addition rather than a string concatenation. The standard math operators for addition, subtraction, multiplication, and division (+, -, *, /) are built into JavaScript.
Comparison operators Another category of operator helps you compare values in scripts — whether two values are the same, for example. These kinds of comparisons return a value of the Boolean type: true or false. Table 8-2 lists the comparison operators. The operator that tests whether two items are equal consists of a pair of equal signs to distinguish it from the single-equal-sign assignment operator.
TABLE 8-2
JavaScript Comparison Operators Symbol
==
Description
Equals
!=
Does not equal
>
Is greater than
>=
Is greater than or equal to
= height)");
The willItFit() function takes two parameters; the body of the function defines two local variables (sx and sy) and then returns a Boolean value of true if the incoming parameters are smaller than the local variables. In traditional form, this function is defined as follows: function willItFit(width, height) { var sx = screen.availWidth; var sy = screen.availHeight; return (sx >= width && sy >= height); }
When this function exists in the browser’s memory, you can invoke it like any other function: if (willItFit(400,500)) { // statements to load image }
One last function creation format is available in IE4+, NN4+, Moz, and other W3C DOM browsers. This advanced technique, called a lambda expression, provides a shortcut for creating a reference to an anonymous function (truly anonymous because the function has no name that you can reference later). The common application of this technique is to assign function references to event handlers when an event object also must be passed. The following is an example of how to assign an anonymous function to an onchange event handler for a form control: document.forms[0].age.onchange = function(event) {isNumber(document.forms[0].age)}
Because an anonymous function evaluates to a reference to a function object, you can use either form of anonymous function in situations where a function reference is called for, including parameters of methods or other functions.
439
Part III: JavaScript Core Language Reference functionObject
Nesting functions Modern browsers also provide for nesting functions inside one another. In the absence of nested functions, each function definition is defined at the global level, whereby every function is exposed and available to all other script code. With nested functions, you can encapsulate the exposure of a function inside another and make that nested function private to the enclosing function. Of course, we don’t recommend reusing function names with this technique, although you can create nested functions with the same name inside multiple global-level functions, as the following skeletal structure shows: function outerA() { // statements function innerA() { // statements } // statements } function outerB() { // statements function innerA() { // statements } function innerB() { // statements } // statements }
A good time to apply a nested function is when a sequence of statements needs to be invoked in multiple places within a large function, and those statements have meaning only within the context of the larger function. In other words, rather than break out the repeated sequence as a separate global function, you keep it all within the scope of the larger function.
Note The premise behind nesting a function is to isolate the function and make it private from the overall script. This results in cleaner script code because nothing is exposed globally without a good reason. As an admittedly strange analogy, the water heater in your house could feasibly be placed outside (global), but it’s generally safer and more organized to place it inside (local). Unlike your mailbox, which must interact with the outside (global) world, your water heater plays an internal (local) role, and therefore lives inside your house. And after all, we don’t want to make our home’s hot water globally available.
You can access a nested function only from statements in its containing function (but in any order). Moreover, all variables defined in the outer function (including parameter variables) are accessible to the inner function; but variables defined in an inner function are not accessible to the outer function. See the section ‘‘Variable scope: Globals and locals’’ later in this chapter for details on how variables are visible to various components of a script.
440
Chapter 23: Function Objects and Custom Objects functionObject.arguments()
Function parameters The function definition requires a set of parentheses after the functionName. If the function does not rely on any information arriving with it when invoked, the parentheses can be empty. But when some kind of data is arriving with a call to the function, you need to assign names to each parameter. Virtually any kind of value can be a parameter: strings, numbers, Boolean operators, and even complete object references such as a form or form element. Choose names for these variables that help you remember the content of those values; also, avoid reusing existing object names as variable names because it’s easy to get confused when objects and variables with the same name appear in the same statements. You must avoid using JavaScript keywords (including the reserved words listed in Appendix C, on the CD) and any global variable name defined elsewhere in your script. (See more about global variables in the following sections.) JavaScript is forgiving about matching the number of parameters in the function definition with the number of parameters passed along from the calling statement. If you define a function with three parameters and the calling statement specifies only two, the third parameter variable value in that function is assigned a null value. For example: function saveWinners(first, second, third) { // statements } oneFunction("George","Gracie");
In the preceding example, the values of first and second inside the function are "George" and "Gracie", respectively; the value of third is null. At the opposite end of the spectrum, JavaScript also doesn’t balk if you send more parameters from the calling statement than the number of parameter variables specified in the function definition. In fact, the language includes a mechanism — the arguments property — that you can add to your function to gather any extraneous parameters that should read your function.
Properties arguments (deprecated) Value: Array of arguments
Read-Only
Compatibility: WinIE4+, MacIE4+, NN3+, Moz+, Safari+, Chrome+ When a function receives parameter values from the statement that invoked the function, those parameter values are silently assigned to the arguments property of the function object. This property is an array of the values, with each parameter value assigned to a zero-based index entry in the array — whether or not parameters are defined for it. You can find out how many parameters are sent by extracting functionName.arguments.length. For example, if four parameters are passed, functionName.arguments.length returns 4. Then, you can use array notation (functionName.arguments[i]) to extract the values of any parameter(s) you want. Theoretically, you never have to define parameter variables for your functions because you can extract the desired arguments array entry instead. Well-chosen parameter variable names, however, are much more readable, so we recommend them over the arguments property in most cases. But you may run into situations in which a single function definition needs to handle multiple calls to the function
441
Part III: JavaScript Core Language Reference functionObject.arity() when each call may have a different number of parameters. The function knows how to handle any arguments over and above the ones given names as parameter variables.
Note It is necessary in some cases to create a function that deliberately accepts a varied number of arguments, in which case the arguments property is the only way to access and process the arguments. For example, if you wanted to create a function that averages test scores, there’s a good chance the number of scores may vary, in which case you would write the function so that it loops through the arguments array, adding up the scores as it carries out the calculation.
Example See Listings 23-1 and 23-2 for a demonstration of both the arguments and caller properties.
arity (deprecated) Value: Integer
Read-Only
Compatibility: WinIE−, MacIE−, NN4+, Moz−, Safari−, Chrome+ See the discussion of the length property later in this chapter.
caller Value: Function object reference
Read-Only
Compatibility: WinIE4+, MacIE4+, NN3+, Moz+, Safari−, Chrome+ When one function invokes another, a chain is established between the two, primarily so that a returned value knows where to go. Therefore, a function invoked by another maintains a reference to the function that called it. Such information is automatically stored in a Function object as the caller property. This relationship reminds me a bit of a subwindow’s opener property, which points to the window or frame responsible for the subwindow’s creation. The value is valid only while the called function is running at the request of another function; when a function isn’t running, its caller property is null. The value of the caller property is a reference to a Function object, so you can inspect its arguments and caller properties (in case it was called by yet another function). Thus, a function can look back at a calling function to see what values it was passed. The functionName.caller property reveals the contents of an entire function definition if the current function was called from another function (including an event handler). If the call for a function comes from a regular JavaScript statement not originating inside a function, the functionName.caller property is null.
Example To help you grasp all that these two properties yield, study Listing 23-1.
Note The function to assign event handlers throughout the code in this chapter and much of the book is addEvent(), a cross-browser event handler explained in detail in Chapter 32, ‘‘Event Objects.’’
442
Chapter 23: Function Objects and Custom Objects functionObject.caller() LISTING 23-1
A Function’s arguments and caller Properties HTML: jsb-23-01.html Function call information Function call information
JavaScript: jsb-23-01.js // initialize when the page has loaded addEvent(window, "load", showArgCaller); var newElem; var newText; function showArgCaller () { // Call the hansel function twice: once directly, // second indirectly from the gretel function. hansel(1, "two", 3); gretel(4, "five", 6, "seven"); } function hansel(x,y) { var args = hansel.arguments; var placeHolderElement = document.getElementById("placeHolder"); if (placeHolderElement) { // a header line newElem = document.createElement("h3"); newElem.className = "objProperty"; newText = document.createTextNode("The caller and the arguments"); // insert the 1st line (text node) into the new h3 newElem.appendChild(newText); // insert the completed h3 into placeholder
continued
443
Part III: JavaScript Core Language Reference functionObject.caller() LISTING 23-1
(continued)
placeHolderElement.appendChild(newElem); // the next line is the caller newElem = document.createElement("div"); newElem.className = "objProperty"; newText = document.createTextNode("hansel.caller is " + hansel.caller); newElem.appendChild(newText); placeHolderElement.appendChild(newElem); // the next line is the number or arguments newElem = document.createElement("div"); newElem.className = "objProperty"; newText = document.createTextNode("hansel.arguments.length is " + hansel.arguments.length); newElem.appendChild(newText); placeHolderElement.appendChild(newElem); // the rest of the lines are the arguments for (var i = 0; i < args.length; i++) { newElem = document.createElement("div"); newElem.className = "objProperty"; newText = document.createTextNode("argument " + i + " is " + args[i]); newElem.appendChild(newText); placeHolderElement.appendChild(newElem); } } } function gretel(x,y,z) { today = new Date(); thisYear = today.getFullYear(); hansel(x,y,z,thisYear); }
When you load this page, the following JavaScript results appear in the browser window: The caller and the arguments hansel.caller is function showArgCaller() { hansel(1, "two", 3); gretel(4, "five", 6, "seven"); } hansel.arguments.length is 3 argument 0 is 1 argument 1 is two argument 2 is 3 The caller and the arguments
444
Chapter 23: Function Objects and Custom Objects functionObject.prototype hansel.caller is function gretel(x, y, z) { today = new Date(); thisYear = today.getFullYear(); hansel(x,y,z,thisYear); } hansel.arguments.length is 4 argument 0 is 4 argument 1 is five argument 2 is 6 argument 3 is 2010 (or whatever the current year is)
As the document loads, the hansel() function is called directly in the onload event handler in the external script. It passes three arguments, even though the hansel() function defines only two. The hansel.arguments property picks up all three arguments just the same. Then the onload event handler invokes the gretel() function, which, in turn, calls hansel() again. But when gretel() makes the call, it passes four parameters. The gretel() function picks up only three of the four arguments sent by the calling statement. It also inserts another value from its own calculations as an extra parameter to be sent to hansel(). The hansel.caller property reveals the entire content of the gretel() function, whereas hansel.arguments picks up all four parameters, including the year value introduced by the gretel() function.
constructor (See object.constructor later in this chapter.)
length Value: Integer
Read-Only
Compatibility: WinIE4+, MacIE4+, NN4+, Moz+, Safari+ As the arguments property of a function proves, JavaScript is very forgiving about matching the number of parameters passed to a function with the number of parameter variables defined for the function. But a script can examine the length property of a Function object to see precisely how many parameter variables are defined for the function. A reference to the property starts with the function name representing the object. For example, consider the following function definition shell: function identify(name, rank, serialNum) { // ... }
A script statement anywhere outside of the function can read the number of parameters with the reference: identify.length
The value of the property in the preceding example is 3. The length property supercedes the NN-only arity property.
prototype (See Chapter 18.)
445
Part III: JavaScript Core Language Reference functionObject.apply()
Methods apply([thisObj[, argumentsArray]]) call([thisObj[, arg1[, arg2[, . . . argN]]]]) Returns: Nothing Compatibility: WinIE5.5+, MacIE−, NN6+, Moz+, Safari+, Chrome+ The apply() and call() methods of a Function object invoke the function. This may seem redundant to the normal way in which script statements invoke functions by simply naming the function, following it with parentheses, passing parameters, and so on. The difference with these methods is that you can invoke the function through the apply() and call() methods using only a reference to the function. For example, if your script defines a function through the new Function() constructor (or other anonymous shortcut supported by the browser), you receive a reference to the function as a result of the constructor. To invoke the function later using only that reference (presumably preserved in a global variable), use either the apply() or call() method. Both of these methods achieve the same result, but choosing one method over the other depends on the form in which the function’s parameters are conveyed (more about that in a moment). The first parameter of both methods is a reference to the object that the function treats as the current object. For garden-variety functions defined in your script, use the keyword this, which means that the function’s context becomes the current object (just like a regular function). In fact, if there are no parameters to be sent to the function, you can omit parameters to both methods altogether. The object reference comes into play when the function being invoked is one that is normally defined as a method to a custom object. (Some of these concepts are covered later in this chapter, so you may need to return here after you are familiar with custom objects.)
Example Consider the following code that generates a custom object and assigns a method to the object to display an alert about properties of the object: // function to be invoked as a method from a ‘car’ object function showCar() { alert(this.make + " : " + this.color); } // ‘car’ object constructor function function Car(make, color) { this.make = make; this.color = color; this.show = showCar; } // create instance of a ‘car’ object var myCar = new Car("Ford", "blue");
The normal way of getting the myCar object to display an alert about its properties is: myCar.show();
446
Chapter 23: Function Objects and Custom Objects functionObject.valueOf() At that point, the showCar() function runs, picking up the current Car object as the context for the this references in the function. In other words, when the showCar() function runs as a method of the object, the function treats the object as the current object. With the call() or apply() methods, however, you don’t have to bind the showCar() function to the myCar object. You can omit the statement in the Car() constructor that assigns the showCar function to a method name for the object. Instead, a script can invoke the showCar() method and instruct it to treat myCar as the current object: showCar.call(myCar);
The showCar() function operates just as before, and the object reference in the call() method’s first parameter slot is treated as the current object for the showCar() function. As for succeeding parameters, the apply() method’s second parameter is an array of values to be passed as parameters to the current function. The order of the values must match the order of parameter variables defined for the function. The call() method, on the other hand, enables you to pass individual parameters in a comma-delimited list. Your choice depends on how the parameters are carried along in your script. If they’re already in array form, use the apply() method; otherwise, use the call() method. The (ECMA) recommended way to invoke a function through this mechanism when no parameters need to be passed is via the call() method.
Note Remember, ECMA is the standards organization that oversees the official JavaScript language standard, which is formally known as ECMAScript. ECMAScript is the language specification, whereas JavaScript is an actual implementation.
toString() valueOf() Returns: String Compatibility: WinIE4+, MacIE4+, NN4+, Moz+, Safari+ Scripts rarely, if ever, summon the toString() and valueOf() methods of a Function object. These methods work internally to allow debugging scripts to display a string version of the function definition. For example, when you enter the name of a function defined in The Evaluator (see Chapter 4) into the top text box, JavaScript automatically converts the function to a string so that its value can be displayed in the Results box. Using these methods or parsing the text they return has little, if any, practical application.
Function Application Notes Understanding the ins and outs of JavaScript functions is the key to successful scripting, especially for complex applications. Additional topics covered in this section include the ways to invoke functions, variable scope in and around functions, recursion, and the design of reusable functions.
Invoking functions A function doesn’t perform any work until a script calls it by name or reference. Scripts invoke functions (that is, get functions to do something) through four routes: document object event
447
Part III: JavaScript Core Language Reference
handlers; JavaScript statements; href attributes pointing to a javascript: URL; and the more modern call() and apply() methods of the Function object. The one approach not yet discussed at length in this book is the javascript: URL (some say pseudo-URL). Several HTML tags have href attributes that normally point to Internet URLs for navigating to another page or loading a MIME file that requires a helper application or plug-in. These HTML tags are usually tags for clickable objects, such as links and client-side image map areas. A JavaScript-enabled browser has a special built-in URL pseudo-protocol — javascript: — that lets the href attribute point to a JavaScript function or method rather than to a URL on the Net. For example, it is common practice to use the javascript: URL to change the contents of two frames from a single link. Because the href attribute is designed to point to only a single URL, you’d be out of luck if it weren’t for the convenient way that JavaScript gives you access to multiframe navigation. You implement multiframe navigation by writing a function that sets the location.href properties of the two frames; then invoke that function from the href attribute. The following example shows what the script may look like: function loadPages() { parent.frames[1].location.href = "page2.html"; parent.frames[2].location.href = "instrux2.html"; } // ... Next
These kinds of function invocations can include parameters, and the functions can do anything you want. One potential side effect to watch out for occurs when the function returns a value (perhaps the function is also invoked from other script locations where a returned value is expected). Because the href attribute sets the target window to whatever the attribute evaluates to, the returned value is assigned to the target window — probably not what you want. To prevent the assignment of a returned value to the href attribute, prefix the function call with the void operator:
If you don’t want the href attribute to do anything (that is, you want to let the onclick event handler do all the work), assign a blank function after the operator:
Experienced programmers of many other languages recognize this operator as a way of indicating that no values are returned from a function or procedure. The operator has that precise functionality here, but in a nontraditional location.
Variable scope: Globals and locals A variable can have two scopes in JavaScript. As you might expect, any variable initialized within the main flow of a script (not inside a function) is a global variable, in that any statement in the same document’s script can access it by name. You can, however, also initialize variables inside a function (in a var statement) so the variable name applies only to statements inside that function; the scope is local to the function, so they are local variables. By limiting the scope of the variable to a single function, you can reuse the same variable name in multiple functions, thereby enabling the variables to carry
448
Chapter 23: Function Objects and Custom Objects
very different information in each function. Keep in mind that when you declare a variable inside of a function without the var keyword, you are creating a global variable and not a local variable. Listing 23-2 demonstrates the various possibilities. LISTING 23-2
Variable Scope Workbench Page HTML: jsb-23-02.html Variable scope Variable scope Charlie Brown has a global dog (Snoopy), a local dog (Gromit), a global toy (Gumby), and a local toy (Pokey).
JavaScript: jsb-23-02.js // initialize when the page has loaded addEvent(window, "load", testValues); var newElem; var newText; var toyGlobal = "Gumby"; var aBoy = "Charlie Brown"; var hisDog = "Snoopy"; function showLocal() { var toyLocal = "Pokey"; return toyLocal; } function showGlobal() { newElem = document.createElement("div"); newElem.className = "objProperty"; newText = document.createTextNode("Global version of hisDog is intact: " + hisDog); // just picked up a global variable value instead // of the local variable in the calling function
continued
449
Part III: JavaScript Core Language Reference
LISTING 23-2
(continued)
newElem.appendChild(newText); placeHolderElement.appendChild(newElem); } function testValues() { // Dangerous ground here -- declaring a global variable in a function placeHolderElement = document.getElementById("placeHolder"); // Now declare the local variable var hisDog = "Gromit"; // initializes local version of "hisDog" if (placeHolderElement) { newElem = document.createElement("div"); newElem.className = "objProperty"; newText = document.createTextNode("aBoy is: " + aBoy); // just picked up a global variable value newElem.appendChild(newText); placeHolderElement.appendChild(newElem); newElem = document.createElement("div"); newElem.className = "objProperty"; newText = document.createTextNode("His toyGlobal is " + toyGlobal); newElem.appendChild(newText); // just picked up another global variable value placeHolderElement.appendChild(newElem); // Do not bother with toyLocal here because it will throw undefined newElem = document.createElement("div"); newElem.className = "objProperty"; newText = document.createTextNode( "toyLocal value returned from the showLocal function is: " + showLocal() ); newElem.appendChild(newText); placeHolderElement.appendChild(newElem); newElem = document.createElement("div"); newElem.className = "objProperty"; newText = document.createTextNode("Local version of hisDog is: " + hisDog); newElem.appendChild(newText); // just picked up another global variable value placeHolderElement.appendChild(newElem); // now call another function that does not set the variable hisDog // and display the value. we’ll see that the global value is intact showGlobal(); } }
450
Chapter 23: Function Objects and Custom Objects
In this page, you define a number of variables — some global, others local — that are spread out in the JavaScript file. When you load this page, it runs the testValues() function, which accounts for the current values of all the variable names. The script then follows up with at least one value extraction that was masked in the function. The results of the JavaScript look like this: aBoy is: Charlie Brown His toyGlobal is Gumby toyLocal value returned from the showLocal function is: Pokey Local version of hisDog is: Gromit Global version of hisDog is intact: Snoopy
Examine the variable initialization throughout the JavaScript file. In the beginning of the script there are several lines of code that are not contained within a function; this is the immediate execution section. In that section you define the first variable (toyGlobal) as a global style outside of any function definition. The var keyword for the global variable is optional but often helpful for enabling you to see at a glance where you initialize your variables. You also define two more global variables: aBoy and hisDog. You then create two short functions. The showLocal() function defines a variable (toyLocal) that only statements in it can use. The showGlobal() function defines a function that simply displays the value of a variable (more on which variable in just a bit). There is also a testValues() function that is the onload event handler. The first thing you’ll notice is a variable (placeHolderElement) declared without the var keyword. Since placeHolderElement is declared within a function, it is a global variable. The testValues() function calls the showGlobal() function that uses the placeHolderElement variable. Why wasn’t this variable declaration made in the immediate execution section of the script? The placeHolderElement variable is a reference to one of the elements on the HTML page that uses these functions. The placeHolderElement variable cannot successfully reference the element until the page is fully loaded. The only way to guarantee that the page is loaded before you declare the variable is to place the variable declaration within the onload event handler. Since the testValues() function is the onload event handler, the only way to make this variable available to other functions is to declare it here globally. Also inside the testValues() function (for purposes of demonstration), you reuse the hisDog variable name. By initializing hisDog with the var statement inside the function, you tell JavaScript to create a separate local variable whose scope is only within the function. This initialization does not disturb the global variable of the same name. It can, however, make things confusing for you as the script author. Statements in the testValues() function attempt to collect the values of variables scattered around the JavaScript file. Even from within this function, JavaScript has no problem extracting global variables directly, including the one defined in the immediate execution section. But JavaScript cannot get the local variable defined in the showLocal() function; that toyLocal variable is private to its own function. If you try to reference the showLocal() function’s variable value from within the showGlobal() function, you will get an error message saying that the variable name is not defined. In the eyes of everyone else outside of the showLocal() function, that’s true. If you really need that value, you can have the function return the value to a calling statement, as you do in the testValues() function. At the beginning of the testValues() function, the script reads the aBoy global value without a hitch. But because you initialized a separate version of hisDog inside that function, only the localized version is available to the testValues() function. If you reassign a global variable name inside a function, you cannot access the global version from inside that function.
451
Part III: JavaScript Core Language Reference
As proof that the global variable — whose name was reused inside the testValues() function — remains untouched, the testValues() function calls the showGlobal() function. The showGlobal() function displays the value of the hisDog variable. Since we’re no longer inside the testValues() function, we see the value of the global variable hisDog. Charlie Brown and his dog, Snoopy, are united. A benefit of this variable-scoping scheme is that you can reuse throwaway variable names in any function you like. For example, you can use the i loop counting variable in every function that employs loops. (In fact, you can reuse it in multiple for loops of the same function because the for loop reinitializes the value at the start of the loop.) If you pass parameters to a function, you can assign the same names to those parameter variables to aid in consistency. For example, a common practice is to pass an entire form object reference as a parameter to a function (using a this.form parameter in the event handler). For every function that catches one of these objects, you can use the variable name form in the parameter: function doSomething(form) { // statements } // ...
If five buttons on your page pass their form objects as parameters to five different functions, each function can assign form (or whatever you want to use) to that parameter value. We recommend reusing variable names only for these throwaway variables. In this case, the variables are all local to functions, so the possibility of a mix-up with global variables does not exist. But the thought of reusing a global variable name as, say, a special case inside a function sends shivers up our spines. Such a tactic is doomed to cause confusion and error.
Caution Reusing a global variable name locally is one of the most subtle and therefore difficult bugs to find in JavaScript code. The local variable ends up temporarily hiding the global variable without making any effort to let you know. Just do yourself a favor and make sure you don’t reuse a global variable name as a local variable in a function. In the same vein, declaring a global variable within a function may also create bugs that are difficult to find in JavaScript code.
Some programmers devise naming conventions to avoid reusing global variables as local variables. A popular scheme puts a lowercase g in front of any global variable name. In the example from Listing 23-2, you could have named the global variables: gToyGlobal gABoy gHisDog gPlaceHolderElement
Then, if you define local variables, don’t use the leading g. A similar scheme involves using an underscore character (_) global instead of a g in front of global variable names. In the example from Listing 23-2, you could have named the local variables: _ToyLocal _HisDog
452
Chapter 23: Function Objects and Custom Objects
Any scheme you employ to prevent the reuse of variable names in different scopes is fine, as long as it does the job. The same can be said of any scheme that clearly identifies global variables. In a multiframe or multiwindow environment, your scripts can also access global variables from any other document currently loaded into the browser. For details about this level of access, see Chapter 27, ‘‘Window and Frame Objects.’’ Variable scoping rules apply equally to nested functions. Any variables defined in an outer function (including parameter variables) are exposed to all functions nested inside. But if you define a new local variable inside a nested function, that variable is not available to the outer function. Instead, you can return a value from the nested function to the statement in the outer function that invokes the nested function.
Parameter variables When a function receives data in the form of parameters, remember that the values may be copies of the data (in the case of run-of-the-mill data values) or references to real objects (such as a form object). In the latter case, you can change the object’s modifiable properties in the function when the function receives the object as a parameter, as shown in the following example: function validateCountry(form) { if (form.country.value == "") { form.country.value = "USA"; } }
Therefore, whenever you pass an object reference as a function parameter, be aware that the changes you make to an object you’ve passed into a function affect the real object. As a matter of style, if our function needs to extract properties, or results of methods, from passed data (such as object properties or string substrings), we like to do that at the start of the function. We initialize as many variables as needed for each piece of data used later in the function. This task enables us to assign meaningful names to the data chunks, rather than rely on potentially long references within the working part of the function (such as using a variable like inputStr instead of form.entry.value). Today’s machines are so incredibly fast that we don’t really need to do this for machine speed; we’re doing it for human speed — the code is now more readable and maintainable. Here’s a quick example: function updateContactInfo(form) { var firstName = form.firstname.value; // or the preferred way: var lastName = document.getElementById("lastname").value; var address1 = document.getElementById("addr1").value; var address2 = document.getElementById("addr2").value; var phone = document.getElementById("phone").value; var email = document.getElementById("email").value; // Process contact info using local variables }
453
Part III: JavaScript Core Language Reference
Notice in this example how the form field information is first stored in local variables, which are then used to carry out the hypothetical updating of contact information. Throughout the remainder of the function you can use the local variables instead of the longer and less wieldy form fields.
Recursion in functions In what may come as a strange surprise, it is possible for functions to call themselves — a process known as recursion. The classic example of programmed recursion is the calculation of the factorial (the factorial for a value of 4 is 4 * 3 * 2 * 1), shown in Listing 23-3. In the third line of this function, the statement calls itself, passing along a parameter of the next lower value of n. As this function executes, diving ever deeper into itself, JavaScript watches intermediate values and performs the final evaluations of the nested expressions. If designed properly, a recursive function eventually stops calling itself, and the program flow eventually returns back to the original function call. Recursive functions are dangerous in the sense that they can easily fall into an infinite state (popularly called an infinite loop). For this reason, it is very important that you test them carefully. In particular, make sure that the recursion is finite: that a limit exists for the number of times it can recurse. In the case of Listing 23-3, that limit is the initial value of n. Failure to watch out for this limit may cause the recursion to overpower the limits of the browser’s memory and even lead to a crash. LISTING 23-3
A JavaScript Function Utilizing Recursion function factorial(n) { if (n > 0) { return n * (factorial(n-1)); } else { return 1; } }
Turning functions into libraries As you start writing functions for your scripts, be on the lookout for ways to make functions generalizable (written so that you can reuse the function in other instances, regardless of the object structure of the page). The likeliest candidates for this kind of treatment are functions that perform specific kinds of validation checks (see examples in Chapter 46, ‘‘Data-Entry Validation,’’ on the CD-ROM), data conversions, or iterative math problems. To make a function generalizable, don’t let it make any references to specific objects by name. Object names generally change from document to document. Instead, write the function so that it accepts a named object as a parameter. For example, if you write a function that accepts a text object as its parameter, the function can extract the object’s data or invoke its methods without knowing anything about its enclosing form or name. Look again, for example, at the factorial() function, but now as part of an entire document in Listing 23-4.
454
Chapter 23: Function Objects and Custom Objects
LISTING 23-4
Calling a Generalizable Function HTML: jsb-23-04.html Variable Scope Trials Variable Scope Trials
Enter an input value: Results:
JavaScript: jsb-23-04.js // initialize when the page has loaded addEvent(window, "load", initialize); function initialize() { // intercept form submission addEvent(document.getElementById("theForm"), "submit", calcFactorial); } function calcFactorial(evt) { // consolidate event handling if (!evt) evt = window.event; // plug transformed input to output field var oInput = document.getElementById("input"); var oOutput = document.getElementById("output");
continued
455
Part III: JavaScript Core Language Reference
LISTING 23-4
(continued)
// if they both exist if (oInput && oOutput) { oOutput.value = factorial(oInput.value); } // cancel form submission // W3C DOM method (hide from IE) if (evt.preventDefault) evt.preventDefault(); // IE method return false; } function factorial(n) { if (n > 0) { return n * (factorial(n - 1)); } else { return 1; } }
This function is designed to be generalizable, accepting only the input value (n) as a parameter. In the form, the onsubmit event handler sends only the input value from one of the form’s fields to the factorial() function. The returned value is assigned to the output field of the form. The factorial() function is totally ignorant about forms, fields, or buttons in this document. If you need this function in another script, you can copy and paste it into that script knowing that it has been pre-tested. Any generalizable function may be part of your personal library of scripts — from which you can borrow — and save time in future scripting tasks. You cannot always generalize a function. Somewhere along the line in your scripts, you will have to have references to JavaScript or custom objects. But if you find that you’re frequently writing functions that perform the same kind of actions, see how you can generalize the code and put the results in your library of ready-made functions. You should also consider placing these reusable library functions in an external .js library file, as you’ve seen us do in this chapter and in others. You can also see Chapter 4 for details on this convenient way to share utility functions among many documents.
Making sense of closures A topic that has confused many an aspiring scripter is closures, which may enter the picture when you declare a function within another function. At the core of JavaScript, closures refer to the fact that you can keep a local variable defined in a function alive even after the function has executed — which normally signals the end of life for a local variable. That’s right, it’s possible for a function to return
456
Chapter 23: Function Objects and Custom Objects
and its local variables to go on living like some kind of strange zombie data. How is this possible? Take a look at an example: function countMe() { var count = 1; var showCount = function() { alert(count); } count++; return showCount; }
The unusual thing to note about this code is how the inner function assigned to the showCount variable is returned by the function. When you call the countMe() function, you receive a reference to the inner function that displays the count variable value. That wouldn’t be a problem, except for the fact that the inner function acts on a variable (count) that is local to the countMe() function. To see the closure come to life, take a look at this code that calls the countMe() function: var countamatic = countMe(); countamatic();
The first line calls the countMe() function, which results in the local count variable being created, and a reference to the inner function being passed out and stored in the countamatic variable. The local variable count is also incremented within the countMe() function. Without knowing about closures, you would clearly be in some serious gray area at this point because the countamatic() function defined in the first line is now set to display the value of a variable that is clearly out of scope. But JavaScript works a miracle by keeping the count variable alive in a closure and still allowing the countamatic() function to access it. Thus, the second statement displays an alert with the number 2 in it. If closures still seem a bit mysterious, just remember that a potential closure is created any time you specify a function within another function. You really only take advantage of a closure when you pass an inner function reference outside the scope of the function in which it is defined. Okay, so closures reveal a sneaky way to manipulate scope in JavaScript, but what good are they? Closures are gaining a great deal of usage in Ajax applications because Ajax programming often uses them to work around inherent limitations in how you normally use the this keyword.
Cross-Reference For more on Ajax, see Chapter 39, ‘‘Ajax, E4X, and XML.’’
Although we could just pawn everything closure-related off on Ajax, we can demonstrate a simple but practical application of how closures can help you carry out the seemingly impossible. Consider the scenario where you want to set a timer that calls a function after an interval of time has elapsed. You may be thinking: No problem — just create a function and pass its reference to the setTimeout() function. End of story. What we didn’t mention is that you need to pass a couple of parameters to the function. See the problem? Unless you design with anonymous functions, there is no mechanism for using parameters when you pass a function reference to another function, as in specifying a timer event handler when
457
Part III: JavaScript Core Language Reference
calling the setTimeout() function. Now take a look at this code that uses closures to circumvent the problem: function wakeupCaller(name, roomnum) { return ( function() { alert("Call " + name + " in room #" + roomnum + "."); } ); }
By placing a zero-param function within a parameterized function, you now have the ingredients for a timer handler that can accept parameters. The next step is to create an actual function reference that uses the closure: var wakeWilson = wakeupCaller("Mr. Wilson", 515);
At this point, you’ve passed parameters to a function and received a zero-param function reference in return, which can then be passed along to the setTimeout() function: setTimeout(wakeWilson, 600000);
Thanks to closures, Mr. Wilson will now get his wake up call!
Caution Before you dive into closures and begin exploiting them in all of your code, let us caution you that they can result in some tricky bugs when used incorrectly. Extensive use of closures involving references to DOM objects can also cause memory leaks (gradual increase of memory used by the browser) if the objects are not disposed of (that is, set to null) when they are no longer needed. Definitely spend the time to explore closures in more detail before you get too wild with them.
Creating Your Own Objects with Object-Oriented JavaScript In all the previous chapters of this book, you’ve seen how conveniently the browser document object models organize all the information about the browser window and its document. More specifically, you learned how to use standard objects as a means of accessing different aspects of the browser window and document. What may not be obvious from the scripting you’ve done so far is that JavaScript enables you to create your own objects in memory — objects with properties and methods that you define. These objects are not user-interface elements on the page, but rather the kinds of objects that may contain data and script functions (behaving as methods) whose results the user can see displayed in the browser window. You actually had a preview of this power in the discussion about arrays (Chapter 18, ‘‘The Array Object’’). An array, you recall, is an ordered collection of data. An object typically contains different kinds of data. It doesn’t have to be an ordered collection of data — although your scripts can
458
Chapter 23: Function Objects and Custom Objects
use objects in constructions that strongly resemble arrays. Moreover, you can attach any number of custom functions as methods for that object. You are in total control of the object’s structure, data, and behavior. The practice of employing custom objects in your JavaScript code is known as object-oriented programming, or OO programming for short. OO has been around a long time and has been used to great success in other programming languages such as C++ and Java. However, the scripted nature of JavaScript has caused OO to catch on a bit more slowly in the JavaScript world. Even so, support for custom objects is a standard part of modern JavaScript-enabled browsers and is something you should consider taking advantage of whenever prudent.
Note To split hairs, technically, we have to clarify that JavaScript isn’t truly an object-oriented language in a strict sense. Instead, JavaScript is considered an object-based language. The difference between object-oriented and object-based is significant and has to do with how objects can be extended. Even so, conceptually, JavaScript’s support of objects is enough akin to true OO languages that it’s not unreasonable to discuss JavaScript in OO terms. You learn about some of the specific object features that allow JavaScript to approach OO languages later in the chapter. What’s of further interest is that ECMAScript now supports the notions of classes, interfaces, etc., in terms that are closer to the traditional OO manner, which means that the next release(s) of JavaScript will start to support these notions as well.
There is no magic to knowing when to use a custom object instead of an array in your application. The more you work with and understand the way custom objects work, the more likely you will think about your data-carrying scripts in these terms — especially if an object can benefit from having one or more methods associated with it. This avenue is certainly not one for beginners, but we recommend that you give custom objects more than a casual perusal after you have gained some JavaScripting experience.
The nuts and bolts of objects An object in JavaScript is really just a collection of properties. Properties can take on the form of data types, functions (methods), or even other objects. In fact, you might find it easier to think of a custom object as an array of values, each of which is mapped to a property (a data type, method, or object). Wait — a method can be a property of an object? We’ll see how in just a bit; for now, take it on faith. A function contained in an object is known as a method. Methods are no different than other functions, except that they are intended to be used in the context of an object, and therefore are assumed to have access to properties of that object. This connection between properties and methods is one of the core concepts prevalent in OO. Objects are created using a special function known as a constructor, which determines the name of the object — the constructor is given the same name as the object. Here’s an example of a constructor function: function Alien() { }
Although this function doesn’t contain any code, it does nonetheless lay the groundwork for creating an Alien object. You can think of a constructor as a blueprint that is then used to create actual objects. A word about naming constructor functions: Conventionally, the constructor name is in
459
Part III: JavaScript Core Language Reference
TitleCase, and each instance variable referencing the object is in camelCase. Here’s an example of how you create an object using a constructor: var myAlien = new Alien();
The new keyword is used, in conjunction with a constructor, to create JavaScript objects.
Creating properties for custom objects Earlier we mentioned that properties are key to objects, so you might be wondering how you go about creating a property for a custom object. Custom object properties are created in the constructor with some help from the this keyword, as the following code reveals: function Alien() { this.name = "Clyde"; this.aggressive = true; }
The this keyword is used to reference the current object, which in this case is the object that is being created by the constructor. So, you use the this keyword to identify new properties for the object. The only problem with this example is that it results in all aliens that are created with the Alien() constructor having the same name and aggression. The fix is to pass in the property values to the constructor so that each alien can be customized upon creation: function Alien(name, aggressive) { this.name = name; this.aggressive = aggressive; }
Now you can create different aliens that each have their own unique property values: var alien1 = new Alien("Ernest", false); var alien2 = new Alien("Wilhelm", true);
To get to the properties of the object (for reading or writing after the object has been created), use the same type of dot syntax you use with DOM objects. To change the name property of one of the objects, the statement would be: alien1.name = "Julius";
Creating methods for custom objects Properties are really only half of the JavaScript OO equation. The other half is methods, which are functions that you tie to objects so that they can access object properties. Following is an example of a method that you might use with the alien class: function attack() { if (this.aggressive) { // Do some attacking and return true to indicate that the attack // commenced
460
Chapter 23: Function Objects and Custom Objects
return true; } else { // Don’t attack and return false to indicate that the attack didn’t // happen return false; } }
Notice that the attack() method references the this.aggressive property to decide if the attack should take place. The only thing missing at this point is the connection between the attack() method and the alien object. Without this connection the this keyword would have no meaning because there would be no associated object. Here’s how the connection is made: function Alien(name, aggressive) { // properties this.name = name; this.aggressive = aggressive; // methods this.attack = attack; }
This code clearly illustrates how methods are really just properties: they are declared the same as properties, so they masquerade as properties. A new property named attack is created and assigned a reference to the attack() method. It’s very important to note that the attack() method is specified by reference (without the parentheses). Here, then, is the creation of an alien object and the invocation of its attack() method: var alien1 = new Alien("Ernest", false); alien1.attack();
The way we have defined the attack method above for the alien object places it in the global namespace, which is not a good thing in terms of OO best practices (as you’ll see later in this chapter when we discuss encapsulation). A better approach is to embed it in the constructor: function Alien(name, aggressive) { // properties this.name = name; this.aggressive = aggressive; // methods this.attack = function(name, aggressive) { if (this.aggressive) { // Do some attacking and return true to indicate that // the attack commenced return true; } else {
461
Part III: JavaScript Core Language Reference
// Don’t attack and return false to indicate that // the attack didn’t happen return false; } }; }
You’re now armed with enough of the basics of JavaScript objects to move on to a more complete example, which the next section provides. This example will be progressively improved over the rest of the sections in this chapter as you build your custom object skills in a step-wise fashion.
An OO example – planetary objects Building on your familiarity with the planetary data array created in Chapter 18, ‘‘The Array Object,’’ this chapter shows you how convenient it is to use the data when it is constructed in the form of an OO design that utilizes custom objects. The application goal for the extended example in this section is to present a drop-down list of the nine planets of the solar system and display the properties of the selected planet. In this chapter, instead of building arrays to hold the data, you build objects — one object for each planet. The design of your planetary object has five properties and one method. The properties of each planet are name, diameter, distance from the sun, year length, and day length. To assign more intelligence to these objects, in Listing 23-5 you give each of them the capability to display their data below the drop-down list. You can conveniently define one function that knows how to behave with any of these planet objects, rather than having to define nine separate functions. When used within the context of an object, a function is actually referred to as a method. LISTING 23-5
OO Planetary Data Presentation HTML: jsb-23-05.html OO Planetary Data Presentation The Daily Planet Select a planet to view its planetary data: Mercury Venus Earth Mars
"; result += "Planetary data for " + this.name + ""; result += "
Diameter
" + this.diameter + "
"; result += "
Distance from Sun
" + this.distance + "
"; result += "
One Orbit Around Sun
" + this.year + "
"; result += "
One Revolution (Earth Time)
" + this.day + "
"; result += "
"; // display results document.write(result); document.close(); }; } // create new Planet objects, and store in a series of reference variables // ‘new’ will create a new Planet instance and insert parameter data into object var mercury = new Planet("Mercury","3100 miles", "36 million miles", "88 days", "59 days"); var venus = new Planet("Venus", "7700 miles", "67 million miles", "225 days", "244 days"); var earth = new Planet("Earth", "7920 miles", "93 million miles", "365.25 days","24 hours"); var mars = new Planet("Mars", "4200 miles", "141 million miles", "687 days", "24 hours, 24 minutes"); continued
463
Part III: JavaScript Core Language Reference
LISTING 23-5
(continued)
var jupiter = new Planet("Jupiter","88,640 miles","483 million miles", "11.9 years", "9 hours, 50 minutes"); var saturn = new Planet("Saturn", "74,500 miles","886 million miles", "29.5 years", "10 hours, 39 minutes"); var uranus = new Planet("Uranus", "32,000 miles","1.782 billion miles", "84 years", "23 hours"); var neptune = new Planet("Neptune","31,000 miles","2.793 billion miles", "165 years", "15 hours, 48 minutes"); var pluto = new Planet("Pluto", "1500 miles", "3.67 billion miles", "248 years", "6 days, 7 hours"); // invoke Planet object method corresponding to the // index of the visitor’s choice function doDisplay(popup) { i = popup.selectedIndex; eval(popup.options[i].text.toLowerCase() + ".showPlanet()"); }
The first task is to define the object constructor function, which performs several important jobs. For one, everything in this function establishes the structure of your custom object: the properties available for data storage and retrieval, and any methods that the object can invoke. The name of the function is the name you use later to create new instances of the object. Therefore, choosing a name that truly reflects the nature of the object is important. And, because you probably want to stuff some data into the function’s properties to get one or more instances of the object loaded and ready for the page’s user, the function definition includes parameters for each of the properties defined in this object definition. Inside the object, you use the this keyword to assign data that comes in as parameters to labeled properties. For this example, we use the same names for both the incoming parameter variables and the properties. That’s primarily for convenience (and is very common practice), but you can assign any parameter and property names you want and connect them any way you like. In the Planet() constructor function, five property slots are reserved for every instance of the object, whether or not any data actually is placed in every property (any unassigned slot has a value of null). The last entry in the Planet() constructor function is the definition of the showPlanet() method. As you do in every JavaScript method you encounter, you must invoke a method by using a reference to the object, a period, and the method name, followed by a set of parentheses. You see that syntax in a minute. The next long block of statements creates the individual objects according to the definition established in the Planet() constructor. Just like in an array, an assignment statement and the keyword new create an object. We assign names that are the real names of planets (the mercury object reference name refers to the Mercury planet object). The act of creating a new object sets aside space in memory (associated with the current document) for this object and its properties. An object created in memory is known as an instance. In this script, you create nine object instances, each with a different set of properties. Note that no parameter is sent
464
Chapter 23: Function Objects and Custom Objects
(or expected by the function) that corresponds to the showPlanet() method. Omitting that parameter here is fine because the specification of that method in the object definition means that the script automatically attaches the method to every version (instance) of the planet object that it creates. This is important, because it links the function (method) to the object, thereby providing it access to the object’s properties. The last function definition, doDisplay(), is an event handler, invoked whenever the user makes a choice from the list of planets. The first statement extracts the index value of the selected item. Using that index value, the script extracts the text. But things get a little tricky because you need to use that text string as a variable name — the name of the planet — so that you can append to it the call to the showPlanet() method. To make the disparate data types come together, use the eval() function (see Chapter 24 for a complete discussion). Inside the parentheses, extract the string for the planet name, change it to lowercase, and concatenate a string that completes the reference to the object’s showPlanet() method. The eval() function evaluates that string, which turns it into a valid method call. Therefore, if the user selects jupiter from the drop-down list, the method call becomes jupiter.showPlanet(). Now it’s time to look back to the showPlanet() method definition. When that method runs in response to a user selection of the planet Jupiter, the method’s only scope is of the jupiter object. Therefore, all references to this.propertyName in showPlanet() refer just to jupiter. The only possibility for this.name in the jupiter object is the value assigned to the name property for jupiter. The same goes for the rest of the properties extracted in the method.
Further encapsulation One of the benefits of using objects in scripting is that all the ‘‘wiring’’ inside the object — properties and methods — are defined within the local variable scope of the object. It’s a concept called encapsulation. Thus, when you use the this keyword to create object properties and assign values to them inside a constructor function, the property names, and any code associated with them, are private to the object and never conflict with global variable or object names. In large scripting projects, especially when multiple programmers are involved, it’s fairly easy for global names to clash. For example, in Internet Explorer, all DOM object IDs become part of the global variable space because that browser allows scripts to reference an element object simply by its ID (unlike the W3C DOM, which uses the document.getElementById() method). As a project grows in size and complexity, it is increasingly important to avoid piling up more and more objects — including function definitions — in the global variable name space. In Listing 23-5, for example, the showPlanet() method is defined in the local name space. It’s a local method to the object because the method definition is defined within the planet() constructor function. If we were to define the showPlanet() method outside of the Planet() constructor function (as shown in an earlier example in this chapter), the showPlanet() method would be taking up a global object name that might be used elsewhere.
Creating an array of objects In Listing 23-5, each of the planet objects is assigned to a global variable whose name is that of the planet. If the idea of custom objects is new to you, this idea probably doesn’t sound so bad, because it’s easy to visualize each variable representing an object. But, as shown in the doDisplay() function, accessing an object by name requires use of the eval() function to convert a string representation to a valid object reference. Although it’s not too important in this simple example, the eval() function is not particularly efficient in JavaScript. If you find yourself using an eval() function, look
465
Part III: JavaScript Core Language Reference
for ways to improve efficiency, such that you can reference an object directly. The way to accomplish that streamlining for this application is to place the objects in an array. To assign the custom objects in Listing 23-5 to an array, first create an empty array and then assign the result of each object constructor call as an entry in the array. The modified code section would result in Listing 23-6. This partial listing of the code from the external JavaScript file shows just the change in the code. The HTML for Listings 23-5 and 23-6 are exactly the same, so only the code from the partial external JavaScript file is included here. Both files are complete on the CD-ROM. LISTING 23-6
Array of Planet Objects JavaScript: partial of jsb-23-06.js // create new Planet objects, and store in an array of reference variables // ‘new’ will create a new Planet instance and insert parameter data into object var planets = new Array ( new Planet("Mercury","3100 miles", "36 million miles", "88 days", "59 days"), new Planet("Venus", "7700 miles", "67 million miles", "225 days", "244 days"), new Planet("Earth", "7920 miles", "93 million miles", "365.25 days","24 hours"), new Planet("Mars", "4200 miles", "141 million miles", "687 days", "24 hours, 24 minutes"), new Planet("Jupiter","88,640 miles","483 million miles", "11.9 years", "9 hours, 50 minutes"), new Planet("Saturn", "74,500 miles","886 million miles", "29.5 years", "10 hours, 39 minutes"), new Planet("Uranus", "32,000 miles","1.782 billion miles", "84 years", "23 hours"), new Planet("Neptune","31,000 miles","2.793 billion miles", "165 years", "15 hours, 48 minutes"), new Planet("Pluto", "1500 miles", "3.67 billion miles", "248 years", "6 days, 7 hours") ); }
The supreme advantage to this approach comes in a modified doDisplay() function, which can use the index value from the select element’s selectedIndex directly: function doDisplay(popup) { i = popup.selectedIndex; planets[i].showPlanet(); }
The presence of so many similar objects cries out for their storage as an array. Here, we are using the numeric value of the drop-down list’s selectedIndex to locate the proper array element.
466
Chapter 23: Function Objects and Custom Objects
Taking advantage of embedded objects One powerful technique for using custom objects is embedding an object within another object. When you place one object inside another object, the object being placed is known as an embedded object or object property. Let’s extend the planet example to help you understand the implications of using a custom object property. Say that you want to beef up the planet page with a photo of each planet. Each photo has a URL for the photo file; each photo also contains other information, such as the copyright notice and a reference number, which displays on the page for the user. One way to handle this additional information is to create a separate object definition for a photo database. Such a definition may look like this: function Photo(name, URL, copyright, refNum) { this.name = name; this.URL = URL; this.copyright = copyright; this.refNum = refNum; }
You then need to create individual photo objects for each picture. One such definition may look like this: mercuryPhoto = new Photo("Planet Mercury", "/images/merc44.gif", "(c)1990 NASA", 28372);
Attaching a photo object to a planet object requires modifying the planet constructor function to accommodate one more property — an object property. The new planet constructor looks like this: function Planet(name, diameter, distance, year, day, photo) { this.name = name; this.diameter = diameter; this.distance = distance; this.year = year; this.day = day; this.showPlanet = showPlanet; this.photo = photo; // add photo property }
When the photo objects are created, you can then create each planet object by passing one more parameter — a photo object you want associated with that object: // create new planet objects, and store in a series of variables Mercury = new Planet("Mercury", "3100 miles", "36 million miles", "88 days", "59 days", mercuryPhoto);
To access a property of a photo object, your scripts then have to assemble a reference that works its way through the connection with the planet object: copyrightData = Mercury.photo.copyright;
The potential of embedded objects of this type is enormous. For example, you can embed all the copy elements and image URLs for an online catalog in a single document. As the user selects items to
467
Part III: JavaScript Core Language Reference
view (or cycles through them in sequence), a new JavaScript-written page displays the information in an instant. This requires only the image to be downloaded — unless the image was pre-cached, as described in the image object discussion in Chapter 29, ‘‘The Document and Body Objects.’’ In this case, everything works instantaneously — no waiting for page after page of catalog. If, by now, you think you see a resemblance between this object-within-an-object construction and a relational database, give yourself a gold star. Nothing prevents multiple objects from having the same sub-object as their properties — like multiple business contacts having the same company object property.
The current way to create objects For current browsers, you can also benefit from a shortcut literal syntax for creating a new object. You can set pairs of property names and their values inside a set of curly braces, and you can assign the whole construction to a variable that becomes the object name. The following script shows how to organize this kind of object constructor: var Earth = {diameter:"7920 miles", distance:"93 million miles", year:"365.25", day:"24 hours", showPlanet:showPlanet};
Colons link name-value pairs, and commas separate multiple name-value pairs. The value portion of a name-value pair can even be an array (using the [...] constructor shortcut) or a nested object (using another pair of curly braces). In fact, you can nest arrays and objects to your heart’s content to create exceedingly complex objects. All in all, this is a very compact way to embed data in a page for script manipulation. If your CGI, XML, and database skills are up to the task, consider using a server program to convert XML data into this compact JavaScript version, with each XML record being its own JavaScript object. For multiple records, assign the curly-braced object definitions to an array entry. Then your scripts on the client can iterate through the data and generate HTML to display the data in a variety of forms, and sorted according to different criteria (thanks to the JavaScript array-sorting powers).
Defining object property getters and setters The idea of creating getters and setters, generally known in JavaScript as accessors, for an object is introduced in Chapter 25, ‘‘Document Object Model Essentials,’’ where they are described in the context of W3C DOM objects. Here, we look at an example of using getters and setters in the context of custom objects. The purpose of a setter is to assign a new value to a property in an object and at the same time check it for validity if necessary. A setter defines how a new value assigned to the property should apply the value to the object. We would define a getter for each property we wanted to read in the object. In our object, we would typically define a getter and setter for each property of the object. If you have a requirement for a read-only property, then you would define only a getter method. As you can see in Listing 23-7, both getter and setter methods in the TitleCaseName object property are written in the form of methods, using the name of the corresponding property. Reading or writing an object’s property value can include sophisticated processing for either operation. This is called object literal notation. Firefox 2.0+, Safari 3.0+, Chrome+, and Opera 9.5+ support this. As of IE8, there is no support for getters and setters for custom objects. This partial listing of the code in the external JavaScript file shows just the change in the code for Listing 23-6. The HTML for
468
Chapter 23: Function Objects and Custom Objects
Listings 23-5 and 23-7 are exactly the same, so only the code from the partial external JavaScript file is included here. Both files are complete on the CD-ROM. LISTING 23-7
Planet Object Constructor Using Getters and Setters JavaScript: partial of jsb-23-07.js // object property with accessors using object literal notation // its property ‘name’, is a String value that is TitleCased when set var TitleCaseName = { _name: null, get name() { return this._name; }, set name(value) { this._name = value.substring(0,1).toUpperCase() + value.substring(1); } }; // definition of Planet object constructor function Planet(name, diameter, distance, year, day) { // properties TitleCaseName.name = name; this.name = TitleCaseName.name; this.diameter = diameter; this.distance = distance; this.year = year; this.day = day; // methods this.showPlanet = function() { // . . . }; }
In our continuing planet scenario, we want to make sure that when a Planet object is created, its name property is in TitleCase, regardless of how the developer programs the code. This is the perfect opportunity for a setter: we want to take the current value of the name property, convert its case, and then apply the new value to the name property. The first thing in the listing is the definition of the getter and setter methods that will be used in the TitleCaseName object. You’ll notice that the function keyword is not used. Once we’ve defined
469
Part III: JavaScript Core Language Reference
our local properties, we define the getters and/or setters. To define each getter, we only need the get keyword, followed by the property name we want to read. Typically, we would return the value of the corresponding property. In our case, we’re only defining a getter that simply reads the current value of the object’s _name property and returns it. We use the underscore prefix in _name to indicate that this property is strictly internal and should not be referenced outside its containing object. Similarly, we use the set keyword to define each setter. In this case, our setter converts the value parameter to TitleCase, and then assigns it to the _name property. The final piece is in the Planet object’s constructor function. Notice the first two properties in this function. In our case, the value supplied at object instantiation for the name property of a planet will ‘‘call’’ the TitleCaseName getter and setter function. In the first of these two lines, we assign the name to TitleCaseName. This invokes the setter, converting the value to TitleCase. In the second line, the getter is invoked, assigning the TitleCased name to Planet name.
Object-Oriented Concepts As mentioned previously, JavaScript is object-based rather than object-oriented. This means that instead of adhering to the class, subclass, and inheritance schemes of object-oriented languages such as Java, JavaScript uses what is called prototype inheritance. This scheme works not only for native and DOM objects but also for custom objects.
Adding a prototype A custom object is frequently defined by a constructor function, which typically parcels out initial values to properties of the object, as in the following example: function Car(plate, model, color) { this.plate = plate; this.model = model; this.color = color; } var car1 = new Car("AB 123", "Ford", "blue");
Current browsers offer a handy shortcut to stuff default values into properties if none are provided (the supplied value is null, 0, or an empty string). The OR operator (||) can let the property assignment statement apply the passed value, if present, or a default value you hard-wire into the constructor. Therefore, you can modify the preceding function to offer default values for the properties: function Car(plate, model, color) { this.plate = plate || "missing"; this.model = model || "unknown"; this.color = color || "unknown"; } var car1 = new Car("AB 123", "Ford", "");
After the preceding statements run, the car1 object has the following properties: car1.plate car1.model car1.color
470
// value = "AB 123" // value = "Ford" // value = "unknown"
Chapter 23: Function Objects and Custom Objects
You can then add a new property to the constructor’s prototype property, as in Car.prototype.companyOwned = true;
Any Car object you already created, or are about to create, automatically inherits the new companyOwned property and its value. You can still override the value of the companyOwned property for any individual Car object. But if you don’t override the property for instances of the Car object, the Car objects whose companyOwned property is not overridden automatically inherit any change to the prototype.companyOwned value. This has to do with the way JavaScript looks for prototype property values. In a similar fashion, we use prototypes in Listing 23-8 in our ongoing improvements to our Planet object. This partial listing of the code in the external JavaScript file shows just the change in the code for Listing 23-7. The HTML for Listings 23-5 and 23-8 are exactly the same, so only the code from the partial external JavaScript file is included here. Both files are complete on the CD-ROM. LISTING 23-8
Prototype inheritance Each time your script attempts to read or write a property of an object, JavaScript follows a specific sequence in search of a match for the property name. The sequence is as follows:
1. If the property has a local value assigned to the current object, this is the value to use. 2. If there is no local value, check the value of the property’s prototype of the object’s constructor.
471
Part III: JavaScript Core Language Reference
3. Continue up the prototype chain until either a match of the property is found (with a value assigned to it) or the search reaches the native Object object. Therefore, if you change the value of a constructor’s prototype property and you do not override the property value in an instance of that constructor, JavaScript returns the current value of the constructor’s prototype property.
Nested objects and prototype inheritance When you begin nesting objects, especially when one object invokes the constructor of another, there is an added wrinkle to the prototype inheritance chain. Let’s continue with the Car object defined earlier. In this scenario, consider the Car object to be akin to a root object that has properties shared among two other types of objects. One of the object types is a company fleet vehicle, which needs the properties of the root Car object (plate, model, color) but also adds some properties of its own. The other object that shares the Car object is an object representing a car parked in the company garage — an object that has additional properties regarding the parking of the vehicle. This explains why the Car object is defined on its own. Now look at the constructor function for the parking record, along with the constructor for the basic Car object: function Car(plate, model, color) { this.plate = plate || "missing"; this.model = model || "unknown"; this.color = color || "unknown"; } function CarInLot(plate, model, color, timeIn, spaceNum) { this.timeIn = timeIn; this.spaceNum = spaceNum; this.carInfo = car; this.carInfo(plate, model, color); }
The CarInLot constructor not only assigns values to its unique properties (timeIn and spaceNum) but it also includes a reference to the Car constructor, arbitrarily assigned to a property called carInfo. This property assignment is merely a conduit that allows property values intended for the Car constructor to be passed within the CarInLot constructor function. To create a CarInLot object, use a statement like the following: var car1 = new CarInLot("AA 123", "Ford", "blue", "10:02AM", "31");
After this statement, the car1 object has the following properties and values: car1.timeIn car1.spaceNum car1.carInfo car1.plate car1.model car1.color
472
// // // // // //
value value value value value value
= = = = = =
"10:02AM" "31" reference to car object constructor function "AA 123" "Ford" "blue"
Chapter 23: Function Objects and Custom Objects
Let’s say that five CarInLot objects are created in the script (car1 through car5). The prototype wrinkle comes into play if, for example, you assign a new property to the Car constructor prototype: Car.prototype.companyOwned = true;
Even though the CarInLot objects use the Car constructor, the instances of CarInLot objects do not have a prototype chain back to the Car object. As the preceding code stands, even though you’ve added a companyOwned property to the Car constructor, no CarInLot object inherits that property (even if you were to create a new CarInLot object after defining the new prototype property for Car). To get the CarInLot instances to inherit the prototype.companyOwned property, you must explicitly connect the prototype of the CarInLot constructor to the Car constructor prior to creating instances of CarInLot objects: CarInLot.prototype = new Car();
The complete sequence, then, is as follows: function Car(plate, model, color) { this.plate = plate || "missing"; this.model = model || "unknown"; this.color = color || "unknown"; } function CarsInLot(plate, model, color, timeIn, spaceNum) { this.timeIn = timeIn; this.spaceNum = spaceNum; this.carInfo = car; this.carInfo(plate, model, color); } CarsInLot.prototype = new Car(); var car1 = new CarsInLot("123ABC", "Ford","blue","10:02AM", "32"); Car.prototype.companyOwned = true;
After this stretch of code runs, the car1 object has the following properties and values: car1.timeIn car1.spaceNum car1.carInfo car1.plate car1.model car1.color car1.companyOwned
// // // // // // //
value value value value value value value
= = = = = = =
"10:02AM" "31" reference to car object constructor function "AA 123" "Ford" "blue" true
NN4+/Moz provides one extra, and proprietary, bit of syntax in this prototype world. The __proto__ property (that’s with double underscores before and after the word proto) returns a reference to the object that is next up the prototype chain. For example, if you inspect the properties of car1.__proto__ after the preceding code runs, you see that the properties of the object next up the prototype chain are as follows: car1.__proto__.plate car1.__proto__.model
// value = "AA 123" // value = "Ford"
473
Part III: JavaScript Core Language Reference objectObject car1.__proto__.color car1.__proto__.companyOwned
// value = "blue" // value = true
This property can be helpful in debugging custom objects and prototype inheritance chain challenges, but the property is not part of the ECMA standard. Therefore, we discourage you from using the property in your production scripts, since it isn’t available in non-Mozilla-based browsers.
Syntax Creating an Object object: function constructorName([arg1,...[,argN]]) { statement(s) } var objName = new constructorName(["argName1",...[,"argNameN"]); var objName = new Object(); var objName = {propName1:propVal1[, propName2:propVal2[,...N]}}
Accessing an Object object properties and methods: objectReference.property | method([parameters])
About this object Although it might sound redundant, the Object object is a vital native object in the JavaScript environment. It is the root object on which all other native objects — such as Date, Array, String, and the like — are based (see Figure 23-1). This object also provides the foundation for creating custom objects, as described earlier in this chapter.
474
Chapter 23: Function Objects and Custom Objects objectObject FIGURE 23-1
The Object object hierarchy. Object
Array
Boolean
Date
Function
Number
String
By and large, your scripts do not access the properties of the native Object object. The same is true for many of its methods, such as toString() and valueOf(), which internally allow debugging alert dialog boxes (and The Evaluator) to display something when referring to an object or its constructor. In the case of methods like toString() and valueOf(), you will typically override these in the child. Similarly, the toSource() method returns a string representation of the source code for an object, which is not something you would typically need to use in a script. A little more practical are the watch() and unwatch() methods of the Object object, which provide a mechanism for taking action when a property value changes. You can call the watch() method and assign a function that is called when a certain property changes. This enables you to handle an internal property change as an event. When you’re finished watching a property, the unwatch() method is used to stop the watchpoint. Listing 23-9 contains an example of how the watch() and unwatch() methods can be used to track the value of a property. LISTING 23-9
Watching an Object Property HTML: jsb-23-09.html Object Watching Watching Over You Enter text here: continued
475
Part III: JavaScript Core Language Reference objectObject.constructor LISTING 23-9
(continued)
JavaScript: jsb-23-09.js function setIt(msg) { document.forms[0].entry.value = msg; } function watchIt(on) { var obj = document.forms[0].entry; if (on) { obj.watch("value",report); } else { obj.unwatch("value"); } } function report(id, oldval, newval) { alert("The field’s " + id + " property on its way from \n’" + oldval + "’\n to \n’" + newval + "’."); return newval; }
You can use a trio of methods (hasOwnProperty(), isPrototypeOf(), and propertyIsEnumerable()) to perform some inspection of the prototype environment of an object instance. They are of interest primarily to advanced scripters who are building extensive, simulated, object-oriented applications.
Chapter 23: Function Objects and Custom Objects objectObject.propertyIsEnumerable() This is the property that is inherited by any custom, Array, String, or other objects, when one of those objects is instantiated. It is a reference to the constructor function that was used to create the object. Be aware, though, that if a prototype were used, this property might not contain a valid value. Using the earlier car example, if you were to create a car with the Car constructor, then the constructor property would refer to Car: var car1 = new Car("AA 123", "Ford", "blue"); if (car1.constructor == Car) // would evaluate to true { // statements dealing with the car object }
Methods hasOwnProperty("propName") Returns: Boolean. Compatibility: WinIE5.5+, MacIE-, NN6+, Moz+, Safari-, Chrome+ The hasOwnProperty() method returns true if the current object instance has the property defined in its constructor or in a related constructor function. But if this property is defined externally, as through assignment to the object’s prototype property, the method returns false. Using the example of the Car and CarInLot objects from earlier in this chapter, the following expressions evaluate to true: car1.hasOwnProperty("spaceNum"); car1.hasOwnProperty("model");
Even though the model property is defined in a constructor that is invoked by another constructor, the property belongs to the car1 object. The following statement, however, evaluates to false: car1.hasOwnProperty("companyOwned");
This property is defined by way of the prototype of one of the constructor functions and is not a built-in property for the object instance.
isPrototypeOf(objRef) Returns: Boolean Compatibility: WinIE5.5+, MacIE-, NN6+, Moz+, Safari-, Chrome+ The isPrototypeOf() method is intended to reveal whether or not the current object has a prototype relation with an object passed as a parameter. In practice, the IE and NN/Moz versions of this method operate differently and return different results.
propertyIsEnumerable("propName") Returns: Boolean Compatibility: WinIE5.5+, MacIE-, NN6+, Moz+, Safari-, Chrome+ In the terminology of the ECMA-262 language specification, a value is enumerable if constructions such as the for. . .in property inspection loop (see Chapter 21, ‘‘Control Structures and Exception
477
Part III: JavaScript Core Language Reference objectObject.toSource() Handling’’) can inspect it. Enumerable properties include values such as arrays, strings, and virtually every kind of object. According to the ECMA specification, this method is not supposed to work its way up the prototype chain.
toSource() Returns: String Compatibility: WinIE5.5+, MacIE-, NN6+, Moz+, Safari-, Chrome+ The toSource() method obtains a string representation of the source code for an object. Unlike the toString() method, which returns a string equivalent of the value of an object, the toSource() method returns the underlying code for the object as a string. Seeing as how this is a very specialized, low-level feature, the method is typically only used internally by JavaScript, and potentially in some debugging scenarios.
toString() Returns: String Compatibility: WinIE5.5+, MacIE-, NN6+, Moz+, Safari-, Chrome+ The toString() method is used to obtain a string representation of the value of an object. It is fairly common to take advantage of this method in situations where an object needs to be examined as raw text. When creating custom objects, you have the ability to create your own toString() method that reveals whatever information about the object you desire to be seen.
unwatch("propName") Returns: Boolean Compatibility: WinIE-, MacIE-, NN6+, Moz+, Safari-, Chrome+ As the counterpart to the watch() method, the unwatch() method terminates a watchpoint that has been set for a particular property.
valueOf() Returns: Object Compatibility: WinIE5.5+, MacIE-, NN6+, Moz+, Safari-, Chrome+ The valueOf() method is used to resolve an object to a primitive data type. This may not always be possible, in which case the method simply returns the object itself. Otherwise, the method returns a primitive value that represents the object.
watch("propName") Returns: Boolean Compatibility: WinIE-, MacIE-, NN6+, Moz+, Safari-, Chrome+ The watch() method is the key to a handy little JavaScript debugging feature known as watchpoints. A watchpoint enables you to specify a function that is called whenever the value of a property is set. You can then carefully track the state of properties and take action when an important property value changes.
478
Chapter 23: Function Objects and Custom Objects objectObject.watch() You set a watchpoint by calling the watch() method and passing the name of the property that you want to watch, like this: obj.watch("count", function(prop, oldval, newval) { document.writeln(prop + " changed from " + oldval + " to " + newval); return newval; } );
In this example, a function is created to output a property change notification and then return the new property value. Every watchpoint handler must follow this same convention of using three arguments that specify the property, old value, and new value, respectively.
479
Global Functions and Statements
I
n addition to all the objects and other language constructs described in the preceding chapters of this reference part of the book, several language items need to be treated on a global scale. These items do not apply to any particular objects (or, in fact, to any object), and you can use them anywhere in a script. If you read earlier chapters, you were introduced to many of these functions and statements. This chapter serves as a convenient place to highlight these all-important items that are otherwise easily forgotten. At the end of the chapter, note the brief introduction to several objects that are built into the Windows-only versions of Internet Explorer. This chapter begins with coverage of the following global functions and statements that are part of the core JavaScript language:
IN THIS CHAPTER Converting strings into object references Creating URL-friendly strings Adding comments to scripts
Part III: JavaScript Core Language Reference decodeURI() Functions
Statements
toString() unescape() unwatch() watch()
Global functions are not tied to the document object model. Instead, they typically enable you to convert data from one type to another. The list of global statements is short, but a couple of them appear extensively in your scripting.
Functions decodeURI("encodedURI") decodeURIComponent("encodedURIComponent") encodeURI("URIString") encodeURIComponent("URIComponentString") Returns: String Compatibility: WinIE5.5+, MacIE−, NN6+, Moz+, Safari+, Opera+, Chrome+ The ECMA-262 standard, as implemented in IE5.5+, NN6+, and Mozilla-based browsers, provides utility functions that perform a more rigorous conversion of strings to valid URI strings, and vice versa, than was achieved earlier via the escape() and unescape() functions (described later in this chapter). In fact, the modern encodeURI(), encodeURIComponent(), decodeURI(), and decodeURIComponent() functions serve as replacements to the now deprecated escape() and unescape() functions. The purpose of the encoding functions is to convert any string to a version that you can use as a Uniform Resource Identifier, such as a web page address or an invocation of a server CGI script. Whereas Latin alphanumeric characters pass through the encoding process untouched, you must use the encoding functions to convert some symbols and other Unicode characters into a form (hexadecimal representations of the character numbers) that the Internet can pass from place to place. The space character, for example, must be encoded to its hex version: %20. Perhaps the biggest difference between the encodeURI() and escape() functions (and their decodeURI() and unescape() counterparts) is that the more modern versions do not encode a wide range of symbols that are perfectly acceptable as URI characters according to the syntax recommended in RFC2396 (http://www.ietf.org/rfc/rfc2396.txt). Thus, the following characters are not encoded via the encodeURI() function: ; / ? : @ & = + $ , - _ . ! ∼ * ‘ ( ) #
Use the encodeURI() and decodeURI() functions only on complete URIs. Applicable URIs can be relative or absolute, but these two functions are wired especially so that symbols that are part of the protocol (://), search string (? and =, for instance), and directory-level delimiters (/) are not encoded. The decodeURI() function should work with URIs that arrive from servers as page
482
Chapter 24: Global Functions and Statements unescape() locations, but be aware that some server CGIs encode spaces into plus symbols (+) that are not decoded back into spaces by the JavaScript function. If the URIs your script needs to decode contain plus symbols in place of spaces, you need to run your decoded URI through a string replacement method to finish the job (regular expressions come in handy here). If you are decoding URI strings that your scripts encoded, use the decode functions only on URIs that were encoded via the corresponding encode function. Do not attempt to decode a URI that was created via the old escape() function, because the conversion processes work according to different rules. The difference between a URI and a URI component is that a component is a single piece of a URI, generally not containing delimiter characters. For example, if you use the encodeURIComponent() function on a complete URI, almost all of the symbols (other than things such as periods) are encoded into hexadecimal versions — including directory delimiters. Therefore, you should use the component-level conversion functions only on quite granular pieces of a URI. For example, if you assemble a search string that has a name-value pair, you can use the encodeURIComponent() function separately on the name and on the value. But if you use that function on the pair that is already in the form name=value, the function encodes the equal symbol to a hexadecimal equivalent. Since the escape() and unescape() functions were sometimes used on strings that weren’t necessarily URL (URI) strings, you will generally use the encodeURIComponent() and decodeURIComponent() functions when modernizing code that utilizes escape() and unescape().
Example Use The Evaluator (see Chapter 4, ‘‘JavaScript Essentials’’) to experiment with the differences between encoding a full URI and a component, and encoding and escaping a URI string. For example, compare the results of the following three statements: escape("http://www.giantco.com/index.htm?code=42") encodeURI("http://www.giantco.com/index.htm?code=42") encodeURIComponent("http://www.giantco.com/index.htm?code=42")
Because the sample URI string is valid as is, the encodeURI() version makes no changes. Experiment further by making the search string value into a string with a space, and see how each function treats that character.
escape("URIString" [,1]) unescape("escapedURIString") Returns: String Compatibility: WinIE3+, MacIE3+, NN2+, Moz+, Safari+, Opera+, Chrome+ If you watch the content of the Location field in your browser, you may occasionally see URLs that include a lot of % symbols, plus some numbers. The format you see is URL encoding (more accurately called URI encoding — Uniform Resource Identifier rather than Uniform Resource Locator). This format allows even multiple word strings and nonalphanumeric characters to be sent as one contiguous string of a very low, common denominator character set. This encoding turns a character, such as a space, into its hexadecimal equivalent value, preceded by a percent symbol. For example, the space character (ASCII value 32) is hexadecimal 20, so the encoded version of a space is %20. All characters, including tabs and carriage returns, can be encoded in this way and sent as a simple string that can be decoded on the receiving end for reconstruction. You can also use this encoding
483
Part III: JavaScript Core Language Reference eval() to preprocess multiple lines of text that must be stored as a character string in databases. To convert a plain-language string to its encoded version, use the escape() method. This function returns a string consisting of the encoded version. For example: var theCode = escape("Hello there"); // result: Hello%20there
Most, but not all, non-alphanumeric characters are converted to escaped versions with the escape() function. One exception is the plus sign, which URLs use to separate components of search strings. If you must encode the plus symbol, too, then add the optional second parameter to the function to make the plus symbol convert to its hexadecimal equivalent (2B): var a = escape("Adding 2+2"); // result: Adding%202+2 var a = escape("Adding 2+2",1); // result: Adding%202%2B2
Note that browser support is not consistent in the treatment of the optional second parameter; the same result could be returned whether or not the second argument is included. The unescape() function was used to convert an escaped string back into plain language. We say ‘‘was’’ because the function is now deprecated thanks to decodeURI() and decodeURIComponent() and shouldn’t be used. The escape() function operates in a way that is approximately midway between the newer functions encodeURI() and encodeComponentURI(). However, the function is now deprecated in lieu of the newer functions and shouldn’t be used.
eval("string") Returns: Object reference Compatibility: WinIE3+, MacIE3+, NN2+, Moz+, Safari+, Opera+, Chrome+ Expression evaluation, as you probably are well aware by now, is an important concept to grasp for scripting with JavaScript (and for programming in general). An expression evaluates to some value. But occasionally, you need to force an additional evaluation on an expression to receive the desired results. The eval() function acts on a string value to force an evaluation of that string expression. Perhaps the most common application of the eval() function is to convert a string version of an object reference to a genuine object reference.
Example The eval() function can evaluate any JavaScript statement or expression stored as a string. This includes string equivalents of arithmetic expressions, object value assignments, and object method invocation. We do not recommend that you rely on the eval() function, however, because this function is inherently inefficient (from the standpoint of performance). Fortunately, you may not need the eval() function to get from a string version of an object’s name to a valid object reference. For example, if your script loops through a series of objects whose names include serial numbers, you can use the object names as array indexes rather than use eval() to assemble the object references. The inefficient way to set the value of a series of fields named data0, data1, and so on, is as follows: function fillFields() { var theObj;
484
Chapter 24: Global Functions and Statements isNaN() for (var i = 0; i < 10; i++) { theObj = eval("document.forms[0].data" + i); theObj.value = i; } }
A more efficient way is to perform the concatenation within the index brackets for the object reference: function fillFields() { for (var i = 0; i < 10; i++) { document.getElementById("myForm").elements["data" + i].value = i; } }
Tip Whenever you are about to use an eval() function, look for ways to use string index values of arrays of objects instead. The W3C DOM makes it even easier with the help of the document.getElementById() method, which takes a string as a parameter and returns a reference to the named object.
isFinite(number) Returns: Boolean Compatibility: WinIE4+, MacIE4+, NN4+, Moz+, Safari+, Opera+, Chrome+ It is rare that you will ever need the isFinite() function, but its purpose is to advise whether a number is beyond the absolute minimum or maximum values that JavaScript can handle. If a number is outside of that range, the function returns false. The parameter to the function must be a number data type.
isNaN(expression) Returns: Boolean Compatibility: WinIE3+, MacIE3+, NN2+, Moz+, Safari+, Opera+, Chrome+ For those instances in which a calculation relies on data coming from a text field or other string-oriented source, you frequently need to check whether the value is a number. If the value is not a number, the calculation may result in a script error.
Example Use the isNaN() function to test whether a value is a number, prior to passing the value onto a calculation. The most common use of this function is to test the result of a parseInt() or parseFloat() function. If the strings submitted for conversion to those functions cannot be converted to a number, the resulting value is NaN (a special symbol indicating ‘‘not a number’’). The isNaN() function returns true if the value is not a number.
485
Part III: JavaScript Core Language Reference Number() A convenient way to use this function is to intercept improper data before it can do damage, as follows: function calc(form) { var inputValue = parseInt(form.entry.value); if (isNaN(inputValue)) { alert("You must enter a number to continue."); } else { // statements for calculation } }
Probably the biggest mistake scripters make with this function is failing to observe the case of all the letters in the function name. The trailing uppercase ‘‘N’’ is easy to miss.
Number("string") parseFloat("string") parseInt("string" [,radix]) Returns: Number Compatibility: WinIE3+, MacIE3+, NN2+, Moz+, Safari+, Opera+, Chrome+ All three of these functions convert a string value into a numeric value. The parseInt() and parseFloat() functions are compatible across all versions of all browsers, including very old browsers; the Number() function was introduced in version 4 browsers. Use the Number() function when your script is not concerned with the precision of the value, and prefers to let the source string govern whether the returned value is a floating-point number or an integer. The function takes a single parameter — a string to convert to a number value. The parseFloat() function also lets the string source value determine whether the returned value is a floating-point number or an integer. If the source string includes any non-zero value to the right of the decimal, the result is a floating-point number. But if the string value were, say, "3.00", the returned value would be an integer value. An extra, optional parameter for parseInt() enables you to define the number base for use in the conversion. If you don’t specify a radix parameter, JavaScript tries to look out for you; but in doing so, JavaScript may cause some difficulty for you. The primary problem arises when the string parameter for parseInt() starts with a zero, which a text box entry or database field might do. In JavaScript, numbers starting with zero are treated as octal (base-8) numbers. Therefore, parseInt("010") yields the decimal value 8. When you apply the parseInt() function, always specify the radix of 10 if you are working in base-10 numbers. You can, however, specify any radix value from 2 through 36. For example, to convert a binary number string to its decimal equivalent, assign a radix of 2 as follows: var n = parseInt("011",2); // result: 3
486
Chapter 24: Global Functions and Statements toString() Similarly, you can convert a hexadecimal string to its decimal equivalent by specifying a radix of 16: var n = parseInt("4F",16); // result: 79
Example Both parseInt() and parseFloat() exhibit a very useful behavior: If the string passed as a parameter starts with at least one number followed by, say, letters, the functions do their jobs on the numeric part of the string and ignore the rest. This is why you can use parseFloat() on the navigator.appVersion string to extract just the reported version number without having to parse the rest of the string. For example, Firefox 1.0 for Windows reports a navigator.appVersion value as 5.0 (Windows; en-US)
But you can get just the numeric part of the string via parseFloat(): var ver = parseFloat(navigator.appVersion);
Note The number stored in the navigator.appVersion property refers to the version number of the underlying browser engine, which helps explain why the reported version in this case is 5.0, even though the Firefox browser application is considered version 1.0.
Because the result is a number, you can perform numeric comparisons to see, for instance, whether the version is greater than or equal to 4.
toString([radix]) Returns: String Compatibility: WinIE4+, MacIE4+, NN4+, Moz+, Safari+, Opera+, Chrome+ Every JavaScript core language object and every DOM document object has a toString() method associated with it. This method is designed to render the contents of the object as a string of text that is as meaningful as possible. Table 24-1 shows the result of applying the toString() method on each of the convertible core language object types. TABLE 24-1
toString() Method Results for Object Types Object Type
Result
String
The same string
Number
String equivalent (but numeric literals cannot be converted)
Boolean
true or false
Array
Comma-delimited list of array contents (with no spaces after commas)
Function
Decompiled string version of the function definition
487
Part III: JavaScript Core Language Reference toString() Many DOM objects can be converted to a string. For example, a location object returns its URL. But when an object has nothing suitable to return for its content as a string, it usually returns a string in the following format: [object objectType]
Example The toString() method is available on all versions of all browsers. By setting the optional radix parameter between 2 and 16, you can convert numbers to string equivalents in different number bases. Listing 24-1 calculates and draws a conversion table for decimal, hexadecimal, octal, and binary numbers between 0 and 20. In this case, the source of each value is the value of the index counter variable, each time the for loop’s statements execute.
Note The function to assign event handlers throughout the code in this chapter and much of the book is addEvent(), a cross-browser event handler explained in detail in Chapter 32, ‘‘Event Objects.’’ The addEvent() function is part of the script file jsb-global.js located on the accompanying CD-ROM in the Content/ folder, where it is accessible to all chapters’ scripts.
LISTING 24-1
Using toString() with Radix Values HTML: jsp-24-01.html Using toString() to convert to other number bases: Using toString() to convert to other number bases:
Chapter 24: Global Functions and Statements toString() text-align: center; padding-left: 2px; padding-right: 2px; } th { font-weight: bold; }
JavaScript: jsb-24-01.js // initialize when the page has loaded addEvent(window, "load", initialize); function initialize() { var theTable = document.getElementById("numberConversions"); if (theTable) { var newRowElem; var newCellElem; var newText; // Insert the rows after the existing row var newRowPosition = 1; // put the converted number data into the table for (var i = 0; i
In this last example, DOM0 is used. Using the W3C DOM, the function and its assignment to a custom property will be coded exactly the same. The difference is how the onclick event handler is identified. In DOM0, the event is defined directly as an attribute of the object in the HTML: on the input tag in the case above. In the W3C DOM the event may be defined within the script, rather than on the HTML element itself: // initialize when the page has loaded addEvent(window, "load", initialize); function initialize() { // add an event to the button addEvent(document.getElementById("theButton"), click); }
Note The function to assign event handlers throughout the code in this chapter and much of the book is addEvent(), a cross-browser event handler explained in detail in Chapter 32. The addEvent() function is part of the script file jsb-global.js, which is located on the accompanying CD-ROM in the Content/ folder, where it is accessible to all chapters’ scripts.
Object Event Handlers An event handler specifies how an object reacts to an event that is triggered by a user action (for example, a button click) or a browser action (for example, the completion of a document load). Going back to the earliest JavaScript-enabled browser, event handlers were defined inside HTML tags as extra attributes. They included the name of the attribute, followed by an equal sign (working as an assignment operator) and a string containing the script statement(s) or function(s) to execute when the event occured (see Chapter 7, ‘‘Scripts and HTML Documents’’). Although event handlers are commonly defined in an object’s HTML tag, you also have the power to assign or change an event handler just as you assign or change the property of an object. The value of an event handler property looks like a function definition. For example, given this HTML definition
508
Chapter 25: Document Object Model Essentials
the value of the object’s onfocus (all lowercase) property is function onfocus() { doIt(); }
You can, however, assign an entirely different function to an event handler by assigning a function reference to the property. Such references don’t include the parentheses that are part of the function’s definition. (You see this again in Chapter 23 when you assign functions to object properties.) Using the same text field definition you just looked at, you can assign a different function to the event handler, because, based on user input elsewhere in the document, you want the field to behave differently when it receives the focus. If you define a function like this function doSomethingElse() { //statements }
You can then assign the function to the field with either: document.formName.entry.onfocus = doSomethingElse;
or document.getElementById("theEntryID").onfocus = doSomethingElse;
Because the new function reference is written in JavaScript, you must observe case for the function name. Additionally, you are best served across all browsers by sticking with all-lowercase event handler names as properties. If your scripts create new element objects dynamically, you can assign event handlers to these objects by way of event handler properties. For example, the following code uses W3C DOM syntax to create a new button input element and assign an onclick event handler that invokes a function defined elsewhere in the script: var newElem = document.createElement("input"); newElem.type = "button"; newElem.value = "Click Here"; newElem.onclick = doIt; document.getElementById("theFormId").appendChild(newElem);
Object Model Smorgasbord A survey of the entire evolution of scriptable browsers since NN2 and IE3 reveals six distinct DOM families. Even if your job entails developing content for just one current browser version, you may be surprised that family members from more than one DOM inhabit your authoring space. Studying the evolution of the object model is extremely valuable for newcomers to scripting. It is too easy to learn the latest object model gadgets in your current browser, only to discover that your heroic scripting efforts are lost on earlier browsers accessing your pages. Even if you plan on supporting only modern browsers, a cursory knowledge of object model history is a useful part of your JavaScript knowledge base. Therefore, take a look at the six major object model types and how they came into
509
Part IV: Document Objects Reference
being. Table 25-1 lists the object model families and the browser versions that support them. Note that a release number is only listed when the level of support for an object model type leaps forward (for example, going from ‘‘limited’’ support to ‘‘most’’ support). Later in this chapter are some guidelines you can follow to help you choose the object model(s) that best suit your users’ appetites. TABLE 25-1
It’s important to realize that even though browsers have come a long way toward providing unified support for web standards, we’re not quite there yet. As of this writing, no current browser fully and accurately supports Levels I and II of the W3C DOM. Firefox 2, Safari 1.3/2, Opera 9, and Chrome 1 have all closed the compatibility gap considerably, but some issues, not severely impacting HTML authoring, remain.
Basic Object Model The first scriptable browser, Netscape Navigator 2, implemented a very basic DOM. Figure 25-1, which you saw earlier in the chapter, provides a visual guide to the objects that were exposed to scripting. The hierarchical structure starts with the window and drills inward toward the document, forms, and form control elements. A document is a largely immutable page on the screen. Only elements that are by nature interactive — links and form elements, such as text fields and buttons — are treated as objects with properties, methods, and event handlers. The heavy emphasis on form controls opened numerous possibilities that were radical ideas at the time. Because a script could inspect the values of form controls, forms could be prevalidated on the client. If the page included a script that performed some calculations, data entry and calculated results were displayed via editable text fields. Additional objects that exist outside the document — window, history, and location objects — provide scriptable access to simple yet practical properties of the browser that loads the page. The most global view of the environment is the navigator object, which includes properties about the browser brand and version.
510
Chapter 25: Document Object Model Essentials
When Internet Explorer 3 arrived on the scene, the short life of Navigator 2 was nearing its end. Even though NN3 was already widely available in prerelease form, Internet Explorer 3 implemented the basic object model from NN2 (plus one window object property from NN3). Therefore, despite the browser version number discrepancy, NN2 and IE3 were essentially the same with respect to their DOMs. For a brief moment in Internet Time, there was nearly complete harmony between Microsoft and Netscape DOMs — albeit at a very simple level.
Basic Object Model Plus Images A very short time after Internet Explorer 3 was released, Netscape released Navigator 3 with an object model that built upon the original version. A handful of existing objects — especially the window object — gained new properties, methods, and/or event handlers. Scripts could also communicate with Java applets as objects. But the biggest new object on the scene was the Image object, along with the array of image objects exposed to the document object. Most of the properties for a Navigator 3 image object gave read-only access to values typically assigned to attributes in the tag. But you could modify one property — the src property — after the page loaded. Scripts could swap out images within the fixed image rectangle. Although these new image objects didn’t have mouse-related event handlers, nesting an image inside a link (which had onmouseover and new onmouseout event handlers) let scripters implement image rollovers to liven up a page. As more new scripters investigated the possibilities of adding JavaScript to their pages, frustration ensued when the image swapping they implemented for Navigator 3 failed to work in Internet Explorer 3. Although you could easily script around the lack of an image object to prevent script errors in Internet Explorer 3, the lack of this cool page feature disappointed many. Had they also taken into account the installed base of Navigator 2 in the world, they would have been disappointed there, too. To confuse matters even more, the Macintosh version of Internet Explorer 3.01 (the second release of the Internet Explorer for Mac browser) implemented scriptable image objects. Despite these rumblings of compatibility problems to come, the object model implemented in Navigator 3 eventually became the baseline reference for future DOMs. With few exceptions, code written for this object model runs on all browsers from Navigator 3 and Internet Explorer 4, on through the latest versions of both brands and other modern browsers.
Navigator 4–Only Extensions The next browser released to the world was Netscape Navigator 4. Numerous additions to the existing objects put more power into the hands of scripters. You could move and resize browser windows within the context of script-detectable screen object properties (for example, how big the user’s screen was). Two concepts that represented new thinking about the object model were an enhanced event model and the layer object.
Event capture model Navigator 4 added many new events to the repertoire. Keyboard events and more mouse events (onmousedown and onmouseup) allowed scripts to react to more user actions on form control elements and links. All of these events worked as they did in previous object models in which event
511
Part IV: Document Objects Reference
handlers were typically assigned as attributes to an element’s tag (although you could also assign event handlers as properties in script statements). To facilitate some of the Dynamic HTML (DHTML) potential in the rest of the Navigator 4 object model, the event model was substantially enhanced. At the root of the system is the idea that when a user performs some physical action on an event-aware object (for example, clicking a form button), the event reaches that button from the top down, through the document object hierarchy. If you have multiple objects that share an event handler, it may be more convenient to capture that event in just one place — the window or document object level — rather than assigning the same event handler to all the elements. The default behavior of Navigator 4 allowed the event to reach the target object, just as it had in earlier browsers. But you could also turn on event capture in the window, document, or layer object. When captured, the event could be handled at the upper level, preprocessed before being passed onto its original target, or redirected to another object altogether. Whether or not you capture events, the Navigator 4 event model produces an event object (with a lowercase e to distinguish it from the static Event object) for each event. That object contains properties that reveal more information about the specific event, such as the keyboard character pressed for a keyboard event or the position of a click event on the page. Any event handler can inspect event object properties to learn more about the event, and then process the event accordingly.
Layers Perhaps the most radical addition to the Navigator 4 object model was a new object that reflected an entirely new HTML element: the layer element. A layer is a container that is capable of holding its own HTML document, yet it exists in a plane in front of the main document. You can move, size, and hide a layer under script control. This new element allowed, for the first time, overlapping elements in an HTML page. To accommodate the layer object in the document object hierarchy, Netscape defined a nesting hierarchy such that a layer was contained by a document. As a result, the document object acquired a property (document.layers) that was an array of layer objects in the document. This array exposed only the first level of layer(s) in the current document object. Each layer had its own document object because each layer could load an external HTML document if desired. As a positionable element, a layer object had numerous properties and methods that allowed scripts to move, hide, show, and change its stacking order. Unfortunately for Netscape, the W3C did not agree to make the tag part of the HTML 4 specification. As such, it is an orphan element that exists only in Navigator 4 (not implemented in Moz1 or later). The same goes for the scripting of the layer object and its nested references.
Internet Explorer 4+ Extensions Microsoft broke important new ground with the release of Internet Explorer 4, which came several months after the release of Navigator 4. The main improvements were in the exposure of all HTML elements, scripted support of Cascading Style Sheets (CSS), and a new event model. Some other additions were available only on Windows 32-bit operating system platforms.
HTML element objects The biggest change to the object model world was that every HTML element became a scriptable object, while still supporting the original object model. Microsoft invented the document.all array
512
Chapter 25: Document Object Model Essentials
(also called a collection). This array contains references to every element in the document, regardless of element nesting. If you assign a unique identifier (name) to the id attribute of an element, you can reference the element by the following syntax: document.all.elementID
In most cases, you can also drop the document.all. part of the reference and begin with only the element ID. Every element object has an entirely new set of properties and methods that give scripters a level of control over document content unlike anything seen before. These properties and methods are explored in more detail in Chapter 26, ‘‘Generic HTML objects,’’ but several groups of properties deserve special mention here. Four properties (innerHTML, innerText, outerHTML, and outerText) provide read/write access to the actual content within the body of a document. This means that you no longer have to use text boxes to display calculated output from scripts. You can modify content inside paragraphs, table cells, or anywhere, on the fly. The browser’s rendering engine immediately reflows a document when the dimensions of an element’s content change. That feature puts the Dynamic in Dynamic HTML. To those of us who scripted the static pages of earlier browsers, this feature — taken for granted today — was nothing short of a revelation. The series of offset properties are related to the position of an element on the page. These properties are distinct from the kind of positioning performed by CSS. Therefore, you can get the dimensions and location of any element on the page, making it easier to move positionable content atop elements that are part of the document and that may appear in various locations due to the browser window’s current size. Finally, the style property is the gateway to CSS specifications defined for the element. It is important that the script can modify the numerous properties of the style object. Therefore, you can modify font specifications, colors, borders, and the positioning properties after the page loads. The dynamic reflow of the page takes care of any layout changes that the alteration requires (for example, adjusting to a bigger font size).
Element containment hierarchy Although Internet Explorer 4 still recognizes the element hierarchy of the original object model (see Figure 25-1), the DOM for Internet Explorer 4 does not extend this kind of hierarchy fully into other elements. If it did, it would mean that td elements inside a table might have to be addressed via its next outer tr or table element (just as a form control element must be addressed through its containing form element). Figure 25-2 shows how all HTML elements are grouped under the document object. The document.all array flattens the containment hierarchy, as far as referencing objects goes. A reference to the most deeply nested TD element is still document.all.cellID. The highlighted pathway from the window object is the predominant reference path used when working with the Internet Explorer 4 document object hierarchy. Element containment in Internet Explorer 4, however, is important for other reasons. Because an element can inherit some style sheet attributes from an element that contains it, you should devise a document’s HTML by embedding every piece of content in a container. Paragraph elements are text containers (with start and end tags), not tall line breaks between text chunks. Internet Explorer 4 introduced the notion of a parent-child relationship between a container and elements nested within it. Also, the position of an element may be calculated relative to the position of its next outermost positioning context.
513
Part IV: Document Objects Reference
FIGURE 25-2
The Internet Explorer 4 document object hierarchy. window frame self top parent navigator link
screen
styleSheets
applets
history form
document images
location plugins
anchor
event embeds
all [elements]
text
radio
button
select
textarea
checkbox
reset
option
password
submit
selection
style
The bottom line here is that element containment doesn’t have anything to do with object references (like the original object model). It has everything to do with the context of an element relative to the rest of the page’s content.
Cascading Style Sheets By arriving a bit later to market with its version 4 browser than Netscape, Microsoft benefited from having the CSS Level 1 specification more fully developed before the browser’s release. Therefore, the implementation is far more complete than that of Navigator 4 (though it is not 100 percent compatible with the standard). The scriptability of style sheet properties is a bit at odds with the first-generation CSS specification, which seemed to ignore the potential of scripting styles with JavaScript. Many CSS attribute names are hyphenated words (for example, text-align, z-index), even though hyphens are not allowed in identifier names in JavaScript. This necessitated conversion of the multiword CSS attribute names to camelCase JavaScript property names. Therefore, text-align becomes textAlign, and z-index becomes zIndex. You can access all of these properties through an element’s style property: document.all.elementID.style.stylePropertyName
or document.getElementById("myElement").style.stylePropertyName
One byproduct of the scriptability of style sheets in Internet Explorer 4 and later is what you might call the phantom page syndrome. This occurs when the layout of a page is handled after the primary HTML for the page has downloaded to the browser. As the page loads, not all content may be visible, or it may be in a visual jumble. An onload event handler in the page then triggers scripts to set styles or content for the page. Elements jump around to get to their final resting places. This may be disconcerting to some users who at first see a link to click, but by the time the cursor reaches the click location, the page has reflowed, thereby moving the link somewhere else on the page.
514
Chapter 25: Document Object Model Essentials
Note For Internet Explorer users with 32-bit Windows operating systems, Internet Explorer 4 includes some extra features in the object model that can enhance presentations. Filters are style sheet additives that offer a variety of visual effects on body text. For example, you can add a drop shadow or a glowing effect to text simply by applying filter styles to the text, or you can create the equivalent of a slide presentation by placing the content of each slide in a positioned div element. Although filters follow the CSS syntax, they are not part of the W3C specification.
Event bubbling Just as Netscape invented an event model for Navigator 4, so did Microsoft for Internet Explorer 4. Unfortunately for cross-browser scripters, the two event models are quite different. Instead of events trickling down the hierarchy to the target element, an Internet Explorer event starts at the target element and, unless instructed otherwise, bubbles up through the element containment hierarchy to reach the window object eventually. At any object along the way, an event handler can perform additional processing on that event, if desired. Therefore, if you want a single event handler to process all click events for the page, assign the event handler to the body or window object so the events reach those objects (provided that the event bubbling isn’t canceled by some other object along the containment hierarchy). Internet Explorer also has an event object (a property of the window object) that contains details about the event, such as the key pressed for a keyboard event and the location of a mouse event. Names for these properties are entirely different from the event object properties of Navigator 4. Despite what seems like incompatible, if not completely opposite, event models in Navigator 4 and Internet Explorer 4, you can make a single set of scripts handle events in both browsers; see Chapter 32, ‘‘Event Objects’’ and Chapter 59, ‘‘Application: Cross-Browser DHTML Map Puzzle’’ (on the CD-ROM) for examples. The Internet Explorer 4 event model continues to be the only model supported by Internet Explorer through version 7.
Internet Explorer 5+ Extensions With the release of Internet Explorer 5, Microsoft built more onto the proprietary object model it launched with Internet Explorer 4. Although the range of objects remained pretty much the same, the number of properties, methods, and event handlers for the objects increased dramatically. Some of those additions were added to meet some of the specifications of the W3C DOM (discussed in the next section), occasionally causing a bit of incompatibility with Internet Explorer 4. But Microsoft also pushed ahead with features only for Windows users that may not necessarily become industry standards: DHTML behaviors and HTML applications. A DHTML behavior is a chunk of script — saved as an external file — that defines some action (usually, a change of one or more style properties) that you can apply to any kind of element. The goal is to create a reusable component that you can load into any document whose elements require that behavior. As an example of a DHTML behavior, you can define a behavior that turns an element’s text to red whenever the cursor rolls atop it, and reverts the text to black when the cursor rolls out. When you assign the behavior to an element in the document (through CSS-like rule syntax), the element picks up that behavior and responds to the user accordingly. You can apply that same behavior to any element(s) in the document.
515
Part IV: Document Objects Reference
Cross-Reference You can see an example of a DHTML behavior in Chapter 26, in the description of the addBehavior() method; you can read an extended discussion in Chapter 50 (on the CD-ROM).
HTML applications (HTAs, in Microsoft parlance) are HTML files that include an XML element known as the hta:application element. You can download an HTA to Internet Explorer 5 or later from the server as though it were a web page (although its file extension is .hta rather than .htm or .html). A user can also install an HTA on a client machine so that it behaves very much like an application, with a desktop icon and significant control over the look of the window. HTAs are granted greater security privileges on the client so that this application can behave more like a regular program. In fact, you can elect to turn off the system menu bar and use DHTML techniques to build your own menu bar for the application. Implementation details of HTAs are beyond the scope of this book, but you should be aware of their existence. More information is available at http://msdn.microsoft.com.
The W3C DOM Conflicting browser object models from Netscape and Microsoft made life difficult for developers. Scripters craved a standard that would serve as a common denominator, much as HTML and CSS standards did for content and styles. The W3C took up the challenge of creating a DOM standard: the W3C DOM. The charter of the W3C DOM working group was to create a DOM that could be applied to both HTML and XML documents. Because an XML document can have tags of virtually any name (as defined by a Document Type Definition or XML Schema), it has no intrinsic structure or fixed vocabulary of elements, as an HTML document does. As a result, the DOM specification had to accommodate the known structure of HTML (as defined in the HTML 4 specification), as well as the unknown structure of an XML document. To make this work effectively, the working group divided the DOM specification into two sections. The first, called the Core DOM, defines specifications for the basic document structure that HTML and XML documents share. This includes notions of a document containing elements that have tag names and attributes; an element is capable of containing zero or more other elements. The second part of the DOM specification addresses the elements and other characteristics that apply only to HTML. The HTML portion inherits all the features of the Core DOM, while providing a measure of backward compatibility to object models already implemented in legacy browsers and providing a framework for new features. It is important for veteran scripters to recognize that the W3C DOM does not specify all features from existing browser object models. Many features of the Internet Explorer 4 (and later) object model are not part of the W3C DOM specification. This means that if you are comfortable in the Internet Explorer environment and wish to shift your focus to writing for the W3C DOM spec, you have to change some practices, as highlighted in this chapter. In many respects, especially with regard to DHTML applications, the W3C DOM is an entirely new DOM with new concepts that you must grasp before you can successfully script in the environment. By the same token, you should be aware that whereas Mozilla-based browsers go to great lengths to implement all of DOM Level 1 and most of Level 2, Microsoft (for whatever reason) features only a partial implementation of the W3C DOM through Internet Explorer 5.5. Although IE6 and
516
Chapter 25: Document Object Model Essentials
later versions implement more W3C DOM features, some important parts — notably, W3C DOM events — are missing. Other modern browsers, such as Chrome 1+, Safari 1.3+, and Opera 9+, provide comprehensive W3C DOM support and have largely closed the gap to compete with Mozilla in terms of supporting the W3C DOM.
DOM levels Like most W3C specifications, one version is rarely enough. The job of the DOM working group was too large to be swallowed whole in one sitting. Therefore, the DOM is a continually evolving specification. The timeline of specification releases rarely coincides with browser releases. Therefore, it is very common for any given browser release to include only some of the most recent W3C version. The first formal specification, DOM Level 1, was released well after NN4 and IE4 shipped. The HTML portion of Level 1 includes the so-called DOM Level 0 (there is no published standard by that name). This is essentially the object model as implemented in Navigator 3 (and for the most part in Internet Explorer 3, plus image objects). Perhaps the most significant omission from Level 1 is an event model (it ignores even the simple event model implemented in NN2 and IE3). DOM Level 2 builds on the work of Level 1. In addition to several enhancements of both the Core and HTML portions of Level 1, Level 2 adds significant new sections (published as separate modules) on the event model, ways of inspecting a document’s hierarchy, XML namespaces, text ranges, style sheets, and style properties. Some modules of the Level 3 DOM have reached Recommendation status. Although IE is still a ways off from implementation to any significant degree, the other major browsers have at least partially implemented some of the modules, including some that are still in working draft status.
What stays the same By adopting DOM Level 0 as the starting point of the HTML portion of the DOM, the W3C provided a way for a lot of existing script code to work even in a W3C DOM-compatible browser. Every object you see in the original object model, starting with the document object (see Figure 25-1) plus the image object, are in DOM Level 0. Almost all of the same object properties and methods are also available. More important, when you consider the changes to referencing other elements in the W3C DOM, we’re lucky that the old ways of referencing objects — such as forms, form control elements, and images — still work. Had the working group started with a clean slate, it is unlikely that the document object would have been given properties consisting of arrays of forms, links, and images. The only potential problems you could encounter with your existing code have to do with a handful of properties that used to belong to the document object. In the new DOM, four style-related properties of the document object (alinkColor, bgColor, linkColor, and vlinkColor) become properties of the body object (referenced as document.body). In addition, the three link color properties pick up new names in the process (aLink, link, and vLink). It appears, however, that for now, IE6 and Moz1 maintain backward compatibility with the older document object color properties. Also note that the DOM specification concerns itself only with the document and its content. Objects such as window, navigator, and screen are not part of the DOM specification through Level 2. Scripters are still at the mercy of browser makers for compatibility in these areas.
517
Part IV: Document Objects Reference
What isn’t available As mentioned earlier, the W3C DOM is not simply a restatement of existing browser specifications. Many convenience features of the Internet Explorer and Netscape Navigator object models do not appear in the W3C DOM. If you developed DHTML content in Internet Explorer 4 or later or in Navigator 4, you had to learn how to get along without some of these conveniences. The Navigator 4 experiment with the tag was not successful in the W3C process. As a result, both the tag and the scripting conventions surrounding it do not exist in the W3C DOM. To some scripters’ relief, the document.layerName referencing scenario (even more complex with nested layers) disappears from the object model. A positioned element is treated as just another element with some special style sheet attributes that enable you to move it anywhere on the page, stack it amid other positioned elements, or hide it from view. Among popular Internet Explorer 4+ features missing from the W3C DOM are the document.all collection of HTML elements and four element properties that facilitate dynamic content: innerHTML, innerText, outerHTML, and outerText. W3C provides a new way for
acquiring an array of all elements in a document, but generating HTML content to replace existing content or to be inserted in a document requires a tedious sequence of statements (see the section ‘‘New DOM concepts,’’ later in this chapter). All the new browsers, however, have implemented the innerHTML property for HTML element objects, and with the exception of Firefox, have implemented the other three properties.
New HTML practices Exploitation of DHTML possibilities in the W3C DOM relies on modern HTML practices that by now have been adopted by the majority of HTML authors. At the core of these practices (espoused by the HTML 4 specification) is making sure that all content is within an HTML container of some kind. Therefore, instead of using the
tag as a separator between blocks of running text, surround each paragraph of the running text with a
...
tag set. If you don’t do it, the browser treats each
tag as the beginning of a paragraph and ends the paragraph element just before the next
tag or other block-level element. Although browsers continue to accept the omission of certain end tags (for td, tr, and li elements, for instance) for backward compatibility, it is best to get into the habit of supplying these end tags if for no other reason than that they help you visualize where an element’s sphere of influence truly begins and ends. Applying this as a best practice also means your code will validate. Any element that you intend to script — whether to change its content or its style — should have an identifier assigned to the element’s id attribute. The identifier should be a unique value within the context of the current web page. Form control elements still require name attributes if you submit the form content to a server. But you can freely assign the same or a different identifier value to a control’s id attribute. Scripts can use either the id or the document.formReference.elementName reference to reach a control object. Identifiers are essentially the same as the values you assign to the name attributes of form and form input elements. Following the same rules for the name attribute value, an id identifier must be a single word (no whitespace); it cannot begin with a numeral (to prevent conflicts in JavaScript); and it should avoid punctuation symbols except for the underscore character.
New DOM concepts With the W3C DOM comes several concepts that may be new to you unless you have worked extensively with the terminology of tree hierarchies. Concepts that have the most impact on your scripting are new ways of referencing elements and nodes.
518
Chapter 25: Document Object Model Essentials
Element referencing Script references to objects in the DOM Level 0 are observed in the W3C DOM for backward compatibility. Therefore, a form input element whose name attribute is assigned the value userName is addressed just as it always is document.forms[0].userName
or document.formName.userName
But because all elements of a document are exposed to the document object, you can use the document object method designed to access any element whose ID is assigned. The method is document.getElementById(), and the sole parameter is a string version of the identifier of the object whose reference you want to get. To help put this in context with what you may have used with the Internet Explorer 4 object model, consider the following HTML paragraph tag:
...
In Internet Explorer 4 or later, you can reference this element with var elem = document.all.myParagraph;
Although the document.all collection is not implemented in the W3C DOM, the document object method (available in Internet Explorer 5 and later, Mozilla, Safari, and others) get ElementById() enables you to access any element by its ID: var elem = document.getElementById("myParagraph");
This method is considered the appropriate technique for referencing an element based upon its ID. Unfortunately for scripters, this method is difficult to type because it is case sensitive, so watch out for that ending lowercase d.
A hierarchy of nodes The issue surrounding containers (described earlier) comes into play for the underlying architecture of the W3C DOM. Every element or free-standing chunk of text in an HTML (or XML) document is an object that is contained by its next outermost container. Let’s look at a simple HTML document to see how this system works. Listing 25-1 is formatted to show the containment hierarchy of elements and string chunks. LISTING 25-1
A Simple HTML Document A Simple Page
continued
519
Part IV: Document Objects Reference
LISTING 25-1
(continued)
This is the one and only paragraph on the page.
What you don’t see in the listing is a representation of the document object. The document object exists automatically when this page loads into a browser. It is important that the document object encompasses everything you see in Listing 25-1. Therefore, the document object has a single nested element: the html element. The html element in turn has two nested elements: head and body. The head element contains the title element, whereas the title element contains a chunk of text. Down in the body element, the p element contains three pieces: a string chunk, the em element, and another string chunk. According to W3C DOM terminology, each container, stand-alone element (such as a br element), or text chunk is known as a node — a fundamental building block of the W3C DOM. Nodes have parent-child relationships when one container holds another. As in real life, parent-child relationships extend only between adjacent generations, so a node can have zero or more children. However, the number of third-generation nodes further nested within the family tree does not influence the number of children associated with a parent. Therefore, in Listing 25-1, the html node has two child nodes: head and body, which are siblings that have the same parent. The body element has one child (p), even though that child contains three children (two text nodes and an em element node). If you draw a hierarchical tree diagram of the document in Listing 25-1, it should look like the illustration in Figure 25-3. FIGURE 25-3
Tree diagram of nodes for the document in Listing 25-1. document +-- +-- | +-- | +--"A Simple Page" +-- +--
+--"This is the " +-- | +--"one and only" +--" paragraph on the page."
520
Chapter 25: Document Object Model Essentials
Note If the document’s source code contains a Document Type Definition (in a DOCTYPE element) above the tag, the browser treats that DOCTYPE node as a sibling of the HTML element node. In that case, the root document node contains two child nodes.
The W3C DOM (through Level 2) defines 12 different types of nodes, 7 of which have direct application in HTML documents. These seven types of nodes appear in Table 25-2; the rest apply to XML. Of the 7 types, the three most common are the document, element, and text types. All W3C DOM browsers (including Internet Explorer 5 and later, Mozilla, Safari, and others) implement the three common node types, whereas Mozilla implements all of them, IE6 implements all but one, and Safari 1 implements all but two. Applying the node types of Table 25-2 to the node diagram in Figure 25-3, you can see that the simple page consists of one document node, six element nodes, and four text nodes. TABLE 25-2
W3C DOM HTML-Related Node Types Type
Number
nodeName
nodeValue
Description
Element
1
tag name
Null
Attribute
2
attribute name
Text
3
Comment
IE
Moz
Safari
Any HTML or XML 6+ tagged element
1+
1+
attribute value
A name-value attribute pair in an element
6+
1+
1+
#text
text content
A text fragment contained by an element
6+
1+
1+
8
#comment
comment text
HTML comment
6+
1+
4+
Document
9
#document
Null
Root document object
6+
1+
1+
DocumentType
10
DOCTYPE
Null
DTD specification
No
1+
4+
Fragment
11
#documentfragment
Null
Series of one or more nodes outside the document
6+
1+
1+
Node properties A node has many properties, most of which are references to other nodes related to the current node. Table 25-3 lists all properties shared by all node types in DOM Level 2.
Note You can find all the properties shown in Table 25-3, that also show themselves to be implemented in Internet Explorer 6+ or Moz1+, in Chapter 26, in the listing of properties that all HTML element objects have in common. That’s because an HTML element, as a type of node, inherits all of the properties of the prototypical node.
521
Part IV: Document Objects Reference
TABLE 25-3
Node Object Properties (W3C DOM Level 2) Property
Value
Description
IE6Win+
IE5Mac+
Moz1
Safari1
nodeName
String
Varies with node type (see Table 25-2)
Yes
Yes
Yes
Yes
nodeValue
String
Varies with node type (see Table 25-2)
Yes
Yes
Yes
Yes
nodeType
Integer
Constant representing each type
Yes
Yes
Yes
Yes
parentNode
Object
Reference to next outermost container
Yes
Yes
Yes
Yes
childNodes
Array
All child nodes in source order
Yes
Yes
Yes
Yes
firstChild
Object
Reference to first child node
Yes
Yes
Yes
Yes
lastChild
Object
Reference to last child node
Yes
Yes
Yes
Yes
previous Sibling
Object
Reference to sibling node up in source order
Yes
Yes
Yes
Yes
nextSibling
Object
Reference to sibling node next in source order
Yes
Yes
Yes
Yes
attributes
NodeMap
Array of attribute nodes
Yes
Some
Yes
Yes
ownerDocument
Object
Containing document object
Yes
Yes
Yes
Yes
namespaceURI
String
URI to namespace definition (element and attribute nodes only)
Yes
No
Yes
Yes
Prefix
String
Namespace prefix (element and attribute nodes only)
Yes
No
Yes
Yes
localName
String
Applicable to namespace-affected nodes
Yes
No
Yes
Yes
522
Chapter 25: Document Object Model Essentials
To help you see the meanings of the key node properties, Table 25-4 shows the property values of several nodes in the simple page shown in Listing 25-1. For each node column, find the node in Figure 25-3, and then follow the list of property values for that node, comparing the values against the actual node structure in Figure 25-3. TABLE 25-4
Properties of Selected Nodes for a Simple HTML Document Properties
Nodes
document
html
p
"one and only"
nodeType
9
1
1
3
nodeName
#document
html
p
#text
nodeValue
Null
null
null
"one and only"
parentNode
Null
document
body
em
previousSibling
Null
null
null
null
nextSibling
Null
null
null
null
childNodes
Html
head body
"This is the" em "paragraph on the page."
(none)
firstChild
Html
head
"This is the"
null
lastChild
Html
body
"paragraph on the page."
null
The nodeType property is an integer that is helpful in scripts that iterate through an unknown collection of nodes. Most content in an HTML document is of type 1 (an HTML element) or 3 (a text node), with the outermost container, the document, of type 9. A node’s nodeName property is either the name of the node’s tag (for an HTML element) or a constant value (preceded by a # [hash mark], as shown in Table 25-2). And, while it may surprise some, the nodeValue property is null except for the text node type, in which case the value is the actual string of text of the node. In other words, for HTML elements, the W3C DOM does not expose a container’s HTML as a string.
The Object-Oriented W3C DOM If you are familiar with concepts of object-oriented (OO) programming, you will appreciate the OO tendencies in the way the W3C defines the DOM. The Node object includes sets of properties (see Table 25-3) and methods (see Table 25-5) that are inherited by every object based on the Node. Most of the objects that inherit the Node’s behavior have their own properties and/or methods that define their specific behaviors. Figure 25-4 shows (in W3C DOM terminology) the inheritance tree from the Node root object. Most items are defined in the Core DOM, whereas items shown in boldface are from the HTML DOM portion.
You can see from the preceding figure that individual HTML elements inherit properties and methods from the generic HTML element, which inherits from the Core Element object, which in turn inherits from the basic Node. It isn’t important to know the Node object inheritance to script the DOM. But it does help in understanding the ECMA Script Language Binding appendix of the W3C DOM recommendation, as well as how a simple element object winds up with so many properties and methods associated with it.
It is doubtful that you will use all of the relationship-oriented properties of a node, primarily because there is some overlap in how you can reach a particular node from any other. The parentNode property is important because it is a reference to the current node’s immediate container. Although the firstChild and lastChild properties point directly to the first and last children inside a container, most scripts generally use the childNodes property with array notation inside a for loop to iterate through child nodes. If there are no child nodes, the childNodes array has a length of zero.
Node methods Actions that modify the HTML content of a node in the W3C DOM world primarily involve the methods defined for the prototype Node. Table 25-5 shows the methods and their support in the W3C DOM–capable browsers. The important methods for modifying content are appendChild(), insertBefore(), removeChild(), and replaceChild(). Note, however, that all of these methods assume that the point of view for the action is from the parent of the nodes being affected by the methods.
524
Chapter 25: Document Object Model Essentials
For example, to delete an element (using removeChild()), you don’t invoke that method on the element being removed, but on its parent element. This leaves open the possibility of creating a library of utility functions that obviate having to know too much about the precise containment hierarchy of an element. A simple function that lets a script appear to delete an element actually does so from its parent: function removeElement(elemID) { var elem = document.getElementById(elemID); elem.parentNode.removeChild(elem); } TABLE 25-5
Node Object Methods (W3C DOM Level 2) Method
Description
IE5+
Moz1
Safari 1
appendChild(newChild)
Adds child node to end of current node
Yes
Yes
Yes
cloneNode(deep)
Grabs a copy of the current node (optionally with children)
Yes
Yes
Yes
hasChildNodes()
Determines whether current node has children (Boolean)
Yes
Yes
Yes
insertBefore(new, ref)
Inserts new child in front of another child
Yes
Yes
Yes
removeChild(old)
Deletes one child
Yes
Yes
Yes
replaceChild(new, old)
Replaces an old child with a new one
Yes
Yes
Yes
isSupported(feature, version)
Determines whether the node supports a particular feature
No
Yes
Yes
If this seems like a long way to go to accomplish the same result as setting the outerHTML property of an Internet Explorer 4 or later object to empty, you are right. Although some of this convolution makes sense for XML, the W3C working group doesn’t seem to have HTML scripters’ best interests in mind, unfortunately. All is not lost, however, as you see later in this chapter.
Generating new node content The final point about the node structure of the W3C DOM focuses on the similarly gnarled way scripters must go about generating content that they want to add or replace on a page. For text-only changes (for example, the text inside a table cell), there is both an easy and a hard way to perform the task. For HTML changes, there is only the hard way (plus a handy workaround discussed later). Let’s look at the hard way first and then pick up the easy way for text changes.
525
Part IV: Document Objects Reference
To generate a new node in the DOM, you look to the variety of methods that are defined for the Core DOM’s document object (and are therefore inherited by the HTML document object). A node creation method is defined for nearly every node type in the DOM. The two important ones for HTML documents are createElement() and createTextNode(). The first generates an element with whatever tag name (string) you pass as a parameter; the second generates a text node with whatever text you pass. When you first create a new element, it exists only in the browser’s memory and not as part of the document containment hierarchy. Moreover, the result of the createElement() method is a reference to an empty element, except for the name of the tag. For example, to create a new p element, use var newElem = document.createElement("p");
The new element has no ID, attributes, or any content. To assign some attributes to this element, you can use the setAttribute() method (a method of every element object) or assign a value to the object’s corresponding property. For example, to assign an identifier to the new element, use either newElem.setAttribute("id", "newP");
or newElem.id = "newP";
Both ways are perfectly legal. Even though the element has an ID at this point, it is not yet part of the document, so you cannot retrieve it via the document.getElementById() method. To add some content to the paragraph, you next generate a text node as a separate object: var newText = document.createTextNode("This is the second paragraph.");
Again, this node is just sitting around in memory waiting for you to apply it as a child of some other node. To make this text the content of the new paragraph, you can append the node as a child of the paragraph element that is still in memory: newElem.appendChild(newText);
If you were able to inspect the HTML that represents the new paragraph element, it would look like the following:
This is the second paragraph.
The new paragraph element is ready for insertion into a document. Using the document shown in Listing 25-1, you can append it as a child of the body element: document.body.appendChild(newElem);
At last, the new element is part of the document containment hierarchy. Now you can reference it just like any other element in the document.
526
Chapter 25: Document Object Model Essentials
Replacing node content The addition of the paragraph shown in the last section requires a change to a portion of the text in the original paragraph (since the first paragraph is no longer the one and only paragraph on the page). As mentioned earlier, you can perform text changes via the replaceChild() method or by assigning new text to a text node’s nodeValue property. Let’s see how each approach works to change the text of the first paragraph’s em element from one and only to first. To use replaceChild(), a script first must generate a valid text node with the new text: var newText = document.createTextNode("first");
The next step is to use the replaceChild() method. But recall that the point of view for this method is the parent of the child being replaced. The child here is the text node inside the em element, so you must invoke the replaceChild() method on the em element. Also, the replaceChild() method requires two parameters. The first parameter is the new node; the second is a reference to the node to be replaced. Because the script statements get pretty long with the getElementById() method, an intermediate step grabs a reference to the text node inside the em element: var oldChild = document.getElementById("emphasis1").childNodes[0];
Now the script is ready to invoke the replaceChild() method on the em element, swapping the old text node with the new: document.getElementById("emphasis1").replaceChild(newText, oldChild);
If you want to capture the old node before it disappears, be aware that the replaceChild() method returns a reference to the replaced node (which is only in memory at this point and not part of the document node hierarchy). You can assign the method statement to a variable and use that old node somewhere else, if needed. This may seem like a long way to go; it is, especially if the HTML you are generating is complex. Fortunately, you can take a simpler approach for replacing text nodes. All it requires is a reference to the text node being replaced. You can assign that node’s nodeValue property its new string value: document.getElementById("emphasis1").childNodes[0].nodeValue = "first";
When an element’s content is entirely text (for example, a table cell that already has a text node in it), this is the most streamlined way to swap text on the fly using W3C DOM syntax. This doesn’t work for the creation of the second paragraph text earlier in this chapter because the text node did not exist yet. The createTextNode() method had to create it explicitly. Also remember that a text node does not have any inherent style associated with it. The style of the containing HTML element governs the style of the text. If you want to change not only the text node’s text, but also how it looks, you have to modify the style property of the text node’s parent element. Browsers that perform these kinds of content swaps and style changes automatically reflow the page to accommodate changes in the size of the content. To summarize, Listing 25-2 is a live version of the modifications made to the original document shown in Listing 25-1. The new version includes a button and a script that makes the changes described throughout this discussion of nodes. Reload the page to start over.
527
Part IV: Document Objects Reference
LISTING 25-2
Adding/Replacing DOM Content A Simple Page function modify() { var newElem = document.createElement("p"); newElem.id = "newP"; var newText = document.createTextNode("This is the second paragraph."); newElem.appendChild(newText); document.body.appendChild(newElem); document.getElementById("emphasis1").childNodes[0].nodeValue = "first"; } Add/Replace Text
This is the one and only paragraph on the page.
Cross-Reference Chapter 26 details node properties and methods that are inherited by all HTML elements. Most are implemented in all modern W3C DOM browsers. Also look to the reference material for the document object in Chapter 29 for other valuable W3C DOM methods.
A de facto standard: innerHTML Microsoft was the first to implement the innerHTML property of all element objects starting with Internet Explorer 4. Although the W3C DOM has not supported this property, scripters frequently find it more convenient to modify content dynamically by way of a string containing HTML markup than by creating and assembling element and text nodes. As a result, most modern W3C DOM browsers, including Moz1 and Safari 1, support the read/write innerHTML property of all element objects as a de facto standard. When you assign a string containing HTML markup to the innerHTML of an existing element, the browser automatically inserts the newly rendered elements into the document node tree. You may also use innerHTML with unmarked text to perform the equivalent of the Internet Explorer–only innerText property.
528
Chapter 25: Document Object Model Essentials
Despite the apparent convenience of the innerHTML property compared with the step-by-step process of manipulating element and text node objects, browsers operate on nodes much more efficiently than on assembly of long strings. This is one case where less JavaScript code does not necessarily translate to greater efficiency.
Static W3C DOM HTML objects The Moz1+ DOM (but unfortunately, not Internet Explorer 5 or later) adheres to the core JavaScript notion of prototype inheritance with respect to the object model. When a page loads into a Moz1+ browser, the browser creates HTML objects based on the prototypes of each object defined by the W3C DOM. For example, if you use The Evaluator Sr. (discussed in Chapter 4, ‘‘JavaScript Essentials’’) to see what kind of object the myP paragraph object is — enter document.getElementById("myP") in the top text box and click the Evaluate button — it reports that the object is based on the HTMLParagraphElement object of the DOM. Every instance of a p element object in the page inherits its default properties and methods from HTMLParagraphElement (which in turn inherits from HTMLElement, Element, and Node objects — all detailed in the JavaScript binding appendix of the W3C DOM specification). You can use scripting to add properties to the prototypes of some of these static objects. To do so, you must use new features added to Moz1+ that are a part of JavaScript 1.5 and ECMAScript 5. Two new methods, __defineGetter__() and __defineSetter__(), enable you to assign functions to a custom property of an object.
Note These methods are Mozilla specific. To prevent their collision with standardized implementations of these features in ECMAScript, the underscore characters on either side of the method name are pairs of underscore characters.
The functions execute whenever the property is read (the function assigned via the __defineGetter__() method) or modified (the function assigned through the __defineSetter__() method). The common way to define these functions is in the form of an anonymous function (see Chapter 23). The formats for the two statements that assign these behaviors to an object prototype are as follows: object.prototype.__defineGetter__("propName", function([param1[,...[,paramN]]]) { // statements return returnValue; }) object.prototype.__defineSetter__("propName", function([param1[,...[,paramN]]]) { // statements return returnValue; })
The example in Listing 25-3 demonstrates how to add a read-only property to every HTML element object in the current document. The property, called childNodeDetail, returns an object. The object has two properties: one for the number of element child nodes and one for the number of text child nodes. Note that the this keyword in the function definition is a reference to the object for which the property is calculated. And because the function runs each time a script statement reads
529
Part IV: Document Objects Reference
the property, any scripted changes to the content after the page loads are reflected in the returned property value. LISTING 25-3
Adding a Read-Only Prototype Property to All HTML Element Objects if (HTMLElement) { HTMLElement.prototype.__defineGetter__("childNodeDetail", function() { var result = {elementNodes:0, textNodes:0 } for (var i = 0; i < this.childNodes.length; i++) { switch (this.childNodes[i].nodeType) { case 1: result.elementNodes++; break; case 3: result.textNodes++; break; } } return result; }) }
To access the property, use it like any other property of the object. For example: var BodyNodeDetail = document.body.childNodeDetail;
The returned value in this example is an object, so you use regular JavaScript syntax to access one of the property values: var BodyElemNodesCount = document.body.childNodeDetail.elementNodes;
Bidirectional event model Despite the seemingly conflicting event models of NN4 (trickle down) and IE4 (bubble up), the W3C DOM event model (defined in Level 2) manages to employ both event propagation models. This gives the scripter the choice of where along an event’s propagation path the event gets processed. To prevent conflicts with existing event model terminology, the W3C model invents many new terms for properties and new methods for events. Some coding probably requires W3C DOM–specific handling in a page aimed at multiple object models. The W3C event model also introduces a new concept called the event listener. An event listener is essentially a mechanism that instructs an object to respond to a particular kind of event — very much
530
Chapter 25: Document Object Model Essentials
like the way the event handler attributes of HTML tags respond to events. But the DOM recommendation points out that it prefers a more script-oriented way of assigning event listeners: the addEventListener() method available for every node in the document hierarchy. Through this method, you advise the browser whether to force an event to bubble up the hierarchy (the default behavior that is also in effect if you use the HTML attribute type of event handler) or to be captured at a higher level. Functions invoked by the event listener receive a single parameter consisting of the event object whose properties contain contextual details about the event (details such as the position of a mouse click, character code of a keyboard key, or a reference to the target object). For example, if a form includes a button whose job is to invoke a calculation function, the W3C DOM prefers the following way of assigning the event handler: document.getElementById("calcButton").addEventListener("click", doCalc, false);
The addEventListener() method takes three parameters. The first parameter is a string of the event to listen for; the second is a reference to the function to be invoked when that event fires; and the third parameter is a Boolean value. When you set this Boolean value to true, it turns on event capture whenever this event is directed to this target. The function then takes its cue from the event object passed as the parameter: function doCalc(evt) { // get shortcut reference to input button’s form var form = evt.target.form; var results = 0; // other statements to do the calculation // form.result.value = results; }
To modify an event listener, you use the removeEventListener() method to get rid of the old listener, and then employ addEventListener() with different parameters to assign the new one. Preventing an event from performing its default action is also a different procedure in the W3C event model than in Internet Explorer. In Internet Explorer 4 (as well as Navigator 3 and 4), you can cancel the default action by allowing the event handler to evaluate to return false. Although this still works in Internet Explorer 5 and later, Microsoft includes another property of the window.event object, called returnValue. Setting that property to false anywhere in the function invoked by the event handler also kills the event before it does its normal job. But the W3C event model uses a method of the event object, preventDefault(), to keep the event from its normal task. You can invoke this method anywhere in the function that executes when the event fires. Detailed information about an event is contained in an event object that must be passed to an event handler function where details may be read. If you assign event handlers via the W3C DOM addEventListener() method or an event handler property, the event object is passed automatically as the sole parameter to the event handler function. Include a parameter variable to catch the incoming parameter: function swap(evt) { // statements here to work with W3C DOM event object }
531
Part IV: Document Objects Reference
But if you assign events through a tag attribute, you must explicitly pass the event object in the call to the function:
Unfortunately, as of Internet Explorer 8 for Windows and Internet Explorer 5 for Macintosh, the W3C DOM event model has yet to be supported by Microsoft. You can, however, make the Internet Explorer and W3C event models work together if you assign event handlers by way of object properties or tag attributes, and throw in a little object detection as described later in this chapter, and in more detail in Chapter 32.
Scripting Trends Although browser scripting had humble beginnings as a way to put some intelligence into form controls, the capabilities of the JavaScript language and DOM have inspired many a web developer to create what are essentially applications. Popular implementations of web-based email systems use extensive scripting and background communication with the server to keep pages updated quickly without the need to fetch and re-render the complete page each time you delete a message from the inbox list. It’s not uncommon for large projects to involve multiple scripters (along with specialists in CSS, server programming, artists, and writers). Wrangling all the code can be a chore.
Separating content from scripting Those who use CSS to style their sites have learned that separating style definitions from the HTML markup makes a huge improvement in productivity when it comes time to change colors or font specifications throughout a site. Instead of having to modify hundreds of tag specifications scattered around the site, all it takes is a simple tweak of a single CSS rule in one .css file for that change to be implemented immediately across the board. The notion of using HTML purely for a page’s structure has also impacted scripting. It is rare these days for a professional scripter to put an event handler attribute inside an HTML tag. That would be considered too much mixing of content with behavior. In other words, the HTML markup should be able to stand on its own so that those with nonscriptable browsers (including those with vision or motor disabilities who use specialized browsers) can still get the fundamental information provided by the page. Any scripting that impacts the display or behavior of the page is added to the page after the HTML markup has loaded and rendered. Even assigning events to elements is done by script after the page load. Script code is more commonly linked into a page from an external .js file. This isn’t part of the separation of content and scripts trend, but a practice that offers many benefits, such as the same code being instantly usable on multiple pages. Additionally, when projects involve many code chefs, scripters can work on their code while writers work on the HTML and designers work on their external CSS code.
Note You will see lots of examples in this book that use event handler attributes inside tags, and scripts embedded within the page. This approach is used primarily for simplicity in demonstrating a language or DOM feature.
532
Chapter 25: Document Object Model Essentials
Using the W3C DOM where possible Basic support for W3C DOM element referencing and content manipulation has been implemented in mainstream browsers for so long that you can be assured that composing scripts for that model will work for the bulk of your visitors. That’s not to say you can assume that every visitor is equipped that way, but the hassles that scripters used to endure to support conflicting object models are behind us for the most part. The days of writing extensive branching code for IE and Netscape are not-so-fond memories. You still want to use object detection techniques to guard against the occasional old browser that stops by. That’s where the technique of assigning event handlers by scripts can save a lot of headaches. Except for some initializations that might occur while the page loads, most script execution in a web page occurs at the instigation of an event: A user clicks a button, types something in a text box, chooses from a select element, and so on. You can prevent older browsers from tripping up on W3C DOM syntax by doing your fundamental object detection right in the event assignment code, as in the following simplified example: function setUpEvents() { if (document.getElementById) { // statements to bind events to elements } } window.onload = setUpEvents;
Now, browsers that don’t have even minimum support for the W3C DOM won’t generate script errors when users click or type, because those events won’t be assigned for those browsers. Then scripts that survive your object detection query can also modify the page, as you saw in Listing 4-2 in Chapter 4.
Handling events You will still find some places where the W3C DOM isn’t enough. This is particularly true in processing events, where Internet Explorer (at least through version 8) does not support the W3C DOM way of getting details about an event to the event handler function. The W3C DOM automatically passes the event object as a parameter to a handler function. In the Internet Explorer model, the event object is a property of the window object. Therefore, your functions have to equalize the differences where necessary. For example, to obtain a single variable representing the event object, regardless of browser, you can use a construction similar to the following: function calculate(evt) { evt = (evt) ? evt : window.event; // more statements to process event }
Additional branching is necessary to inspect important details of the event. For example, the Internet Explorer event object property pointing to the object that received the event is called srcElement, whereas the W3C DOM version is called target. Again, a little bit of equalizing code in the event handler function can handle the disparity. When your script has a reference to the element receiving
533
Part IV: Document Objects Reference
the event, you can start using W3C DOM properties and methods of the element, because Internet Explorer supports those. You can find more details on event objects in Chapter 32.
Standards Compatibility Modes (DOCTYPE Switching) Both Microsoft and Netscape/Mozilla discovered that they had, over time, implemented CSS features in ways that ultimately differed from the published standards that came later (usually after much wrangling among working-group members). To compensate for these differences and make a clean break to be compatible with the standards, the major browser makers decided to let the page author’s choice of header element details determine whether the document was designed to follow the old way (sometimes called quirks mode) or the standards-compatible way. The tactic, known informally as DOCTYPE switching, is implemented in Internet Explorer 6 and later, Internet Explorer 5 for the Mac, all Mozilla-based browsers, and all WebKit-based browsers. Although most of the differences between the two modes are small, there are some significant differences between the two modes in Internet Explorer 6 and later, particularly when styles or DHTML scripts rely on elements designed with borders, margins, and padding. Microsoft’s original box model measured the dimensions of elements in a way that differed from the eventual CSS standard. To place the affected browsers in CSS standards–compatible mode, you should include a element at the top of every document that specifies any of the following details (the first statement is for HTML5):
534
Chapter 25: Document Object Model Essentials
Be aware, however, that older versions of Internet Explorer for Windows, such as Internet Explorer 5 or Internet Explorer 5.5, are ignorant of the standards-compatible mode and will use the old Microsoft quirks mode regardless of the setting. But using a standards-compliant mode DOCTYPE is more likely to force your content and style sheets to render similarly across the latest browsers.
Where to Go from Here These past two chapters provided an overview of the core language and object model issues that anyone designing pages that use JavaScript must confront. The goal here is to stimulate your own thinking about how to embrace or discard levels of compatibility with your pages as you balance your desire to generate cool pages and serve your audience. From here on, the difficult choices are up to you. To help you choose the objects, properties, methods, and event handlers that best suit your requirements, all the chapters in Part III and the rest of Part IV provide in-depth references to the DOM and core JavaScript language features. Observe the compatibility ratings for each language term very carefully to help you determine which features best suit your audience’s browsers. Most example listings are complete HTML pages that you can load in various browsers to see how they work. Many others invite you to explore how things work through The Evaluator Sr. (see Chapter 4). Play around with the files, making modifications to build your own applications or expanding your working knowledge of JavaScript in the browser environment. The language and object models have grown in the handful of years they have been in existence. The amount of language vocabulary has increased astronomically. It takes time to drink it all in and feel comfortable that you are aware of the powers available to you. Don’t worry about memorizing the vocabulary. It’s more important to acquaint yourself with the features and come back later when you need the implementation details. Be patient. Be persistent. The reward will come.
535
Generic HTML Element Objects
T
he object model specifications implemented in Internet Explorer 4+ and W3C (Mozilla-based and WebKit-based) browsers feature a large set of scriptable objects that represent what we often call generic HTML elements. Generic elements can be divided into two groups. One group, such as the band strike elements, defines font styles to be applied to enclosed sequences of text. The need for these elements (and the objects that represent them) is all but gone due to more page designers using style sheets. The second group of elements assigns context to content within their start and end tags. Examples of contextual elements include h1, blockquote, and the ubiquitous p element. Although browsers sometimes have consistent visual ways of rendering contextual elements by default (for example, the large bold font of an tag), the specific rendering is not the intended purpose of the tags. No formal standard dictates that text within an em element must be italicized: The style simply has become the custom since the very early days of browsers. All of these generic elements share a large number of scriptable properties, methods, and event handlers. The sharing extends not only among generic elements, but also among virtually every renderable element — even if it has additional, element-specific properties, methods, and/or event handlers that we cover in depth in other chapters of this reference. Rather than repeat the details of these shared properties, methods, and event handlers for each object throughout this reference, we describe them in detail only in this chapter (unless there is a special behavior, bug, or trick associated with the item in some object described elsewhere). In succeeding reference chapters, each object description includes a list of the object’s properties, methods, and event handlers, but we do not list shared items over and over (making it hard to find items that are unique to a particular element). Instead, you see a pointer back to this chapter for the items in common with generic HTML element objects.
Generic Objects Table 26-1 lists all of the objects that we treat in this reference as generic objects. All of these objects share the properties, methods, and event handlers described in succeeding sections and have no special items that require additional coverage elsewhere in this book.
537
IN THIS CHAPTER Working with HTML element objects Common properties and methods Event handlers of all element objects
Part IV: Document Objects Reference elementObject TABLE 26-1
Generic HTML Element Objects Formatting Objects
Contextual Objects
b
acronym
big
address
center
cite
i
code
nobr
dfn
rt
del
ruby
div
s
em
small
ins
strike
kbd
sub
listing
sup
p
tt
plaintext
u
pre
wbr
samp span strong var xmp
Properties
Methods
Event Handlers
accessKey
addBehavior()
onactivate
all[]
addEventListener()
onafterupdate
attributes[]
appendChild()
onbeforecopy
baseURI
applyElement()
onbeforecut
behaviorUrns[]
attachEvent()
onbeforedeactivate
canHaveChildren
blur()
onbeforeeditfocus
canHaveHTML
clearAttributes()
onbeforepaste
538
Chapter 26: Generic HTML Element Objects elementObject Properties
Methods
Event Handlers
childNodes[]
click()
onbeforeupdate
children
cloneNode()
onblur
cite
compareDocumentPosition()
oncellchange
className
componentFromPoint()
onclick
clientHeight
contains()
oncontextmenu
clientLeft
createControlRange()
oncontrolselect
clientTop
detachEvent()
oncopy
clientWidth
dispatchEvent()
oncut
contentEditable
doScroll()
ondataavailable
currentStyle
dragDrop()
ondatasetchanged
dateTime
fireEvent()
ondatasetcomplete
dataFld
focus()
ondblclick
dataFormatAs
getAdjacentText()
ondeactivate
dataSrc
getAttribute()
ondrag
dir
getAttributeNode()
ondragend
disabled
getAttributeNodeNS()
ondragenter
document
getAttributeNS()
ondragleave
filters[]
getBoundingClientRect()
ondragover
firstChild
getClientRects()
ondragstart
height
getElementsByTagName()
ondrop
hideFocus
getElementsByTagNameNS()
onerrorupdate
id
getExpression()
onfilterchange
innerHTML
getFeature()
onfocus
innerText
getUserData()
onfocusin
isContentEditable
hasAttribute()
onfocusout
isDisabled
hasAttributeNS()
onhelp
isMultiLine
hasAttributes()
onkeydown
isTextEdit
hasChildNodes()
onkeypress
continued
539
Part IV: Document Objects Reference elementObject TABLE 26-1
(continued )
Properties
Methods
Event Handlers
lang
insertAdjacentElement()
onkeyup
language
insertAdjacentHTML()
onlayoutcomplete
lastChild
insertAdjacentText()
onlosecapture
length
insertBefore()
onmousedown
localName
isDefaultNamespace()
onmouseenter
namespaceURI
isEqualNode()
onmouseleave
nextSibling
isSameNode()
onmousemove
nodeName
isSupported()
onmouseout
nodeType
item()
onmouseover
nodeValue
lookupNamespaceURI()
onmouseup
offsetHeight
lookupPrefix()
onmousewheel
offsetLeft
mergeAttributes()
onmove
offsetParent
normalize()
onmoveend
offsetTop
releaseCapture()
onmovestart
offsetWidth
removeAttribute()
onpaste
outerHTML
removeAttributeNode()
onpropertychange
outerText
removeAttributeNS()
onreadystatechange
ownerDocument
removeBehavior()
onresize
parentElement
removeChild()
onresizeend
parentNode
removeEventListener()
onresizestart
parentTextEdit
removeExpression()
onrowenter
prefix
removeNode()
onrowexit
previousSibling
replaceAdjacentText()
onrowsdelete
readyState
replaceChild()
onrowsinserted
recordNumber
replaceNode()
onscroll
runtimeStyle
scrollIntoView()
onselectstart
scopeName
setActive()
scrollHeight
setAttribute()
scrollLeft
setAttributeNode()
540
Chapter 26: Generic HTML Element Objects elementObject.accessKey Properties
Methods
scrollTop
setAttributeNodeNS()
scrollWidth
setAttributeNS()
sourceIndex
setCapture()
style
setExpression()
tabIndex
setUserData()
tagName
swapNode()
tagUrn
tags()
textContent
toString()
title
urns()
Event Handlers
uniqueID unselectable width
Syntax To access element properties or methods, use this: (IE4+) [document.all.]objectID.property | method([parameters]) (IE5+/W3C) document.getElementById(objectID).property | method([parameters])
Note It’s important to note that unless you have the specific need of supporting IE4, which is highly unlikely at this point in time, you should rely solely on the latter approach of referencing element properties and methods via the getElementById() method.
About these objects All objects listed in Table 26-1 are document object model (DOM) representations of HTML elements that influence either the font style or the context of some HTML content. The large set of properties, methods, and event handlers associated with these objects also applies to virtually every other DOM object that represents an HTML element. Discussions about object details in this chapter apply to dozens of other objects described in succeeding chapters of this reference section.
Part IV: Document Objects Reference elementObject.accessKey For many elements, you can specify a keyboard character (letter, numeral, or punctuation symbol) that — when typed as an Alt+key combination (on the Win32 OS platform), a Ctrl+key combination (on the MacOS), or a Shift+Esc+key combination (on Opera) — brings focus to that element. An element that has focus is the one that is set to respond to keyboard activity. If the newly focused element is out of view in the document’s current scroll position, the document is scrolled to bring that focused element into view (also see the scrollIntoView() method). The character you specify can be an uppercase or lowercase value, but these values are not case sensitive. If you assign the same letter to more than one element, the user can cycle through all elements associated with that accessKey value. Internet Explorer gives some added powers to the accessKey property in some cases. For example, if you assign an accessKey value to a label element object, the focus is handed to the form element associated with that label. Also, when elements such as buttons have focus, pressing the spacebar acts the same as clicking the element with a mouse. Exercise some judgment in selecting characters for accessKey values. If you assign a letter that is normally used to access one of the browser’s built-in menus (for example, Alt+F for the File menu in IE), that accessKey setting overrides the browser’s normal behavior. To users who rely on keyboard access to menus, your control over that key combination can be disconcerting. In other browsers your accessKey assignment will not override the browser’s normal behavior.
Example Listing 26-1 shows an example of how to use the accessKey property to manipulate the keyboard interface for navigating a web page. When you load the script in Listing 26-1, adjust the height of the browser window so that you can see nothing below the second dividing rule. Enter any character in the Settings portion of the page and press Enter. (The Enter key may cause your computer to beep.) Pressing the Enter key does not do anything visible in your browser; it just assigns the character you entered into the textbox to the appropriate element. Then hold down the Alt (Windows) or Ctrl (Mac) key (or Shift+Esc keys in Opera) while pressing the same keyboard key. The element from below the second divider should come into view.
Note The property assignment event handling technique employed throughout the code in this chapter and much of the book is a deliberate simplification to make the code more readable. It is generally better to use the more modern approach of binding events using the addEventListener() (NN6+/Moz/W3C) or attachEvent() (IE5+) method. A modern cross-browser event handling technique is explained in detail in Chapter 32.
LISTING 26-1
Controlling the accessKey Property HTML: jsb26-01.html accessKey Property
542
Chapter 26: Generic HTML Element Objects elementObject.accessKey accessKey Property Lab Settings: Assign an accessKey value to the Button below and press Return: Assign an accessKey value to the Text Box below and press Return: Assign an accessKey value to the Table below (IE5.5+ only) and press Return: Then press Alt (Windows) or Control (Mac) or ShiftESC (Opera) + the key Size the browser window to view nothing lower than this line.
Quantity
Description
Price
4
Primary Widget
$14.96
10
Secondary Widget
$114.96
continued
543
Part IV: Document Objects Reference elementObject.all[ ] LISTING 26-1
(continued)
JavaScript: jsb26-01.js function assignKey(type, elem) { if (window.event) // IE, Opera, Safari, Chrome { if (window.event.keyCode == 13) { switch (type) { case "button": document.getElementById("access1").accessKey = elem.value; break; case "text": document.getElementById("access2").accessKey = elem.value; break; case "table": document.getElementById("myTable").accessKey = elem.value; } return false; } } }
Related Item: scrollIntoView() method
all[] Value: Array of nested element objects
Read-Only
Compatibility: WinIE4+, MacIE4+, NN-, Moz-, Safari+ (partial), Opera+, Chrome+ (partial) Originally exclusive to Internet Explorer, the all property is a collection (array) of every HTML element and (in IE5+) XML tag within the scope of the current object. Opera now supports it fully, while WebKit-based browsers (such as Safari and Chome) support it only as a property of the document object. Even so, you should strongly consider using the document.getElementById() method (as described in Chapter 29), which is the official W3C and cross-browser approach for referencing elements. The document.getElementById() method is supported in IE5+. Items in this array appear in source-code order, and the array is oblivious to element containment among the items. For HTML element containers, the source-code order is dependent on the position of the start tag for the element; end tags are not counted. But for XML tags, end tags appear as separate entries in the array. Every document.all collection contains objects for the html, head, title, and body element objects even if the actual HTML source code omits the tags. The object model creates these objects for every document that is loaded into a window or frame. Although the document.all reference may be the most common usage, the all property is available for any container element. For example, document.forms[0].all exposes all elements defined within the first form of a page.
544
Chapter 26: Generic HTML Element Objects elementObject.attributes[ ] You can access any element that has an identifier assigned to its id attribute by that identifier in string form (as well as by index integer). Rather than use the performance-costly eval() function to convert a string to an object reference, use the string value of the name as an array index value: var paragraph = document.all["myP"];
Internet Explorer enables you to use either square brackets or parentheses for single collection index values. Thus, the following two examples evaluate identically: var paragraph = document.all["myP"]; var paragraph = document.all("myP");
In the rare case that two or more elements within the all collection have the same ID, the syntax for the string index value returns a collection of just those identically named elements. But you can use a second argument (in parentheses) to signify the integer of the initial collection and thus single out a specific instance of that named element: var secondRadio = document.all("group0",1);
As a more readable alternative, you can use the item() method (described later in this chapter) to access the same kinds of items within a collection: var secondRadio = document.all.item("group0",1);
Also see the tags() method (later in this chapter) as a way to extract a set of elements from an all collection that matches a specific tag name.
Example Use The Evaluator (see Chapter 4) to experiment with the all collection. Enter the following statements one at a time in the lower text box, and review the results in the text area for each: document.all myTable.all myP.all
If you encounter a numbered element within a collection, you can explore that element to see which tag is associated with it. For example, if one of the results for the document.all collection says document.all.8=[object], enter the following statement in the topmost text box: document.all[8].tagName
Related Items: item(), tags(), document.getElementById() methods
attributes[] Value: Array of attribute object references
Read-Only
Compatibility: WinIE5+, MacIE5+, NN6+, Moz+, Safari+, Opera+, Chrome+ The attributes property consists of an array of attributes specified for an element. In IE5+, the attributes array contains an entry for every possible property that the browser has defined for its elements — even if the attribute is not set explicitly in the HTML tag. Also, any attributes that
545
Part IV: Document Objects Reference elementObject.attributes[ ] you add later via script facilities such as the setAttribute() method are not reflected in the attributes array. In other words, the IE5+ attributes array is fixed, using default values for all properties except those that you explicitly set as attributes in the HTML tag. Mozilla browsers’ attributes property returns an array that is a named node map (in W3C DOM terminology) — an object that has its own properties and methods to read and write attribute values. For example, you can use the getNamedItem(attrName) and item(index) methods on the array returned from the attributes property to access individual attribute objects via W3C DOM syntax. IE5 and Mozilla had different ideas about what an attribute object should be. Mozilla is dependent on the W3C DOM node inheritance model, discussed in Chapter 25. In the past, the larger set of properties in the W3C DOM node were solely supported by Mozilla. Now, as you can see, IE supports more of the W3C DOM. Table 26-2 shows the variety of properties of an attribute object as defined by the two object models. The WebKit-based browsers offer the same property support as Mozilla, while Opera lies in between. TABLE 26-2
Attribute Object Properties Property
IE5
Moz
Description
attributes
Yes
Yes
Array of nested attribute objects (null)
childNodes
No
Yes
Child node array
firstChild
No
Yes
First child node
lastChild
No
Yes
Last child node
localName
No
Yes
Name within current namespace
name
Yes
Yes
Attribute name
nameSpaceURI
Yes
Yes
XML namespace URI
nextSibling
Yes
Yes
Next sibling node
nodeName
Yes
Yes
Attribute name
nodeType
Yes
Yes
Node type (2)
nodeValue
Yes
Yes
Value assigned to attribute
ownerDocument
Yes
Yes
Document object reference
ownerElement
Yes
Yes
Element node reference
parentNode
Yes
Yes
Parent node reference
prefix
Yes
Yes
XML namespace prefix
previousSibling
Yes
Yes
Previous sibling node
specified
Yes
Yes
Whether attribute is explicitly specified (Boolean)
value
Yes
Yes
Value assigned to attribute
546
Chapter 26: Generic HTML Element Objects elementObject.canHaveChildren The most helpful property of an attribute object is the Boolean specified property. In IE, this lets you know whether the attribute is explicitly specified in the element’s tag. Because Mozilla returns only explicitly specified attributes in the attributes array, the value in Mozilla is always true. Most of the time, however, you’ll probably use an element object’s getAttribute() and setAttribute() methods to read and write attribute values.
Example Use The Evaluator (see Chapter 4) to examine the values of the attributes array for some of the elements in that document. Enter each of the following expressions in the bottom text box, and see the array contents in the Results text area for each: document.body.attributes document.getElementById("myP").attributes document.getElementById("myTable").attributes
If you have both IE5+ and a W3C DOM–compatible browser, compare the results you get for each of these expressions. To view the value of a single attribute in WinIE5+ by accessing the attributes array, enter the following statement in the top text box: document.getElementById("myForm2").attributes["name"].value
For W3C browsers, IE6+, and MacIE5, use the W3C DOM syntax: document.getElementById("myForm2").attributes.getNamedItem("name").value
Related Items: getAttribute(), mergeAttributes(), removeAttribute(), setAttribute() methods
baseURI Value: Full URI string
Read-Only
Compatibility: WinIE-, MacIE-, NN6+, Moz+, Safari+, Opera+, Chrome+ This property reveals the full path to the source from which the element was served. The property is handy in applications that import XML data, in which case the source of an XML element is likely different from the HTML page in which it is being processed.
behaviorUrns[] Value: Array of behavior URN strings
Read-Only
Compatibility: WinIE5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe Internet Explorer behaviorUrns property is designed to provide a list of addresses, in the form of URNs (Uniform Resource Names), of all behaviors assigned to the current object. If there are no behaviors, the array has a length of zero. In practice, however, IE5+ always returns an array of empty strings. Perhaps the potential exposure of URNs by script was deemed to be a privacy risk. Related Item: urns() method
Part IV: Document Objects Reference elementObject.canHaveChildren Useful in some dynamic content situations, the canHaveChildren property reveals whether a particular element is capable of containing a child (nested) element. Most elements that have start and end tags (particularly the generic elements covered in this chapter) can contain nested elements. A nested element is referred to as a child of its parent container.
Example Listing 26-2 shows an example of how to use the canHaveChildren property to visually identify elements on a page that can have nested elements. This example uses color to demonstrate the difference between an element that can have children and one that cannot. The first button sets the color style property of every visible element on the page to red. Thus, elements (including the normally non-childbearing ones such as hr and input) are affected by the color change. But if you reset the page and click the largest button, only those elements that can contain nested elements receive the color change. LISTING 26-2
Reading the canHaveChildren Property HTML: jsb26-02.html canHaveChildren Property canHaveChildren Property Lab Your basic checkbox
Quantity
Description
Price
548
Chapter 26: Generic HTML Element Objects elementObject.canHaveHTML
4
Primary Widget
$14.96
10
Secondary Widget
$114.96
JavaScript: jsb26-02.js function colorAll() { var elems = document.getElementsByTagName("*"); for (var i = 0; i < elems.length; i++) { elems[i].style.color = "red"; } } function colorChildBearing() { var elems = document.getElementsByTagName("*"); for (var i = 0; i < elems.length; i++) { if (elems[i].canHaveChildren) { elems[i].style.color = "red"; } } }
Compatibility: WinIE5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeNot all HTML elements are containers of HTML content. The canHaveHTML property lets scripts find out whether a particular object can accept HTML content, such as for insertion or replacement by object methods. The value for a p element, for example, is true. The value for a br element is false. The property is read-only for all elements except HTML Components, in which case it is read/write.
549
Part IV: Document Objects Reference elementObject.childNodes[ ]
Example Use The Evaluator (see Chapter 4) in WinIE5+ to experiment with the canHaveHTML property. Enter the following statements in the top text box, and observe the results: document.getElementById("input").canHaveHTML document.getElementById("myP").canHaveHTML
The first statement returns false because an input element (the top text box, in this case) cannot have nested HTML. But the myP element is a p element that gladly accepts HTML content. Related Items: appendChild(), insertAdjacentHTML(), insertBefore() methods
childNodes[] Value: Array of node objects
Read-Only
Compatibility: WinIE5+, MacIE5+, NN6+, Moz+, Safari+, Opera+, Chrome+ The childNodes property consists of an array of node objects contained by the current object. Note that child nodes consist of both element objects and text nodes. Therefore, depending on the content of the current object, the number of childNodes and children collections may be different.
Caution If you use the childNodes array in a for loop that iterates through a sequence of HTML (or XML) elements, watch out for the possibility that the browser treats source-code whitespace (blank lines between elements and even simple carriage returns between elements) as text nodes. This potential problem affects MacIE5 and W3C-based browsers. If present, these extra text nodes occur primarily surrounding block elements.
Note Most looping activity through the childNodes array aims to examine, count, or modify element nodes within the collection. If that is your script’s goal, test each node returned by the childNodes array, and verify that the nodeType property is 1 (element) before processing that node; otherwise, skip the node. The skeletal structure of such a loop follows:
for (var i = 0; i < myElem.childNodes.length; i++) { if (myElem.childNodes[i].nodeType == 1) { statements to work on element node i } } The presence of these phantom text nodes also impacts the nodes referenced by the firstChild and lastChild properties, described later in this chapter.
Example Listing 26-3 contains an example of how you might code a function that walks the child nodes of a given node. The walkChildNodes() function shown in the listing accumulates and returns a hierarchical list of child nodes from the point of view of the document’s HTML element (the default) or any element whose ID you pass as a string parameter. This function is embedded in The Evaluator so
550
Chapter 26: Generic HTML Element Objects elementObject.childNodes[ ] that you can inspect the child node hierarchy of that page or (when using evaluator.js for debugging as described in Chapter 48 on the CD-ROM) the node hierarchy within any page you have under construction. Try it out in The Evaluator by entering the following statements in the top text box: walkChildNodes() walkChildNodes(document.getElementById("myP"))
The results of this function show the nesting relationships among all child nodes within the scope of the initial object. It also shows the act of drilling down to further childNodes collections until all child nodes are exposed and catalogued. Text nodes are labeled accordingly. The first 15 characters of the actual text are placed in the results to help you identify the nodes when you compare the results against your HTML source code.
LISTING 26-3
Collecting Child Nodes function walkChildNodes(objRef, n) { var obj; if (objRef) { if (typeof objRef == "string") { obj = document.getElementById(objRef); } else { obj = objRef; } } else { obj = (document.body.parentElement) ? document.body.parentElement : document.body.parentNode; } var output = ""; var indent = ""; var i, group, txt; if (n) { for (i = 0; i < n; i++) { indent += "+---"; } } else
continued
551
Part IV: Document Objects Reference elementObject.children LISTING 26-3
(continued)
{ n = 0; output += "Child Nodes of \n=====================\n"; } group = obj.childNodes; for (i = 0; i < group.length; i++) { output += indent; switch (group[i].nodeType) { case 1: output += "\n"; break; case 3: txt = group[i].nodeValue.substr(0,15); output += "[Text:\"" + txt.replace(/[\r\n]/g,""); if (group[i].nodeValue.length > 15) { output += "..."; } output += "\"]\n"; break; case 8: output += "[!COMMENT!]\n"; break; default: output += "[Node Type = " + group[i].nodeType + "]\n"; } if (group[i].childNodes.length > 0) { output += walkChildNodes(group[i], n+1); } } return output; }
children Value: Array of element objects Compatibility: WinIE4+, MacIE4+, NN-, Moz+, Safari+, Opera+, Chrome+
552
Read-Only
Chapter 26: Generic HTML Element Objects elementObject.children The children property consists of an array of element objects contained by the current object. Unlike the childNodes property, children does not take into account text nodes, but focuses strictly on the HTML (and XML) element containment hierarchy from the point of view of the current object. Children exposed to the current object are immediate children only. If you want to get all element objects nested within the current object (regardless of how deeply nested they are), use the all collection instead.
Example Listing 26-4 shows how you can use the children property to walk the child nodes of a given node. This function accumulates and returns a hierarchical list of child elements from the point of view of the document’s HTML element (the default) or any element whose ID you pass as a string parameter. This function is embedded in The Evaluator so that you can inspect the parent–child hierarchy of that page or (when using evaluator.js for debugging as described in Chapter 48 on the CD-ROM) the element hierarchy within any page you have under construction. Try it out in The Evaluator by entering the following statements in the top text box: walkChildren("myTable")
Notice in this example that the walkChildren() function is called with the name of an element instead of a call to document.getElementId(). This reveals the flexibility of the walkChildren() function and how it can operate on either an object or the name of an object (element). The walkChildNodes() function in Listing 26-3 offers the same flexibility. The results of the walkChildren() function show the nesting relationships among all parent and child elements within the scope of the initial object. It also shows the act of drilling down to further children collections until all child elements are exposed and cataloged. The element tags also display their id and/or name attribute values if any are assigned to the elements in the HTML source code. LISTING 26-4
Collecting Child Elements function walkChildren(objRef, n) { var obj; if (objRef) { if (typeof objRef == "string") { obj = document.getElementById(objRef); } else { obj = objRef; }
continued
553
Part IV: Document Objects Reference elementObject.cite LISTING 26-4
(continued)
} else { obj = document.body.parentElement; } var output = ""; var indent = ""; var i, group; if (n) { for (i = 0; i < n; i++) { indent += "+---"; } } else { n = 0; output += "Children of \n=====================\n"; } group = obj.children; for (i = 0; i < group.length; i++) { output += indent + "\n"; if (group[i].children.length > 0) { output += walkChildren(group[i], n+1); } } return output; }
Compatibility: WinIE6+, MacIE-, NN6+, Moz+, Safari+, Opera+, Chrome+ The cite property contains a URL that serves as a reference to the source of an element, as in the author of a quote. The property is intended to apply to only the blockquote, q, del, and
554
Chapter 26: Generic HTML Element Objects elementObject.className ins element objects, but IE supports it in a wider range of text content objects. This may or may not be a mistake, so it’s probably not a safe bet to use the property outside its intended elements.
className Value: String
Read/Write
Compatibility: WinIE4+, MacIE4+, NN6+, Moz+, Safari+, Opera+, Chrome+ A class name is an identifier that is assigned to the class attribute of an element. To associate a cascading style sheets (CSS) rule with several elements in a document, assign the same identifier to the class attributes of those elements, and use that identifier (preceded by a period) as the CSS rule’s selector. An element’s className property enables the application of different CSS rules to that element under script control. Listing 26-5 shows an example of such a script.
Example The style of an element toggles between on and off in Listing 26-5 by virtue of setting the element’s className property alternatively to an existing style sheet class selector name and an empty string. When you set the className to an empty string, the default behavior of the h1 element governs the display of the first header. A click of the button forces the style sheet rule to override the default behavior in the first h1 element. LISTING 26-5
Working with the className Property HTML: jsb26-05.html className Property .special { font-size:16pt; color:red; } className Property Lab
continued
555
Part IV: Document Objects Reference elementObject.clientHeight LISTING 26-5
(continued)
ARTICLE I
Congress shall make no law respecting an establishment of religion, or prohibiting the free exercise thereof; or abridging the freedom of speech, or of the press; or the right of the people peaceably to assemble, and to petition the government for a redress of grievances.
ARTICLE II
A well regulated militia, being necessary to the security of a free state, the right of the people to keep and bear arms, shall not be infringed.
JavaScript: jsb26-05.js function toggleSpecialStyle(elemID) { var elem = (document.all) ? document.all(elemID) : document.getElementById(elemID); if (elem.className == "") { elem.className = "special"; } else { elem.className = ""; } }
You can also create multiple versions of a style rule with different class selector identifiers and apply them at will to a given element. Related Items: rule, stylesheet objects (Chapter 38); id property
clientHeight clientWidth Value: Integer
Read-Only
Compatibility: WinIE4+, MacIE4+, NN7, Moz1.0.1+, Safari+, Opera+, Chrome+ These two properties by and large reveal the pixel height and width of the content within an element whose style sheet rule includes height and width settings. In theory, these measures do not take into account any margins, borders, or padding that you add to an element by way of style sheets. In practice, however, different combinations of borders, margins, and padding influence these values in unexpected ways. One of the more reliable applications of the clientHeight property enables you to discover, for example, where the text of an overflowing element ends. To read the rendered
556
Chapter 26: Generic HTML Element Objects elementObject.clientHeight dimensions of an element, you are better served across browsers with the offsetHeight and offsetWidth properties. For the document.body object, the clientHeight and clientWidth properties return the inside height and width of the window or frame (plus or minus a couple of pixels). These take the place of desirable, but nonexistent, window properties in IE. Unlike earlier versions, Internet Explorer 5+ expanded the number of objects that employ these properties to include virtually all objects that represent HTML elements. Values for these properties in Mozilla-based browsers are zero except for document.body, which measures the browser’s current content area.
Example Listing 26-6 for IE includes an example of how to size content dynamically on a page based on the client-area width and height. This example calls upon the clientHeight and clientWidth properties of a div element that contains a paragraph element. Only the width of the div element is specified in its style sheet rule, which means that the paragraph’s text wraps inside that width and extends as deeply as necessary to show the entire paragraph. The clientHeight property describes that depth. The clientHeight property then calculates where a logo image should be positioned immediately after div, regardless of the length of the text. As a bonus, the clientWidth property helps the script center the image horizontally with respect to the paragraph’s text. LISTING 26-6
Using clientHeight and clientWidth Properties HTML: jsb26-06.html clientHeight and clientWidth Properties Position and Show Logo Art
Lorem ipsum dolor sit amet, consectetaur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim adminim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit involuptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident.
continued
557
Part IV: Document Objects Reference elementObject.clientLeft LISTING 26-6
(continued)
JavaScript: jsb26-01.js function showLogo() { var paragraphW = document.getElementById("myDIV").clientWidth; var paragraphH = document.getElementById("myDIV").clientHeight; // correct for Windows/Mac discrepancies var paragraphTop = (document.getElementById("myDIV").clientTop) ? document.getElementById("myDIV").clientTop : document.getElementById("myDIV").offsetTop; var logoW = document.getElementById("logo").style.pixelWidth; // center logo horizontally against paragraph document.getElementById("logo").style.pixelLeft = (paragraphW-logoW) / 2; // position image immediately below end of paragraph document.getElementById("logo").style.pixelTop = paragraphTop + paragraphH; document.getElementById("logo").style.visibility = "visible"; }
To assist in the vertical positioning of the logo, the offsetTop property of the div object provides the position of the start of the div with respect to its outer container (the body). Unfortunately, MacIE uses the clientTop property to obtain the desired dimension. That measure (assigned to the paragraphTop variable), plus the clientHeight of the div, provides the top coordinate of the image. Related Items: offsetHeight, offsetWidth properties
clientLeft clientTop Value: Integer
Read-Only
Compatibility: WinIE4+, MacIE4+, NN-, Moz+, Safari+, Opera+, Chrome+ The purpose and names of the clientLeft and clientTop properties are confusing at best. Unlike the clientHeight and clientWidth properties, which apply to the content of an element, the clientLeft and clientTop properties return essentially no more information than the thickness of a border around an element — provided that the element is positioned. If you do not specify a border or do not position the element, the values are zero (although the document.body object can show a couple of pixels in each direction without explicit settings). If you are trying to read the left and top coordinate positions of an element, the offsetLeft and offsetTop properties are more valuable in WinIE; as shown in Listing 26-6, however, the clientTop property returns a suitable value in MacIE. Virtually all elements have the clientLeft and clientTop properties in IE5+, whereas support in MacIE is less consistent. Related Items: offsetLeft, offsetTop properties
Chapter 26: Generic HTML Element Objects elementObject.contentEditable IE5.5 introduced the concept of editable HTML content on a page. Element tags can include a contentEditable attribute whose value is echoed via the contentEditable property of the element. The default value for this property is inherit, which means that the property inherits whatever setting this property has in the hierarchy of HTML containers outward to the body. If you set the contentEditable property to true, that element and all nested elements set to inherit the value become editable; conversely, a setting of false turns off the option to edit the content. Some browsers automatically provide a visual cue for editable elements by giving an editable element a glowing blue border.
Example Listing 26-7 demonstrates how to use the contentEditable property to create a very simple poetry editor. When you click the button of a freshly loaded page, the toggleEdit() function captures the opposite of the current editable state via the contentEditable property of the div that is subject to edit. You switch on editing for that element in the next statement by assigning the new value to the contentEditable property of the div. For added impact, turn the text of the div to red to provide additional user feedback about what is editable on the page. The button label is also switched to one that indicates the action invoked by the next click of that button. LISTING 26-7
Using the contentEditable Property HTML: jsb26-07.html Editable Content .normal { color: black; } .editing { color: red; } Poetry Editor
Turn on editing to modify the following text:
Roses are red, Violets are blue.
continued
559
Part IV: Document Objects Reference elementObject.currentStyle LISTING 26-7
Compatibility: WinIE5+, MacIE5+, NN-, Moz-, Safari-, Opera-, ChromeEvery element has style attributes applied to it, even if those attributes are the browser’s default settings. Because an element’s style object reflects only those properties whose corresponding attributes are explicitly set via CSS statements, you cannot use the style property of an element object to view default style settings applied to an element. That’s where the currentStyle property comes in. This property returns a read-only style object that contains values for every possible style property applicable to the element. If a style property is explicitly set via CSS statement or script adjustment, the current reading for that property is also available here. Thus, a script can inquire about any property to determine whether it should change to meet some scripted design goal.
560
Chapter 26: Generic HTML Element Objects elementObject.dataSrc For example, if you surround some text with an tag, the browser by default turns that text into an italic font style. This setting is not reflected in the element’s style object (fontStyle property) because the italic setting was not set via CSS; by contrast, the element object’s currentStyle.fontStyle property reveals the true, current fontStyle property of the element as italic.
Example To change a style property setting, access it via the element’s style object. Use The Evaluator (see Chapter 4) to compare the properties of the currentStyle and style objects of an element. For example, an unmodified copy of The Evaluator contains an em element whose ID is "myEM". Enter document.getElementById("myEM").style in the bottom property listing text box and press Enter. Notice that most of the property values are empty. Now enter document.getElementById("myEM").currentStyle in the property listing text box and press Enter. Every property has a value associated with it. Related Items: runtimeStyle, style objects (Chapter 38); window.getComputedStyle() for W3C DOM browsers (Chapter 27)
dateTime Value: Date string
Read-Only
Compatibility: WinIE6+, MacIE-, NN6+, Moz+, Safari+, Opera+, Chrome+ The dateTime property contains a date/time value that is used to establish a timestamp for an element. Similar to the cite property, the dateTime property is intended to apply to a lesser number of element objects (del and ins) than is actually supported in IE. This may or may not be a mistake, so it’s probably not a safe bet to use the property outside its intended elements.
dataFld dataFormatAs dataSrc Value: String
Read/Write
Compatibility: WinIE4+, MacIE5, NN-, Moz-, Safari-, Opera-, ChromeThe dataFld, dataFormatAs, and dataSrc properties (along with more element-specific properties such as dataPageSize and recordNumber) are part of the Internet Explorer data-binding facilities based on ActiveX controls. The Win32 versions of IE4 and later have several ActiveX objects built into the browsers that facilitate direct communication between a web page and a data source. Data sources include text files, XML data, HTML data, and external databases (MacIE supports text files only). Data binding is a very large topic, much of which extends more to discussions about Microsoft Data Source Objects (DSOs), ODBC, and JDBC — subjects well beyond the scope of this book. But data binding is a powerful tool and can be of use even if you are not a database guru. Therefore, this discussion of the three primary properties — dataFld, dataFormatAs, and dataSrc — briefly covers data binding through Microsoft’s Tabular Data Control DSO. This allows any page to access, sort, display, and filter (but not update) data downloaded into a web page from an external text file (commonly, comma- or tab-delimited data). You can load data from an external text file into a document with the help of the Tabular Data Control (TDC). You retrieve the data by specifying the TDC object within an tag set and specifying additional parameters, such as the URL of the text file and field delimiter characters. The object
561
Part IV: Document Objects Reference elementObject.dataSrc element can go anywhere within the body of your document. (We tend to put it at the bottom of the code so that all normal page rendering happens before the control loads.) Retrieving the data simply brings it into the browser and does not, on its own, render the data on the page. If you haven’t worked with embedded objects in IE, the classid attribute value might seem a bit strange. The most perplexing part to some is the long value of numeric data signifying the Globally Unique Identifier (GUID) for the object, which is IE’s way of uniquely identifying objects. You must enter this value exactly as shown in the following example for the proper ActiveX TDC to run. The HTML syntax for this object is as follows: [additional optional parameters]
Table 26-3 lists the parameters available for the TDC. Only the DataURL parameter is required. Other parameters — such as FieldDelim, UseHeader, RowDelim, and EscapeChar — may be helpful, depending on the nature of the data source.
TABLE 26-3
Tabular Data Control Parameters Parameter
Description
CharSet
Character set of the data source file. Default is latin1.
DataURL
URL of data source file (relative or absolute).
EscapeChar
Character used to escape delimiter characters that are part of the data. Default is empty. A common value is "\".
FieldDelim
Delimiter character between fields within a record. Default is comma (,). For a Tab character, use a value of .
Language
ISO language code of source data. Default is en-us.
TextQualifier
Optional character surrounding a field’s data. Default is empty.
RowDelim
Delimiter character between records. Default is newline (NL).
UseHeader
Set to true if the first row of data in the file contains field names. Default is false.
The value you assign to the object element’s id attribute is the identifier that your scripts use to communicate with the data after the page and data completely load. Therefore, you can have as many uniquely named TDCs loaded in your page as there are data source files you want to access at the same time. The initial binding of the data to HTML elements usually comes when you assign values to the datasrc and datafld attributes of the elements. The datasrc attribute points to the dso identifier (matching the id attribute of the object element, preceded by a hash symbol), whereas the datafld attribute points to the name of the field whose data should be extracted. When you use
562
Chapter 26: Generic HTML Element Objects elementObject.dataSrc data binding with an interactive element such as a table, multiple records are displayed in consecutive rows of the table (more about this in a moment). Adjust the dataSrc and dataFld properties if you want the same HTML element (other than a table) to change the data that it displays. These properties apply to a subset of HTML elements that can be associated with external data: a, applet, body, button, div, frame, iframe, img, input (most types), label, marquee, object, param, select, span, and textarea objects. In some cases, your data source may store chunks of HTML-formatted text for rendering inside an element. Unless directed otherwise, the browser renders a data source field as plain text — even if the content contains HTML formatting tags. But if you want the HTML to be observed during rendering, you can set the dataFormatAs property (or, more likely, the dataformatas attribute of the tag) to HTML. The default value is text.
Example Listing 26-8 is a simple document that has two TDC objects associated with it. The external files are different formats of the U.S. Bill of Rights document. One file is a traditional, tab-delimited data file consisting of only two records. The first record is a tab-delimited sequence of field names (named "Article1", "Article2", and so on). The second record is a tab-delimited sequence of article content defined in HTML: ARTICLE I
Congress shall make...
The second file is a raw-text file consisting of the full Bill of Rights with no HTML formatting attached. When you load Listing 26-8, only the first article of the Bill of Rights appears in a blue-bordered box. Buttons enable you to navigate to the previous and next articles in the series. Because the data source is a traditional, tab-delimited file, the nextField() and prevField() functions calculate the name of the next source field and assign the new value to the dataFld property. All of the data is already in the browser after the page loads, so cycling through the records is as fast as the browser can reflow the page to accommodate the new content. LISTING 26-8
Binding Data to a Page HTML: jsb26-08.html Data Binding #display { width:500px; border:10px ridge blue; padding:20px; } .hiddenControl
continued
563
Part IV: Document Objects Reference elementObject.dataSrc LISTING 26-8
(continued)
{ display:none; } U.S. Bill of Rights
JavaScript: jsb26-08.js function nextField() { var elem = document.getElementById("display"); var fieldName = elem.dataFld; var currFieldNum = parseInt(fieldName.substring(7, fieldName.length),10); currFieldNum = (currFieldNum == 10) ? 1 : ++currFieldNum; elem.dataFld = "Article" + currFieldNum; } function prevField() { var elem = document.getElementById("display"); var fieldName = elem.dataFld; var currFieldNum = parseInt(fieldName.substring(7, fieldName.length),10);
Another button on the page enables you to switch between the initial piecemeal version of the document and the unformatted version in its entirety. To load the entire document as a single record, the FieldDelim and RowDelim parameters of the second object element eliminate their default values by replacing them with characters that don’t appear in the document at all. And because the external file does not have a field name in the file, the default value (column1 for the lone column in this document) is the data field. Thus, in the toggleComplete() function, the dataSrc property is changed to the desired object element ID; the dataFld property is set to the correct value for the data source; and the dataFormatAs property is changed to reflect the different intention of the source content (to be rendered as HTML or as plain text). When the display shows the entire document, you can hide the two radio buttons by assigning a className value to the span element that surrounds the buttons. The className value is the identifier of the class selector in the document’s style sheet. When the toggleComplete() function resets the className property to empty, the default properties (normal inline display style) take hold. One further example demonstrates the kind of power available to the TDC under script control. Listing 26-9 displays table data from a tab-delimited file of Academy Awards information. The data file has eight columns of data, and each column heading is treated as a field name: Year, Best Picture, Best Director, Best Director Film, Best Actress, Best Actress Film, Best Actor, and Best Actor Film. For the design of the page, only five fields from each record appear: Year, Film, Director, Actress, and Actor. Notice in the listing that the HTML for the table and its content is bound to the data source object and the fields within the data. The dynamic part of this example is apparent in how you can sort and filter the data, after it is loaded into the browser, without further access to the original source data. The TDC object features Sort and Filter properties that enable you to act on the data currently loaded in the browser. The simplest kind of sorting indicates on which field (or fields, via a semicolon-delimited list of field names) the entire data set should be sorted. Leading the name of the sort field is either a plus (to indicate ascending) or minus (descending) symbol. After setting the data object’s Sort property, invoke its
565
Part IV: Document Objects Reference elementObject.dataSrc Reset() method to tell the object to apply the new property. The data in the bound table is imme-
diately redrawn to reflect any changes. Similarly, you can tell a data collection to display records that meet specific criteria. In Listing 26-9, two select lists and a pair of radio buttons provide the interface to the Filter property’s settings. For example, you can filter the output to display only those records in which the Best Picture was the same picture of the winning Best Actress’s performance. Simple filter expressions are based on field names: dataObj.Filter = "Best Picture" = "Best Actress Film";
LISTING 26-9
Sorting Bound Data HTML: jsb26-09.html Data Binding - Sorting thead { background-color:yellow; text-align:center; } Academy Awards 1978-2005
Sort list by year from newest to oldest or from oldest to newest.
Filter listings for records whose Best Picture Best Director’s Film Best Actress’ Film Best Actor’s Film is is not
566
Chapter 26: Generic HTML Element Objects elementObject.dataSrc Best Picture Best Director’s Film Best Actress’ Film Best Actor’s Film
Year
Film
Director
Actress
Actor
JavaScript: jsb26-09.js function sortByYear(type) { oscars.Sort = (type == "normal") ? "-Year" : "+Year"; oscars.Reset(); } function filterInCommon(form) { var filterExpr1 = form.filter1.options[form.filter1.selectedIndex].value; var filterExpr2 = form.filter2.options[form.filter2.selectedIndex].value; var operator = (form.operator[0].checked) ? "=" : ""; var filterExpr = filterExpr1 + operator + filterExpr2; oscars.Filter = filterExpr; oscars.Reset(); }
567
Part IV: Document Objects Reference elementObject.dir Related Items: recordNumber, table.dataPageSize properties
dir Value: "ltr" | "rtl"
Read/Write
Compatibility: WinIE5+, MacIE5+, NN6+, Moz+, Safari+, Opera+, Chrome+ The dir property (based on the dir attribute of virtually every text-oriented HTML element) controls whether an element’s text is rendered left to right (the default) or right to left. By and large, this property (and HTML attribute) is necessary only when you need to override the default directionality of a language’s character set as defined by the Unicode standard.
Example Changing this property value in a standard U.S. version of a browser only makes the right margin the starting point for each new line of text (in other words, the characters are not rendered in reverse order). You can experiment with this in The Evaluator by entering the following statements in the expression evaluation field: document.getElementById("myP").dir = "rtl"
Related Item: lang property
disabled Value: Boolean
Read/Write
Compatibility: WinIE4+, MacIE4+, NN6+, Moz+, Safari+, Opera+, Chrome+ Though only form elements have a disabled property in IE4 and IE5, this property is associated with every HTML element in IE5.5+. W3C DOM browsers apply the property only to form control and style element objects. Disabling an HTML element (like form elements) usually gives the element a dimmed look, indicating that it is not active. A disabled element does not receive any events. It also cannot receive focus, either manually or by script. But a user can still select and copy a disabled body text element.
Note If you disable a form control element, the element’s data is not submitted to the server with the rest of the form elements. If you need to keep a form control locked down but still submit it to the server, use the form element’s onsubmit event handler to enable the form control right before the form is submitted.
Example Use The Evaluator (see Chapter 4) to experiment with the disabled property on both form elements (IE4+ and W3C) and regular HTML elements (WinIE5.5+). For IE4+ and W3C browsers, see what happens when you disable the output text area by entering the following statement in the top text box: document.forms[0].output.disabled = true
The text area is disabled for user entry, although you can still set the field’s value property via script (which is how the true returned value got there).
568
Chapter 26: Generic HTML Element Objects elementObject.filters[ ] If you have WinIE5.5+, disable the myP element by entering the following statement in the top text box: document.getElementById("myP").disabled = true
The sample paragraph’s text turns gray. Related Item: isDisabled property
document Value: document object
Read-Only
Compatibility: WinIE4+, MacIE4+, NN-, Moz-, Safari-, Opera+, ChromeIn the context of HTML element objects as exposed in IE4+/Opera, the document property is a reference to the document that contains the object. Though it is unlikely that you will need to use this property, document may come in handy for complex scripts and script libraries that handle objects in a generic fashion and do not know the reference path to the document containing a particular object. You might need a reference to the document to inspect it for related objects. The W3C version of this property is ownerDocument.
Example The following simplified function accepts a parameter that can be any object in a document hierarchy. The script finds out the reference of the object’s containing document for further reference to other objects: function getCompanionFormCount(obj) { var ownerDoc = obj.document; return ownerDoc.forms.length; }
Because the ownerDoc variable contains a valid reference to a document object, the return statement uses that reference to return a typical property of the document object hierarchy. Related Item: ownerDocument property
filters[] Value: Array
Read-Only
Compatibility: WinIE4+, MacIE4+, NN-, Moz-, Safari-, Opera-, ChromeFilters are IE-specific style sheet add-ons that offer a greater variety of font rendering (such as drop shadows) and transitions between hidden and visible elements. Each filter specification is a filter object. The filters property contains an array of filter objects defined for the current element. You can apply filters to the following set of elements: bdo, body, button, fieldset, img, input, marquee, rt, ruby, table, td, textarea, th, and positioned div and span elements. See Chapter 38 for details about style sheet filters.
569
Part IV: Document Objects Reference elementObject.firstChild Related Item: filter object
firstChild lastChild Value: Node object reference
Read-Only
Compatibility: WinIE5+, MacIE5+, NN6+, Moz+, Safari+, Opera+, Chrome+ W3C DOM-based DOMs are built around an architecture known as a node map. Each object defined by HTML is a node in the map. A node has relationships with other nodes in the document — relationships described in family terms of parents, siblings, and children. A child node is an element that is contained by another element. The container is the parent of such a child. Just as an HTML element can contain any number of child elements, so can a parent object have zero or more children. A list of those children (returned as an array) can be read from an object by way of its childNodes property: var nodeArray = document.getElementById("elementID").childNodes;
Though you can use this array (and its length property) to get a reference to the first or last child node, the firstChild and lastChild properties offer shortcuts to those positions. These are helpful when you wish to insert a new child before or after all of the others, and you need a reference point for methods that add elements to the document’s node list.
Example Listing 26-10 contains an example of how to use the firstChild and lastChild properties to access child nodes. These two properties come in handy in this example, which adds and replaces li elements to an existing ol element. You can enter any text you want to appear at the beginning or end of the list. Using the firstChild and lastChild properties simplifies access to the ends of the list. For the functions that replace child nodes, the example uses the replaceChild() method. Alternatively for IE4+, you can modify the innerText property of the objects returned by the firstChild or lastChild property. This example is especially interesting to watch when you add items to the list: The browser automatically renumbers items to fit the current state of the list.
Caution See the discussion of the childNodes property earlier in this chapter for details about the presence of phantom nodes in some browser versions. The problem may influence your use of the firstChild and lastChild properties.
Note As handy as it may be, in a strict W3C approach to JavaScript, you wouldn’t use the innerHTML property because it isn’t officially part of the W3C standard. However, it is often too powerful a convenience property to ignore, as much of the code throughout this book is a testament. The book does show the W3C node manipulation alternative to innerHTML in some examples. Refer to Chapter 29 for a thorough explanation and examples of the W3C alternative to innerHTML.
570
Chapter 26: Generic HTML Element Objects elementObject.firstChild LISTING 26-10
Using firstChild and lastChild Properties HTML: jsb26-10.html firstChild and lastChild Properties firstChild and lastChild Property Lab Enter some text to add to or replace in the OL element:
Initial Item 1
Initial Item 2
Initial Item 3
Initial Item 4
JavaScript: jsb26-10.js // helper function for prepend() and append() function makeNewLI(txt) { var newItem = document.createElement("LI"); newItem.innerHTML = txt; return newItem; } function prepend(form)
continued
571
Part IV: Document Objects Reference elementObject.height LISTING 26-10
(continued)
{ var newItem = makeNewLI(form.input.value); var firstLI = document.getElementById("myList").firstChild; document.getElementById("myList").insertBefore(newItem, firstLI); } function append(form) { var newItem = makeNewLI(form.input.value); var lastLI = document.getElementById("myList").lastChild; document.getElementById("myList").appendChild(newItem); } function replaceFirst(form) { var newItem = makeNewLI(form.input.value); var firstLI = document.getElementById("myList").firstChild; document.getElementById("myList").replaceChild(newItem, firstLI); } function replaceLast(form) { var newItem = makeNewLI(form.input.value); var lastLI = document.getElementById("myList").lastChild; document.getElementById("myList").replaceChild(newItem, lastLI); }
Compatibility: WinIE4+, MacIE4+, NN4+, Moz+, Safari+, Opera+, Chrome+ The height and width properties described here are not the identically named properties that belong to an element’s style. Rather, these properties reflect the values normally assigned to height and width attributes of elements such as img, applet, table, and so on. As such, these properties are accessed directly from the object (for example, document .getElementById("myTable").width) rather than through the style object (for example, document.getElementById("myDIV").style.width). Only elements for which the HTML 4.x standard provides height and width attributes have the corresponding properties. Values for these properties are either integer pixel values (numbers or strings) or percentage values (strings only). If you need to perform some math on an existing percentage value, use the parseInt() function to extract the numeric value for use with math calculations. If an element’s height and width attributes are set as percentage values, you can use the offsetHeight and offsetWidth properties in many modern browsers to get the rendered pixel dimensions.
572
Chapter 26: Generic HTML Element Objects elementObject.hideFocus Property values are read/write for the image object in most recent browser versions because you can resize an image object in after the page loads. Properties are read/write for some other objects (such as the table object) — but not necessarily all others that support these properties. In general, you cannot set the value of these properties to something less than is required to render the element. This is particularly true of a table. If you attempt to set the height value to less than the amount of pixels required to display the table as defined by its style settings, your changes have no effect (even though the property value retains its artificially low value). For other objects, however, you can set the size to anything you like, and the browser scales the content accordingly (images, for example). If you want to see only a segment of an element (in other words, to crop the element), use a style sheet to set the element’s clipping region.
Example The following example demonstrates how to use the width property by increasing the width of a table by 10 percent: var tableW = parseInt(document.getElementById("myTable").width); document.getElementById("myTable").width = (tableW * 1.1) + "%";
Because the initial setting for the width attribute of the table element is set as a percentage value, the script calculation extracts the number from the percentage width string value. In the second statement, the old number is increased by 10 percent and turned into a percentage string by appending the percentage symbol to the value. The resulting string value is assigned to the width property of the table. Related Items: clientHeight, clientWidth properties; style.height, style.width properties
hideFocus Value: Boolean
Read/Write
Compatibility: WinIE5.5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeIn IE for Windows, button types of form controls and links display a dotted rectangle around some part of the element whenever that element has focus. If you set the tabindex attribute or tabIndex property of any other kinds of elements in IE5+, they, too, display that dotted line when given focus. You can still let an element receive focus but hide that dotted line by setting the hideFocus property of the element object to true (default value is false). Hiding focus does not disable the element. In fact, if the element about to receive focus is scrolled out of view, the page scrolls to bring the element into view. Form controls that respond to keyboard action (for example, pressing the spacebar to check or uncheck a checkbox control) also continue to work as normal. For some designers, the focus rectangle harms the design goals of the page. The hideFocus property gives them more control over the appearance while maintaining consistency of operation with other pages. There is no corresponding HTML attribute for a tag, so you can use an onload event handler in the page to set the hideFocus property of desired objects after the page loads.
Example Use The Evaluator (see Chapter 4) to experiment with the hideFocus property in WinIE5.5+. Enter the following statement in the top text box to assign a tabIndex value to the myP element so that by default, the element receives focus and the dotted rectangle: document.getElementById("myP").tabIndex = 1
573
Part IV: Document Objects Reference elementObject.id Press the Tab key several times until the paragraph receives focus. Now disable the focus rectangle: document.getElementById("myP").hideFocus = true
If you now press the Tab key several times, the dotted rectangle does not appear around the paragraph. To prove that the element still receives focus, scroll the page down to the bottom so that the paragraph is not visible (you may have to resize the window). Click one of the focusable elements at the bottom of the page and then press the Tab key slowly until the Address field toolbar has focus. Press the Tab key once. The page scrolls to bring the paragraph into view, but there is no focus rectangle around the element. Related Items: tabIndex property; srcollIntoView() method
id Value: String
(See text)
Compatibility: WinIE4+, MacIE4+, NN6+, Moz+, Safari+, Opera+, Chrome+ The id property returns the identifier assigned to an element’s id attribute in the HTML code. A script cannot modify the ID of an existing element or assign an ID to an element that lacks one. But if a script creates a new element object, an identifier may be assigned to it by way of the id property.
Example Rarely do you need to access this property in a script — unless you write an authoring tool that iterates through all elements of a page to extract the IDs assigned by the author. You can retrieve an object reference when you know the object’s id property (via the document.getElementById(elemID) method). But if for some reason your script doesn’t know the ID of, say, the second paragraph of a document, you can extract that ID as follows: var elemID = document.getElementsByTagName("p")[1].id;
Related Item: className property
innerHTML innerText Value: String
Read/Write
Compatibility: WinIE4+, MacIE4+, NN6+, Moz+, Safari+, Opera+, Chrome+ One way that Internet Explorer exposes the contents of an element is through the innerHTML and innerText properties. (NN6+/Moz offer only the innerHTML property.) All content defined by these inner properties consists of document data that is contained by an element’s start and end tags but does not include the tags themselves (see the outerText and outerHTML properties). Setting these inner properties is a common way to modify a portion of a page’s content after the page loads. The innerHTML property contains not only the text content for an element as seen on the page, but also every bit of HTML tagging that is associated with that content. (If there are no tags in the content, the text is rendered as is.) For example, consider the following bit of HTML source code:
"How are you?" he asked.
574
Chapter 26: Generic HTML Element Objects elementObject.innerHTML The value of the paragraph object’s innerHTML property (document.getElementById ("paragraph1").innerHTML) is "How are you?" he asked.
The browser interprets any HTML tags included in a string you assign to an element’s innerHTML property as tags. This also means that you can introduce entirely new nested elements (or child nodes in the modern terminology) by assigning a slew of HTML content to an element’s innerHTML property. The document’s object model adjusts itself to the newly inserted content. By contrast, the innerText property knows only about the text content of an element container. In the example you just saw, the value of the paragraph’s innerText property (document .getElementById("paragraph1").innerText) is "How are you?" he asked.
It’s important to remember that if you assign a string to the innerText property of an element, and that string contains HTML tags, the tags and their angle brackets appear in the rendered page and are not interpreted as live tags. The W3C DOM Level 3 adds a textContent property that serves as the standard equivalent of innerText. IE does not support textContent. Do not modify the innerHTML property to adjust the HTML for frameset, html, head, or title objects. You may modify table constructions through either innerHTML or the various table-related methods that create or delete rows, columns, and cells (see Chapter 41). It is also safe to modify the contents of a cell by setting its innerHTML or innerText property. When the HTML you insert includes a tag, be sure to include the defer attribute to the opening tag. This goes even for scripts that contain function definitions, which you might consider to be deferred automatically. The innerHTML property is not supported by the W3C DOM, but it does share widespread support in all modern browsers. You could argue that a pure W3C DOM node manipulation approach is more structured than just assigning HTML code to innerHTML, but the ease of making a single property assignment has so far won out in the practicality of everyday scripting. Whenever possible, the examples in this book use the W3C approach to alter the HTML code for a node, but there are several instances where innerHTML is simply too concise an option to resist.
Example Listing 26-11 contains an example of how to use the innerHTML and innerText properties to alter dynamically the content within a page. The page generated in the listing contains an h1 element label and a paragraph of text. The purpose is to demonstrate how the innerHTML and innerText properties differ in their intent. Two text boxes contain the same combination of text and HTML tags that replaces the inner content of the paragraph’s label. If you apply the default content of the first text box to the innerHTML property of the label1 object, the italic style is rendered as such for the first word. In addition, the text in parentheses is rendered with the help of the small style sheet rule assigned by virtue of the surrounding tags. But if you apply that same content to the innerText property of the label object, the tags are rendered as is. Use this as a laboratory to experiment with some other content in both text boxes. See what happens when you insert a tag within some text in both text boxes.
575
Part IV: Document Objects Reference elementObject.innerHTML LISTING 26-11
Using innerHTML and innerText Properties HTML: jsb26-11.html innerHTML and innerText Properties h1 { font-size:18pt; font-weight:bold; font-family:"Comic Sans MS", Arial, sans-serif; } .small { font-size:12pt; font-weight:400; color:gray; }
ARTICLE I
Congress shall make no law respecting an establishment of religion, or prohibiting the free exercise thereof; or abridging the freedom of speech, or of the press; or the right of the people peaceably to assemble, and to petition the government for a redress of grievances.
576
Chapter 26: Generic HTML Element Objects elementObject.isContentEditable
JavaScript: jsb26-11.js function setGroupLabelAsText(form) { var content = form.textInput.value; if (content) { document.getElementById("label1").innerText = content; } } function setGroupLabelAsHTML(form) { var content = form.HTMLInput.value; if (content) { document.getElementById("label1").innerHTML = content; } }
Related Items: outerHTML, outerText, textContent properties; replaceNode() method
isContentEditable Value: Boolean
Read-Only
Compatibility: WinIE5.5+, MacIE-, NN-, Moz-, Safari 1.2+, Opera+, Chrome+ The isContentEditable property returns a Boolean value indicating whether a particular element object is set to be editable (see the discussion of the contentEditable property earlier in this chapter). This property is helpful because if a parent element’s contentEditable property is set to true, a nested element’s contentEditable property likely is set to its default value inherit. But because its parent is editable, the isContentEditable property of the nested element returns true.
Example Use The Evaluator (see Chapter 4) to experiment with both the contentEditable and isContentEditable properties on the myP and nested myEM elements (reload the page to start with a known version). Check the current setting for the myEM element by typing the following statement in the top text box: myEM.isContentEditable
This value is false because no element upward in the element containment hierarchy is set to be editable yet. Next, turn on editing for the surrounding myP element: myP.contentEditable = true
577
Part IV: Document Objects Reference elementObject.isDisabled At this point, the entire myP element is editable because its child element is set, by default, to inherit the edit state of its parent. Prove it by entering the following statement in the top text box: myEM.isContentEditable
Although the myEM element is shown to be editable, no change has accrued to its contentEditable property: myEM.contentEditable
This property value remains the default inherit. Related Item: contentEditable property
isDisabled Value: Boolean
Read-Only
Compatibility: WinIE5.5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe isDisabled property returns a Boolean value that indicates whether a particular element object is set to be disabled (see the discussion of the disabled property earlier in this chapter). This property is helpful; if a parent element’s disabled property is set to true, a nested element’s disabled property likely is set to its default value of false. But because its parent is disabled, the isDisabled property of the nested element returns true. In other words, the isDisabled property returns the actual disabled status of an element regardless of its disabled property.
Example Use The Evaluator (see Chapter 4) to experiment with both the disabled and isDisabled properties on the myP and nested myEM elements (reload the page to start with a known version). Check the current setting for the myEM element by typing the following statement in the top text box: myEM.isDisabled
This value is false because no element upward in the element containment hierarchy is set for disabling yet. Next, disable the surrounding myP element: myP.disabled = true
At this point, the entire myP element (including its children) is disabled. Prove it by entering the following statement in the top text box: myEM.isDisabled
Although the myEM element is shown as disabled, no change has accrued to its disabled property: myEM.disabled
This property value remains the default false. Related Item: disabled property
Chapter 26: Generic HTML Element Objects elementObject.lang The isMultiLine property returns a Boolean value that reveals whether the element object is capable of occupying or displaying more than one line of text. It is important that this value does not reveal whether the element actually occupies multiple lines; rather, it indicates the potential of doing so. For example, a text input element cannot wrap to multiple lines, so its isMultiLine property is false. However, a button element can display multiple lines of text for its label, so it reports true for the isMultiLine property.
Example Use The Evaluator (see Chapter 4) to read the isMultiLine property for elements on that page. Try the following statements in the top text box: document.body.isMultiLine document.forms[0].input.isMultiLine myP.isMultiLine myEM.isMultiLine
All but the text field form control report that they are capable of occupying multiple lines.
isTextEdit Value: Boolean
Read-Only
Compatibility: WinIE4+, MacIE4+, NN-, Moz-, Safari-, Opera-, ChromeThe isTextEdit property reveals whether an object can have a WinIE TextRange object created with its content (see Chapter 33 on the CD-ROM). You can create TextRange objects from only a limited selection of objects in IE4+ for Windows: body, button, button, image and radio type input, and textarea. This property always returns false in MacIE.
Example Good coding practice dictates that your script check for this property before invoking the createTextRange() method on any object. A typical implementation is as follows: if (document.getElementById("myObject").isTextEdit) { var myRange = document.getElementById("myObject").createTextRange(); // [more statements that act on myRange] }
Related Items: createRange() method; TextRange object (Chapter 33 on the CD-ROM)
lang Value: ISO language code string
Read/Write
Compatibility: WinIE4+, MacIE4+, NN6+, Moz+, Safari+, Opera+, Chrome+ The lang property governs the written language system used to render an element’s text content when overriding the default browser’s language system. The default value for this property is an empty string unless the corresponding lang attribute is assigned a value in the element’s tag. Modifying the property value by script control does not appear to have any effect in the current browser implementations.
579
Part IV: Document Objects Reference elementObject.language
Example Values for the lang property consist of strings containing valid ISO language codes. Such codes have, at minimum, a primary language code (for example, "fr" for French) plus an optional region specifier (for example, "fr-ch" for Swiss French). The code to assign a Swiss German value to an element looks like the following: document.getElementById("specialSpan").lang = "de-ch";
language Value: String
Read/Write
Compatibility: WinIE4+, MacIE4+, NN-, Moz-, SafariIE4+’s architecture allows for multiple scripting engines to work with the browser. Two engines are included with the basic Windows version browser: JScript (compatible with JavaScript) and Visual Basic Scripting Edition (VBScript). The default scripting engine is JScript. But if you wish to use VBScript or some other scripting language in statements that are embedded within event handler attributes of a tag, you can specifically direct the browser to apply the desired scripting engine to those script statements by way of the language attribute of the tag. The language property provides scripted access to that property. Unless you intend to modify the event handler HTML code and replace it with a statement in VBScript (or any other non-JScript-compatible language installed with your browser), you do not need to modify this property (or read it, for that matter). Valid values include JScript, javascript, vbscript, and vbs. Third-party scripting engines have their own identifier for use with this value. Internet Explorer 5 observes language="xml" as well. Be aware that this attribute was deprecated in HTML4.01, so depending on the DOCTYPE you use, code using this attribute will not validate. You can accomplish the same objective with type (see Chapter 4). Related Item: script element object
lastChild (See firstChild)
length Value: Integer
Read-Only and Read/Write
Compatibility: WinIE3+, MacIE3+, NN2+, Moz+, Safari+, Opera+, Chrome+ The length property returns the number of items in an array or collection of objects. Its most common application is as a boundary condition in a for loop. Though arrays and collections commonly use integer values as index values (always starting with zero), the length value is the actual number of items in the group. Therefore, to iterate through all items of the group, the condition expression should include a less-than ( 2) { oneChild = mainObj.lastChild; mainObj.removeChild(oneChild); } }
The final part of the demonstration uses the removeChild() method to peel away all children of the ul element until just two items are left standing. Again, the lastChild property comes in handy as the truncateList() function keeps removing the last child until only two remain. Related Items: removeChild(), replaceChild() methods; nodes and children (Chapter 25)
applyElement(elementObject[, type]) Returns: Nothing Compatibility: WinIE5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe applyElement() method enables you to insert a new element as the parent or child of the current object. An important feature of this method is that the new object is wrapped around the current object (if the new element is to become the parent) or the current object’s content (if the new element is to become a child). When the new element becomes a child, all previous children are nested further by one generation to become immediate children of the new element. You can imagine how the resulting action of this method affects the containment hierarchy of the current element, so you must be careful how you use the applyElement() method. One parameter, a reference to the object to be applied, is required. This object may be generated from constructions such as document.createElement() or from one of the child or node methods that returns an object. The second parameter is optional, and it must be one of the following values:
622
Parameter Value
Description
outside
New element becomes the parent of the current object.
inside
New element becomes the immediate child of the current object.
Chapter 26: Generic HTML Element Objects elementObject.applyElement() If you omit the second parameter, the default value (outside) is assumed. Listing 26-22 shows how the applyElement() method is used both with and without default values.
Example To help you visualize the impact of the applyElement() method with its different parameter settings, Listing 26-22 enables you to apply a new element (an em element) to a span element inside a paragraph. At any time, you can view the HTML of the entire p element to see where the em element is applied, as well as its impact on the element containment hierarchy for the paragraph. After you load the page, inspect the HTML for the paragraph before doing anything else. Notice the span element and its nested code element, both of which surround the one-word content. If you apply the em element inside the span element (click the middle button), the span element’s first (and only) child element becomes the em element; the code element is now a child of the new em
element. LISTING 26-22
Using the applyElement() Method HTML: jsb26-22.html applyElement() Method #mySpan { font-size:x-large; } applyElement() Method
A simple paragraph with a special word in it. How special? Click an apply button, then click the show button.
continued
623
Part IV: Document Objects Reference elementObject.attachEvent() LISTING 26-22
(continued)
JavaScript: jsb26-22.js function applyOutside() { var newItem = document.createElement("EM"); newItem.id = newItem.uniqueID; // no 2nd argument--use default: outside document.getElementById("mySpan").applyElement(newItem); } function applyInside() { var newItem = document.createElement("EM"); newItem.id = newItem.uniqueID; document.getElementById("mySpan").applyElement(newItem, "inside"); } function showHTML() { alert(document.getElementById("myP").outerHTML); }
The visible results of applying the em element inside and outside the span element in this case are the same. But you can see from the HTML results that each element impacts the element hierarchy quite differently. Related Items: insertBefore(), appendChild(), insertAdjacentElement() methods
attachEvent("eventName", functionRef) detachEvent("eventName", functionRef) Returns: Boolean Compatibility: WinIE5+, MacIE-, NN-, Moz-, Safari-, Opera+, ChromeThe attachEvent() method originated as a means to bind events for IE behaviors (see Chapter 51 on the CD-ROM). But the method has gained acceptance as an IE alternative to the W3C addEventListener() event binding method. To illustrate the method’s usage, we want you to first consider the following example of the typical property assignment approach to binding an event handler: myObject.onmousedown = setHilite;
The version with attachEvent() is as follows: myObject.attachEvent("onmousedown", setHilite);
624
Chapter 26: Generic HTML Element Objects elementObject.blur() Both parameters are required. The first parameter is a string version (case insensitive) of the event name. The second is a reference to the function to be invoked when the event fires for this object. A function reference is an unquoted, case-sensitive identifier for the function without any parentheses (which also means that you cannot pass parameters in this function call). There is a subtle benefit to using attachEvent() over the event property binding approach. When you use attachEvent(), the method returns a Boolean value of true if the event binding succeeds. IE triggers a script error if the function reference fails, so don’t rely on a returned value of false to catch these kinds of errors. Also, there is no validation that the object recognizes the event name. If you have used attachEvent() to bind an event handler to an object’s event, you can disconnect that binding with the detachEvent() method. The parameters are the same as for attachEvent(). The detachEvent() method cannot unbind events whose associations are established via tag attributes or event property settings. The W3C DOM event model provides functionality similar to these IE-only methods: addEventListener() and removeEventListener().
Example Use The Evaluator (see Chapter 4) to create an anonymous function that is called in response to an onmousedown event of the first paragraph on the page. Begin by assigning the anonymous function to global variable a (already initialized in The Evaluator) in the top text box: a = new Function("alert(‘Function created at " + (new Date()) + "’)")
The quote marks and parentheses can get jumbled easily, so enter this expression carefully. When you enter the expression successfully, the Results box shows the function’s text. Now assign this function to the onmousedown event of the myP element by entering the following statement in the top text box: document.getElementById("myP").attachEvent("onmousedown", a)
The Results box displays true when successful. If you mouse down on the first paragraph after the evaluator panel, an alert box displays the date and time when the anonymous function was created (when the new Date() expression was evaluated). Now disconnect the event relationship from the object by entering the following statement in the top text box: document.getElementById("myP").detachEvent("onmousedown", a)
blur() focus() Returns: Nothing Compatibility: WinIE3+, MacIE3+, NN2+, Moz+, Safari+, Opera+, Chrome+ The blur() method removes focus from an element, whereas the focus() method gives focus to an element. Even though the blur() and focus() methods have been around since the earliest scriptable browsers, not every focusable object has enjoyed these methods since the beginning.
625
Part IV: Document Objects Reference elementObject.blur() Browsers before IE4 and NN6 limited these methods primarily to the window object and form control elements.
Windows For window objects, the blur() method (NN3+, IE4+, Opera) pushes the referenced window to the back of all other open windows. If other browser suite windows (such as email or newsreader windows) are open, the window receiving the blur() method is placed behind these windows as well. In Safari and Firefox, the blur() method pushes the referenced window only behind the window that opened it. In Chrome, the window.blur() method does not work, as demonstrated if you click the Put Me in Back button in Listing 26-23a. For that matter, the window.focus() method does not work in Chrome either, as demonstrated if you click the Bring Main to Front button in Listing 26-23a. The window.focus() method does not work in IE8 either.
Caution When it works, the window.blur() method does not consistently adjust the stacking order of the current window in the different browsers. But a script in a window can invoke the focus() method of another window to bring that other window to the front (provided that a scriptable linkage, such as the window.opener property, exists between the two windows).
The minute you create another window for a user in your web-site environment, you must pay attention to window layer management. With browser windows so easily activated by the slightest mouse click, a user can lose a smaller window behind a larger one in a snap. Most inexperienced users don’t think to check the Windows taskbar or browser menu bar (if the browser is so equipped) to see whether a smaller window is still open and then activate it. If that subwindow is important to your site design, you should present a button or other device in each window that enables users to switch among windows safely. The window.focus() method brings the referenced window to the front of all the windows. Rather than supply a separate button on your page to bring a hidden window forward, you should build your window-opening functions in such a way that if the window is already open, the function automatically brings that window forward (as shown in Listing 26-23a). This removes the burden of window management from your visitors. The key to success with this method is making sure that your references to the desired windows are correct. Therefore, be prepared to use the window.opener property to refer to the main window if a subwindow needs to bring the main window back into focus.
Form control elements The blur() and focus() methods apply primarily to text-oriented form controls: text input, select, and textarea elements. Just as a camera lens blurs when it goes out of focus, a text object blurs when it loses focus — when someone clicks or tabs out of the field. Under script control, blur() deselects whatever may be selected in the field, and the text insertion pointer leaves the field. The pointer does not proceed to the next field in tabbing order, as it does if you perform a blur by tabbing out of the field manually. For a text object, having focus means that the text insertion pointer is flashing in that text object’s field. Giving a field focus is like opening it up for human editing.
626
Chapter 26: Generic HTML Element Objects elementObject.blur() Setting the focus of a text box or textarea does not by itself enable you to place the cursor at any specified location in the field. The cursor usually appears at the beginning of the text. To prepare a field for entry to remove the existing text, use both the focus() and select() methods in series. There is a caveat about using focus() and select() together to preselect the content of a text box for immediate editing: Many versions of Internet Explorer fail to achieve the desired results due to an internal timing problem. You can work around this problem (and remain compatible with other browsers) by initiating the focus and selection actions through a setTimeout() method. A common design requirement is to position the insertion pointer at the end of a text box or textarea so that a user can begin appending text to existing content immediately. This is possible in IE4+ with the help of the TextRange object. The following script fragment moves the text insertion pointer to the end of a textarea element whose ID is myTextarea: var range = document.getElementById("myTextarea").createTextRange(); range.move("textedit"); range.select();
You should be very careful in combining blur() or focus() methods with onblur and onfocus event handlers — especially if the event handlers display alert boxes. Many combinations of these events and methods can cause an infinite loop in which it is impossible to dismiss the alert dialog box completely. On the other hand, there is a useful combination for older browsers that don’t offer a disabled property for text boxes. The following text box event handler can prevent users from entering text in a text box: onfocus = "this.blur()";
Some operating systems and browsers enable you to give focus to elements such as buttons (including radio and checkbox buttons) and hypertext links (encompassing both a and area elements). Typically, once such an element has focus, you can accomplish the equivalent of a mouse click on the element by pressing the spacebar. This is helpful for accessibility to those who have difficulty using a mouse. An unfortunate side effect of button focus in Win32 environments is that the focus highlight (a dotted rectangle) remains around the button after a user clicks it and until another object gets focus. You can eliminate this artifact for browsers and objects that implement the onmouseup event handler by including the following event handler in your buttons: onmouseup = "this.blur()";
IE5.5+ recognizes the often undesirable effect of that dotted rectangle and lets scripts set the hideFocus property of an element to true to keep that rectangle hidden while giving the element focus. It is a trade-off for the user, however, because there is no visual feedback about which element has focus.
Other elements For other kinds of elements that support the focus() method, you can bring an element into view in lieu of the scrollIntoView() method. Link (a) and area elements in Windows versions of IE
627
Part IV: Document Objects Reference elementObject.blur() display the dotted rectangle around them after a user brings focus to them. To eliminate that artifact, use the same onmouseup = "this.blur()";
event handler (or IE5.5+ hideFocus property) just described for form controls.
Example Listing 26-23a contains an example of using the focus() and blur() methods to tinker with changing the focus of windows. This example creates a two-window environment; from each window, you can bring the other window to the front. The main window uses the object returned by window.open() to assemble the reference to the new window. In the subwindow (whose content is created entirely on-the-fly by JavaScript), self.opener is summoned to refer to the original window, whereas self.blur() operates on the subwindow itself. Blurring one window and focusing on another window yields the same result of sending the window to the back of the pile. LISTING 26-23a
The window.focus() and window.blur() Methods HTML: jsb26-23.html Window Focus() and Blur() Window focus() and blur() Methods
JavaScript: jsb26-23.js // declare global variable name var newWindow = null; function makeNewWindow() { // check if window already exists if (!newWindow || newWindow.closed) { // store new window object in global variable newWindow = window.open("","","width=250,height=250"); // pause briefly to let IE3 window finish opening
628
Chapter 26: Generic HTML Element Objects elementObject.blur() setTimeout("fillWindow()",100); } else { // window already exists, so bring it forward newWindow.focus(); } } // assemble new content and write to subwindow function fillWindow() { var newContent = "Another Sub Window"; newContent += ""; newContent += "A Salmon-Colored Subwindow."; newContent += ""; newContent += ""; newContent += ""; // write HTML to new window document newWindow.document.write(newContent); newWindow.document.close(); }
A key ingredient to the success of the makeNewWindow() function in Listing 26-23a is the first conditional expression. Because newWind is initialized as a null value when the page loads, that is its value the first time through the function. But after you open the subwindow the first time, newWind is assigned a value (the subwindow object) that remains intact even if the user closes the window. Thus, the value doesn’t revert to null by itself. To catch the possibility that the user has closed the window, the conditional expression also sees whether the window is closed. If it is, a new subwindow is generated, and that new window’s reference value is reassigned to the newWind variable. On the other hand, if the window reference exists and the window is not closed, the focus() method brings that subwindow to the front. In Listing 26-23a you can see where the subwindow’s content is created entirely on-the-fly by JavaScript. One of the nice little tools in IE and Firefox is the ability to view generated source. It’s a little ugly, in that all the code is on a single line. We’ve formatted the generated source for you in Listing 26-23b so that you can see just what was created entirely on-the-fly in Listing 26.23a. LISTING 26-23b
The Source Code Generated On-the-Fly in Listing 26-23a Another Sub Window
continued
629
Part IV: Document Objects Reference elementObject.clearAttributes() LISTING 26-23b
(continued)
A Salmon-Colored Subwindow.
You can see the focus() method for a text object in action in the description of the select() method for text objects in Chapter 36. Related Items: window.open(), document.formObject.textObject.select() methods
clearAttributes() Returns: Nothing Compatibility: WinIE5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe clearAttributes() method removes all attributes from an element except the name and id values. Thus, styles and event handlers are removed, as are custom attributes assigned in either the HTML source code or later by script. You should know that the clearAttributes() method does not alter the length of the element’s attributes collection, because the collection always contains all possible attributes for an element. (See the attributes property for elements earlier in this chapter.) This method is handy if you wish to construct an entirely new set of attributes for an element and prefer to start out with a blank slate. Be aware, however, that unless your scripts immediately assign new attributes to the element, the appearance of the element reverts to its completely unadorned form until you assign new attributes. This means that even positioned elements find their way back to their source-code order until you assign a new positioning style. If you simply want to change the value of one or more attributes of an element, it is faster to use the setAttribute() method or adjust the corresponding properties. To accomplish a result in NN6+/Moz that simulates that of IE5+’s clearAttributes(), you must iterate through all attributes of an element and remove those attributes (via the removeAttribute() method) whose names are other than id and name.
Example Use The Evaluator (see Chapter 4) to examine the attributes of an element before and after you apply clearAttributes(). To begin, display the HTML for the table element on the page by entering the following statement in the top text box: myTable.outerHTML
Notice the attributes associated with the
tag. Look at the rendered table to see how attributes such as border and width affect the display of the table. Now enter the following statement in the top text box to remove all removable attributes from this element: myTable.clearAttributes()
630
Chapter 26: Generic HTML Element Objects elementObject.cloneNode() First, look at the table. The border is gone, and the table is rendered only as wide as is necessary to display the content with no cell padding. Finally, view the results of the clearAttributes() method in the outerHTML of the table again: myTable.outerHTML
The source-code file has not changed, but the object model in the browser’s memory reflects the changes you made. Related Items: attributes property; getAttribute(), setAttribute(), removeAttribute(), mergeAttributes(), and setAttributeNode() methods
click() Returns: Nothing Compatibility: WinIE4+, MacIE4+, NN2+, Moz+, Safari+, Opera+, Chrome+ The click() method lets a script perform nearly the same action as clicking an element. Before NN4 and IE4, the click() method invoked on a button did not trigger the onclick event handler for the object. This has significant impact if you expect the onclick event handler of a button to function even if a script performs the click. For earlier browser versions, you have to invoke the event handler statements directly. Also, just because a script is clicking a button, not all buttons in all platforms change their appearance in response. For example, NN4 on the Mac does not change the state of a checkbox clicked remotely. If you want to script the action of clicking a button, you can safely invoke the resulting event handler function directly. And if the element is a radio button or checkbox, handle the change of state directly (for example, set the checked property of a checkbox) rather than expect the browser to take care of it for you.
Example Use The Evaluator (see Chapter 4) to experiment with the click() method. The page includes various types of buttons at the bottom. You can click the checkbox, for example, by entering the following statement in the top text box: document.myForm2.myCheckbox.click()
If you use a recent browser version, you most likely can see the checkbox change states between checked and unchecked each time you execute the statement. Related Item: onclick event handler
cloneNode(deepBoolean) Returns: Node object reference Compatibility: WinIE5+, MacIE5+, NN6+, Moz+, Safari+, Opera+, Chrome+ The cloneNode() method makes an exact copy of the current node object. This copy does not have a parent node or other relationship with any element after the copy exists (of course, the original node remains in place). The clone also does not become part of the document’s object model (the node tree) unless you explicitly insert or append the node somewhere on the page. The copy includes all element attributes, including the id attribute. Because the value returned by the cloneNode() method is
631
Part IV: Document Objects Reference elementObject.compareDocumentPosition() a genuine Node object, you can operate on it with any Node object methods while it is still in the nondocument object state. The Boolean parameter of the cloneNode() method controls whether the copy of the node includes all child nodes (true) or just the node itself (false). For example, if you clone a paragraph element by itself, the clone consists only of the raw element (equivalent of the tag pair, including attributes in the start tag) and none of its content. But including child nodes makes sure that all content within that paragraph element is part of the copy. This parameter is optional in IE5 (defaulting to false), but it is required in other W3C-compatible browsers.
Example Use The Evaluator (see Chapter 4) to clone, rename, and append an element found in The Evaluator’s source code. Begin by cloning the paragraph element named myP along with all of its content. Enter the following statement in the top text box: a = document.getElementById("myP").cloneNode(true)
The variable a now holds the clone of the original node, so you can change its id attribute at this point by entering the following statement: a.setAttribute("id", "Dolly")
If you want to see the properties of the cloned node, enter a in the bottom text box. The precise listing of properties you see depends on the browser you’re using; in either case, you should be able to locate the id property, whose value is now Dolly. As a final step, append this newly named node to the end of the body element by entering the following statement in the top text box: document.body.appendChild(a)
You can now scroll down to the bottom of the page and see a duplicate of the content. But because the two nodes have different id attributes, they cannot confuse scripts that need to address one or the other. Related Items: Node object (Chapter 25); appendChild(), removeChild(), removeNode(), replaceChild(), and replaceNode() methods
compareDocumentPosition(nodeRef) Returns: Integer Compatibility: WinIE-, MacIE-, NN6+, Moz1.4+, Safari+, Opera+, Chrome+ This method determines the tree position of one node with respect to another node. More specifically, the nodeRef object provided as a parameter (Node B) is compared with the object on which the method is called (Node A). The result is returned from the method as an integer value that can contain one or more of the comparison masks listed in Table 26-8. The integer value returned by the compareDocumentPosition() method is actually a bitmask, which explains why the values in Table 26-8 are powers of 2. This allows the method to return multiple comparison values simply by adding them together. For example, a return value of 20 indicates that Node B is contained by Node A (16) and also that Node B follows Node A (4).
632
Chapter 26: Generic HTML Element Objects elementObject.componentFromPoint() TABLE 26-8
Comparison Return Flags Integer Value
Constant
0
Description
Node B and Node A are one and the same.
1
DOCUMENT_POSITION_DISCONNECTED
No connection exists between the nodes.
2
DOCUMENT_POSITION_PRECEDING
Node B precedes Node A.
4
DOCUMENT_POSITION_FOLLOWING
Node B follows Node A.
8
DOCUMENT_POSITION_CONTAINS
Node B contains Node A (and therefore precedes it).
16
DOCUMENT_POSITION_CONTAINED_BY
Node B is contained by Node A (and therefore follows it).
32
DOCUMENT_POSITION_IMPLEMENTATION_ SPECIFIC
The comparison is determined by the browser.
Related Item: contains() method
componentFromPoint(x,y) Returns: String Compatibility: WinIE5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe componentFromPoint() method assists in some event-related tasks. You can use it for a kind of collision detection (in other words, to determine whether an event occurs inside or outside a particular element). If the element has scroll bars, the method can provide additional information about the event, such as which component of the scroll bar the user activates. A key aspect of this method is that you invoke it on any element that you want to use as the point of reference. For example, if you want to find out whether a mouseup event occurs in an element whose ID is myTable, invoke the method as follows: var result = document.getElementById("myTable").componentFromPoint( i event.clientX, event.clientY);
Parameters passed to the method are x and y coordinates. These coordinates do not have to come from an event, but the most likely scenario links this method with an event of some kind. Mouse events (other than onclick) work best. The value returned by the method is a string that provides details about where the coordinate point is with respect to the current element. If the coordinate point is inside the element’s rectangle, the returned value is an empty string. Conversely, if the point is completely outside the element, the returned value is the string "outside". For scroll-bar pieces, the list of possible returned values is quite lengthy (as shown in Table 26-9).
633
Part IV: Document Objects Reference elementObject.componentFromPoint() TABLE 26-9
Returned Values for componentFromPoint() Returned String
Element Component at Coordinate Point
(empty)
Inside the element content area
outside
Outside the element content area
handleBottom
Resize handle at bottom
handleBottomLeft
Resize handle at bottom left
handleBottomRight
Resize handle at bottom right
handleLeft
Resize handle at left
handleRight
Resize handle at right
handleTop
Resize handle at top
handleTopLeft
Resize handle at top left
handleTopRight
Resize handle at top right
scrollbarDown
Scroll-bar down arrow
scrollbarHThumb
Scroll-bar thumb on horizontal bar
scrollbarLeft
Scroll-bar left arrow
scrollbarPageDown
Scroll-bar page-down region
scrollbarPageLeft
Scroll-bar page-left region
scrollbarPageRight
Scroll-bar page-right region
scrollbarPageUp
Scroll-bar page-up region
scrollbarRight
Scroll-bar right arrow
scrollbarUp
Scroll-bar up arrow
scrollbarVThumb
Scroll-bar thumb on vertical bar
You do not have to use this method for most collision or event detection, however. The event object’s srcElement property returns a reference to whatever object receives the event.
Example Listing 26-24 demonstrates how the componentFromPoint() method can be used to determine exactly where a mouse event occurred. As presented, the method is associated with a textarea object that is specifically sized to display both vertical and horizontal scroll bars. As you click various areas of the textarea and the rest of the page, the status bar displays information about the location of the event with the help of the componentFromPoint() method.
634
Chapter 26: Generic HTML Element Objects elementObject.componentFromPoint() The script uses a combination of the event.srcElement property and the componentFromPoint() method to help you distinguish how you can use each one for different types of event processing. The srcElement property is used initially as a filter to decide whether the status bar will reveal further processing about the textarea element’s event details. The onmousedown event handler in the body element triggers all event processing. IE events bubble up the hierarchy (and no events are canceled in this page), so all mousedown events eventually reach the body element. Then the whereInWorld() function can compare each mousedown event from any element against the text area’s geography.
LISTING 26-24
Using the componentFromPoint() Method HTML: jsb26-24.html componentFromPoint() Method componentFromPoint() Method
Tracking the mouseDown event relative to the textarea object. View results in status bar.
This is Line 1 This is Line 2 This is Line 3 This is Line 4 This is Line 5 This is Line 6
JavaScript: jsb26-24.js function whereInWorld(elem) { var x = event.clientX; var y = event.clientY; var component = document.getElementById("myTextarea").componentFromPoint(x,y); if (window.event.srcElement == document.getElementById("myTextarea")) { continued
635
Part IV: Document Objects Reference elementObject.contains() LISTING 26-24
(continued)
if (component == "") { status = "mouseDown event occurred inside the element"; } else { status = "mouseDown occurred on the element\’s " + component; } } else { status = "mouseDown occurred " + component + " of the element"; } }
Related Item: event object
contains(elementObjectReference) Returns: Boolean Compatibility: WinIE4+, MacIE4+, NN-, Moz-, Safari+-, Opera+, Chrome+ The contains() method reports whether the current object contains another known object within its HTML containment hierarchy. Note that this is not geographical collision detection of overlapping elements, but the determination of whether one element is nested somewhere within another. The scope of the contains() method extends as deeply within the current object’s hierarchy as is necessary to locate the object. In essence, the contains() method examines all of the elements that are part of an element’s all array. Therefore, you can use this method as a shortcut replacement for a for loop that examines each nested element of a container for the existence of a specific element. The parameter to the contains() method is a reference to an object. If you have only the element’s ID as a string to go by, you can use the document.getElementById() method to generate a valid reference to the nested element.
Note
An element always contains itself.
Example Using The Evaluator (Chapter 4), see how the contains() method responds to the object combinations in each of the following statements as you enter them in the top text box: document.body.contains(document.getElementById("myP")) document.getElementById("myP").contains(document.getElementById("myEM")) document.getElementById("myEM").contains(document.getElementById("myEM")) document.getElementById("myEM").contains(document.getElementById("myP"))
636
Chapter 26: Generic HTML Element Objects elementObject.dispatchEvent() Feel free to test other object combinations within this page. Related Items: item(), document.getElementById() methods
createControlRange("param") Returns: Integer ID Compatibility: WinIE5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe createControlRange() method is used to create a control range for a selection of text. Although the method is implemented for several elements, it is intended solely for the selection object and, therefore, should be used only on that object. Related Item: selection object
detachEvent() (See attachEvent())
dispatchEvent(eventObject) Returns: Boolean Compatibility: WinIE-, MacIE-, NN6+, Moz+, Safari+, Opera+, Chrome+ The dispatchEvent() method allows a script to fire an event aimed at any object capable of supporting that event. This is the W3C event model way of generalizing mechanisms that earlier browsers sometimes mimic with object methods such as click() and focus(). The process of generating one of these events is similar to the way a script generates a new node and inserts that node somewhere into the DOM. For events, however, the object that is created is an Event object, which is generated via the document.createEvent() method. An event generated in this manner is simply a specification about an event. Use properties of an event object to supply specifics about the event, such as its coordinates or mouse button. Then dispatch the event to a target object by invoking that target object’s dispatchEvent() method and passing the newly created Event object as the sole parameter. Interpreting the meaning of the Boolean value that the dispatchEvent() method returns is not straightforward. The browser follows the dispatched event through whatever event propagation is in effect for that object and event type (either bubbling or capture). If any of the event listener functions triggered by this dispatched event invokes the preventDefault() method, the dispatchEvent() method returns false to indicate that the event did not trigger the native action of the object; otherwise, the method returns true. Notice that this returned value indicates nothing about propagation type or how many event listeners run as a result of dispatching this event.
Caution Although the dispatchEvent() method was implemented in NN6, the browser does not yet provide a way to generate new events from scratch. And if you attempt to redirect an existing event to another object via the dispatchEvent() method, the browser is prone to crashing. In other words, Mozilla-based browsers are much better candidates for scripts that use dispatchEvent().
637
Part IV: Document Objects Reference elementObject.dispatchEvent()
Example Listing 26-25 demonstrates how to fire events programmatically using the W3C DOM dispatchEvent() method. Notice the syntax in the doDispatch() function for creating and initializing a new mouse event, supported most reliably in Mozilla-based browsers. The behavior is identical to that of Listing 26-26 later in this chapter, which demonstrates the IE5.5+ equivalent: fireEvent().
LISTING 26-25
Using the dispatchEvent() Method HTML: jsb26-25.html Using the dispatchEvent() Method #mySPAN { font-style:italic; } #ctrlPanel { font-weight:bold; } dispatchEvent() Method
This is a paragraph (with a nested SPAN) that receives click events.
Control Panel
Cancel event bubbling.
638
Chapter 26: Generic HTML Element Objects elementObject.dispatchEvent()
JavaScript: jsb26-25.js // assemble a couple event object properties function getEventProps(evt) { var msg = ""; var elem = evt.target; msg += "event.target.nodeName: " + elem.nodeName + "\n"; msg += "event.target.parentNode: " + elem.parentNode.id + "\n"; msg += "event button: " + evt.button; return msg; } // onClick event handlers for body, function bodyClick(evt) { var msg = "Click event processed msg += getEventProps(evt); alert(msg); checkCancelBubble(evt); } function pClick(evt) { var msg = "Click event processed msg += getEventProps(evt); alert(msg); checkCancelBubble(evt); } function spanClick(evt) { var msg = "Click event processed msg += getEventProps(evt); alert(msg); checkCancelBubble(evt); }
myP, and mySPAN
in BODY\n\n";
in P\n\n";
in SPAN\n\n";
// cancel event bubbling if checkbox is checked function checkCancelBubble(evt) { if (document.controls.bubbleOn.checked) { evt.stopPropagation();
continued
639
Part IV: Document Objects Reference elementObject.doScroll() LISTING 26-25
(continued)
} } // assign onClick event handlers to three elements function init() { document.body.onclick = bodyClick; document.getElementById("myP").onclick = pClick; document.getElementById("mySPAN").onclick = spanClick; } // invoke dispatchEvent() on object whose ID is passed as parameter function doDispatch(objID, evt) { // create empty mouse event var newEvt = document.createEvent("MouseEvents"); // initialize as click with button ID 3 newEvt.initMouseEvent("click", true, true, window, 0, 0, 0, 0, 0, false, false, false, false, 3, null); // send event to element passed as param document.getElementById(objID).dispatchEvent(newEvt); // don’t let button clicks bubble evt.stopPropagation(); }
Related Item: fireEvent() method
doScroll("scrollAction") Returns: Nothing Compatibility: WinIE5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe doScroll() method is used to control the scrolling of an element by triggering its scroll bars. Although a subtle distinction, doScroll() doesn’t move the scroll bars to a specific position; instead, it simulates a scroll-bar click. The end result is an onscroll event being fired, which is what you would expect from a simulated scroll. The string parameter to doScroll() can be one of the following values to indicate what kind of scrolling is to take place: scrollbarUp, scrollbarDown, scrollbarLeft, scrollbarRight, scrollbarPageUp, scrollbarPageDown, scrollbarPageLeft, scrollbarPageRight, scrollbarHThumb, or scrollbarVThumb.
Chapter 26: Generic HTML Element Objects elementObject.fireEvent() The dragDrop() method initiates a mouse drag-and-drop sequence by triggering an ondragstart event. The return value is a Boolean that indicates when the user releases the mouse button (true).
fireEvent("eventType"[, eventObjectRef]) Returns: Boolean Compatibility: WinIE5.5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeAlthough some objects have methods that emulate physical events (for example, the click() and focus() methods), WinIE5.5+ generalizes the mechanism by letting a script direct any valid event to any object. The fireEvent() method is the vehicle. One required parameter is the event type, formatted as a string. IE event types are coded just like the property names for event handlers (for example, onclick, onmouseover, and so on). A second, optional parameter is a reference to an existing event object. This object can be an event that some user or system action triggers (meaning that the fireEvent() method is in a function invoked by an event handler). The existing event can also be an object created by the IE5.5+ document.createEventObject() method. In either case, the purpose of providing an existing event object is to set the properties of the event object that the fireEvent() method creates. The event type is defined by the method’s first parameter, but if you have other properties to set (for example, coordinates or a keyboard key code), those properties are picked up from the existing object. Here is an example of a sequence that creates a new mousedown event, stuffs some values into its properties, and then fires the event at an element on the page: var newEvent = document.createEventObject(); newEvent.clientX = 100; newEvent.clientY = 30; newEvent.cancelBubble = false; newEvent.button = 1; document.getElementById("myElement").fireEvent("onmousedown", newEvent);
Events generated by the fireEvent() method are just like regular IE window.event objects, and they have several important event object properties that the browser presets. It is important that cancelBubble is set to false and returnValue is set to true — just like a regular user- or system-induced event. This means that if you want to prevent event bubbling and/or prevent the default action of the event’s source element, the event handler functions must set these event object properties just like normal event handling in IE. The fireEvent() method returns a Boolean value that the returnValue property of the event determines. If the returnValue property is set to false during event handling, the fireEvent() method returns false. Under normal processing, the method returns true. The W3C DOM (Level 2) event model includes the dispatchEvent() method to accommodate script-generated events (and Event object methods to create event objects), which is roughly the W3C equivalent of the fireEvent() method.
Example Listing 26-26 contains script code that shows how to fire events programmatically using the fireEvent() method. Three buttons in the example page enable you to direct a click event to each of the three elements that have event handlers defined for them. The events fired this way are artificial, generated via the createEventObject() method. For demonstration purposes, the button property of these scripted events is set to 3. This property value is assigned to the event
641
Part IV: Document Objects Reference elementObject.fireEvent() object that eventually gets directed to an element. With event bubbling left on, the events sent via fireEvent() behave just like the physical clicks on the elements. Similarly, if you disable event
bubbling, the first event handler to process the event cancels bubbling, and no further processing of that event occurs. Notice that event bubbling is canceled within the event handlers that process the event. To prevent the clicks of the checkbox and action buttons from triggering the body element’s onclick event handlers, event bubbling is turned off for the buttons right away.
LISTING 26-26
Using the fireEvent() Method HTML: jsb26-26.html Using the fireEvent() Method #mySPAN { font-style:italic; } #ctrlPanel { font-weight:bold; } fireEvent() Method
This is a paragraph (with a nested SPAN) that receives click events.
Control Panel
Cancel event bubbling.
JavaScript: jsb26-26.js // assemble a couple event object properties function getEventProps() { var msg = ""; var elem = event.srcElement; msg += "event.srcElement.tagName: " + elem.tagName + "\n"; msg += "event.srcElement.id: " + elem.id + "\n"; msg += "event button: " + event.button; return msg; } // onClick event handlers for body, function bodyClick() { var msg = "Click event processed msg += getEventProps(); alert(msg); checkCancelBubble(); } function pClick() { var msg = "Click event processed msg += getEventProps(); alert(msg); checkCancelBubble(); } function spanClick() { var msg = "Click event processed msg += getEventProps(); alert(msg); checkCancelBubble(); }
myP, and mySPAN
in BODY\n\n";
in P\n\n";
in SPAN\n\n";
// cancel event bubbling if checkbox is checked function checkCancelBubble() { event.cancelBubble = document.controls.bubbleOn.checked; } // assign onClick event handlers to three elements
continued
643
Part IV: Document Objects Reference elementObject.getAdjacentText() LISTING 26-26
(continued)
function init() { document.getElementById("myBODY").onclick = bodyClick; document.getElementById("myP").onclick = pClick; document.getElementById("mySPAN").onclick = spanClick; } // invoke fireEvent() on object whose ID is passed as parameter function doFire(objID) { var newEvt = document.createEventObject(); newEvt.button = 3; document.all(objID).fireEvent("onclick", newEvt); // don’t let button clicks bubble event.cancelBubble = true; }
Related Item: dispatchEvent() method
focus() (See blur())
getAdjacentText("position") Returns: String Compatibility: WinIE5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe getAdjacentText() method enables you to extract copies of plain-text components of an element object (in other words, without any HTML tag information). The sole parameter is one of four case-insensitive string constant values that indicate from where, in relation to the current object, the text should be extracted. The values are:
644
Parameter Value
Description
beforeBegin
Text immediately in front of the element’s tag, back to the preceding tag
afterBegin
Text that begins inside the element tag, up to the next tag (whether it be a nested element or the element’s end tag)
beforeEnd
Text immediately in front of the element’s end tag, back to the preceding tag (whether it be a nested element or the element’s start tag)
afterEnd
Text immediately following the element’s end tag, forward until the next tag
Chapter 26: Generic HTML Element Objects elementObject.getAttribute() If the current object has no nested elements, both the afterBegin and beforeEnd versions return the same as the object’s innerText property. When the current object is encased immediately within another element (for example, a td element inside a tr element), there is no text before the element’s beginning or after the element’s end, so these values are returned as empty strings. The strings returned from this method are roughly equivalent to values of text fragment nodes in the W3C DOM, but IE5+ treats these data pieces as string data types rather than as text node types. W3C DOM equivalents for the four versions are document.getElementById("objName").previousSibling.nodeValue document.getElementById("objName").firstChild.nodeValue document.getElementById("objName").lastChild.nodeValue document.getElementById("objName").nextSibling.nodeValue
Example Use The Evaluator (see Chapter 4) to examine all four adjacent text possibilities for the myP and nested myEM elements in that document. Enter each of the following statements in the top text box, and view the results: document.getElementById("myP").getAdjacentText("beforeBegin") document.getElementById("myP").getAdjacentText("afterBegin") document.getElementById("myP").getAdjacentText("beforeEnd") document.getElementById("myP").getAdjacentText("afterEnd")
The first and last statements return empty strings because the myP element has no text fragments surrounding it. The afterBegin version returns the text fragment of the myP element up to, but not including, the EM element nested inside. The beforeEnd string picks up after the end of the nested EM element and returns all text to the end of myP. Now see what happens with the nested myEM element: document.getElementById("myEM").getAdjacentText("beforeBegin") document.getElementById("myEM").getAdjacentText("afterBegin") document.getElementById("myEM").getAdjacentText("beforeEnd") document.getElementById("myEM").getAdjacentText("afterEnd")
Because this element has no nested elements, the afterBegin and beforeEnd strings are identical — the same value as the innerText property of the element. Related Items: childNodes, data, firstChild, lastChild, nextSibling, nodeValue, and previousSibling properties
getAttribute("attributeName"[, caseSensitivity]) Returns: (See text) Compatibility: WinIE4+, MacIE4+, NN6+, Moz+, Safari+, Opera+, Chrome+ The getAttribute() method returns the value assigned to a specific attribute of the current object. You can use this method as an alternative to retrieving properties of an object, particularly when your
645
Part IV: Document Objects Reference elementObject.getAttributeNode() script presents you the attribute name as a string (in contrast to a fully formed reference to an object and its property). Thus, the following example statements yield the same data: var mult = document.getElementById("mySelect").multiple; var mult = document.getElementById("mySelect").getAttribute("multiple");
Returned value types from getAttribute() are either strings (including attribute values assigned as unquoted numeric values) or Booleans (for example, the multiple property of a select element object).
Note The W3C DOM Level 2 standard recommends getAttribute() and setAttribute() for reading and writing element object attribute values, rather than reading and writing those values by way of their corresponding properties. Although using these methods is certainly advisable for XML elements, the same DOM standard sends conflicting signals by defining all kinds of properties for HTML element objects. Browsers, of course, will support access via properties well into the future, so don’t feel obligated to change your ways just yet.
All browsers that support the getAttribute() method require one parameter, which is a string of the attribute name. By default, this parameter is not case sensitive. Note that this has impact on custom attributes that you might assign to HTML or XML elements in your documents. Attribute names are automatically converted to lowercase when they are turned into properties of the object. Therefore, you must avoid reusing attribute names, even if you use different case letters in the source-code assignments. IE includes an optional extension to the method in the form of a second parameter that enables you to be more specific about the case sensitivity of the first parameter. The default value of the second parameter is false, which means that the first parameter is not case sensitive. A value of true makes the first parameter case sensitive. This matters only if you use setAttribute() to add a parameter to an existing object and if the IE version of that method insists on case sensitivity. The default behavior of setAttribute() respects the case of the attribute name. See also the discussion of the setAttribute() method later in this chapter with regard to setAttribute()’s influence on the IE attributes property.
Example Use The Evaluator (see Chapter 4) to experiment with the getAttribute() method for the elements in the page. You can enter the following sample statements in the top text box to view attribute values: document.getElementById("myTable").getAttribute("cellpadding") document.getElementById("myTable").getAttribute("border")
Related Items: attributes property; document.createAttribute(), setAttribute() methods
getAttributeNode("attributeName") Returns: Attribute node object Compatibility: WinIE6+, MacIE-, NN6+, Moz+, Safari+, Opera+, Chrome+ In the W3C DOM, an attribute is an object that inherits all the properties of a Node object (see Chapter 25). As its name implies, an attribute object represents a name-value pair of an attribute that
646
Chapter 26: Generic HTML Element Objects elementObject.getAttributeNode() is explicitly defined inside an element’s tag. The ability to treat attributes as node objects is far more important when working with XML than HTML, but it is helpful to understand attribute nodes within the context of the W3C DOM object-oriented view of a document. It is important that attribute nodes specifically are not recognized as nodes of a document hierarchy. Therefore, an attribute node is not a child node of the element that defines the attribute. The nodeness of attributes comes into play when addressing the contents of an object’s attributes property. The W3C attributes property builds on the DOM’s formal structure by returning an object known (internally) as a named node map. Like an array, the named node map has a length property (facilitating for loop iteration through the map), plus several methods that allow for inserting, removing, reading, or writing attribute name-value pairs within the node map. An attribute object inherits all the properties of the Node object. Table 26-10 lists the properties of an attribute object. All of this is a long way to explain the W3C DOM getAttributeNode() method, which returns a W3C DOM attribute object. The sole parameter of the method is a case-insensitive string version of the attribute’s name. Then you can use any of the properties shown in Table 26-10 to get or set attribute values. Of course, HTML attributes are generally exposed as properties of HTML elements, so it is usually easier to read or write the object’s properties directly.
TABLE 26-10
Attribute Object Properties of W3C DOM–Compatible Browsers attributes childNodes firstChild lastChild name nextSibling nodeName nodeType nodeValue ownerDocument parentNode previousSibling specified value
647
Part IV: Document Objects Reference Generic.getAttributeNodeNS()
Example Use The Evaluator (see Chapter 4) to explore the getAttributeNode() method. The Results textarea element provides several attributes to check out. Because the method returns an object, enter the following statements in the bottom text box so you can view the properties of the attribute node object returned by the method: document.getElementById("myTextArea").getAttributeNode("cols") document.getElementById("myTextArea").getAttributeNode("rows") document.getElementById("myTextArea").getAttributeNode("wrap") document.getElementById("myTextArea").getAttributeNode("style")
All (except the last) statements display a list of properties for each attribute node object. The last statement, however, returns nothing because the style attribute is not specified for the element. You can also use The Evaluator to explore the properties of the attribute object returned by the getAttributeNode() method. Enter the following statement in the top text box: document.getElementById("myTextArea").getAttributeNode("cols").value
Related Items: attributes property; getAttribute(), removeAttributeNode(), setAttributeNode() methods
getAttributeNodeNS("namespaceURI", "localName") Returns: Attribute node object Compatibility: WinIE-, MacIE-, NN6+, Moz+, Safari+-, Opera+, Chrome_ This method returns a W3C DOM attribute object. The first parameter of the method is a URI string matching a URI assigned to a label in the document. The second parameter is the local name portion of the attribute you are getting. Related Items: attributes, namespaceURI, localName properties; getAttributeNode(), setAttributeNodeNS() methods
getAttributeNS("namespaceURI", "localName") Returns: (See text) Compatibility: WinIE-, MacIE-, NN6+, Moz+, Safari+-, Opera+, Chrome+ This method returns the value assigned to a specific attribute of the current object when that attribute’s name is defined by way of an XML namespace definition within the document. The first parameter of the method is a URI string matching a URI assigned to a namespace label in a tag defined earlier in the document. The second parameter is the local name portion of the attribute whose value you are getting. Returned value types from getAttributeNS() are either strings (including attribute values assigned as unquoted numeric values) or Booleans (for example, the multiple property of a select element object). In the W3C DOM, Netscape, Safari, and Opera, return values are always strings. Related Items: attributes, namespaceURI, localName properties; getAttribute(), getAttributeNodeNS(), setAttributeNodeNS() methods
648
Chapter 26: Generic HTML Element Objects elementObject.getClientRects()
getBoundingClientRect() getClientRects() Returns: getBoundingClientRect() returns a TextRectangle object; getClientRects() returns an array of TextRectangle objects Compatibility: WinIE5+, MacIE-, NN-, Moz+-, Safari+-, Opera+, Chrome+ Original with IE5+, most modern browsers assign to every content-holding element a rectangle that describes the space that the element occupies on the page. This rectangle is called a bounding rectangle, and it is expressed as a TextRectangle object (even when the content is an image or some other kind of object). A TextRectangle object has four properties (top, left, bottom, and right) that are the pixel coordinates that define the rectangle. You can get the same information from older browsers that do not support the TextRectangle object with offsetTop, offsetLeft, offsetHeight, and offsetWidth. The getBoundingClientRect() method returns a TextRectangle object that describes the bounding rectangle of the current object. You can access an individual measure of an object’s bounding rectangle, as in the following example: var parTop = document.getElementById("myP").getBoundingClientRect().top;
For elements that consist of text, such as paragraphs, the dimensions of individual TextRectangles for each line of text in the element influence the dimensions of the bounding rectangle. For example, if a paragraph contains two lines, and the second line extends only halfway across the width of the first line, the width of the second line’s TextRectangle object is only as wide as the actual text in the second line. But because the first line extends close to the right margin, the width of the encompassing bounding rectangle is governed by that wider, first line TextRectangle. Therefore, an element’s bounding rectangle is as wide as its widest line and as tall as the sum of the height of all TextRectangle objects in the paragraph. The method getClientRects() enables you to obtain a collection of line-by-line TextRectangle objects for an element. It returns an array of all TextRectangle objects that fall within the current object the moment the method is invoked. Each TextRectangle object has its own top, left, bottom, and right coordinate properties. You can then, for example, loop through all objects in this array to calculate the pixel width of each line. If you want to find out the aggregate height and/or maximum width of the entire collection, you can use the getBoundingClientRect() method as a shortcut. The length of the collection returned by getClientRects() is where you’ll see differences between the browsers. WebKit-based browsers and earlier releases of Mozilla-based browsers have only one TextRectangle object in the collection returned by getClientRects() for each block element found in the argument passed to it. IE and the most recent releases of Mozilla-based browsers will do the same only if a width is specified for a block element. Presto-based browsers always return a collection of one regardless of how many elements, block or not, are involved. All that we’ve said so far just pertains to an argument that is not identified by a block element (for example, the argument passed to getClientRects() in Listing 26-27a is a span element). If the argument is a block element (for example a div), then the only browser that returns a collection of TextRectangle objects for each line is IE. Obviously, this can be very frustrating for scripters. Keep this in mind when looking at Listings 26-27a and 26-27b in the various browsers.
Example Listing 26-27a employs only the getClientRects() method. (We’ll look at both methods in Listing 26-27b in a moment.) The element passed to the getClientRects() method is a span and it contains two paragraphs and an ordered list. The area contained by it is colored blue. There is a button that generates an alert about the length of the collection that is returned by the method.
649
Part IV: Document Objects Reference elementObject.getClientRects() LISTING 26-27a
How many TextRectangle objects are in the collection?
Lorem ipsum dolor sit amet, consectetaur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim adminim veniam, quis nostrud exercitation ullamco:
laboris
nisi
aliquip ex ea commodo
Duis aute irure dolor in reprehenderit involuptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deseruntmollit anim id est laborum. Et harumd und lookum like Greek to me, dereud facilis est er expedit distinct.
650
Chapter 26: Generic HTML Element Objects elementObject.getClientRects() JavaScript: jsb26-27a.js function howMany() { var clientRects = document.getElementById("main").getClientRects(); alert("The length of the rectangle returned by getClientRects() is =" + clientRects.length + "."); }
Listing 26-27b employs both the getBoundingClientRect() and getClientRects() methods in a demonstration of how they differ. While the listing works in all major browsers, due to the differences you’ve already since in the collection returned by the getClientRects() method, you’ll only really see anything meaningful in IE, and you’ll only really want to use it in IE anyway. Keep in mind, though, that you don’t have to use the two methods together; there are many things you can do regardless of the browser with just the getBoundingClientRect() method. As with Listing 26-27a, a set of elements is grouped within a span element named main. The group consists of two paragraphs and an unordered list, all of whose text is colored blue. Two controls enable you to set the position of an underlying highlight rectangle to any line of your choice. A checkbox enables you to set whether the highlight rectangle should be only as wide as the line or the full width of the bounding rectangle for the entire span element. All the code is located in the hilite() function. The select and checkbox elements invoke this function. Early in the function, the getClientRects() method is invoked for the main element to capture a snapshot of all TextRectangles for the entire element. This array comes in handy when the script needs to get the coordinates of a rectangle for a single line, as chosen in the select element. Whenever the user chooses a number from the select list, and the value is less than the total number of TextRectangle objects in clientRects, the function begins calculating the size and location of the underlying yellow highlighter. When the Full Width checkbox is checked, the left and right coordinates are obtained from the getBoundingClientRect() method because the entire span element’s rectangle is the space you’re interested in; otherwise, you pull the left and right properties from the chosen rectangle in the clientRects array. Next comes the assignment of location and dimension values to the hiliter object’s style property. The top and bottom are always pegged to whatever line is selected, so the clientRects array is polled for the chosen entry’s top and bottom properties. The previously calculated left value is assigned to the hiliter object’s pixelLeft property, whereas the width is calculated by subtracting the left from the right coordinates. Notice that the top and left coordinates also take into account any vertical or horizontal scrolling of the entire body of the document. If you resize the window smaller, line wrapping throws off the original line count. However, an invocation of hilite() from the onresize event handler applies the currently chosen line number to whatever content falls in that line after resizing. Because the z-index style property of the hiliter element is set to -1, the element always appears beneath the primary content on the page. If the user selects a line number beyond the current number of lines in the main element, the hiliter element is hidden.
651
Part IV: Document Objects Reference elementObject.getBoundingClientRect() LISTING 26-27b
Using getBoundingClientRect() HTML: jsb26-27b.html getClientRects() and getBoundClientRect() Methods #main { color:blue; } getClientRects() and getBoundClientRect() Methods Choose a line to highlight: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Full Width (bounding rectangle)
Lorem ipsum dolor sit amet, consectetaur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim adminim veniam, quis nostrud exercitation ullamco:
652
Chapter 26: Generic HTML Element Objects elementObject.getBoundingClientRect()
laboris
nisi
aliquip ex ea commodo
Duis aute irure dolor in reprehenderit involuptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deseruntmollit anim id est laborum Et harumd und lookum like Greek to me, dereud facilis est er expedit distinct.
JavaScript: jsb26-27b.js function hilite() { var hTop, hLeft, hRight, hBottom, hWidth; var selectList = document.getElementById("choice"); var n = parseInt(selectList.options[selectList.selectedIndex].value) - 1; var clientRects = document.getElementById("main").getClientRects(); var mainElem = document.getElementById("main"); if (n >= 0 && n < clientRects.length) { if (document.forms[0].fullWidth.checked) { hLeft = mainElem.getBoundingClientRect().left; hRight = mainElem.getBoundingClientRect().right; } else { hLeft = clientRects[n].left; hRight = clientRects[n].right; } document.getElementById("hiliter").style.pixelTop = clientRects[n].top + document.getElementById("myBody").scrollTop; document.getElementById("hiliter").style.pixelBottom = clientRects[n].bottom; document.getElementById("hiliter").style.pixelLeft = hLeft + document.getElementById("myBody").scrollLeft; document.getElementById("hiliter").style.pixelWidth = hRight - hLeft; document.getElementById("hiliter").style.visibility = "visible"; } else if (n > 0) { continued
653
Part IV: Document Objects Reference elementObject.getElementsByTagName() LISTING 26-27b
(continued)
alert("The content does not have that many lines."); document.getElementById("hiliter").style.visibility = "hidden"; } }
Related Item: TextRectangle object (Chapter 33, on the CD-ROM)
getElementsByTagName("tagName") Returns: Array of element objects Compatibility: WinIE5+, MacIE5+, NN6+, Moz+, Safari+, Opera+, Chrome+ The getElementsByTagName() method returns an array of all elements contained by the current object whose tags match the tag name supplied as the sole parameter to the method. The tag name parameter must be in the form of a string and is case insensitive. The group of elements returned in the array includes only those elements that are within the containment scope of the current object. Therefore, if you have two table objects in a document, and you invoke the getElementsByTagName("td") method on one of them, the list of returned table cell elements is confined to those cells within the current table object. The current element is not included in the returned array. For MacIE5, WinIE6+, and all other supporting browsers, the method accepts a wildcard character ("*") for matching descendent elements regardless of tag name. The resulting array of elements is nearly identical to what IE4+ returns via the document.all collection.
Example Use The Evaluator (see Chapter 4) to experiment with the getElementsByTagName() method. Enter the following statements one at a time in the top text box, and study the results: document.body.getElementsByTagName("div") document.body.getElementsByTagName("div").length document.getElementById("myTable").getElementsByTagName("td").length
Because the getElementsByTagName() method returns an array of objects, you can use one of those returned values as a valid element reference: document.getElementsByTagName("form")[0].getElementsByTagName("input").length
Related Items: getElementByTagNameNS(), getElementById(), tags() methods
getElementsByTagNameNS("namespaceURI", "localName") Returns: Array of element objects Compatibility: WinIE-, MacIE-, NN6+, Moz+, Safari+, Opera+, Chrome+
654
Chapter 26: Generic HTML Element Objects elementObject.getUserData() This method returns an array of all elements contained by the current object (within an XML document) as specified in the two parameters. The first parameter of the method is a URI string matching a URI assigned to a label in the document. The second parameter is the local name portion of the attribute whose value you are getting. Returned value types from getAttributeNS() are either strings (including attribute values assigned as unquoted numeric values) or Booleans (for example, the multiple property of a select element object). Related Items: attributes, namespaceURI, localName properties; getElementsByTagNameNS(), getElementById(), tags() methods
getExpression("attributeName") Returns: String Compatibility: WinIE5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe getExpression() method returns the text of the expression that was assigned to an element’s attribute via the setExpression() method. The returned value is not the value of the expression, but the expression itself. If you want to find out the current value of the expression (assuming that the variables used are within the scope of your script), you can use the eval() function on the call to getExpression(). This action converts the string to a JavaScript expression and returns the evaluated result. One parameter, a string version of the attribute name, is required.
Example See Listing 26-32 for the setExpression() method. This listing demonstrates the kinds of values returned by getExpression(). Related Items: document.recalc(), removeExpression(), setExpression() methods
getFeature("feature", "version") Returns: Object Compatibility: WinIE-, MacIE-, NN-, Moz1.7.2+, Safari-, Opera+, ChromeAccording to the W3C DOM specification, the getFeature() method accepts a scripting feature and version, and returns an object that implements the APIs for the feature. Examples of possible feature parameters to this method are Core and Events, which correspond to DOM modules. As recently as Mozilla 1.8.1 (Firefox 2.0), the getFeature() method returns an object but the object exposes no API features to the script. Related Item: implementation.hasFeature() method
getUserData("key") Returns: Object Compatibility: WinIE-, MacIE-, NN6-, Moz1.7.2+, Safari+-, Opera-, Chrome+ The getUserData() method enables you to access custom user data that has been associated with a node. A given node can have multiple objects of user data, in which case each one is identified
655
Part IV: Document Objects Reference elementObject.hasAttribute() through a text key. This key is the parameter that you pass into getUserData() to obtain a user data object. As of Mozilla 1.8.1 (Firefox 2.0), the method is only partially implemented and, therefore, still not useful.
hasAttribute("attributeName") Returns: Boolean Compatibility: WinIE+, MacIE-, NN6+, Moz+, Safari+, Opera+, Chrome+ The hasAttribute() method returns true if the current object has an attribute whose name matches the sole parameter; it returns false otherwise. Related Items: hasAttributeNS(), hasAttributes() methods
hasAttributeNS("namespaceURI", "localName") Returns: Boolean Compatibility: WinIE-, MacIE-, NN6+, Moz+, Safari+, Opera+, Chrome+ The hasAttributeNS() method returns true if the current object has an attribute as identified by the two parameters; it returns false otherwise. The first parameter of the method is a URI string matching a URI assigned to a label in the document. The second parameter is the local name portion of the attribute whose value you are getting. Related Items: attributes, namespaceURI, localName properties; hasAttribute(), hasAttributes() methods
hasAttributes() Returns: Boolean Compatibility: WinIE+, MacIE-, NN6+, Moz+, Safari+, Opera+, Chrome+ The hasAttributes() method returns true if the current object has any attributes explicitly assigned within the tag; it returns false otherwise. Related Items: hasAttribute(), hasAttributeNS() methods
hasChildNodes() Returns: Boolean Compatibility: WinIE5+, MacIE5+, NN6+, Moz+, Safari+, Opera+, Chrome+ The hasChildNodes() method returns true if the current object has child nodes nested within; it returns false otherwise. A child node is not necessarily the same as a child element, so the following two expressions return true when the current object has at least one child node: document.getElementById("myObject").hasChildNodes() document.getElementById("myObject").childNodes.length > 0
You cannot use the second expression interchangeably with the following statement (which uses the children property): document.getElementById("myObject").children.length > 0
656
Chapter 26: Generic HTML Element Objects elementObject.insertAdjacentElement() You generally use the hasChildNodes() method in a conditional expression to make sure such nodes exist before performing operations on them: if (document.getElementById("myObject").hasChildNodes() { // [statements that apply to child nodes] }
Example Use The Evaluator (see Chapter 4) to experiment with the hasChildNodes() method. If you enter the following statement in the top text box document.getElementById("myP").hasChildNodes()
the returned value is true. You can find out how many nodes there are by getting the length of the childNodes array: document.getElementById("myP").childNodes.length
This expression reveals a total of three nodes: the two text nodes and the em element between them. Check out whether the first text node has any children: document.getElementById("myP").childNodes[0].hasChildNodes()
The response is false because text fragments do not have any nested nodes. But check out the em element, which is the second child node of the myP element: document.getElementById("myP").childNodes[1].hasChildNodes()
The answer is true because the em element has a text fragment node nested within it. Sure enough, the statement document.getElementById("myP").childNodes[1].childNodes.length
yields a node count of 1. You can also go directly to the em element in your references: document.getElementById("myEM").hasChildNodes() document.getElementById("myEM").childNodes.length
If you want to see the properties of the text fragment node inside the em element, enter the following in the bottom text box: document.getElementById("myEM").childNodes[0]
You can see that the data and nodeValue properties for the text fragment return the text "all". Related Items: childNodes property; appendChild(), removeChild(), replaceChild() methods.
Part IV: Document Objects Reference elementObject.insertAdjacentHTML() The insertAdjacentElement() method inserts an element object (coming from a variety of sources) into a specific position relative to the current object. Both parameters are required. The first must be one of four possible case-insensitive locations for the insertion, shown in the following table:
Location
Description
beforeBegin
Before the current element’s start tag
afterBegin
After the start tag but before any nested content
beforeEnd
Before the end tag but after all other nested content
afterEnd
After the end tag
These locations are relative to the current object. The element type of the current object (a block-level or inline element) has great bearing on how the inserted element is rendered. For example, suppose that you create a b element (using document.createElement()) and assign some inner text to it. You then use insertAdjacentElement() in an effort to insert this b element before some text in a p element. Because a p element is a block-level element, the location beforeBegin places the new b element before the start tag of the p element. This means, however, that the bold text appears in a text line above the start of the p element because a
tag begins a new block at the left margin of its container (unless instructed otherwise by style sheets). The resulting HTML looks like the following: The new element.
The original paragraph element.
To make the new b element a part of the p element — but in front of the existing p element’s content — use the afterBegin location. The resulting HTML looks like the following:
The new element.The original paragraph element.
To complete the demonstration of the four location types, the following is the result of the beforeEnd location:
The original paragraph element. The new element.
And this is the result of the afterEnd location:
The original paragraph element.
The new element.
The object to be inserted is a reference to an element object. The object reference can come from any expression that evaluates to an element object or, more likely, from the result of the document.createElement() method. Bear in mind that the object generated by document.createElement() initially has no content, and all attribute values are set to default values. Moreover, the object is passed to insertAdjacentElement() by reference, which means that there is only one instance of that object. If you attempt to insert that object in two places with two statements, the object is moved from the first location to the second. If you need to copy an existing object so that the original is not moved or otherwise disturbed by this method, use the cloneNode() method to specify the true parameter to capture all nested content of the node.
658
Chapter 26: Generic HTML Element Objects elementObject.insertAdjacentText()
Example Use The Evaluator (see Chapter 4) in WinIE5+ to experiment with the insertAdjacentElement() method. The goal of the experiment is to insert a new h1 element above the myP element. All actions require you to enter a sequence of statements in the top text box. Begin by storing a new element in the global variable a: a = document.createElement("h1")
Give the new object some text: a.innerText = "New Header"
Now insert this element before the start of the myP object: myP.insertAdjacentElement("beforeBegin", a)
Notice that you have not assigned an id property value to the new element. But because the element was inserted by reference, you can modify the inserted object by changing the object stored in the a variable: a.style.color = "red"
The inserted element is also part of the document hierarchy, so you can access it through hierarchy references such as myP.previousSibling. The parent element of the newly inserted element is the body. Thus, you can inspect the current state of the HTML for the rendered page by entering the following statement in the top text box: document.body.innerHTML
If you scroll down past the first form, you can find the element that you added along with the style attribute. Related Items: document.createElement(), applyElement() methods
insertAdjacentHTML("location", "HTMLtext") insertAdjacentText("location", "text") Returns: Nothing Compatibility: WinIE4+, MacIE4+, NN-, Moz-, Safari+, Opera+, Chrome+ These two methods insert HTML or straight text at a location relative to the current element. They are intended for use after a page loads, rather than inserting content while the page loads (in which case you can use document.write() wherever you need evaluated content to appear on the page).
659
Part IV: Document Objects Reference elementObject.insertAdjacentText() The first parameter must be one of four possible case-insensitive locations for the insertion, shown in the following table:
Location
Description
beforeBegin
Before the current element’s start tag
afterBegin
After the start tag but before any nested content
beforeEnd
Before the end tag but after all other nested content
afterEnd
After the end tag
These locations yield the same results as described in the insertAdjacentElement() function discussed earlier in this chapter. Whether you use insertAdjacentHTML() or insertAdjacentText() depends on the nature of your content and what you want the browser to do with it. If the content contains HTML tags that you want the browser to interpret and render as though it were part of the page source code, use the insertAdjacentHTML() method. All tags become objects in the document’s object model. But if you want only to display some text (including HTML tags in their raw form), use insertAdjacentText(). The rendering engine does not interpret any tags included in the string passed as the second parameter. Instead, these tags are displayed as characters on the page. This distinction is identical to the one between the innerHTML and innerText properties. The difference between insertAdjacentHTML() and insertAdjacentElement() is the nature of the content that you insert. The former enables you to accumulate the HTML as a string, whereas the latter requires the creation of an element object. Also, the two methods in this section work with IE4+ (including Mac versions), whereas insertAdjacentElement() requires the newer object model of WinIE5+. If the HTML you pass as the second parameter of insertAdjacentHTML() contains tags, you must set the defer attribute in the opening tag. This prevents script statements from executing as you insert them.
Example Use The Evaluator (see Chapter 4) to experiment with these two methods. The example here demonstrates the result of employing both methods in an attempt to add some HTML to the beginning of the myP element. Begin by assigning a string of HTML code to the global variable a: a = "Important News!"
Because this HTML is to go on the same line as the start of the myP paragraph, use the afterBegin parameter for the insert method: myP.insertAdjacentHTML("afterBegin", a)
660
Chapter 26: Generic HTML Element Objects elementObject.insertBefore() Notice that there is no space after the exclamation mark of the inserted HTML. But to prove that the inserted HTML is genuinely part of the document’s object model, now you can insert the text of a space after the b element whose ID is myB: myB.insertAdjacentText("afterEnd", " ")
Each time you evaluate the preceding statement (by repeatedly clicking the Evaluate button or pressing Enter with the cursor in the top text box), another space is added. You should also see what happens when the string to be inserted with insertAdjacentText() contains HTML tags. Reload The Evaluator, and enter the following two statements in the top text box, evaluating each one in turn: a = "Important News!" myP.insertAdjacentText("afterBegin", a)
The HTML is not interpreted but is displayed as plain text. There is no object named myB after executing this latest insert method. Related Items: innerText, innerHTML, outerText, outerHTML properties; insertAdjacentElement(), replaceAdjacentText() methods
insertBefore(newChildNodeObject, referenceChildNode) Returns: Node object Compatibility: WinIE5+, MacIE5+, NN6+, Moz+, Safari+, Opera+, Chrome+ The insertBefore() method is the W3C DOM syntax for inserting a new child node into an existing element. Node references for both parameters must be valid Node objects (including those that document.createElement() generates). The behavior of this method might seem counterintuitive at times. If you include the second parameter (a reference to an existing child node of the current element — optional in IE), the new child node is inserted before that existing one. But if you omit the second parameter (or its value is null), the new child node is inserted as the last child of the current element — in which case the method acts the same as the appendChild() method. The true power of this method is summoned when you specify that second parameter; from the point of view of a parent element, you can drop a new child into any spot among its existing children. If an inserted node already exists in the document tree, it will be removed from its previous position. Bear in mind that the insertBefore() method works from a parent element. Internet Explorer provides additional methods, such as insertAdjacentElement(), to operate from the perspective of what will become a child element.
Example Listing 26-28 demonstrates how the insertBefore() method can insert child elements (li) inside a parent (ol) at different locations, depending on the second parameter. A text box enables you to enter your choice of text and/or HTML for insertion at various locations within the ol element. If you don’t specify a position, the second parameter of insertBefore() is passed as null — meaning that the new child node is added to the end of the existing children. But choose a spot from the select
661
Part IV: Document Objects Reference elementObject.insertBefore() list where you want to insert the new item. The value of each select list option is an index of one of the first three child nodes of the ol element.
LISTING 26-28
Using the insertBefore() Method HTML: jsb26-28.html insertBefore() Method insertBefore() Method
Enter text or HTML for a new list item:
Before which existing item? None specified 1 2 3
Originally the First Item
Originally the Second Item
Originally the Third Item
JavaScript: jsb26-28.js function doInsert(form) { if (form.newText) { var newChild = document.createElement("LI"); newChild.innerHTML = form.newText.value;
662
Chapter 26: Generic HTML Element Objects elementObject.isSupported() var choice = form.itemIndex.options[form.itemIndex.selectedIndex].value; var insertPoint = (isNaN(choice)) ? null : document.getElementById("myUL").childNodes[choice]; document.getElementById("myUL").insertBefore(newChild, insertPoint); } }
Related Items: appendChild(), replaceChild(), removeChild(), insertAdjacentElement() methods
isDefaultNamespace("namespaceURI") Returns: Boolean Compatibility: WinIE-, MacIE-, NN6-, Moz1.7.2+, Safari+, Opera+, Chrome+ This method checks whether the specified namespace matches the default namespace of the current node.
isEqualNode(nodeRef) isSameNode(nodeRef) Returns: Integer ID Compatibility: WinIE-, MacIE-, NN-, Moz1.7.2+, Safari+, Opera+, Chrome+ When it comes to nodes, there is a distinct difference between a node being equal to another node and a node being the same as another node. Equality has a very specific meaning with respect to nodes: Two nodes are considered equal if they have the same values for the attributes, childNodes, localname, namespaceURI, nodeName, nodeType, nodeValue, and prefix properties. Together, these properties essentially reflect the content of a node. What they don’t reflect is the relative position of a node within a document, which means that nodes can be equal and reside in different locations in the node tree. Two nodes are considered the same if . . . well, they are the same identical node. The isEqualNode() method checks for node equality, whereas isSameNode() checks whether two nodes are the same. Both methods expect a node reference as their only parameter. Currently, Opera does not support the isEqualNode() method.
isSupported("feature", "version") Returns: Boolean Compatibility: WinIE-, MacIE-, NN6+, Moz+, Safari+, Opera+, Chrome+ The isSupported() method returns true if the current node supports required portions of the specified W3C DOM module and version; it returns false otherwise. The first parameter accepts any of the following case-sensitive DOM module name strings: Core, XML, HTML, Views, StyleSheets, CSS, CSS2, Events, UIEvents, MouseEvents, MutationEvents, HTMLEvents, Range, and Traversal. The second parameter accepts a string representation of the major and minor DOM module version, such as "2.0" for DOM Level 2.
663
Part IV: Document Objects Reference elementObject.item()
Example Use The Evaluator (see Chapter 4) to experiment with the isSupported() method. If you have multiple versions of NN6 or later and Mozilla, try the following (and others) to see how the support for various modules has evolved: document.body.isSupported("CSS", "2.0") document.body.isSupported("CSS2", "2.0") document.body.isSupported("Traversal", "2.0")
If you have access to Safari, Opera, or Chrome, try the same methods there to see the differences in modules supported compared with Mozilla-based browsers.
item(index | "index" [, subIndex]) Returns: Object Compatibility: WinIE4+, MacIE4+, NN6+, Moz+, Safari+, Opera+, Chrome+ The item() method works with most objects that are themselves collections of other objects. In W3C DOM terminology, these kinds of objects are known as named node lists (for objects such as nodes and attributes) or HTML collections (for objects such as elements of a form). You may call the item() method with a single numeric parameter that is the index value of the desired object within the collection. If you know the index number of the item, you can use JavaScript array syntax instead. The following two statements return the same object reference: document.getElementById("myTable").childNodes.item(2) document.getElementById("myTable").childNodes[2]
The method also supports a string of the ID of an object within the collection. (Integer values are required for the attributes, rules, and TextRectangle objects, however.) Additionally, if the collection has more than one object with the same ID (never a good idea except when necessary), a second numeric parameter enables you to select which identically named group you want (using zero-based index values within that subgroup). This obviously does not apply to collections, such as attributes and rules, which have no ID associated with them. The method returns a reference to the object specified by the parameters.
Example Use The Evaluator (see Chapter 4) to experiment with the item() method. Type the following statements in the top text box, and view the results for each. W3C and IE5: document.getElementById("myP").childNodes.length document.getElementById("myP").childNodes.item(0).data document.getElementById("myP").childNodes.item(1).nodeName
W3C, IE4, and IE5:
664
Chapter 26: Generic HTML Element Objects elementObject.mergeAttributes() document.forms[1].elements.item(0).type
The first approach is helpful when your script is working with a string version of an object’s name. If your script already knows the object reference, the second approach is more efficient and compact. Related Items: All object element properties that return collections (arrays) of other objects
lookupNamespaceURI("prefix") lookupPrefix("namespaceURI") Returns: Namespace or prefix string (see description) Compatibility: WinIE-, MacIE-, NN-, Moz1.7.2+, Safari+, Opera+, Chrome+ These two methods use one piece of information to look up the other. The lookupNamespaceURI() method accepts a prefix as its only parameter and returns a URI string for the node if the prefix matches a previously defined namespace. Operating in the reverse, the lookupPrefix() method accepts a namespace URI string and returns a prefix string for the node if the namespace parameter matches a previously defined namespace.
mergeAttributes("sourceObject") Returns: Nothing Compatibility: WinIE5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe mergeAttributes() method is a convenient way to propagate attributes in newly created elements without painstakingly adding attributes one at a time. When you have an object whose attributes can function as a prototype for other elements, those attributes (except for the id attribute) can be applied to a newly created element instantaneously. The default action of this method is not to duplicate the id or name attributes of the element. However, IE5.5+ introduced an extra Boolean parameter, preserveIDs, that enables you to duplicate these two attributes by setting the parameter to false (true is the default).
Example Listing 26-29 demonstrates the usage of mergeAttributes() in the process of replicating the same form input field while assigning a unique ID to each new field. So that you can see the results as you go, we display the HTML for each input field in the field. The doMerge() function begins by generating two new elements: a p element and an input element. Because these newly created elements have no properties associated with them, a unique ID is assigned to the input element through the uniqueID property. Attributes from the field in the source code (field1) are merged into the new input element. Thus, all attributes except name and id are copied to the new element. The input element is inserted into the p element, and the p element is appended to the document’s form element. Finally, the outerHTML of the new element is displayed in its field. Notice that except for the name and id attributes, all others are copied. This includes style sheet attributes and event handlers. To prove that the event handler works in the new elements, you can add a space to any one of them and press Tab to trigger the onchange event handler that changes the content to all-uppercase characters.
665
Part IV: Document Objects Reference elementObject.mergeAttributes() LISTING 26-29
Using the mergeAttributes() Method HTML: jsb2-29.html mergeAttributes() Method mergeAttributes() Method
JavaScript: jsb26-29.js function doMerge(form) { var newPElem = document.createElement("p"); var newInputElem = document.createElement("input"); newInputElem.id = newInputElem.uniqueID; newInputElem.mergeAttributes(form.field1); newPElem.appendChild(newInputElem); form.appendChild(newPElem); newInputElem.value = newInputElem.outerHTML; } // called by onChange event handler of fields function upperMe(field) { field.value = field.value.toUpperCase(); }
666
Chapter 26: Generic HTML Element Objects elementObject.normalize() Related Items: clearAttributes(), cloneNode(), removeAttributes() methods
normalize() Returns: Nothing Compatibility: WinIE6+, MacIE5+, NN7+, Moz+, Safari1.2+, Opera+, Chrome+ In the course of appending, inserting, removing, and replacing child nodes of an element, it is conceivable that two text nodes can end up adjacent to each other. Although this typically has no effect on the rendering of the content, some XML-centric applications that rely heavily on the document node hierarchy to interpret content properly may not like having two text nodes sitting next to each other. The proper form of a node hierarchy is for a single text node to be bounded by other node types. The normalize() method sweeps through the child nodes of the current node object and combines adjacent text nodes into a single text node. The effect obviously impacts the number of child nodes of an element, but it also cleanses the nested node hierarchy.
Example Use The Evaluator (see Chapter 4) to experiment with the normalize() method. The following sequence adds a text node adjacent to one in the myP element. A subsequent invocation of the normalize() method removes the division between the adjacent text nodes. Begin by confirming the number of child nodes of the myP element: document.getElementById("myP").childNodes.length
Three nodes initially inhabit the element. Next, create a text node, and append it as the last child of the myP element: a = document.createTextNode("This means you!") document.getElementById("myP").appendChild(a)
With the new text now rendered on the page, the number of child nodes increases to four: document.getElementById("myP").childNodes.length
You can see that the last child node of myP is the text node you just created: document.getElementById("myP").lastChild.nodeValue
But by invoking normalize() on myP, all adjacent text nodes are accumulated into single nodes: document.getElementById("myP").normalize()
You can see that the myP element is back to three child nodes, and the last child is a combination of the two previously distinct, but adjacent, text nodes: document.getElementById("myP").childNodes.length document.getElementById("myP").lastChild.nodeValue
Related Items: document.createTextNode(), appendChild(), insertBefore(), removeChild(), replaceChild() methods
667
Part IV: Document Objects Reference elementObject.releaseCapture()
releaseCapture() setCapture(containerBoolean) Returns: Nothing Compatibility: WinIE5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeYou can instruct a single object on a page to capture all mouse events (onmousedown, onmouseup, onmousemove, onmouseout, onmouseover, onclick, and ondblclick) via the WinIE-specific setCapture() method. A primary scenario for mouse event capture is when some content appears on the page that you wish to leave as the center of user focus — items such as pull-down menus, context menus, or simulated modal window areas. When such items appear onscreen, you want the effect of blocking all mouse events except those that apply to the menu or currently visible pseudowindow. When the region disappears, mouse events can be released so that individual elements (such as buttons and links elsewhere on the page) respond to mouse events. Event capture does not block the events. Instead, the events are redirected to the object set to capture all mouse events. Events bubble up from that point unless explicitly canceled (see Chapter 32). For example, consider a document that has a tag containing an onclick event handler that governs the entire document at all times. If you turn on event capture for a div somewhere in the document, the click event first goes to the div. That div might have an onclick event handler that looks to process click events when they occur in some of its child elements. If the event handler for the div does not also cancel the bubbling of that click event, the body element’s onclick event handler eventually receives and processes the event, even though the div initially captured the event. Deciding which object should capture events is an important design issue to confront. With event capture engaged, all mouse events (no matter where they occur) get funneled to the object set to capture the events. Therefore, if you design an application whose entire interface consists of clicking and dragging positionable elements, you can set one of those elements (or even the document object) to perform the capturing. For pop-up regions, however, it is generally more logical and convenient for your coding to assign the capture mechanism to the primary container of the pop-up content (usually, a positioned div). The setCapture() method has one optional Boolean parameter. The parameter controls whether mouse events on child elements within the capturing object are under control of the event capture mechanism. The default value (true) means that all mouse events targeted at elements within the current object go to the current object rather than to the original target — the most likely way you will use setCapture() for things such as pop-up and context menus. But if you specify false as the parameter, mouse events occurring in child elements of the capturing container receive their events directly. From there, regular event bubbling upward from the target ensues (see Chapter 32). You may encounter odd behavior when the region you set up to capture mouse events contains form elements such as text input fields and select lists. Because these elements require mouse events to gain focus for interaction, the event capture mechanism inhibits access to these items. To work around this behavior, you can examine the click event’s srcElement property to see whether the click was on one of these elements and script the focus of that element (or instruct the user to press the Tab key until the element gets focus manually). After an object is set to capture events, your other code must define which events actually do something and decide whether events should bubble up beyond the capturing element. You need to worry about bubbling only if your design includes mouse event handlers in elements higher up the element containment hierarchy. You may not want those event handlers to fire while event capture is on; in this case, you need to cancel the bubbling of those events in the capturing object. If your application design requires that the pop-up area be hidden and event handling be returned to normal (such as after the user makes a pop-up menu selection), use the releaseCapture() method
668
Chapter 26: Generic HTML Element Objects elementObject.releaseCapture() in conjunction with hiding the container. Because event capture can be engaged for only one element at a time, you can release capture by invoking the releaseCapture() method from the container or from the document object. Event capture is automatically disengaged when the user performs any of the following actions:
Gives focus to any other window
Displays any system modal dialog window (for example, alert window)
Scrolls the page
Opens a browser context menu (by right-clicking)
Tabs to give focus to the Address field in the browser window
Therefore, you may want to set the document object’s onlosecapture event handler to hide any container that your script displays in concert with event capture. Also be aware that even though mouse events may be captured to prevent mouse access to the rest of the page, keyboard events are not captured. Thus, using the event capture mechanism to simulate modal windows is not foolproof: A user can tab to any form element or link in the page and press the spacebar or Enter key to activate that element. Event capture, as defined in the W3C DOM, operates differently from WinIE event capture. In the W3C DOM, you can instruct the browser to substitute event capture of any kind of event for the normal event bubbling behavior. For example, you can attach an event listener to the body element in such a way that it sees all click events aimed at elements contained by the body element before the events reach their target elements. (See Chapter 25 and Chapter 32, for more on the W3C DOM event model and how to integrate it into cross-browser applications.)
Example Listing 26-30 demonstrates the usage of setCapture() and releaseCapture() in a quick-and-dirty context menu for WinIE5+. The job of the context menu is to present a list of numbering styles for the ordered list of items on the page. Whenever the user brings up the context menu atop the ol element, the custom context menu appears. Event capture is turned on in the process to prevent mouse actions elsewhere on the page from interrupting the context menu choice. Even a click of the link set up as the title of the list is inhibited while the context menu is visible. A click anywhere outside the context menu hides the menu. Clicking a choice in the menu changes the listStyleType property of the ol object and hides the menu. Whenever the context menu is hidden, event capture is turned off so that clicking the page (such as the link) works as normal. For this design, onclick, onmouseover, and onmouseout event handlers are assigned to the div element that contains the context menu. To trigger the display of the context menu, the ol element has an oncontextmenu event handler. This handler invokes the showContextMenu() function. In this function, event capture is assigned to the context menu div object. The div is also positioned at the location of the click before it is set to be visible. To prevent the system’s regular context menu from also appearing, the event object’s returnValue property is set to false. Now that all mouse events on the page go through the contextMenu div object, let’s examine what happens with different kinds of events triggered by user action. As the user rolls the mouse, a flood of mouseover and mouseout events fires. The event handlers assigned to the div manage these events. But notice that the two event handlers, highlight() and unhighlight(), perform action only when the srcElement property of the event is one of the menu items in the div. Because the page has no other onmouseover or onmouseout event handlers defined for elements up the containment hierarchy, you do not have to cancel event bubbling for these events.
669
Part IV: Document Objects Reference elementObject.releaseCapture() When a user clicks the mouse button, different things happen, depending on whether event capture is enabled. Without event capture, the click event bubbles up from wherever it occurred to the onclick event handler in the body element. (An alert dialog box displays to let you know when the event reaches the body.) But with event capture turned on (the context menu is showing), the handleClick() event handler takes over to apply the desired choice whenever the click is atop one of the context menu items. For all click events handled by this function, the context menu is hidden, and the click event is canceled from bubbling up any higher (no alert dialog box appears). This takes place whether the user makes a choice in the context menu or clicks anywhere else on the page. In the latter case, all you need is for the context menu to go away as the real context menu does. For added insurance, the onlosecapture event handler hides the context menu when a user performs any of the actions just listed that cancel capture.
removeAttribute("attributeName"[, caseSensitivity]) Returns: Boolean (IE), nothing (NN/DOM) Compatibility: WinIE4+, MacIE4+, NN6+, Moz+, Safari+, Opera+, Chrome+ If you create an attribute with the setAttribute() method, you can eliminate that attribute from the element object via the removeAttribute() method. The required parameter is the name of the attribute. Internet Explorer permits you to set and remove attributes such that the attribute names are case sensitive. The default behavior of removeAttribute() in IE (the second parameter is a Boolean value) is false. Therefore, if you supply a value of true for the case-sensitivity parameter in setAttribute(), you should set the parameter to true in removeAttribute() to ensure a proper balance between created and removed attributes. The W3C DOM (NN/Moz-/WebKit-based) version of the removeAttribute() method has a single parameter (a case-insensitive attribute name) and returns no value. The returned value in IE is true
672
Chapter 26: Generic HTML Element Objects elementObject.setAttributeNode() if the removal succeeds and false if it doesn’t succeed (or if the attribute is one that you set in some other manner).
Example Use The Evaluator (see Chapter 4) to experiment with the removeAttribute() method for the elements in the page. See the examples for the setAttribute() method later in this chapter, and enter the corresponding removeAttribute() statements in the top text box. Interlace statements using getAttribute() to verify the presence or absence of each attribute. Related Items: attributes property; document.createAttribute(), getAttribute(), setAttribute() methods
removeAttributeNode(attributeNode) setAttributeNode(attributeNode) Returns: Attribute object Compatibility: WinIE6+, MacIE-, NN6+, Moz+, Safari+, Opera+, Chrome+ As discussed in the coverage of the getAttributeNode() method earlier in this chapter, the W3C DOM treats a name–value attribute pair as an attribute object. An attribute object is a distinct node within a named node map — a collection of attribute objects belonging to an element. Understanding named node maps and attribute objects is more useful in an XML environment, where attributes can not only contain valuable data, but also are not exposed to the DOM as properties you can access via script. Instead of accessing an object’s properties, you work with the actual attributes. If you want to insert an attribute in the formal W3C methodology, you can use document.createAttribute() to generate a new attribute object. Subsequent script statements assign values to the nodeName and nodeValue properties to give the attribute its traditional
name–value pair. You can then insert that new attribute object into the attribute list of an object via the setAttributeNode() method. The sole parameter is an attribute object, and the return value is a reference to the newly inserted attribute object. To remove an attribute node from an element using this syntax, employ the removeAttributeNode() method. Again, the sole parameter is an attribute object. If your script knows only the attribute’s name, you can use getAttributeNode() to obtain a valid reference to the attribute object. The removeAttributeNode() method returns a reference to
the removed attribute object. That object remains in the browser’s memory, but it is not part of the document hierarchy. By capturing this removed attribute object in a variable, you have the flexibility to modify and assign it to another object elsewhere in the document. In practice, you may rarely, if ever, need to address attributes as nodes. Other methods — notably getAttribute(), removeAttribute(), and setAttribute() — do the job when your scripts
have only the name (as a string) of an attribute belonging to an element.
Example Use The Evaluator (see Chapter 4) to experiment with the setAttributeNode() and removeAttributeNode() methods for the p element in the page. The task is to create and add a style attribute to the p element. Begin by creating a new attribute and storing it temporarily in the global variable a: a = document.createAttribute("style")
673
Part IV: Document Objects Reference elementObject.removeAttributeNS() Assign a value to the attribute object: a.nodeValue = "color:red"
Now insert the new attribute into the p element: document.getElementById("myP").setAttributeNode(a)
The paragraph changes color in response to the newly added attribute. Due to the NN6 bug that won’t allow the method to return a reference to the newly inserted attribute node, you can artificially obtain such a reference: b = document.getElementById("myP").getAttributeNode("style")
Finally, use the reference to the newly added attribute to remove it from the element: document.getElementById("myP").removeAttributeNode(b)
Upon the removal of the attribute, the paragraph resumes its initial color. See the example for the setAttribute() method later in this chapter to discover how you can perform this same kind of operation with setAttribute(). Related Items: attributes property; document.createAttribute(), getAttribute(), getAttributeNode(), setAttribute() methods
removeAttributeNS("namespaceURI", "localName") Returns: Nothing Compatibility: WinIE-, MacIE-, NN6+, Moz+, Safari+, Opera+, Chrome+ This method removes the attribute specified in the two parameters. The first parameter of the method is a URI string matching a URI assigned to a label in the document. The second parameter is the local name portion of the attribute whose value you are removing. Related Items: attributes, namespaceURI, localName properties; removeAttribute(), getAttributeNS(), setAttributeNS() methods
removeBehavior(ID) Returns: Boolean Compatibility: WinIE5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe removeBehavior() method detaches a behavior from an object. It assumes that the behavior was added to the object via the addBehavior() method. The return value of the addBehavior() method is a unique identifier for that particular behavior. This identifier is the required parameter for the removeBehavior() method. Thus, you can add two behaviors to an object and remove just one of them if you so desire. If the removal succeeds, the removeBehavior() method returns true; otherwise, it returns false.
Example See Listing 26-19a and Listing 26-19b earlier in this chapter for examples of how to use addBehavior() and removeBehavior().
674
Chapter 26: Generic HTML Element Objects elementObject.removeExpression() Related Item: addBehavior() method
removeChild(nodeObject) Returns: Node object reference Compatibility: WinIE5+, MacIE5+, NN6+, Moz+, Safari+, Opera+, Chrome+ The removeChild() method erases a child element from the current element. Content associated with the child element is no longer visible on the page, and the object is no longer part of the document object hierarchy. As destructive as that sounds, the specifications for the deleted object are not necessarily lost to the ether. The removeChild() method returns a reference to the removed node. By assigning this value to a variable, you can hold on to that object specification for insertion later in the session. You are free to use this value as a parameter to such methods as appendChild(), replaceChild(), swapNode(), and insertBefore(). Remember that removeChild() is invoked from the point of view of a parent element. If you simply want to remove an element, you can do so more directly (in WinIE5+ only) with the removeNode() method. The IE removeNode() method also allows a node to remove itself, which isn’t possible via the removeChild() method.
Example You can see an example of removeChild() as part of Listing 26-21 earlier in this chapter. Related Items: appendChild(), replaceChild(), removeNode() methods
removeEventListener() (See addEventListener())
removeExpression("propertyName") Returns: Boolean Compatibility: WinIE5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeIf you assign an expression to an object property (including an object’s style object) via the setExpression() method, you can remove it under script control with the removeExpression() method. The sole parameter is the name of the property in string form. Property names are case sensitive. The method returns true if the removal succeeds; otherwise, false is returned. Be aware that removing an expression does not alter the value that is currently assigned to the property. In other words, you can use setExpression() to set a property’s value and then remove the expression so that no further changes are made when the document recalculates expressions. If this is your goal, however, you are probably better served by simply setting the property directly via scripting.
Example You can experiment with all three expression methods in The Evaluator (Chapter 4). The following sequence adds an expression to a style sheet property of the myP element on the page and then removes it.
675
Part IV: Document Objects Reference elementObject.removeNode() To begin, enter the number 24 in the bottom one-line text box in The Evaluator (but don’t press Enter or click the List Properties button). This is the value used in the expression to govern the fontSize property of the myP object. Next, assign an expression to the myP object’s style object by entering the following statement in the top text box: myP.style.setExpression("fontSize","document.forms[0]. i inspector.value","JScript")
Now you can enter different font sizes in the bottom text box and have the values immediately applied to the fontSize property. (Keyboard events in the text box automatically trigger the recalculation.) The default unit is px, but you can also append other units (such as pt) to the value in the text box to see how different measurement units influence the same numeric value. Before proceeding to the next step, enter a value other than 16 (the default fontSize value). Finally, enter the following statement in the top text box to disconnect the expression from the property: myP.style.removeExpression("fontSize")
Notice that although you can no longer adjust the font size from the bottom text box, the most recent value assigned to it sticks to the element. To prove it, enter the following statement in the top text box to see the current value: myP.style.fontSize
Related Items: document.recalc(), getExpression(), setExpression() methods
removeNode(removeChildrenFlag) Returns: Node object reference Compatibility: WinIE5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeYou can use the removeNode() method to delete the current node from an element hierarchy in WinIE5+. The sole parameter is a Boolean value that directs the method to remove only itself (without its child nodes) or the node and all of its children (value of true). The method returns a reference to the node object removed. This removed object is no longer accessible to the DOM. But the returned value contains all properties of the object as it existed before you removed it (including properties such as outerHTML and explicitly set style sheet rules). Thus, you can use this value as a parameter to insert the node elsewhere in the document. Although the W3C DOM does not have a removeNode() method, the cross-browser method whose behavior most closely resembles removeNode() is the removeChild() method. The scope of the removeChild() method is one level up the object hierarchy from the object you use for the removeNode() method.
Example Examine Listing 26-21 for the appendChild() method to understand the difference between removeChild() and removeNode(). In the restore() function, you can replace this statement mainObj.removeChild(oneChild);
676
Chapter 26: Generic HTML Element Objects elementObject.replaceAdjacentText() in IE5+ with oneChild.removeNode(true);
The difference is subtle, but it is important to understand. See Listing 26-31 later in this chapter for another example of the removeNode() method. Related Items: Node object; appendChild(), cloneChild(), removeChild(), replaceChild(), replaceNode() methods
replaceAdjacentText("location", "text") Returns: String Compatibility: WinIE5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe replaceAdjacentText() method enables you to replace one chunk of document text with another in a specific position relative to the current object. Be aware that this method works only for plain text and not HTML tags. The returned value is the string of the text that you replace. Both parameters are required. The first must be one of four possible case-insensitive locations for the insertion, shown in the following table: Location
Description
beforeBegin
Before the current element’s start tag
afterBegin
After the start tag but before any nested content
beforeEnd
Before the end tag but after all other nested content
afterEnd
After the end tag
This method is best used with inline (rather than block) elements when specifying the beforeBegin and afterEnd parameters. For example, if you attempt to use replaceAdjacentText() with beforeBegin on the second of two consecutive paragraph elements, the replacement text is inserted into the end of the first paragraph. You can think of the replaceAdjacentText() method in terms of text fragment nodes. The method replaces the text fragment node (given any one of the four position parameters) with new text. Replacing the text of a simple element with either the afterBegin or beforeEnd locations is the same as assigning that text to the object’s innerText property.
Example Use The Evaluator (see Chapter 4) to experiment with the replaceAdjacentText() method. Enter each of the following statements in the top text box, and watch the results in the myP element (and its nested myEM element) below the solid rule: document.getElementById("myEM").replaceAdjacentText("afterBegin", "twenty")
Notice that the myEM element’s new text picks up the behavior of the element. In the meantime, the replaced text (all) is returned by the method and displayed in the Results box: document.getElementById("myEM").replaceAdjacentText("beforeBegin", "We need")
677
Part IV: Document Objects Reference elementObject.replaceChild() All characters of the text fragment, including spaces, are replaced. Therefore, you may need to supply a trailing space, as shown here, if the fragment you replace has a space: document.getElementById("myP").replaceAdjacentText("beforeEnd", "good people.")
This is another way to replace the text fragment following the myEM element, but it is also relative to the surrounding myP element. If you now attempt to replace text after the end of the myP block-level element document.getElementById("myP").replaceAdjacentText("afterEnd", "Hooray!")
the text fragment is inserted after the end of the myP element’s tag set. The fragment is just kind of floating in the DOM as an unlabeled text node. Related Items: innerText, outerText properties; getAdjacentText(), insertAdjacentHTML(), insertAdjacentText() methods
replaceChild(newNodeObject, oldNodeObject) Returns: Node object reference Compatibility: WinIE5+, MacIE5+, NN6+, Moz+, Safari+, Opera+, Chrome+ The replaceChild() method enables you to swap an existing child node object for a new node object. Parameters for the replaceChild() method are node object references, and they must be in the order of the new object followed by the object you want to replace. The old object must be an immediate child node of the parent used to invoke the method, and the new object must also be a legal child element within the document containment hierarchy. The method returns a reference to the child object that you replaced with the new object. This reference can be used as a parameter to any of the node-oriented insertion or replacement methods. Remember that replaceChild() is invoked from the point of view of a parent element. If you simply want to change an element, you can do so more directly in WinIE5+ with the swapNode() or replaceNode() method.
Example You can see an example of replaceChild() as part of Listing 26-21 (for the appendChild property) earlier in this chapter. Related Items: appendChild(), removeChild(), replaceNode(), swapNode() methods
replaceNode("newNodeObject") Returns: Node object reference Compatibility: WinIE5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe replaceNode() method is related to the replaceChild() method, but you invoke this method on the actual node you want to replace (instead of the object’s parent). The sole parameter is a reference to a valid node object, which you can generate via the document.createElement() method or copy from an existing node. The value returned from the method is a reference to the
678
Chapter 26: Generic HTML Element Objects elementObject.replaceNode() object that you replace. Thus, you can preserve a copy of the replaced node by storing the results in a variable for use later. If the node you replace contains other nodes, the replaceNode() method removes all contained nodes of the original from the document. Therefore, if you want to change a wrapper node but want to maintain the original children, your script must capture the children and put them back into the new node as shown in the following example.
Example Listing 26-31 demonstrates three node-related methods: removeNode(), replaceNode(), and swapNode(). These methods work in WinIE5+ only. The page rendered from Listing 26-31 begins with a ul type list of four items. Four buttons control various aspects of the node structure of this list element. The first button invokes the replace() function, which changes the ul type to ol. To do this, the function must temporarily tuck away all child nodes of the original ul element so that they can be added back into the new ol element. At the same time, the old ul node is stored in a global variable (oldNode) for restoration in another function. To replace the ul node with an ol, the replace() function creates a new, empty ol element and assigns the myOL ID to it. Next, the children (li elements) are stored en masse as an array in the variable innards. The child nodes are then inserted into the empty ol element, using the insertBefore() method. Notice that as each child element from the innards array is inserted into the ol element, the child element is removed from the innards array. That’s why the loop to insert the child nodes is a while loop that constantly inserts the first item of the innards array to the new element. Finally, the replaceNode() method puts the new node in the old node’s place, and the old node (just the ul element) is stored in oldNode. The restore() function operates in the inverse direction of the replace() function. The same juggling of nested child nodes is required. The third button invokes the swap() function, whose script exchanges the first and last nodes. The swapNode() method, like the others in this discussion, operates from the point of view of the node. Therefore, the method is attached to one of the swapped nodes, and the other node is specified as a parameter. Because of the nature of the ol element, the number sequence remains fixed, but the text of the li node swaps. To demonstrate the removeNode() method, the fourth function removes the last child node of the list. Each call to removeNode() passes the true parameter to guarantee that the text nodes nested inside each li node are also removed. Experiment with this method by setting the parameter to false (the default). Notice how the parent-child relationship changes when you remove the li node. LISTING 26-31
Using Node-Related Methods HTML: jsb26-31.html
continued
679
Part IV: Document Objects Reference elementObject.replaceNode() LISTING 26-31
(continued)
removeNode(), replaceNode(), and swapNode() Methods Node Methods Here is a list of items:
First Item
Second Item
Third Item
Fourth Item
JavaScript: jsb26-31.js // store original node between changes var oldNode; // replace UL node with OL function replace() { if (document.getElementById("myUL")) { var newNode = document.createElement("OL"); newNode.id = "myOL"; var innards = document.getElementById("myUL").children; while (innards.length > 0) { newNode.insertBefore(innards[0]); } oldNode = document.getElementById("myUL").replaceNode(newNode); } } // restore OL to UL function restore() {
680
Chapter 26: Generic HTML Element Objects elementObject.scrollIntoView() if (document.getElementById("myOL") && oldNode) { var innards = document.getElementById("myOL").children; while (innards.length > 0) { oldNode.insertBefore(innards[0]); } document.getElementById("myOL").replaceNode(oldNode); } } // swap first and last nodes function swap() { if (document.getElementById("myUL")) { document.getElementById("myUL").firstChild.swapNode( document.getElementById("myUL").lastChild); } if (document.getElementById("myOL")) { document.getElementById("myOL").firstChild.swapNode( document.getElementById("myOL").lastChild); } } // remove last node function remove() { if (document.getElementById("myUL")) { document.getElementById("myUL").lastChild.removeNode(true); } if (document.getElementById("myOL")) { document.getElementById("myOL").lastChild.removeNode(true); } }
You can accomplish the same functionality shown in Listing 26-31 in a cross-browser fashion using the W3C DOM. In place of the removeNode() and replaceNode() methods, use removeChild() and replaceChild() methods to shift the point of view (and object references) to the parent of the ul and ol objects: the document.body. Also, you need to change the document.all references to document.getElementById(). Related Items: removeChild(), removeNode(), replaceChild(), swapNode() methods
Part IV: Document Objects Reference elementObject.setActive() The scrollIntoView() method scrolls the page (vertically and/or horizontally as needed) such that the current object is visible within the window or frame that contains it. A single parameter, a Boolean value, controls the location of the element within the viewable space. A value of true (the default) causes the element to be displayed so that its top is aligned with the top of the window or frame (provided that the document beneath it is long enough to allow this amount of scrolling). But a value of false causes the bottom of the element to align with the bottom of the viewable area. In most cases, you want the former so that the beginning of a page section is at the top of the viewable area. But if you don’t want a user to see content below a certain element when you jump to the new view, use the false parameter. For form elements, you must use the typical form element reference (document.formName .elementName.scrollIntoView()) unless you also specify an ID attribute for the element (document.getElementById("elementID").scrollIntoView()).
Example Use The Evaluator (see Chapter 4) to experiment with the scrollIntoView() method. Resize the browser window height so that you can see only the top text box and the Results text area. Enter each of the following statements in the top text box, and see where the myP element comes into view: myP.scrollIntoView() myP.scrollIntoView(false)
Expand the height of the browser window until you can see part of the table lower on the page. If you enter myTable.scrollIntoView(false)
in the top text box, the page scrolls to bring the bottom of the table to the bottom of the window. But if you use the default parameter (true or empty) myTable.scrollIntoView()
the page scrolls as far as it can in an effort to align the top of the element as closely as possible to the top of the window. The page cannot scroll beyond its normal scrolling maximum (although if the element is a positioned element, you can use dynamic positioning to place it wherever you want — including off the page). Also, if you shrink the window and try to scroll the top of the table to the top of the window, be aware that the table element contains a caption element, so the caption is flush with the top of the window. Related Items: window.scroll(), window.scrollBy(), window.scrollTo() methods
setActive() Returns: Nothing Compatibility: WinIE5.5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe setActive() method lets a script designate an element object as the active element. However, unlike in the focus() method, the window does not scroll the active element into view. Any onFocus event handler defined for the element fires when setActive() is invoked without the browser’s giving the element focus.
682
Chapter 26: Generic HTML Element Objects elementObject.setAttribute()
Example Use The Evaluator (see Chapter 4) to compare the setActive() and focus() methods. With the page scrolled to the top and the window sized so that you cannot see the sample checkbox near the bottom of the page, enter the following statement in the top text box: document.getElementById("myCheckbox").setActive()
Scroll down to see that the checkbox has operational focus (press the spacebar to see). Now scroll back to the top, and enter the following: document.getElementById("myCheckbox").focus()
This time, the checkbox gets focus, and the page automatically scrolls the object into view. Related Item: focus() method
setAttribute("attributeName", value[, caseSensitivity]) Returns: Nothing Compatibility: WinIE4+, MacIE4+, NN6+, Moz+, Safari+, Opera+, Chrome+ The setAttribute() method assigns a new value to an existing attribute of the current object or inserts an entirely new attribute name–value pair among the attributes of the current object. This method represents an alternative syntax to setting a property of the object directly.
Note The W3C DOM Level 2 standard recommends getAttribute() and setAttribute() for reading and writing element object attribute values, rather than reading and writing those values by way of their corresponding properties. Although using these methods is certainly advisable for XML elements, the same DOM standard sends conflicting signals by defining all kinds of properties for HTML element objects. Browsers, of course, will support access via properties well into the future, so don’t feel obligated to change your ways just yet.
The first two parameters of setAttribute() are required. The first is the name of the attribute. The default behavior of this method respects the case of the attribute name. Therefore, if you use setAttribute() to adjust the value of an existing attribute in default mode, the first parameter must match the case of the attribute as known by the object model for the current document. Remember that all names of all attributes assigned as inline source-code attributes are automatically converted to lowercase letters. A value you assign to the attribute is the second parameter. For cross-browser compatibility, the value should be either a string or Boolean data type. IE provides an optional third parameter to control the case-sensitivity issue for the attribute name. The default value (true) has a different impact on your object depending on whether you use setAttribute() to assign a new attribute or reassign an existing one. In the former case, the third parameter as true means that the attribute name assigned to the object observes the case of the first parameter. In the latter case, the third parameter as true means that the attribute isn’t reassigned unless the first parameter matches the case of the attribute currently associated with the object. Instead, a new attribute with a different case sequence is created. Attempting to manage the case sensitivity of newly created attributes is fraught with peril, especially if you try to reuse names but with different case sequences. We strongly recommend using default case-sensitivity controls for setAttribute() and getAttribute().
683
Part IV: Document Objects Reference elementObject.setAttributeNode() See also the W3C DOM facilities for treating attributes as node objects in the discussions of the getAttributeNode() and removeAttributeNode() methods earlier in this chapter.
Example Use The Evaluator (see Chapter 4) to experiment with the setAttribute() method for the elements in the page. Setting attributes can have immediate impact on the layout of the page (just as setting an object’s properties can). Enter the following sample statements in the top text box to view attribute values. document.getElementById("myTable").setAttribute("width", "80%") document.getElementById("myTable").setAttribute("border", "5")
setAttributeNodeNS("attributeNode") Returns: Attribute object Compatibility: WinIE-, MacIE-, NN6+, Moz+, Safari+, Opera+, Chrome+ This method inserts or replaces an attribute in the current element. The sole parameter is an attribute object, and the return value is a reference to the newly inserted attribute object. When the method is invoked, the browser looks for a pairing of local name and namespace URI between the nodes. If there is a match, the node replaces the matched node; otherwise, the node is inserted. Related Items: attributes, namespaceURI, localName properties; removeAttributeNS(), getAttributeNS(), and setAttributeNS() methods
setAttributeNS("namespaceURI", "qualifiedName", "value") Returns: Nothing Compatibility: WinIE-, MacIE-, NN6+, Moz+, Safari+, Opera+, Chrome+ This method inserts or replaces an attribute in the current element, as specified in the three parameters. The first parameter of the method is a URI string matching a URI assigned to a label in the document. The second parameter is the local name portion of the attribute whose value you are getting. If a match is found among these parameters, the value in the third parameter is assigned to the existing attribute; otherwise, the value is inserted as a new attribute. Related Items: attributes, namespaceURI, localName properties; removeAttributeNS(), getAttributeNS(), and setAttributeNodeNS() methods
684
Chapter 26: Generic HTML Element Objects elementObject.setExpression()
setCapture(containerBoolean) (See releaseCapture())
setExpression("propertyName", "expression",["language"]) Returns: Nothing Compatibility: WinIE5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeUse the setExpression() method to assign the result of an executable expression to the value of an element object property. This method can assign values to both HTML element objects and style objects that belong to them. The setExpression() method is a scripted way of assigning expressions to attributes. But you can also assign expressions directly to style sheet definitions in the HTML tag of an element using the expression() syntax, as in the following example:
The setExpression() method requires three parameters. The first parameter is the name of the property (in string form) to which you assign the expression. Property names are case sensitive. The second parameter is a string form of the expression to be evaluated to supply a value for the property. Expressions can refer to global variables or properties of other objects in the same document (provided that the property is anything other than an array). An expression may also contain math operators. Pay close attention to the data type of the evaluated value of the expression. The value must be a valid data type for the property. For example, the URL of the body background image must be a string. But for numeric values, you can generally use number and string types interchangeably because the values are converted to the proper type for the property. Even for expressions that evaluate to numbers, encase the expression inside quotes. It may not be necessary in all cases, but if you get into the habit of using quotes, you’ll have fewer problems for strings or complex expressions that require them. You are not limited to using JavaScript as the language for the expression because you can also specify the scripting language of the expression in the optional third parameter. Acceptable parameter values for the language are JScript JavaScript VBScript
For all intents and purposes, JScript and JavaScript are the same. Both languages are ECMA-262 compatible. JScript is the default value for the language parameter. One reason to use setExpression() for dynamic properties is to let the property always respond to the current conditions on the page. For example, if you set a property that is dependent on the current width of the body, you want a recalculation that is applied to the property if the user resizes the window. The browser automatically responds to many events and updates any dynamic properties. In essence, the browser recalculates the expressions and applies the new values to the property. Keyboard events in particular trigger this kind of automatic recalculation for you. But if your scripts perform actions on their own (in other words, not triggered by events), your scripts need to force the recalculation of the expressions. The document.recalc() method takes care of this, but you must invoke it to force the recalculation of dynamic properties in these cases.
685
Part IV: Document Objects Reference elementObject.setExpression()
Example Listing 26-32 shows the setExpression(), recalc(), and getExpression() methods at work in a DHTML-based clock. Figure 26-1 shows the clock. As time clicks by, the bars for hours, minutes, and seconds adjust their widths to reflect the current time. At the same time, the innerHTML of span elements to the right of each bar display the current numeric value for the bar. FIGURE 26-1
A bar-graph clock created with dynamic expressions
The dynamically calculated values in this example are based on the creation of a new Date object over and over again to get the current time from the client computer clock. It is from the Date object (stored in the variable called now) that the hour, minute, and second values are retrieved. Some other calculations are involved so that a value for one of these time components is converted to a pixel value for the width of the bars. The bars are divided into 24 (for the hours) and 60 (for the minutes and seconds) parts, so the scale for the two types differs. For the 60-increment bars in this application, each increment is set to 5 pixels (stored in shortWidth); the 24-increment bars are 2.5 times the shortWidth. As the document loads, the three span elements for the colored bars are given no width, which means that they assume the default width of zero. But after the page loads, the onload event handler invokes the init() function, which sets the initial values for each bar’s width and the text (innerHTML) of the three labeled spans. After these initial values are set, the init() function invokes the updateClock() function.
686
Chapter 26: Generic HTML Element Objects elementObject.setExpression() In the updateClock() function, a new Date object is created for the current instant. The document.recalc() method is called, instructing the browser to recalculate the expressions that were set in the init() function and assign the new values to the properties. To keep the clock ticking, the setTimeout() method is set to invoke this same updateClock() function in 1 second. To see what the getExpression() method does, you can click the button on the page. It simply displays the returned value for one of the attributes that you assign using setExpression(). LISTING 26-32
This clock uses Dynamic Properties to calculate bar width and time numbers:
Hours:
Minutes:
continued
687
Part IV: Document Objects Reference elementObject.setExpression() LISTING 26-32
(continued)
Seconds:
JavaScript: jsb26-32.js var now = new Date(); var shortWidth = 5; var multiple = 2.5; function init() { with (document.all) { hoursBlock.style.setExpression("width", "now.getHours() * shortWidth * multiple","jscript"); hoursLabel.setExpression("innerHTML", "now.getHours()","jscript"); minutesBlock.style.setExpression("width", "now.getMinutes() * shortWidth","jscript"); minutesLabel.setExpression("innerHTML", "now.getMinutes()","jscript"); secondsBlock.style.setExpression("width", "now.getSeconds() * shortWidth","jscript"); secondsLabel.setExpression("innerHTML", "now.getSeconds()","jscript"); } updateClock(); } function updateClock() { now = new Date(); document.recalc(); setTimeout("updateClock()",1000); }
688
Chapter 26: Generic HTML Element Objects elementObject.tags() function showExpr() { alert("Expression for the \’Hours\’ innerHTML property is:\r\n" + document.getElementById("hoursLabel").getExpression("innerHTML") + "."); }
Related Items: document.recalc(), removeExpression(), setExpression() methods
setUserData("key", dataObj, dataHandler) Returns: Object Compatibility: WinIE-, MacIE-, NN-, Moz1.7.2+, Safari+, Opera-, Chrome+ The setUserData() method is designed to allow for the addition of user data to a node. This user data comes in the form of an object and is associated with a node through a string key. By requiring a key for an object of user data, the setUserData() method allows you to set multiple pieces of data (objects) on a single node. The last parameter to the method is an event handler function reference that is called whenever the data object is cloned, imported, deleted, renamed, or adopted. Although some support for the setUserData() method was added in Moz1.7.2, the method still isn’t supported to the degree that you can actually use it, as of Moz1.8.1.
swapNode(otherNodeObject) Returns: Node object reference Compatibility: WinIE5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe swapNode() method exchanges the positions of two nodes within an element hierarchy. Contents of both nodes are preserved in their entirety during the exchange. The single parameter must be a valid node object (perhaps created with document.createElement() or copied from an existing node). A return value is a reference to the object whose swapNode() method was invoked.
Example See Listing 26-31 (the replaceNode() method) for an example of the swapNode() method in action. Related Items: removeChild(), removeNode(), replaceChild(), replaceNode() methods
tags("tagName") Returns: Array of element objects Compatibility: WinIE4+, MacIE4+, NN-, Moz-, Safari+, Opera+, Chrome+ The tags() method does not belong to every element, but it is a method of every collection of objects (such as all, forms, and elements). The method is best thought of as a kind of filter for the elements that belong to the current collection. For example, to get an array of all p elements inside a document, use this expression: document.all.tags("P")
689
Part IV: Document Objects Reference elementObject.toString() You must pass a parameter string consisting of the tag name you wish to extract from the collection. The tag name is case insensitive. The return value is an array of references to the objects within the current collection whose tags match the parameter. If there are no matches, the returned array has a length of zero. If you need cross-browser compatibility, use the getElementsByTagName() method described earlier in this chapter, and pass a wildcard value of "*".
Example Use The Evaluator (see Chapter 4) to experiment with the tags() method. Enter the following statements one at a time in the top text box, and study the results: document.all.tags("div") document.all.tags("div").length myTable.all.tags("td").length
Because the tags() method returns an array of objects, you can use one of those returned values as a valid element reference: document.all.tags("form")[1].elements.tags("input").length
The browsers that support tags do not all support it for the same HTML elements. For example, WebKit-based browsers do not support tags as part of table. Related Item: getElementsByTagName() method
toString("param") Returns: String Compatibility: WinIE4+, MacIE4+, NN6+, Moz+, Safari+, Opera+, Chrome+ The toString() method returns a string representation of the element object, which unfortunately can mean different things to different browsers. Don’t expect entirely consistent results across browsers, especially when you consider that IE simply returns a generic "[object]" string.
urns("behaviorURN") Returns: Array of element objects Compatibility: WinIE5+, MacIE-, NN-, Moz-, Safari-, opera-, ChromeThe urns() method does not belong to every element, but it is a method of every collection of objects. You must pass a parameter string consisting of the URN (Uniform Resource Name) of a behavior resource (most typically .htc) assigned to one or more elements of the collection. The parameter does not include the extension of the filename. If there is no matching behavior URN for the specified parameter, the urns() method returns an array of zero length. This method is related to the behaviorUrns property, which contains an array of behavior URNs assigned to a single element object.
Example In case the urns() method is reconnected in the future, you can add a button and function to Listing 26-19b that reveals whether the makeHot.htc behavior is attached to the myP element. Such a function looks like this:
690
Chapter 26: Generic HTML Element Objects elementObject.ondeactivate function behaviorAttached() { if (document.all.urns("makeHot")) { alert("There is at least one element set to \‘makeHot\’."); } }
Related Item: behaviorUrns property
Event handlers onactivate ondeactivate Compatibility: WinIE5.5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe onactivate and ondeactivate event handlers are similar to the onfocus and onblur event handlers, respectively, as well as to the IE5.5+ onfocusin and onfocusout events. Starting with IE5.5+, it is possible to manage the activation of an element and the focus of an element separately. The onactivate and ondeactivate events correspond to the activation of an element, whereas onfocusin and onfocusout deal with focus. In many cases, activation and focus go hand in hand, but not always. If an element receives activation, the onactivate event fires for that element just before the activation takes hold; conversely, just before the element loses activation, events fire in the sequence onbeforedeactivate, ondeactivate, onblur. Only elements that by their nature can accept activation (for example, links and form input controls) or that have a tabindex attribute set can become the active element (and, therefore, fire these events). WinIE5.5+ maintains the original onfocus and onblur event handlers. But because the behaviors are so close to those of the onactivate and ondeactivate events, we don’t recommend mixing the old and new event handler names in your coding style. If you script exclusively for WinIE5.5+, which is unlikely in this day and age, you can use the newer terminology throughout. And if you truly want to track the focus of an element in IE, consider using onfocusin and onfocusout instead.
Example You can modify Listing 26-34 later in this chapter by substituting onactivate for onfocus and ondeactivate for onblur. Use The Evaluator (see Chapter 4) to experiment with the onbeforedeactivate event handler. To begin, set the myP element so it can accept focus: myP.tabIndex = 1
If you repeatedly press the Tab key, the myP paragraph will eventually receive focus — indicated by the dotted rectangle around it. To see how you can prevent the element from losing focus, assign an anonymous function to the onbeforedeactivate event handler, as shown in the following statement: myP.onbeforedeactivate = new Function("event.returnValue=false")
691
Part IV: Document Objects Reference elementObject.onafterupdate Now you can press Tab all you like or click other focusable elements all you like, and the myP element will not lose focus until you reload the page (which clears away the event handler). Please do not do this on your pages unless you want to infuriate and alienate your site visitors. Related Items: onblur, onfocus, onfocusin, onfocusout event handlers
onafterupdate onbeforeupdate Compatibility: WinIE4+, MacIE5+, NN-, Moz-, Safari-, Opera-, ChromeThe onafterupdate and onbeforeupdate event handlers fire on a bound data object in IE whenever the data in the object is being updated. The onbeforeupdate event is fired just before the update occurs, whereas onafterupdate is fired after the data has been successfully updated.
onbeforecopy Compatibility: WinIE5+, MacIE-, NN-, Moz-, Safari1.3+, Opera-, Chrome+ The onbeforecopy event handler fires before the actual copy action takes place whenever the user initiates a content copy action via the Edit menu (including the Ctrl+C, for Windows, and Command+C, for Mac, keyboard shortcuts) or the right-click context menu. In all browsers, if the user copies with a keyboard shortcut, the copy operation will be completed. If the user accesses the Copy command via the Edit or context menu different browsers behave differently. In WebKit-based browsers, the menu displays, the user selects copy and then the onbeforecopy event fires. The onbeforecopy event fires before either menu can display in IE. In practice, the event may fire twice even though you expect it only once. Just because the onbeforecopy event fires, it does not guarantee that a user will complete the copy operation (for example, the context menu may close before the user makes a selection). Unlike paste-related events, the onbeforecopy event handler does not work with form input elements. Just about any other HTML element is fair game, however.
Example In Listing 26-33, the function invoked by the ‘‘Latin’’ paragraph element’s onbeforecopy event handler merely issues an alert. If your audience is limited in their browser use, you could use the onbeforecopy event handler to preprocess information prior to an actual copy action. LISTING 26-33
The onbeforecopy Event Handler HTML: jsb26-33.html onbeforecopy event handler .keyword
692
Chapter 26: Generic HTML Element Objects elementObject.onbeforecut { color: blue; font-weight:bold; } onbeforecopy event handler
Select one or more characters in the Latin paragraph. then execute a copy command:
edit menu
context menu
ctrl-c (on Windows)
command-c (on Mac)
Browsers that support onbeforecopy, do not behave consistently. You may not be able to use all of the copy commands normally available to you. Test all the different ways to copy text and see what happens.
Browsers that do not support onbeforecopy will still allow you to copy -- you just won’t see an alert.
lorem ipsum dolor sit amet, consectetaur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. ut enim adminim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex commodo consequat.
paste results here:
JavaScript: jsb26-33.js function beforeCopy() { alert("onbeforecopy is supported by your browser"); }
Part IV: Document Objects Reference elementObject.onbeforedeactivate The onbeforecut event handler fires before the actual cut action takes place whenever the user initiates a content cut via the Edit menu (including the Ctrl+X keyboard shortcut) or the right-click context menu. If you add the onbeforecut event handler to an HTML element, the context menu usually disables the Cut menu item. But assigning a JavaScript call to this event handler brings the Cut menu item to life. If the user accesses the Cut command via the Edit or context menu, different browsers behave differently. In WebKit-based browsers, the menu displays, the user selects cut and then the onbeforecut event fires. In IE the onbeforecut event fires before either menu displays. In practice, the event may fire twice even though you expect it only once. Just because the onbeforecut event fires, it does not guarantee that a user will complete the cut operation (for example, the context menu may close before the user makes a selection).
Example You can use the onbeforecut event handler to preprocess information prior to an actual cut action. You can try this by editing a copy of Listing 26-33, changing the onbeforecopy event handler to onbeforecut. Related Items: onbeforecopy, oncut event handlers
onbeforeeditfocus Compatibility: WinIE5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe onbeforeeditfocus event handler is triggered whenever you edit an element on a page in an environment such as Microsoft’s DHTML Editing ActiveX control or with the editable page content feature of IE5.5+. This discussion focuses on the latter scenario because it is entirely within the scope of client-side JavaScript. The onbeforeeditfocus event fires just before the element receives its focus. (There may be no onscreen feedback that editing is turned on unless you script it yourself.) The event fires each time a user clicks the element, even if the element just received edit focus elsewhere in the same element.
Example Use The Evaluator (see Chapter 4) to explore the onbeforeeditfocus in WinIE5.5+. In the following sequence, you assign an anonymous function to the onbeforeeditfocus event handler of the myP element. The function turns the text color of the element to red when the event handler fires: document.getElementById("myP").onbeforeeditfocus = new Function("document.getElementById(‘myP’).style.color=‘red’")
Now turn on content editing for the myP element: document.getElementById("myP").contentEditable = true
Now if you click inside the myP element on the page to edit its content, the text turns red before you begin editing. In a page scripted for this kind of user interface, you would include some control that turns off editing and changes the color to normal.
694
Chapter 26: Generic HTML Element Objects elementObject.onblur Related Items: document.designMode, contentEditable, isContentEditable properties
onbeforepaste Compatibility: WinIE5+, MacIE-, NN-, Moz-, Safari 1.3+, Opera-, Chrome+ Like onbeforecopy and onbeforecut, the onbeforepaste event occurs differently in different browsers. In WebKit-based browsers, the menu displays, the user selects paste and then the onbeforepaste event fires. In IE, the onbeforepaste event fires just prior to the display of either the context or menu-bar Edit menu when the current object is selected (or has a selection within it). The primary value of this event comes when you use scripts to control the copy-and-paste process of a complex object. Such an object may have multiple kinds of data associated with it, but your script captures only one of the data types. Or you may want to put some related data about the copied item (for example, the id property of the element) into the clipboard. By using the onbeforepaste event handler to set the event.returnValue property to false, you guarantee that the pasted item is enabled in the context or Edit menu (provided that the clipboard is holding some content). A handler invoked by onpaste should then apply the specific data subset from the clipboard to the currently selected item.
Example See Listing 26-44 for the onpaste event handler (later in this chapter) to see how the onbeforepaste and onpaste event handlers work together. Related Items: oncopy, oncut, onpaste event handlers
onbeforeupdate (See onafterupdate)
onblur Compatibility: WinIE3+, MacIE3+, NN2+, Moz+, Safari+, Opera+, Chrome+ The onblur event fires when an element that has focus is about to lose focus because some other element is about to receive focus. For example, a text input element fires the onblur event when a user tabs from that element to the next one inside a form. The onblur event of the first element fires before the onfocus event of the next element. The availability of the onblur event has expanded with succeeding generations of script-capable browsers. In the earlier versions, blur and focus were largely confined to text-oriented input elements (including the select element). These are safe to use with all scriptable browser versions. The window object received the onblur event handler starting with NN3 and IE4. IE4 also extended the event handler to more form elements, predominantly on the Windows operating system because that OS has a user interface clue (the dotted rectangle) when items such as buttons and links receive focus (so that you may act upon them by pressing the spacebar). For IE5+, the onblur event handler is available to virtually every HTML element. For most of those elements, however, blur and focus are not possible unless you assign a value to the tabindex attribute of the element’s tag. For example, if you assign tabindex="1" inside a
tag, the user can bring focus to that paragraph (highlighted with the dotted rectangle in Windows in some of the browsers) by clicking the paragraph or pressing the Tab key until that item receives focus in sequence. If you plan to use the onblur event handler on window or text-oriented input elements, be aware that there might be some unexpected and undesirable consequences of scripting for the event. For
695
Part IV: Document Objects Reference elementObject.onblur example, in IE, a window object that has focus loses focus (and triggers the onblur event) if the user brings focus to any element on the page (or even clicks a blank area on the page). Similarly, the interaction between onblur, onfocus, and the alert() dialog box can be problematic with text input elements. This is why we generally recommend using the onchange event handler to trigger form validation routines. If you should employ both the onblur and onchange event handler for the same element, the onchange event fires before onblur. For more details about using this event handler for data validation, see Chapter 46 on the CD-ROM. WinIE5.5+ added the ondeactivate event handler, which fires immediately before the onblur event handler. Both the onblur and ondeactivate events can be blocked if the onbeforedeactivate event handler function sets event.returnValue to false.
Example More often than not, a page author uses the onblur event handler to exert extreme control over the user, such as preventing a user from exiting a text box unless that user types something in the box. This is not a web-friendly practice, and it is one that we discourage because there are intelligent ways to ensure that a field has something typed into it before a form is submitted (see Chapter 46 on the CD-ROM). Listing 26-34 simply demonstrates the impact of the tabindex attribute with respect to the onblur and onfocus events. Notice that as you press the Tab key, only the second paragraph issues the events, even though all three paragraphs have event handlers assigned to them. LISTING 26-34
onblur and onfocus Event Handlers HTML: jsb26-34.html onblur and onfocus Event Handlers onblur and onfocus Event Handlers Start tabbing and see what happens
Lorem ipsum dolor sit amet, consectetaur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim adminim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
Bis nostrud exercitation ullam mmodo consequet. Duis aute involuptate velit esse cillum dolore eu fugiat nulla pariatur. At vver eos et accusam dignissum qui blandit est praesent luptatum delenit aigueexcepteur sint occae.
Unte af phen
696
Chapter 26: Generic HTML Element Objects elementObject.onclick neigepheings atoot Prexs eis phat eit sakem eit vory gast te Plok peish ba useing phen roxas. Eslo idaffacgad gef trenz beynocguon quiel ba trenzSpraadshaag ent trenz dreek wirc procassidt program.
JavaScript: jsb26-34.js function showBlur() { var id = event.srcElement.id; alert("Element \"" + id + "\" has blurred."); } function showFocus() { var id = event.srcElement.id; alert("Element \"" + id + "\" has received focus."); }
oncellchange Compatibility: WinIE5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe oncellchange event handler is part of the data binding of IE and fires when data changes in the data provider, which is usually a bound control. When responding to this event, you can analyze the dataFld property to find out which field in the recordset has changed.
onclick Compatibility: WinIE3+, MacIE3+, NN2+, Moz+, Safari+, Opera+, Chrome+ The onclick event fires when a user presses down (with the primary mouse button) and releases the button with the pointer atop the element (both the down and up strokes must be within the rectangle of the same element). The event also fires with non-mouse-click equivalents in operating systems such as Windows. For example, you can use the keyboard to give focus to a clickable object and then press the spacebar or Enter key to perform the same action as clicking the element. In IE, if the element object supports the click() method, the onclick event fires with the invocation of that method (notice that this does not apply to Navigator or other browsers). The onclick event is closely related to other mouse events. The other related events are onmousedown, onmouseup, and ondblclick. The onmousedown event fires when the user makes contact with the mouse switch on the downstroke of a click action. Next comes the onmouseup event (when the contact breaks). Only then does the onclick event fire — provided that the onmousedown and onmouseup events have fired in the same object. See the discussions on the onmousedown and onmouseup events later in this chapter for examples of their usage.
697
Part IV: Document Objects Reference elementObject.onclick Interaction with the ondblclick event is simple: The onclick event fires (after the first click), followed by the ondblclick event (after the second click). See the discussion of the ondblclick event handler later in this chapter for more about the interaction of these two event handlers. When used with objects that have intrinsic actions when users click them (namely, links and areas), the onclick event handler can perform all of the actions — including navigating to the destination normally assigned to the href attribute of the element. For example, to be compatible with all scriptable browsers, you can make an image clickable if you surround its tag with an link tag. This lets the onclick event of that tag substitute for the missing onclick event handler of earlier tags. If you assign an onclick event handler without special protection, the event handler will execute, and the intrinsic action of the element will be carried out. Therefore, you need to block the intrinsic action. To accomplish this, the event handler must evaluate to the statement return false. You can do this in two ways. The first is to append a return false statement to the script statement assigned to the event handler:
As an alternative, you can let the function invoked by the event handler supply the false part of the return false statement, as shown in the following sequence: function yourFunction() { // [statements that do something here] return false; } ...
Either methodology is acceptable. A third option is to not use the onclick event handler at all but assign a javascript: pseudo-URL to the href attribute (see the Link object in Chapter 30). The event model in IE4+ provides one more way to prevent the intrinsic action of an object from firing when a user clicks it. If the onclick event handler function sets the returnValue property of the event object to false, the intrinsic action is canceled. Simply include the following statement in the function invoked by the event handler: event.returnValue = false;
The event model of the W3C DOM has a different approach to canceling the default action. In the event handler function for an event, invoke the eventObj.cancelDefault() method. A common mistake made by scripting beginners is to use a submit type input button as a button intended to perform some script action rather than submitting a form. The typical scenario is an input element of type submit assigned an onclick event handler to perform some local action. The submit input button has an intrinsic behavior, just like links and areas. Although you can block the intrinsic behavior, as just described, you should use an input element of type button. If you are experiencing difficulty with an implementation of the onclick event handler (such as trying to find out which mouse button was used for the click), it may be that the operating system or default browser behavior is getting in the way of your scripting. But you can usually get what you need via the onmousedown event handler. (The onmouseup event may not fire when you use the secondary mouse button to click an object.) Use the onclick event handler whenever possible to capture user clicks, because this event behaves most like users are accustomed to in their daily computing work. But fall back on onmousedown in an emergency.
698
Chapter 26: Generic HTML Element Objects elementObject.onclick
Example The onclick event handler is one of the simplest to grasp and use. Listing 26-35 demonstrates its interaction with the ondblclick event handler and shows you how to prevent a link’s intrinsic action from activating when combined with click events. As you click and/or double-click the link, the text in the span element displays a message associated with each event. Notice that if you double-click, the click event fires first, with the first message immediately replaced by the second. For demonstration purposes, we show both backward-compatible ways of canceling the link’s intrinsic action. In practice, decide on one style and stick with it. LISTING 26-35
Using onclick and ondblclick Event Handlers HTML: jsb26-35.html onclick and ondblclick Event Handlers onclick and ondblclick Event Handlers A sample link. (Click type: ) JavaScript: jsb26-35.js var timeout; function clearOutput() { document.getElementById("clickType").innerHTML = ""; } function showClick() { document.getElementById("clickType").innerHTML = "single"; clearTimeout(timeout); timeout = setTimeout("clearOutput()", 3000); } function showDblClick() { document.getElementById("clickType").innerHTML = "double"; clearTimeout(timeout); timeout = setTimeout("clearOutput()", 3000); return false; }
699
Part IV: Document Objects Reference elementObject.oncontextmenu Related Items: click() method; oncontextmenu, ondblclick, onmousedown, onmouseup event handlers
oncontextmenu Compatibility: WinIE5+, MacIE-, NN7+, Moz+, Safari+, Opera-, Chrome+ The oncontextmenu event fires when the user clicks an object with the secondary (usually the right) mouse button. The only click-related events that fire with the secondary button are onmousedown and oncontextmenu. To block the intrinsic application menu display of the oncontextmenu event, use any of the event cancellation methodologies available in for your browser (as just described in the onclick event handler description: two variations of evaluating the event handler to return false; assigning false to the event.returnValue property). It is not uncommon to wish to block the context menu from appearing so that users are somewhat inhibited from downloading copies of images or viewing the source code of a frame. Be aware, however, that if a user turns Active Scripting off in WinIE5+, the event handler cannot prevent the context menu from appearing. Another possibility for this event is to trigger the display of a custom context menu constructed with other DHTML facilities. In this case, you must also disable the intrinsic context menu so that both menus do not display at the same time.
Example See Listing 26-30 earlier in this chapter for an example of using the oncontextmenu event handler with a custom context menu. Related Items: releaseCapture(), setCapture() methods
oncontrolselect Compatibility: WinIE5.5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe oncontrolselect event fires just before a user makes a selection on an editable element while the page is in edit mode. It’s important to note that it is the element itself that is selected to trigger this event, not the content within the element. Related Items: onresizeend, onresizestart event handlers
oncopy oncut Compatibility: WinIE5+, MacIE4+, NN-, Moz+, Safari1.3+, Opera-, Chrome+ The oncopy and oncut events fire immediately after the user or script initiates a copy or cut edit action on the current object. Each event is preceded by its associated before event, which fires before any Edit or context menu appears (or before the copy or cut action, if initiated by keyboard shortcut). Use these event handlers to provide edit functionality to elements that don’t normally allow copying or cutting. In such circumstances, you need to enable the Copy or Cut menu items in the context or Edit menu by setting the event.returnValue for the onbeforecopy or onbeforecut event handlers to false. Then your oncopy or oncut event handlers must manually stuff a value into the clipboard by way of the setdata() method of the IE clipboardData object. If you use the setdata() method in your oncopy or oncut event handler, you must also set the
700
Chapter 26: Generic HTML Element Objects elementObject.oncut event.returnValue property to false in the handler function to prevent the default copy or cut action from wiping out your clipboard contents.
Because you are in charge of what data is stored in the clipboard, you are not limited to a direct copy of the data. For example, you might wish to store the value of the src property of an image object so that the user can paste it elsewhere on the page. In the case of the oncut event handler, your script is also responsible for cutting the element or selected content from the page. To eliminate all of the content of an element, you can set the element’s innerHTML or innerText property to an empty string. For a selection, use the selection.createRange() method to generate a TextRange object whose contents you can manipulate through the TextRange object’s methods.
Example Listing 26-36 shows both the onbeforecut and oncut event handlers in action (as well as onbeforepaste and onpaste). Notice that the handleCut() function not only stuffs the selected word into the IE clipboardData object, but also erases the selected text from the table cell element from where it came. If you replace the onbeforecut and oncut event handlers with onbeforecopy and oncopy (and change handleCut() to not eliminate the inner text of the event source element), the operation works with copy and paste instead of cut and paste. We demonstrate this later in the chapter in Listing 26-44. LISTING 26-36
Cutting and Pasting under Script Control HTML: jsb26-36.html onbeforecut and oncut Event Handlers Using a range object td { text-align:center; } th { text-decoration:underline; } .blanks { text-decoration:underline; } onbeforecut and oncut Event Handlers
Your goal is to cut and paste one noun and one adjective from the following table into the blanks of the sentence. Select a word from continued
701
Part IV: Document Objects Reference elementObject.oncut LISTING 26-36
(continued)
the table and use the Edit or context menu to cut it from the table. Select one or more spaces of the blanks in the sentence and choose Paste to replace the blank with the clipboard contents.
Nouns
Adjectives
truck
round
doll
red
ball
pretty
Pat said, "Oh my, the is so !"
Reset
JavaScript: jsb26-36.js function selectWhole() { var obj = window.event.srcElement; var range = document.body.createTextRange(); range.moveToElementText(obj); range.select(); event.returnValue = false; } function handleCut() { var rng = document.selection.createRange(); clipboardData.setData("Text",rng.text); var elem = event.srcElement; elem.innerText = ""; event.returnValue = false; }
702
Chapter 26: Generic HTML Element Objects elementObject.ondblclick function handlePaste() { var elem = window.event.srcElement; if (elem.className == "blanks") { elem.innerHTML = clipboardData.getData("Text"); } event.returnValue = false; } function handleBeforePaste() { var elem = window.event.srcElement; if (elem.className == "blanks") { event.returnValue = false; } }
Related Items: onbeforecopy, onbeforecut, onbeforepaste, and onpaste event handlers
ondataavailable ondatasetchanged ondatasetcomplete Compatibility: WinIE4+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThese three events are part of the data binding of IE and are fired to help reflect the state of data that is being transmitted. The ondataavailable event fires when data is transmitted from the data source, whereas the ondatasetcomplete event indicates that the recordset has completely downloaded from the data source. The ondatasetchanged event is fired when the recordset of a data source has somehow changed.
ondblclick Compatibility: WinIE4+, MacIE4+, NN4+, Moz+, Safari+, Opera+, Chrome+ The ondblclick event fires after the second click of a double-click sequence. The timing between clicks depends on the client’s mouse control panel settings. The onclick event also fires, but only after the first of the two clicks. In general, it is rarely a good design to have an element perform one task when the mouse is single-clicked and a different task if double-clicked. With the event sequence employed in modern browsers, this isn’t practical anyway (the onclick event always fires, even when the user double-clicks). But it is not uncommon to have the mouse down action perform some helper action. You see this in most icon-based file systems: If you click a file icon, it is highlighted at mouse down to select the item; you can double-click the item to launch it. In either case, one event’s action does not impede the other nor confuse the user.
Example See Listing 26-35 (for the onclick event handler) to see the ondblclick event in action.
703
Part IV: Document Objects Reference elementObject.ondrag Related Items: onclick, onmousedown, onmouseup event handlers
ondrag, ondragend, ondragstart Compatibility: WinIE5+, MacIE-, NN-, Moz+, Safari 1.3+, Opera-, Chrome+ The ondrag event fires after the ondragstart event and continues firing repeatedly while the user drags a selection or object onscreen. Unlike the onmousemove event, which fires only as the cursor moves onscreen, the ondrag event continues to fire even when the cursor is stationary. In most browsers, users can drag objects to other browser windows or other applications. The event fires while the dragging extends beyond the browser window. Because the event fires regardless of what is underneath the dragged object, you can use it in a game or training environment in which the user has only a fixed amount of time to complete a dragging operation (for example, matching similar pairs of objects). If the browser accommodates downloadable cursors, the ondrag event could cycle the cursor through a series of cursor versions to resemble an animated cursor. Understanding the sequence of drag-related events during a user drag operation can be helpful if your scripts need to micromanage the actions (usually not necessary for basic drag-and-drop operations). Consider the drag-and-drop operation shown in Figure 26-2. FIGURE 26-2
A typical drag-and-drop operation
704
Chapter 26: Generic HTML Element Objects elementObject.ondrag It helps to imagine that the cells of the table with draggable content are named like spreadsheet cells: truck is cell A1; round is B1; doll is A2; and so on. During the drag operation, many objects are the targets of a variety of drag-related events. Table 26-11 lists the event sequence and the event targets. In practice, some of the events shown in Table 26-11 may not fire. Much has to do with how many event handlers you trap that need to execute scripts along the way. The other major factor is the physical speed at which the user performs the drag-and-drop operation (which interacts with the CPU processing speed). The kinds of events that are most likely to be skipped are the ondragenter and ondragleave events, and perhaps some ondragover events if the user flies over an object before its ondragover event has a chance to fire. Despite this uncertainty about drag-related event reliability, you can count on several important ones to fire all the time. The ondragstart, ondrop (if over a drop target), and ondragend events — as well some interstitial ondrag events — will definitely fire in the course of dragging onscreen. All but ondrop direct their events to the source element, whereas ondrop fires on the target.
Example Listing 26-37 shows several drag-related event handlers in action. The page resembles the example in Listing 26-36, but the scripting behind the page is quite different. In this example, the user is encouraged to select individual words from the Nouns and Adjectives columns and drag them to the blanks of the sentence. To beef up the demonstration, Listing 26-37 shows you how to pass the equivalent of array data from a drag source to a drag target. At the same time, the user has a fixed amount of time (2 seconds) to complete each drag operation. The ondragstart and ondrag event handlers are placed in the tag because those events bubble up from any element that the user tries to drag. The scripts invoked by these event handlers filter the events so that the desired action is triggered only by the hot elements inside the table. This approach to event handlers prevents you from having to duplicate event handlers for each table cell. The ondragstart event handler invokes setupDrag(). This function cancels the ondragstart event except when the target element (the one about to be dragged) is one of the td elements inside the table. To make this application smarter about what kind of word is dragged to which blank, it passes not only the word’s text, but also some extra information about the word. This lets another event handler verify that a noun has been dragged to the first blank, whereas an adjective has been dragged to the second blank. To help with this effort, class names are assigned to the td elements to distinguish the words from the Nouns column from the words of the Adjectives column. The setupDrag() function generates an array consisting of the innerText of the event’s source element plus the element’s class name. But the event.dataTransfer object cannot store array data types, so the Array.join() method converts the array to a string with a colon separating the entries. This string, then, is stuffed into the event.dataTransfer object. The object is instructed to render the cursor display during the drag-and-drop operation so that when the cursor is atop a drop target, the cursor is the copy style. Finally, the setupDrag() function is the first to execute in the drag operation, so a timer is set to the current clock time to time the drag operation. The ondrag event handler (in the body) captures the ondrag events that are generated by whichever table cell element is the source element for the action. Each time the event fires (which is a lot during the action), the timeIt() function is invoked to compare the current time against the reference time (global timer) set when the drag starts. If the time exceeds 2 seconds (2,000 milliseconds), an alert dialog box notifies the user. To close the alert dialog box, the user must unclick the mouse button to end the drag operation.
705
Part IV: Document Objects Reference elementObject.ondrag TABLE 26-11
Events and Their Targets during a Typical Drag-and-Drop Operation Event
Target
Discussion
ondragstart
cell A1
The very first event that fires during a drag-and-drop operation.
ondrag
cell A1
Fires continually on this target throughout the entire operation. Other events get interspersed, however.
ondragenter
cell A1
Even though the cursor hasn’t moved from cell A1 yet, the ondragenter event fires upon first movement within the source element.
ondragover
cell A1
Fires continually on whatever element the cursor rests on at that instant. If the user simply holds the mouse button down and does not move the cursor during a drag, the ondrag and ondragover events fire continually, alternating between the two.
(repetition)
cell A1
ondrag and ondragover events fire alternately while the cursor remains atop cell A1.
ondragenter
table
The table element, represented by the border and/or cell padding, receives the ondragenter event when the cursor touches its space.
ondragleave
cell A1
Notice that the ondragleave event fires after the ondragenter event fires on another element.
ondrag
cell A1
Still firing away.
ondragover
table
The source element for this event shifts to the table because that’s what the cursor is over at this instant. If the cursor doesn’t move from this spot, the ondrag (cell A1) and ondragover (table) events continue to fire in turn.
ondragenter
cell B1
The drag is progressing from the table border space to cell B1.
ondragleave
table
The table element receives the ondragleave event when the cursor exits its space.
ondrag
cell A1
The ondrag event continues to fire on the cell A1 object.
ondragover
cell B1
The cursor is atop cell B1 now, so the ondragover event fires for that object. Fires multiple times (depending on the speed of the computer and the user’s drag action), alternating with the previous ondrag event. More of the same as the cursor progresses from cell B1 through the table border again to cell B2, the table again, cell B3, and the outermost edge of the table.
ondragenter
body
Dragging is free of the table and is floating free on the bare body element.
ondragleave
table
Yes, you just left the table.
ondrag
cell A1
Still alive and receiving this event.
706
Chapter 26: Generic HTML Element Objects elementObject.ondrag Event
Target
Discussion
ondragover
body
That’s where the cursor is now. Fires multiple times (depending on the speed of the computer and the user’s drag action), alternating with the previous ondrag event.
ondragenter
blank1
The cursor reaches the span element whose ID is blank1, where the empty underline is.
ondragleave
body
Just left the body for the blank.
ondrag
cell A1
Still kicking.
ondragover
blank1
That’s where the cursor is now. Fires multiple times (depending on the speed of the computer and the user’s drag action), alternating with the previous ondrag event.
ondrop
blank1
The span element gets the notification of a recent drop.
ondragend
cell A1
The original source element gets the final word that dragging is complete. This event fires even if the drag does not succeed because the drag does not end on a drop target.
To turn the blank span elements into drop targets, their ondragenter, ondragover, and ondrop event handlers must set event.returnValue to false; also, the event.dataTransfer .dropEffect property should be set to the desired effect (copy, in this case). These event handlers are placed in the p element that contains the two span elements, again for simplicity. Notice, however, that the cancelDefault() functions do their work only if the target element is one of the span elements whose ID begins with blank. As the user releases the mouse button, the ondrop event handler invokes the handleDrop() function. This function retrieves the string data from event.dataTransfer and restores it to an array data type (using the String.split() method). A little bit of testing makes sure that the word type (noun or adjective) is associated with the desired blank. If so, the source element’s text is set to the drop target’s innerText property; otherwise, an error message is assembled to help the user know what went wrong. LISTING 26-37
Your goal is to drag one noun and one adjective from the following table into the blanks of the sentence. Select a word from the table and drag it to the desired blank. When you release the mouse, the word will appear in the blank. You have two seconds to complete each blank.
Nouns
Adjectives
truck
round
doll
red
ball
pretty
Pat said, "Oh my, the is so !"
Reset
JavaScript: jsb26-37.js var timer;
708
Chapter 26: Generic HTML Element Objects elementObject.ondrag function setupDrag() { if (event.srcElement.tagName != "TD") { // don’t allow dragging for any other elements event.returnValue = false; } else { // setup array of data to be passed to drop target var passedData = [event.srcElement.innerText, event.srcElement.className]; // store it as a string event.dataTransfer.setData("Text", passedData.join(":")); event.dataTransfer.effectAllowed = "copy"; timer = new Date(); } } function timeIt() { if (event.srcElement.tagName == "TD" && timer) { if ((new Date()) - timer > 2000) { alert("Sorry, time is up. Try again."); timer = 0; } } } function handleDrop() { var elem = event.srcElement; var passedData = event.dataTransfer.getData("Text"); var errMsg = ""; if (passedData) { // reconvert passed string to an array passedData = passedData.split(":"); if (elem.id == "blank1") { if (passedData[1] == "noun") { event.dataTransfer.dropEffect = "copy"; event.srcElement.innerText = passedData[0]; } else { errMsg = "You can’t put an adjective into the noun placeholder."; } } else if (elem.id == "blank2") continued
709
Part IV: Document Objects Reference elementObject.ondragenter LISTING 26-37
(continued)
{ if (passedData[1] == "adjective") { event.dataTransfer.dropEffect = "copy"; event.srcElement.innerText = passedData[0]; } else { errMsg = "You can’t put a noun into the adjective placeholder."; } } if (errMsg) { alert(errMsg); } } } function cancelDefault() { if (event.srcElement.id.indexOf("blank") == 0) { event.dataTransfer.dropEffect = "copy"; event.returnValue = false; } }
One event handler not shown in Listing 26-37 is ondragend. You can use this event to display the elapsed time for each successful drag operation. Because the event fires on the drag source element, you can implement it in the tag and filter events similar to the way the ondragstart or ondrag event handlers filter events for the td element. Related Items: event.dataTransfer object; ondragenter, ondragleave, ondragover, ondrop event handlers
ondragenter ondragleave ondragover Compatibility: WinIE5+, MacIE-, NN-, Moz+, Safari 1.3+, Opera-, Chrome+ These events fire during a drag operation. When the cursor enters the rectangular space of an element on the page, the ondragenter event fires on that element. Immediately thereafter, the ondragleave event fires on the element from which the cursor came. Although this may seem to occur out of sequence from the physical action, the events always fire in this order. Depending on the speed of the client computer’s CPU and the speed of the user’s dragging action, one or the other of these events may not fire — especially if the physical action outstrips the computer’s capability to fire the events in time.
710
Chapter 26: Generic HTML Element Objects elementObject.ondragenter The ondragover event fires continually while a dragged cursor is atop an element. In the course of dragging from one point on the page to another, the ondragover event target changes with the element beneath the cursor. If no other drag-related events are firing (the mouse button is still down in the drag operation, but the cursor is not moving), the ondrag and ondragover events fire continually, alternating between the two. You should have the ondragover event handler of a drop target element set the event .returnValue property to false. See the discussion of the ondrag event handler earlier in this chapter for more details on the sequence of drag-related events.
Example Listing 26-38 shows the ondragenter and ondragleave event handlers in use. The simple page displays (via the status bar) the time of entry to one element of the page. When the dragged cursor leaves the element, the ondragleave event handler hides the status-bar message. No drop target is defined for this page, so when you drag the item, the cursor remains the no-drop cursor. LISTING 26-38
Using ondragenter and ondragleave Event Handlers HTML: jsb26-38.html ondragenter and ondragleave Event Handlers ondragenter and ondragleave Event Handlers
Select any character(s) from this paragraph, and slowly drag it around the page. When the dragging action enters the large header above, the status bar displays when the onDragEnter event handler fires. When you leave the header, the message is cleared via the onDragLeave event handler.
JavaScript: jsb26-38.js function showEnter() { status = "Entered at: " + new Date(); event.returnValue = false; }
continued
711
Part IV: Document Objects Reference elementObject.ondragstart LISTING 26-38
(continued)
function clearMsg() { status = ""; event.returnValue = false; }
Related Items: ondrag, ondragend, ondragstart, ondrop event handlers
ondragstart (See ondrag)
ondrop Compatibility: WinIE5+, MacIE-, NN-, Moz+, Safari 1.3+, Opera-, Chrome+ The ondrop event fires on the drop target element as soon as the user releases the mouse button at the end of a drag-and-drop operation. For IE, Microsoft recommends that you denote a drop target by applying the ondragenter, ondragover, and ondrop event handlers to the target element. In each of those event handlers, you should set the dataTransfer.dropEffect to the transfer effect you wish to portray in the drag-and-drop operation (signified by a different cursor for each type). These settings should match the dataTransfer.effectAllowed property that is usually set in the ondragstart event handler. Each of the three drop-related handlers should also override the default event behavior by setting the event.returnValue property to false. See the discussion of the ondrag event handler earlier in this chapter for more details on the sequence of drag-related events.
Example See Listing 26-37 of the ondrag event handler to see how to apply the ondrop event handler in a typical drag-and-drop scenario. Related Items: event.dataTransfer object; ondrag, ondragend, ondragenter, ondragleave, ondragover, ondragstart event handlers
onerrorupdate Compatibility: WinIE4+, MacIE5+, NN-, Moz-, Safari-, Opera-, ChromeThe onerrorupdate event handler is part of the data binding of IE and fires when an error occurs while updating the data in the data source object.
onfilterchange Compatibility: WinIE4+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe onfilterchange event fires whenever an object’s visual filter switches to a new state or a transition completes (a transition may be extended over time). Only objects that accommodate filters and transitions in IE (primarily block elements and form controls) receive the event.
712
Chapter 26: Generic HTML Element Objects elementObject.onfilterchange A common usage of the onfilterchange event is to trigger the next transition within a sequence of transition activities. This may include an infinite loop transition, for which the object receiving the event toggles between two transition states. If you don’t want to get into a loop of that kind, place the different sets of content in their own positionable elements, and use the onfilterchange event handler in one to trigger the transition in the other.
Example Listing 26-39 demonstrates how the onfilterchange event handler can trigger a second transition effect after another one completes. The onload event handler triggers the first effect. Although the onfilterchange event handler works with most of the same objects in IE4 as IE5, the filter object transition properties are not reflected in a convenient form. The syntax shown in Listing 26-39 uses the more modern ActiveX filter control found in IE5.5+ (described in Chapter 38). LISTING 26-39
The completion of the first transition ("circle-in") triggers the second ("circle-out"). Play It Again
continued
713
Part IV: Document Objects Reference elementObject.onfocus LISTING 26-39
(continued)
JavaScript: jsb26-39.js function init() { image1.filters[0].apply(); image2.filters[0].apply(); start(); } function start() { image1.style.visibility = "hidden"; image1.filters[0].play(); } function finish() { // verify that first transition is done (optional) if (image1.filters[0].status == 0) { image2.style.visibility = "visible"; image2.filters[0].play(); } }
Related Item: filter object
onfocus Compatibility: WinIE3+, MacIE3+, NN2+, Moz+, Safari+, Opera+, Chrome+ The onfocus event fires when an element receives focus, usually following some other object’s losing focus. (The element losing focus receives the onblur event before the current object receives the onfocus event.) For example, a text input element fires the onfocus event when a user tabs to that element while navigating through a form via the keyboard. Clicking an element also gives that element focus, as does making the browser the frontmost application on the client desktop.
714
Chapter 26: Generic HTML Element Objects elementObject.onhelp The availability of the onfocus event has expanded with succeeding generations of script-capable browsers. In earlier versions, blur and focus were largely confined to text-oriented input elements such as the select element. The window object received the onfocus event handler starting with NN3 and IE4. IE4 also extended the event handler to more form elements, predominantly on the Windows operating system because that OS has a user interface clue (the dotted rectangle) when items such as buttons and links receive focus (so that users may act on them by pressing the spacebar). For IE5+, the onfocus event handler is available to virtually every HTML element. For most of those elements, however, you cannot use blur and focus unless you assign a value to the tabindex attribute of the element’s tag. For example, if you assign tabindex="1" inside a
tag, the user can bring focus to that paragraph (highlighted with the dotted rectangle in Windows) by clicking the paragraph or pressing the Tab key until that item receives focus in sequence. WinIE5.5 adds the onfocusin event handler, which fires immediately before the onfocus event handler. You can use one or the other, but there is little need to include both event handlers for the same object unless you wish to block an item temporarily from receiving focus. To prevent an object from receiving focus in IE5.5+, include an event.returnValue=false statement in the onfocusin event handler for the same object. In other browsers, you can usually get away with assigning onfocus="this.blur()" as an event handler for elements such as form controls. However, this is not a foolproof way to prevent a user from changing a control’s setting. Unfortunately, there are few reliable alternatives short of disabling the control.
Example See Listing 26-34 earlier in this chapter for an example of the onfocus and onblur event handlers. Related Items: onactivate, onblur, ondeactivate, onfocusin, onfocusout event handlers
onfocusin onfocusout Compatibility: WinIE6+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe onfocusin and onfocusout events fire to indicate that an element is about to receive focus or has just lost focus. These events are closely related to onactivate and ondeactivate except that in IE5.5+ activation and focus can be distinguished from each other. For example, if you set an element as the active element through setActive(), the element becomes active, but it does not gain the input focus. However, if you set the focus of an element with a call to focus(), the element is activated and gains input focus. Related Items: onactivate, onblur, ondeactivate, onfocus event handlers
onhelp Compatibility: WinIE4+, MacIE5+, NN-, Moz-, Safari-, Opera-, ChromeThe onhelp event handler fires in Windows whenever an element of the document has focus and the user presses the F1 function key on a Windows PC. As of MacIE5, the event fires only on the window (in other words, event handler specified in the tag) and does so via the dedicated Help key on a Mac keyboard. Browser Help menu choices do not activate this event. To prevent the browser’s Help window from appearing, the event handler must evaluate to return false (for IE4+) or set the event.returnValue property to false (IE5+). Because the event handler can be associated with individual elements of a document in the Windows version, you can create a context-sensitive help system. However, if the focus is in the Address field of the browser window, you cannot intercept the event. Instead, the browser’s Help window appears.
715
Part IV: Document Objects Reference elementObject.onhelp
Example Listing 26-40 is a rudimentary example of a context-sensitive help system that displays help messages tailored to the kind of text input required by different text boxes. When the user gives focus to either of the text boxes, a small legend appears to remind the user that help is available by a press of the F1 help key. MacIE5 provides only generic help.
Name: Year of Birth: JavaScript: jsb26-40.js function showNameHelp() { alert("Enter your first and last names."); event.cancelBubble = true;
716
Chapter 26: Generic HTML Element Objects elementObject.onkeyup return false; } function showYOBHelp() { alert("Enter the four-digit year of your birth. For example: 1972"); event.cancelBubble = true; return false; } function showGenericHelp() { alert("All fields are required."); event.cancelBubble = true; return false; } function showLegend() { document.getElementById("legend").style.visibility = "visible"; } function hideLegend() { document.getElementById("legend").style.visibility = "hidden"; } function init() { var msg = ""; if (navigator.userAgent.indexOf("Mac") != -1) { msg = "Press \’help\’ key for help."; } else if (navigator.userAgent.indexOf("Win") != -1) { msg = "Press F1 for help."; } document.getElementById("legend").style.visibility = "hidden"; document.getElementById("legend").innerHTML = msg; }
Related Items: window.showHelp(), window.showModalDialog() methods
onkeydown onkeypress onkeyup Compatibility: WinIE4+, MacIE4+, NN4+, Moz+, Safari+, Opera+, Chrome+ When someone presses and releases a keyboard key, a sequence of three events fires in quick succession. The onkeydown event fires when the key makes its first contact. This is followed immediately by the onkeypress event. When contact is broken by the key release, the onkeyup event fires.
717
Part IV: Document Objects Reference elementObject.onkeyup If you hold a character key down until it begins autorepeating, the onkeydown and onkeypress events fire with each repetition of the character. The sequence of events can be crucial in some keyboard event handling. Consider the scenario that wants the focus of a series of text boxes to advance automatically after the user enters a fixed number of characters (for example, date, month, and two-digit year). By the time the onkeyup event fires, the character associated with the key-press action is already added to the box and you can accurately determine the length of text in the box, as shown in this simple example: Simple entry form function jumpNext(fromFld, toFld) { if (fromFld.value.length == 2) { document.dateForm.elements[toFld].focus(); document.dateForm.elements[toFld].select(); } } Month: Day: Year:
These three events do not fire for all keys of the typical PC keyboard on all browser versions that support keyboard events. The only keys that you can rely on supporting the events in all browsers shown in the preceding compatibility chart are the alphanumeric keys represented by ASCII values, including the spacebar and Enter (Return on the Mac), but excluding all function keys, arrow keys, and other navigation keys. Modifier keys, such as Shift, Ctrl (PC), Alt (PC), Command (Mac), and Option (Mac), generate some events on their own (depending on browser and version). However, functions invoked by other key events can always inspect the pressed states of these modifier keys.
Caution The onkeydown event handler works in Mozilla-based browsers only starting with Mozilla 1.4 (and Netscape 7.1).
Scripting keyboard events almost always entails examining which key is pressed so that some processing or validation can be performed on that key press. This is where the situation gets very complex if you are writing for cross-browser implementation. In some cases, even writing just for Internet
718
Chapter 26: Generic HTML Element Objects elementObject.onkeyup Explorer gets tricky because nonalphanumeric keys generate only the onkeydown and onkeyup events. In fact, to comprehend keyboard events fully, you need to make a distinction between key codes and character codes. Every PC keyboard key has a key code associated with it. This key code is always the same regardless of what other keys you press at the same time. Only the alphanumeric keys (letters, numbers, spacebar, and so on), however, generate character codes. The code represents the typed character produced by that key. The value might change if you press a modifier key. For example, if you press the A key by itself, it generates a lowercase a character (character code 97); if you also hold down the Shift key, that same key produces an uppercase A character (character code 65). The key code for that key (65 for Western-language keyboards) remains the same no matter what. That brings us, then, to where these different codes are made available to scripts. In all cases, the code information is conveyed as one or two properties of the browser’s event object. IE’s event object has only one such property: keyCode. It contains key codes for onkeydown and onkeyup events but character codes for onkeypress events. The NN6+/Moz event object, on the other hand, contains two separate properties: charCode and keyCode. You can find more details and examples about these event object properties in Chapter 32. The bottom-line script consideration is to use either onkeydown or onkeyup event handlers when you want to look for nonalphanumeric key events (for example, function keys, arrow and page-navigation keys, and so on). To process characters as they appear in text boxes, use the onkeypress event handler. You can experiment with these events and codes in Listing 26-41, as well as in examples from Chapter 32.
Common keyboard event tasks WinIE4+ enables you to modify the character that a user who is editing a text box enters. The onkeypress event handler can modify the event.keyCode property and allow the event to continue (in other words, don’t evaluate to return false or set the event.returnValue property to false). The following IE function (invoked by an onkeypress event handler) makes sure that text entered in a text box is all uppercase, even if you type it as lowercase: function assureUpper() { if (event.keyCode >= 97 && event.keyCode 31 && (charCode < 48 || charCode > 57)) { alert("Please make sure entries are numbers only."); return false; } return true; } Enter any positive integer:
Whenever a user enters a non-number, the user receives a warning, and the character is not appended to the text box’s text. Keyboard events also enable you to script the submission of a form when a user presses the Enter (Return on the Mac) key within a text box. The ASCII value of the Enter/Return key is 13. Therefore, you can examine each key press in a text box and submit the form whenever value 13 arrives, as shown in the following function: function checkForEnter(evt) { evt = (evt) ? evt : event; var charCode = (evt.charCode) ? evt.charCode : ((evt.which) ? evt.which : evt.keyCode); if (charCode == 13) { document.forms[0].submit(); return false; } return true; }
By assigning the checkForEnter() function to each box’s onkeypress event handler, you suddenly add some extra power to a typical HTML form. You can intercept Ctrl+keyboard combinations (letters only) in HTML pages most effectively in IE, but only if the browser itself does not use the combination. In other words, you cannot redirect Ctrl+key combinations that the browser uses for its own control. The onkeypress keyCode value for Ctrl+key combinations ranges from 1 through 26 for letters A through Z (except for those used by the browser, in which case no keyboard event fires).
720
Chapter 26: Generic HTML Element Objects elementObject.onkeyup
Example Listing 26-41 is a working laboratory that you can use to better understand the way keyboard event codes and modifier keys work in IE5+ and W3C browsers. The actual code of the listing is less important than watching the page while you use it. For every key or key combination that you press, the page shows the keyCode value for the onkeydown, onkeypress, and onkeyup events. If you hold down one or more modifier keys while performing the key press, the modifier-key name is highlighted for each of the three events. Note that when run in NN6+/Moz-based browsers/WebKit-based browsers, the keyCode value is not the character code. In older browsers, you may need to click the page for the document object to recognize the keyboard events. The best way to watch what goes on during keyboard events is to press and hold a key to see the key codes for the onkeydown and onkeypress events. Then release the key to see the code for the onkeyup event. Notice, for instance, that if you press the A key without any modifier key, the onkeydown event key code is 65 (A), but the onkeypress key code in IE (and the charCode property in NN6+/Moz-based browsers/WebKit-based browsers) is 97 (a). If you then repeat the exercise but hold the Shift key down, all three events generate the 65 (A) key code (and the Shift modifier labels are highlighted). Releasing the Shift key causes the onkeyup event to show the key code for the Shift key. In another experiment, press any of the four arrow keys. No key code is passed for the onkeypress event because those keys don’t generate those events. They do, however, generate onkeydown and onkeyup events. LISTING 26-41
Spend some time with this lab, and try all kinds of keys and key combinations until you understand the way the events and key codes work. Related Item: String.fromCharCode() method
onlayoutcomplete Compatibility: WinIE5.5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe onlayoutcomplete event handler fires when a print or print-preview layout operation completes on the current layout rectangle (LayoutRect object). This event is primarily used as the basis for overflowing content from one page to another during printing. In response to the onlayoutcomplete event, the contentOverflow property can be inspected to determine whether page content has indeed overflowed the current layout rectangle.
onlosecapture Compatibility: WinIE5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe onlosecapture event handler fires whenever an object that has event capture turned on no longer has that capture. Event capture is automatically disengaged when the user performs any of the following actions:
Gives focus to any other window
Displays any system modal dialog box (for example, alert window)
Scrolls the page
Opens a browser context menu (right-clicking)
Tabs to give focus to the Address field in the browser window
A function associated with the onlosecapture event handler should perform any cleanup of the environment due to an object’s no longer capturing mouse events.
724
Chapter 26: Generic HTML Element Objects elementObject.onmouseup
Example See Listing 26-30 earlier in this chapter for an example of how to use onlosecapture with an event-capturing scenario for displaying a context menu. The onlosecapture event handler hides the context menu when the user performs any action that causes the menu to lose mouse capture. Related Items: releaseCapture(), setCapture() methods
onmousedown onmouseup Compatibility: WinIE4+, MacIE4+, NN4+, Moz+, Safari+, Opera+, Chrome+ The onmousedown event handler fires when the user presses any button on a mouse. The onmouseup event handler fires when the user releases the mouse button, provided that the object receiving the event also received an onmousedown event. When a user performs a typical click of the mouse button atop an object, mouse events occur in the following sequence: onmousedown, onmouseup, and onclick. But if the user presses the mouse atop an object and then slides the cursor away from the object, only the onmousedown event fires. These events enable authors and designers to add more applicationlike behavior to images that act as action or icon buttons. If you notice the way most buttons work, the appearance of the button changes while you press the mouse button and reverts to its original style when you release the mouse button (or you drag the cursor out of the button). These events enable you to emulate that behavior. The event object created with every mouse button action has a property that reveals which mouse button the user pressed. NN4’s event model called that property the which property. IE4+ and NN6+/Moz-based browsers/WebKit-based browsers call it the button property (but with different values for the buttons). It is most reliable to test for the mouse button number on either the onmousedown or onmouseup event rather than on onclick. The onclick event object does not always contain the button information.
Example To demonstrate a likely scenario of changing button images in response to rolling atop an image, pressing down on it, releasing the mouse button, and rolling away from the image, Listing 26-42 presents a pair of small navigation buttons (left- and right-arrow buttons). Images are preloaded into the browser cache as the page loads so that response to the user is instantaneous the first time the user calls upon new versions of the images. LISTING 26-42
Using onmousedown and onmouseup Event Handlers HTML: jsb26-42.html onmousedown and onmouseup Event Handlers #imgHolder {
continued
725
Part IV: Document Objects Reference elementObject.onmouseup LISTING 26-42
Roll atop and click on the buttons to see how the link event handlers swap the subtlety different images:
JavaScript: jsb26-42.js var var var var var var
RightNormImg = new Image(16,16); RightUpImg = new Image(16,16); RightDownImg = new Image(16,16); LeftNormImg = new Image(16,16); LeftUpImg = new Image(16,16); LeftDownImg = new Image(16,16);
Chapter 26: Generic HTML Element Objects elementObject.onmousemove function setImage(imgName, type) { var imgFile = eval(imgName + type + "Img.src"); document.images[imgName].src = imgFile; return false; }
Related Item: onclick event handler
onmouseenter onmouseleave Compatibility: WinIE5.5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeWinIE5.5 introduced the onmouseenter and onmouseleave event handlers. Both event handlers operate just like the onmouseover and onmouseout event handlers, respectively. Microsoft simply offers an alternative terminology. The old and new events continue to fire in IE5.5+. The old ones fire just before the new ones for each act of moving the cursor atop, and exiting from atop, the object. If you are scripting exclusively for IE5.5+, you should use the new terminology; otherwise, stay with the older versions.
Example You can modify Listing 26-43 with the IE5.5 syntax by substituting onmouseenter for onmouseover and onmouseleave for onmouseout. The effect is the same. Related Items: onmouseover, onmouseout event handlers
onmousemove Compatibility: WinIE4+, MacIE4+, NN4+, Moz+, Safari+, Opera+, Chrome+ The onmousemove event handler fires whenever the cursor is atop the current object and the mouse is moved, even by a single pixel. You do not have to press the mouse button for the event to fire, although the event is most commonly used in element dragging — especially in NN/FF3.4-/Opera, where no ondrag event handler is available. Even though the granularity of this event can be at the pixel level, you should not use the number of event firings as a measurement device. Depending on the speed of cursor motion and the performance of the client computer, the event may not fire at every pixel location. In IE4+ and W3C DOM-compatible browsers, you can assign the onmousemove event handler to any element (although you can drag only with positioned elements). When designing a page that encourages users to drag multiple items on a page, it is most common to assign the onmousemove event handler to the document object and let all such events bubble up to the document for processing.
Example See Chapter 43 and Chapter 59 on the CD-ROM for examples of using mouse events to control element dragging on a page. Related Items: ondrag, onmousedown, onmouseup event handlers
727
Part IV: Document Objects Reference elementObject.onmouseout
onmouseout onmouseover Compatibility: WinIE3+, MacIE3+, NN2+, Moz+, Safari+, Opera+, Chrome+ The onmouseover event fires for an object whenever the cursor rolls into the rectangular space of the object on the screen. The onmouseout event handler fires when you move the cursor outside the object’s rectangle. These events most commonly display explanatory text about an object in the window’s status bar and effect image swapping (so-called mouse rollovers). Use the onmouseover event handler to change the state to a highlighted version; use the onmouseout event handler to restore the image or status bar to its normal setting. Although these two events have been in object models of scriptable browsers since the beginning, they were not available to most objects in earlier browsers. IE4+ and W3C DOM-compatible browsers provide support for these events on every element that occupies space onscreen. IE5.5+ includes an additional pair of event handlers — onmouseenter and onmouseleave — that duplicates the onmouseover and onmouseout events but with different terminology. The old event handlers fire just before the new versions.
Note The onmouseout event handler commonly fails to fire if the event is associated with an element that is near a frame or window edge and the user moves the cursor quickly outside the current frame.
Example Listing 26-43 uses the U.S. Pledge of Allegiance with four links to demonstrate how to use the onmouseover and onmouseout event handlers. Notice that for each link, the handler runs a general-purpose function that sets the window’s status message. The function returns a true value, which the event handler call evaluates to replicate the required return true statement needed for setting the status bar. In one status message, we supply a URL in parentheses to let you evaluate how helpful you think it is for users. LISTING 26-43
Using onmouseover and onmouseout Event Handlers HTML: jsb26-43.html onmouseover and onmouseout Event Handlers onmouseover and onmouseout Event Handlers Pledge of Allegiance I pledge allegiance to the flag of the United States of America, and to the Republic for which it stands, one nation under God, indivisible, with liberty and justice for all.
JavaScript: jsb26-43.js function setStatus(msg) { window.status = msg; return true; } // destination of all link HREFs function emulate() { alert("Not going there in this demo."); }
Related Items: onmouseenter, onmouseleave, onmousemove event handlers
onmousewheel Compatibility: WinIE6+, MacIE-, NN-, Moz+, Safari+, Opera+, Chrome+ The onmousewheel event handler fires in response to the user’s rotating the mouse wheel. When responding to the onmousewheel event, you can check the wheelDelta property to find out how far the mouse wheel has been rotated. The wheelDelta property expresses mouse wheel rotations in multiples of 120, with positive values indicating a rotation away from the user and negative values corresponding to a rotation toward the user. The W3C equivalent is DOMMouseScroll. Related Item: onmousemove event handler
Part IV: Document Objects Reference elementObject.onmoveend Not to be confused with onmousemove, the onmove event has nothing to do with the mouse. Instead, the onmove event is fired whenever a positionable element is moved. For example, if a div element is created as an absolutely positioned moveable element, you can track its movement by responding to the onmove event. The offsetLeft and offsetTop properties can be used within this event handler to determine the exact location of the element as it is moving. Related Items: onmoveend, onmovestart event handlers
onmoveend onmovestart Compatibility: WinIE5.5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe onmovestart and onmoveend event handlers fire in response to a positionable element’s being moved on a page. More specifically, the onmovestart event is triggered when an element first starts moving and the onmoveend event fires when the element stops moving. In between the onmovestart and onmoveend events firing, multiple onmove events may be sent out to indicate the movement of the element. Related Item: onmove event handler
onpaste Compatibility: WinIE5+, MacIE-, NN-, Moz+, Safari 1.3+, Opera-, Chrome+ The onpaste event fires immediately after the user or script initiates a paste edit action on the current object. The event is preceded by the onbeforepaste event, which fires prior to any edit or context menu that appears (or before the paste action if initiated by keyboard shortcut). Use this event handler to provide edit functionality to elements that don’t normally allow pasting. In such circumstances, you need to enable the Paste menu item in the context or Edit menu by setting the event.returnValue for the onbeforepaste event handler to false. Then your onpaste event handler must manually retrieve data from the clipboard (by way of the getData() method of the IE clipboardData object) and handle the insertion into the current object. Because you are in charge of what data is stored in the clipboard, you are not limited to a direct copy of the data. For example, you might wish to store the value of the src property of an image object so that you can paste it elsewhere on the page.
Example Listing 26-44 demonstrates how to use the onbeforepaste and onpaste event handlers (in conjunction with onbeforecopy and oncopy) to let scripts control the data-transfer process during a copy-and-paste user operation. A table contains words to be copied (one column of nouns, one column of adjectives) and then pasted into blanks in a paragraph. The onbeforecopy and oncopy event handlers are assigned to the table element because the events from the td elements bubble up to the table container and there is less HTML code to contend with. Inside the paragraph, two span elements contain underscored blanks. To paste text into the blanks, the user must first select at least one character of the blanks. (See Listing 26-37, which gives a drag-and-drop version of this application.) The onbeforepaste event handler in the paragraph (which gets the event as it bubbles up from either span) sets the event.returnValue property to false, thus allowing the Paste item to appear in the context and Edit menus (not a normal occurrence in HTML body content).
730
Chapter 26: Generic HTML Element Objects elementObject.onpaste At paste time, the innerHTML property of the target span is set to the text data stored in the clipboard. The event.returnValue property is set to false here as well to prevent normal system pasting from interfering with the controlled version.
LISTING 26-44
Using onbeforepaste and onpaste Event Handlers HTML: jsb26-44.html onbeforepaste and onpaste Event Handlers td { text-align:center; } th { text-decoration:underline; } .blanks { text-decoration:underline; } onbeforepaste and onpaste Event Handlers Be very precise when selecting characters
Your goal is to copy and paste one noun and one adjective from the following table into the blanks of the sentence. Select a word from the table and use a menu to copy it to the clipboard. Select one or more spaces of the blanks in the sentence and choose Paste from a menu to replace the blank with the clipboard contents.
Nouns
Adjectives
truck
round
continued
731
Part IV: Document Objects Reference elementObject.onpaste LISTING 26-44
(continued)
doll
red
ball
pretty
Pat said, "Oh my, the is so !"
Reset
JavaScript: jsb26-44.js function selectWhole() { var obj = window.event.srcElement; var range = document.body.createTextRange(); range.moveToElementText(obj); range.select(); event.returnValue = false; } function handleCopy() { var rng = document.selection.createRange(); clipboardData.setData("Text",rng.text); event.returnValue = false; } function handlePaste() { var elem = window.event.srcElement; if (elem.className == "blanks") { elem.innerHTML = clipboardData.getData("Text"); } event.returnValue = false; } function handleBeforePaste() { var elem = window.event.srcElement;
732
Chapter 26: Generic HTML Element Objects elementObject.onpropertychange if (elem.className == "blanks") { event.returnValue = false; } }
Related Items: oncopy, oncut, onbeforepaste event handlers
onpropertychange Compatibility: WinIE5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe onpropertychange event fires in WinIE5+ whenever a script modifies an object’s property. This includes changes to the properties of an object’s style. Changing properties by way of the setAttribute() method also triggers this event. A script can inspect the nature of the property change because the event.propertyName property contains the name (as a string) of the property that was just changed. In the case of a change to an object’s style object, the event.propertyName value begins with "style." as in style.backgroundcolor. You can use this event handler to localize any object-specific postprocessing of changes to an object’s properties. Rather than include the postprocessing statements inside the function that makes the changes, you can make that function generalized (perhaps to modify properties of multiple objects).
Example Listing 26-45 shows how you can respond programmatically to an object’s properties being changed. The page generated by the listing contains four radio buttons that alter the innerHTML and style.color properties of a paragraph. The paragraph’s onpropertychange event handler invokes the showChange() function, which extracts information about the event and displays the data in the status bar of the window. Notice that the property name includes style. when you modify the style sheet property. LISTING 26-45
Using the onPropertyChange Property HTML: jsb26-45.html onpropertychange Event Handler onpropertychange Event Handler
continued
733
Part IV: Document Objects Reference elementObject.onpropertychange LISTING 26-45
(continued)
This is a sample paragraph.
Text: Normal Short Color: Black Red
JavaScript: jsb26-45.js function init() { elem = document.getElementById("myP"); } function normalText() { if (elem.textContent) { elem.textContent = "This is a sample paragraph."; } else { elem.innerText = "This is a sample paragraph."; } } function shortText() { if (elem.textContent) { elem.textContent = "Short stuff."; } else { elem.innerText = "Short stuff."; } } function normalColor() { elem.style.color = "black"; }
734
Chapter 26: Generic HTML Element Objects elementObject.onresize function hotColor() { elem.style.color = "red"; } function showChange() { var objID = event.srcElement.id; var propName = event.propertyName; var newValue = eval(objID + "." + propName); var msg = "The " + propName + " property of the " + objID; msg += " object has changed to \"" + newValue + "\"."; alert(msg); }
Related Items: style property; setAttribute() method
onreadystatechange Compatibility: WinIE4+, MacIE-, NN7+, Moz1.0.1+, Safari 1.2+, Opera+, Chrome+ The onreadystatechange event handler fires whenever the ready state of an object changes. See details about these states in the discussion of the readyState property earlier in this chapter (and notice the limits for IE4). The change of state does not guarantee that an object is in fact ready for script statements to access its properties. Always check the readyState property of the object in any script that the onreadystatechange event handler invokes. This event fires for objects that are capable of loading data: applet, document, frame, frameset, iframe, img, link, object, script, and XML objects. The event doesn’t fire for other types of objects unless a Microsoft DHTML behavior is associated with the object. The onreadystatechange event does not bubble; neither can you cancel it. Related Item: readyState property
onresize Compatibility: WinIE4+, MacIE4+, NN4+, Moz+, Safari+, Opera+, Chrome+ The onresize event handler fires whenever an object is resized in response to a variety of user or scripted actions. Most elements include this event handler, provided that the object has dimensional style attributes (for example, height, width, or position) assigned to it. The onresize event does not bubble. Resizing the browser window or frame does not cause the window’s onload event handler to fire.
Example If you want to capture the user’s resizing of the browser window (or frame), you can assign a function to the onresize event handler either via script window.onresize = handleResize;
735
Part IV: Document Objects Reference elementObject.onresizeend or by an HTML attribute of the body element:
Related Item: window.resize() method
onresizeend onresizestart Compatibility: WinIE5.5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe onresizeend and onresizestart event handlers fire only on a resizable object in Windows edit mode. Related Item: oncontrolselect event handler
onrowenter onrowexit Compatibility: WinIE4+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe onrowenter and onrowexit events fire in response to changes in the current row of recordset data in IE data binding. More specifically, onrowenter is triggered when the data for the current row of data has changed and new data is available on the data source object. The onrowexit event is triggered when the current row is changing, meaning that another row of data is being selected; the event is fired just before the row changes. Related Items: onrowsdelete, onrowsinserted event handlers
onrowsdelete onrowsinserted Compatibility: WinIE5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe onrowsdelete event fires when one or more rows of data are about to be deleted from the recordset in IE data binding. Conversely, the onrowsinserted event is triggered when one or more rows of data have been inserted into the recordset. Related Items: onrowenter, onrowexit event handlers
onscroll Compatibility: WinIE4+, MacIE4+, NN-, Moz+, Safari+, Opera_, Chrome+ The onscroll event handler fires whenever the scroll box within a scroll bar of an element is repositioned. In simpler terms, when the user clicks and drags the scroll box with the mouse, the onscroll event is fired. That’s not the only action that triggers the event, however. An onscroll event is also fired in response to the user’s clicking the scroll arrow, clicking the scroll bar, or pressing any of the following keys: Home, End, Space, Page Up, or Page Down. A call to the doScroll() method also triggers the event, as does the user’s holding down the Up Arrow or Down Arrow key. Related Item: doScroll() method
Chapter 26: Generic HTML Element Objects elementObject.onselectstart The onselectstart event handler fires when a user begins to select content on the page. Selected content can be inline text, images, or text within an editable text box. If the user selects more than one object, the event fires in the first object affected by the selection.
Example Use the page from Listing 26-46 to see how the onselectstart event handler works when a user selects across multiple elements on a page. As the user begins a selection anywhere on the page, the ID of the object receiving the event appears in the status bar. Notice that the event doesn’t fire until you actually make a selection. When no other element is under the cursor, the body element fires the event. LISTING 26-46
Part IV: Document Objects Reference elementObject.onselectstart LISTING 26-46
(continued)
text
text
text
text
JavaScript: jsb26-46.js function showObj() { var objID = event.srcElement.id; alert("Selection started with object: " + objID); }
Related Item: onselect event handler for a variety of objects
738
Window and Frame Objects
A
quick look at the basic document object model diagram in Chapter 25, ‘‘Document Object Model Essentials,’’ (refer to Figure 25-1) reveals that the window object is the outermost global container of all document-related objects that you script with JavaScript. All HTML and JavaScript activity takes place inside a window. That window may be a standard Windows, Mac, or XWindows application-style window, complete with scroll bars, toolbars, and other chrome; you can also generate windows that have only some of a typical window’s chrome. A frame is also a window, even though a frame doesn’t have many accoutrements beyond scroll bars. The window object is where everything begins when JavaScript references objects. Modern browsers treat the frameset as a special kind of window object, so it is also covered in this chapter. Of all the objects associated with browser scripting, the window and window-related objects have by far the most object-specific terminology associated with them. This necessitates a rather long chapter to keep the whole discussion in one place.
Window Terminology The window object is often a source of confusion when you first learn about the document object model. A number of synonyms for window objects muck up the works: top, self, parent, and frame. Aggravating the situation is the fact that these terms are also properties of a window object. Under some conditions, a window is its own parent, but if you define a frameset with two frames, you have only one parent among a total of three window objects. It doesn’t take long before the whole subject can make your head hurt. If you do not use frames in your web applications, these headaches never appear. But if frames are part of your design plan, you should get to know how frames affect the object model.
739
IN THIS CHAPTER Scripting communication among multiple frames Creating and managing new windows Controlling the size, position, and appearance of the browser window Details of window, frame, frameset, and iframe objects
Part IV: Document Objects Reference
Frames The application of frames has become a religious issue among web designers: Some swear by them; others swear at them. We believe, after careful consideration, that there can be compelling reasons to use frames at times. Historically, any humungous document with a hierarchy, or that depends on a file system, might be a good candidate. For example, if you have a document that requires considerable scrolling to get through, you may want to maintain a static set of navigation controls that are visible at all times. By placing those controls — be they links or image maps — in a separate frame, you have made the controls available for immediate access, regardless of the scrolled condition of the main document. However, you could use an Ajax framework to provide such navigational controls instead of using HTML frames. Be aware that creating bookmarks and printing documents in frames can range anywhere from impossible to difficult. Frames can be a problem for folks with disabilities. Most web designers provide an alternative flat HTML document with links for those types of situations.
Creating frames The task of defining frames in a document remains the same whether or not you’re using JavaScript. The simplest framesetting document consists of tags that are devoted to setting up the frameset, as follows: My Frameset
The preceding HTML document, which the user never sees, defines the frameset for the entire browser window. Each frame must have a URL reference (specified by the src attribute) for a document to load into that frame. Assigning a name to each frame with the name attribute greatly simplifies the scripting of frame content.
The frame object model Perhaps the key to successful frame scripting is understanding that the object model in the browser’s memory at any given instant is determined by the HTML tags in the currently loaded documents. All canned object model graphics in this book, such as Figure 27-1, do not reflect the precise object model for your document or document set. For a single, frameless document, the object model starts with just one window object, which contains one document, as shown in Figure 27-1. In this simple structure, the window object is the starting point for all references to any loaded object. Because the window is always there — it must be there for a document to load into — a reference to any object in the document can omit a reference to the current window. In a simple two-framed frameset model (see Figure 27-2), the browser treats the container of the initial, framesetting, document as the parent window. The only visible evidence that the document exists is the framesetting document’s title in the browser window title bar.
740
Chapter 27: Window and Frame Objects
FIGURE 27-1
The simplest window-document relationship. Window
Document
FIGURE 27-2
The parent and frames are part of the object model. Top Parent
Top Parent
Top Parent
Document
Document
Each tag inside the tag set creates another window object into which a document is loaded. Each of those frames, then, has a document object associated with it. From the point of view of a given document, it has a single window container, just as in the model shown in Figure 27-1. And although the parent object is not visible to the user, it remains in the object model in memory. The presence of the parent often makes it a convenient repository for variable data that needs to be shared by multiple child frames, or that must persist between loading different documents inside a child frame. In even more complex arrangements, as shown in Figure 27-3, a child frame itself may load a framesetting document. In this situation, the difference between the parent and top objects starts to come into focus. The top window is the only one in common with all frames in Figure 27-3. As you see in a moment, when frames need to communicate with other frames (and their documents), you must fashion references to the distant object via the window object that they all have in common.
741
Part IV: Document Objects Reference
FIGURE 27-3
Three generations of window objects.
Top Parent
Child Frame
Child Frame Parent
Document
Child Frame
Child Frame
Document
Document
Referencing frames The purpose of an object reference is to help JavaScript locate the desired object in the object model currently held in memory. A reference is a road map for the browser to follow so that it can track down, say, the value of a particular text field in a particular document. Therefore, when you construct a reference, think about where the script appears in the object model and how the reference can help the browser determine where it should go to find the distant object. In a two-generation scenario, such as the one shown in Figure 27-2, three intergenerational references are possible:
Parent-to-child
Child-to-parent
Child-to-child
Assuming that you need to access an object, function, or variable in the relative’s frame, the following are the corresponding reference structures: frameName.objFuncVarName, parent.objFuncVarName. and parent.frameName.objFuncVarName. The rule is this: Whenever a reference must point to another frame, begin the reference with the window object that the two destinations have in common. To demonstrate that rule on the complex model in Figure 27-3, if the left child frame’s document needs to reference the document at the bottom right of the map, the reference structure is top.frameName.frameName.document. ...
Follow the map from the top window object, down through two frames, to the final document. JavaScript has to take this route, so your reference must help it along.
742
Chapter 27: Window and Frame Objects
Top versus parent After seeing the previous object maps and reference examples, you may be wondering, Why not use top as the leading object in all transframe references? From an object model point of view, you’ll have no problem doing that: A parent in a two-generation scenario is also the top window. What you can’t count on, however, is your framesetting document’s always being the top window object in someone’s browser. Take the instance where a web site loads other web sites into one of its frames. At that instant, the top window object belongs to someone else. If you always specify top in references intended just for your parent window, your references won’t work, and will probably lead to script errors for the user. Our advice, then, is to use parent in references whenever you mean one generation above the current document.
Preventing framing You can use your knowledge of top and parent references to prevent your pages from being displayed inside another web site’s frameset. Your top-level document must check whether it is loaded into its own top, or parent, window. When a document is in its own top window, a reference to the top property of the current window is equal to a reference to the current window (the window synonym self seems most grammatically fitting here). If the two values are not equal, you can script your document to reload itself as a top-level document. When it is critical that your document be a top-level document, include the script in Listing 27-1 in the head portion of your document: LISTING 27-1
Preventing a Document from Getting Framed if (top != self) { top.location = location; }
Your document may appear momentarily inside the other site’s frameset, but then the slate is wiped clean, and your top-level document rules the browser window.
Ensuring framing When you design a web application around a frameset, you may want to make sure that a page always loads the complete frameset. Consider the possibility that a visitor adds only one of your frames to a bookmarks list. On the next visit, only the bookmarked page appears in the browser, without your frameset, which may contain valuable navigation aids to the site. A script can make sure that a page always loads into its frameset by comparing the URLs of the top and self windows. If the URLs are the same, it means that the page needs to load the frameset. Listing 27-2 shows the simplest version of this technique, which loads a fixed frameset. For a more complete implementation that passes a parameter to the frameset so that it opens a specific page in one of the frames, see the location.search property in Chapter 28, ‘‘Location and History Objects.’’
743
Part IV: Document Objects Reference
LISTING 27-2
Forcing a Frameset to Load if (top.location.href == window.location.href) { top.location.href = " myFrameset.html"; }
Switching from frames to frameless Some sites load themselves in a frameset by default, and offer users the option of getting rid of the frames. Modern browsers let you modify a frameset’s cols or rows properties on the fly to simulate adding or removing frames from the current view (see the frameset element object later in this chapter). Legacy browsers, on the other hand, don’t allow you to change the makeup of a frameset dynamically after it has loaded, but you can load the content page of the frameset into the main window. The workaround for older browsers is to include a button or link whose action loads that document into the top window object: top.location.href = "mainBody.html";
A switch back to the frame version entails nothing more complicated than loading the framesetting document.
Inheritance versus containment Scripters who have experience in object-oriented programming environments probably expect frames to inherit properties, methods, functions, and variables, defined in a parent object. That’s not the case with scriptable browsers. You can, however, still access those parent items when you make a call to the item with a complete reference to the parent. For example, if you want to define a deferred function in the framesetting parent document that all frames can share, the scripts in the frames refer to that function with this reference: parent.myFunc()
You can pass arguments to such functions and expect returned values.
Frame synchronization A pesky problem for some scripters’ plans is that including immediate scripts in the framesetting document is dangerous. Such scripts tend to rely on the presence of documents in the frames being created by this framesetting document. But if the frames have not yet been created, and their documents have not yet loaded, the immediate scripts will likely crash and burn. One way to guard against this problem is to trigger all such scripts from the frameset’s onload event handler. In theory, this handler won’t trigger until all documents have successfully loaded into the child frames defined by the frameset. At the same time, be careful with onload event handlers in the
744
Chapter 27: Window and Frame Objects
documents that go into a frameset’s frames. If one of those scripts relies on the presence of a document in another frame (one of its brothers or sisters), you’re doomed to eventual failure. Anything coming from a slow network or server to a slow modem can get in the way of other documents loading into frames in the ideal order. One way to work around these problems is to create a Boolean variable in the parent document to act as a flag for the successful loading of subsidiary frames. When a document loads into a frame, its onload event handler can set that flag to true to indicate that the document has loaded. Any script that relies on a page being loaded should use an if construction to test the value of that flag before proceeding. It is best to construct the code so that the parent’s onload event handler triggers all the scripts that you want to run after loading. You should also test your pages thoroughly for any residual effects that may accrue if someone resizes a window or clicks Reload.
Blank frames Often, you may find it desirable to create a frame in a frameset, but not put any document in it until the user has interacted with various controls or other user interface elements in other frames. Most modern browsers have a somewhat empty document in one of their internal URLs (about:blank). However, this URL is not guaranteed to be available on all browsers. If you need a blank frame, let your framesetting document write a generic HTML document to the frame directly from the src attribute for the frame, as shown in the skeletal code in Listing 27-3. Loading an empty HTML document requires no additional transactions. LISTING 27-3
Creating a Blank Frame
Viewing frame source code Studying other scripters’ work is a major tool for learning JavaScript (or any programming language). With most scriptable browsers, you can easily view the source code for any frame, including those
745
Part IV: Document Objects Reference windowObject frames whose content is generated entirely, or in part, by JavaScript. Click the desired frame to activate it (a subtle border may appear just inside the frame on some browser versions, but don’t be alarmed if the border doesn’t appear). Then select Frame Source (or equivalent) from the View menu (or from the right-click submenu). You can also print or save a selected frame.
Frames versus frame element objects With the expansion of object models that expose every HTML element to scripting, a terminology conflict comes into play. Everything that you have read about frames thus far in the chapter refers to the original object model, where a frame is just another kind of window with a slightly different referencing approach. That still holds true, even in the latest browsers. But when the object model also exposes HTML elements, the notion of the frame element object is somewhat distinct from the frame object of the original model. The frame element object represents an object whose properties are dominated by the attributes you set inside the tag. This provides access to settings, such as the frame border and scrollability — the kinds of properties that are not exposed to the original frame object. References to the frame and frame element objects are also different. You’ve seen plenty of examples of how to reference an old-fashioned frame earlier in this chapter. But access to a frame element object is either via the element’s id attribute or through the child node relationship of the enclosing frameset element (you cannot use the parentNode property to back your way out of the current document to the frame element that encloses the document). The strategy we prefer is assigning an id attribute to tags and accessing the frame element object by way of the document object that lives in the parent (or top) of the frameset hierarchy. Therefore, to access the frameBorder property of a frame element object from a script living in any frame of a frameset, the syntax is parent.document.all.frame1ID.frameBorder
or (for IE5+/Moz/W3C) parent.document.getElementById("frame1ID").frameBorder
When the reference goes through the frame element object, you can still reach the document object in that frame via the element object’s contentWindow or contentDocument properties (see the frame element object later in this chapter).
window Object
746
Properties
Methods
Event Handlers
appCore
addEventListener()†
onabort††
clientInformation
alert()
onafterprint
clipboardData
attachEvent()†
onbeforeprint
closed
back()
onbeforeunload
Chapter 27: Window and Frame Objects windowObject Properties
Methods
Event Handlers
components[]
blur()†
onblur†
content
clearInterval()
onchange††
controllers[]
clearTimeout()
onclick††
crypto
close()
onclose††
defaultStatus
confirm()
onerror
dialogArguments
createPopup()
onfocus†
dialogHeight
detachEvent()†
onhelp
dialogLeft
dispatchEvent()†
onkeydown††
dialogTop
dump()
onkeypress††
dialogWidth
execScript()
onkeyup††
directories
find()
onload
document
fireEvent()†
onmousedown††
event
focus()†
onmousemove††
external
forward()
onmouseout††
frameElement
geckoActiveXObject()
onmouseover††
frames[]
getComputedStyle()
onmouseup††
fullScreen
getSelection()
onmove
history
home()
onreset††
innerHeight
moveBy()
onresize
innerWidth
moveTo()
onscroll
length
navigate()
onselect††
location
open()
onsubmit††
locationbar
openDialog()
onunload
menubar
print()
name
prompt()
navigator
removeEventListener()†
netscape
resizeBy()
offscreenBuffering
resizeTo()
opener
scroll()
outerHeight
scrollBy()
Event
747
Part IV: Document Objects Reference windowObject Properties
Methods
outerWidth
scrollByLines()
pageXOffset
scrollByPages()
pageYOffset
scrollTo()
parent
setActive()†
personalbar
setInterval()
pkcs11
setTimeout()
prompter
showHelp()
returnValue
showModalDialog()
screen
showModelessDialog()
screenLeft
sizeToContent()
screenTop
stop()
screenX screenY scrollbars scrollMaxX scrollMaxY scrollX scrollY self sidebar status statusbar toolbar top window † ††
See Chapter 26, ‘‘Generic HTML Element Objects.’’ To handle captured or bubbled events of other objects in IE4+ and W3C DOM browsers.
Syntax Creating a window: var windowObject = window.open([parameters]);
About this object The window object has the unique position of being at the top of the object hierarchy, encompassing even the almighty document object. This exalted position gives the window object a number of properties and behaviors unlike those of any other object. Chief among its unique characteristics is that because everything takes place in a window, you can usually omit the window object from object references. You’ve seen this behavior in previous chapters when we invoked document methods, such as document.write(). The complete reference is window.document.write(). But because the activity was taking place in the window that held the document running the script, that window was assumed to be part of the reference. For single-frame windows, this concept is simple enough to grasp. As previously stated, among the list of properties for the window object is one called self. This property is synonymous with the window object itself (which is why it shows up in hierarchy diagrams as an object). Having a property of an object that is the same name as the object may sound confusing, but this situation is not that uncommon in object-oriented environments. We discuss the reasons why you may want to use the self property as the window’s object reference in the self property description that follows. As indicated earlier in the syntax definition, you don’t always have to create a window object specifically in JavaScript code. Your browser usually opens a window after you start it up. That window is a valid window object, even if the window is blank. Therefore, after a user loads your page into the browser, the window object part of that document is automatically created for your script to access as it pleases. One conceptual trap to avoid is believing that a window object’s event handler or custom property assignments outlive the document whose scripts make the assignments. Except for some obvious physical properties of a window, each new document that loads into the window starts with a clean slate of window properties and event handlers. Your script’s control over an existing (already open) window’s user interface elements varies widely with the browser and browser version for which your application is intended. Before the version 4 browsers, the only change you could make to an open window was to the status line at the bottom of the browser window. Version 4 browsers added the ability to control such properties as the size, location, and (with signed scripts in Navigator and Mozilla) the presence of chrome elements (toolbars and scroll bars, for example) on the fly. Many of these properties can be changed beyond specific safe limits only if you cryptographically sign the scripts (see Chapter 49, ‘‘Security and Netscape Signed Scripts,’’ on the CD-ROM) and/or the user grants permission for your scripts to make those modifications. Window properties are far more flexible on all browsers when your scripts generate a new window (with the window.open() method): You can influence the size, toolbar, or other view options of a
749
Part IV: Document Objects Reference windowObject.appCore window. Recent browser versions provide even more options for new windows, including the position of the window and whether the window should display a title bar. Again, if an option can conceivably be used to deceive a user (for example, silently hiding one window that monitors activity in another window), signed scripts and/or user permission are necessary. The window object is also the level at which a script asks the browser to display any of three styles of dialog boxes (a plain alert dialog box, an OK/Cancel confirmation dialog box, or a prompt for user text entry). Although dialog boxes are extremely helpful for cobbling together debugging tools for your own use (see Chapter 48, ‘‘Debugging Scripts,’’ on the CD-ROM), they can be very disruptive to visitors who navigate through web sites. Because most JavaScript dialog boxes are modal (that is, you cannot do anything else in the browser until you dismiss the dialog box), use them sparingly, if at all. Remember that some users may create macros on their computers to visit sites unattended. Should such an automated visitor to your site encounter a modal dialog box, it is trapped on your page until a human intervenes. All dialog boxes generated by JavaScript identify themselves as being generated by JavaScript. This is primarily a security feature to prevent deceitful scripts from creating system- or application-style dialog boxes that convince visitors to enter private information. It should also discourage dialog box usage in web-page design. And that’s good, because dialog boxes tend to annoy users. With the exception of the IE- and Safari-specific modal, and IE-specific modeless, dialog boxes (see the window.showModalDialog() and window.showModeless() methods), JavaScript dialog boxes are not particularly flexible in letting you fill them with text or graphic elements beyond the basics. In fact, you can’t even change the text of the dialog-box buttons or add buttons. With Dynamic HTML (DHTML)-capable browsers, you can use positioned div or iframe elements to simulate dialog-box behavior in a cross-browser way. With respect to the W3C DOM, the window is outside the scope of the standard through DOM Level 2. The closest that the standard comes to acknowledging a window at all is the document.defaultView property, which evaluates to the window object in today’s browsers (predominantly Mozilla). But the formal DOM standard specifies no properties or methods for this view object.
Properties appCore components[] content controllers[] prompter sidebar Values: (See text)
Read-Only
Compatibility: WinIE-, MacIE-, NN6+, Moz+, Safari-, Opera-, ChromeNN6+/Mozilla provide scriptable access to numerous services that are part of the xpconnect package (xp stands for cross-platform), which is part of the larger NPAPI (Netscape Plugin Application Programming Interface). The xpconnect services allow scripts to work with COM objects and the mozilla.org XUL (XML-based User Interface Language) facilities — lengthy subjects that extend well beyond the scope of this book. You can begin to explore this subject within the context of Mozilla-based browsers and scripting at http://www.mozilla.org/scriptable/.
750
Chapter 27: Window and Frame Objects windowObject.clipboardData
clientInformation Value: navigator object
Read-Only
Compatibility: WinIE4+, MacIE4+, NN-, Moz-, Safari 1.2+, Opera-, Chrome+ In an effort to provide scriptable access to browser-level properties while avoiding reference to the Navigator browser brand, Microsoft created the clientInformation property. Its value is identical to that of the navigator object — an object name that is also available in IE. Although Safari 1.2 adopted usage of the clientInformation property, you should use the navigator object for cross-browser applications. (See Chapter 42, ‘‘The Navigator and Other Environment Objects,’’ on the CD-ROM.) Related Item: navigator object
clipboardData Value: Object
Read/Write
Compatibility: WinIE5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeUse the clipboardData object to transfer data for such actions as cutting, copying, and pasting under script control. The object contains data of one or more data types associated with a transfer operation. Use this property only when editing processes via the Edit menu (or keyboard equivalents) or the context menu controlled by script — typically in concert with edit-related event handlers. Working with the clipboardData object requires knowing about its three methods, shown in Table 27-1. Familiarity with the edit-related event handlers (before and after versions of cut, copy, and paste) is also helpful (see Chapter 26). TABLE 27-1
window.clipboardData Object Methods Method
Returns
Description
clearData([format])
Nothing
Removes data from the clipboard. If no format parameter is supplied, all data is cleared. Data formats can be one or more of the following strings: Text, URL, File, HTML, Image.
getData(format)
String
Retrieves data of the specified format from the clipboard. The format is one of the following strings: Text, URL, File, HTML, Image. The clipboard is not emptied when you get the data so that the data can be retrieved in several sequential operations.
setData(format, data) Boolean
Stores string data in the clipboard. The format is one of the following strings: Text, URL, File, HTML, Image. For nontext data formats, the data must be a string that specifies the path or URL to the content. Returns true if the transfer to the clipboard is successful.
You cannot use the clipboardData object to transfer data between pages that originate from different domains or arrive via different protocols (http versus https).
751
Part IV: Document Objects Reference windowObject.closed
Example See Listings 26-36 and 26-44 in Chapter 26, ‘‘Generic HTML Element Objects,’’ to see how the clipboardData object is used with a variety of edit-related event handlers. Related Items: event.dataTransfer property; onbeforecopy, onBeforeCut, onbeforepaste, oncopy, oncut, onpaste event handlers
closed Value: Boolean
Read-Only
Compatibility: WinIE4+, MacIE4+, NN3+, Moz+, Safari+, Opera+, Chrome+ When you create a subwindow with the window.open() method, you may need to access object properties from that subwindow, such as setting the value of a text field. Access to the subwindow is via the window object reference that is returned by the window.open() method, as in the following code fragment: var newWind = window.open("someURL.html","subWind"); ... newWind.document.entryForm.ZIP.value = "00000";
In this example, the newWind variable is not linked live to the window, but is only a reference to that window. If the user should close the window, the newWind variable still contains the reference to the now-missing window. Thus, any script reference to an object in that missing window will likely cause a script error. What you need to know before accessing items in a subwindow is whether the window is still open. The closed property returns true if the window object has been closed, either by script or by the user. Any time you have a script statement that can be triggered after the user has an opportunity to close the window, test for the closed property before executing that statement.
Example Listing 27-4 is a basic window-opening and window-closing example. The script begins by initializing a global variable, newWind, which is used to hold the object reference to the second window. This value needs to be global so that other functions can reference the window for tasks, such as closing. For this example, the new window contains some HTML code written dynamically to it, rather than loading an existing HTML file into it. Therefore, the URL parameter of the window.open() method is left as an empty string. Next comes a brief delay to allow Internet Explorer (especially versions 3 and 4) to catch up with opening the window, so that content can be written to it. The delay (using the setTimeout() method described later in this chapter) invokes the finishNewWindow() function, which uses the global newWind variable to reference the window for writing. The document.close() method closes writing to the document — a different kind of close from a window close. A separate function, closeWindow(), is responsible for closing the subwindow. As a final test, an if condition looks at two conditions: (1) whether the window object has ever been initialized with a value other than null (in case you click the window-closing button before ever having created the new window) and (2) whether the window’s closed property is null or false. If either condition is true, the close() method is sent to the second window.
752
Chapter 27: Window and Frame Objects windowObject.closed
Note This is a simple example, so the property assignment event-handling technique employed uses the more modern approach of binding events, using the addEventListener() (NN6+/Moz/W3C) or attachEvent() (IE5+) methods. This modern, cross-browser event-handling technique is explained in detail in Chapter 32, ‘‘Event Objects.’’ The event-handling technique employed throughout most of the code in this chapter and much of the book is a deliberate simplification to make the code more readable. It is generally better to use the more modern approach of binding events, as we do in this example.
LISTING 27-4
Checking Before Closing a Window HTML: jsb27-04.html window.closed Property window.closed Property
The new window might open behind this window.
JavaScript: jsb27-04.js // initialize when the page has loaded addEvent(window, "load", initialize); // global variables var oNewWinForm; var oOpenNewWin; var oCloseNewWin; // initialize global var for new window object // so it can be accessed by all functions on the page var newWind;
continued
753
Part IV: Document Objects Reference windowObject.closed LISTING 27-4
(continued)
function initialize () { // get IE4+ or W3C DOM reference for an ID if (document.getElementById) { oNewWinForm = document.getElementById("newWinForm"); oOpenNewWin = document.getElementById("openNewWin"); oCloseNewWin = document.getElementById("closeNewWin"); } else { oNewWinForm = document.newWinForm; oOpenNewWin = document.oNewWinForm.openNewWin; oCloseNewWin = document.oNewWinForm.closeNewWin; } addEvent(oOpenNewWin, ‘click’, newWindow); addEvent(oCloseNewWin, ‘click’, closeWindow); } // make the new window and put some stuff in it function newWindow() { newWind = window.open("","subwindow","height=200,width=200"); setTimeout("finishNewWindow()", 100); } function finishNewWindow() { var output = ""; output += "A Sub-window"; output += ""; newWind.document.write(output); newWind.document.close(); } // close subwindow function closeWindow() { if (newWind && !newWind.closed) { newWind.close(); } else { alert("The window is no longer open"); } }
754
Chapter 27: Window and Frame Objects windowObject.defaultStatus To complete the example of the window opening and closing, notice that the subwindow is given a button whose onclick event handler (bound in the initialization() function) closes the main window/tab. In some modern browsers, the user is presented with an alert asking to confirm the closure of the main browser window/tab. Other browsers simply ignore the request with, in some cases, a warning in the error console. Safari closes the main window/tab without any warning. Related Items: window.open(), window.close() methods
components (See appCore)
controllers (See appCore)
crypto pkcs11 Values: Object references
Read-Only
Compatibility: WinIE-, MacIE-, NN6+, Moz+, Safari-, Opera-, ChromeThe crypto and pkcs11 properties return references to browser objects that are relevant to internal public-key cryptography mechanisms. These subjects are beyond the scope of this book, but you can read more about Netscape’s efforts on this front at http://www.mozilla.org/projects/ security/.
defaultStatus Value: String
Read/Write
Compatibility: WinIE3+, MacIE3+, NN2+, Moz+, Safari+, Opera+, ChromeAfter a document is loaded into a window or frame, the status bar’s message field can display a string that is visible any time the mouse pointer is not atop an object that takes precedence over the status bar (such as a link object or an image map). The window.defaultStatus property is normally an empty string, but you can set this property at any time. Any setting of this property will be temporarily overridden when a user moves the mouse pointer on top of a link object (see window.status property for information about customizing this temporary status-bar message). Probably the most common time to set the window.defaultStatus property is when a document loads into a window. You can do this as an immediate script statement that executes from the head or body portion of the document or as part of a document’s onload event handler.
Example Unless you plan to change the default status-bar text while a user spends time at your web page, the best time to set the property is when the document loads. In Listing 27-5, notice that we also read this property to reset the status bar in an onmouseout event handler. Setting the status property to empty also resets the status bar to the defaultStatus setting. When testing, remember that even though modern browsers support the status property, some of them do not display scripted status-bar text associated with links, in order to prevent link spoofing.
755
Part IV: Document Objects Reference windowObject.dialogArguments LISTING 27-5
Setting the Default Status Message window.defaultStatus property window.defaultStatus = "Welcome to my Web site."; window.defaultStatus property
Microsoft
Mozilla
If you need to display single or double quotes in the status bar (as in both links in Listing 27-5), use escape sequences (\’ and \") as part of the strings being assigned to these properties. Related Item: window.status property
dialogArguments Value: Varies
Read-Only
Compatibility: WinIE4+, MacIE4+, NN-, Moz+, Safari+, Opera-, Chrome+ The dialogArguments property is available only in a window that is generated by the showModalDialog() or the IE-specific showModelessDialog() methods. Those methods allow a parameter to be passed to the dialog-box window, and the dialogArguments property lets the dialog box window’s scripts access that parameter value. The value can be in the form of a string, number, or JavaScript array (convenient for passing multiple values).
Example See Listing 27-36 for the window.showModalDialog() method, to see how arguments can be passed to a dialog box and retrieved via the dialogArguments property. Related Items: window.showModalDialog(), window.showModelessDialog() methods
756
Chapter 27: Window and Frame Objects windowObject.dialogTop
dialogHeight dialogWidth Value: String
Read/Write
Compatibility: WinIE4+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeScripts in a document located inside a modal or IE-specific modeless dialog box (generated by showModalDialog() or showModelessDialog()) can read or modify the height and width of the dialog-box window via the dialogHeight and dialogWidth properties. Scripts can access
these properties from the main window only for modeless dialog boxes, which remain visible while the user can control the main window contents. Values for these properties are strings and include the unit of measure, the pixel (px).
Example Dialog boxes sometimes provide a button or icon that reveals more details or more complex settings for advanced users. You can create a function that handles the toggle between two sizes. The following function assumes that the document in the dialog box has a button whose label also toggles between Show Details and Hide Details. The button’s onclick event handler invokes the function as toggleDetails(this): function toggleDetails(btn) { if (dialogHeight == "200px") { dialogHeight = "350px"; btn.value = "Hide Details"; } else { dialogHeight = "200px"; btn.value = "Show Details"; } }
In practice, you also have to toggle the display style sheet property of the extra material between none and block to make sure that the dialog box does not display scroll bars in the smaller dialog-box version. Related Items: window.dialogLeft, window.dialogTop properties
dialogLeft dialogTop Value: String
Read/Write
Compatibility: WinIE4+, MacIE4+, NN-, Moz-, Safari-, Opera-, ChromeScripts in a document located inside a modal or IE-specific modeless dialog box (generated by showModalDialog() or showModelessDialog()) can read or modify the left and top coordinates of the dialog-box window via the dialogLeft and dialogTop properties. Scripts can access these
757
Part IV: Document Objects Reference windowObject.directories properties from the main window only for modeless dialog boxes, which remain visible while the user can control the main window contents. Values for these properties are strings and include the unit of measure, the pixel (px). If you attempt to change these values so that any part of the dialog-box window would be outside the video monitor, the browser overrides the settings to keep the entire window visible.
Example Although usually not a good idea because of the potentially jarring effect on a user, you can reposition a dialog-box window that has been resized by script (or by the user if you let the dialog box be resizable). The following statements in a dialog-box window document’s script re-center the dialog-box window: dialogLeft = (screen.availWidth/2) - (parseInt(dialogWidth)/2) + "px"; dialogHeight = (screen.availHeight/2) - (parseInt(dialogHeight)/2) + "px";
Note that the parseInt() functions are used to read the numeric portion of the dialogWidth and dialogHeight properties so that the values can be used for arithmetic. Related Items: window.dialogHeight, window.dialogTopWidth properties
Compatibility: WinIE-, MacIE-, NN4+, Moz+, Safari-, Opera-, ChromeBeyond the rectangle of the content region of a window (where your documents appear), the Netscape browser window displays an amalgam of bars and other features known collectively as chrome. All browsers can elect to remove these chrome items when creating a new window (as part of the third parameter of the window.open() method), but until signed scripts were available in Navigator 4, these items could not be turned on and off in the main browser window, or in any existing window. Navigator 4 promoted these elements to first-class objects contained by the window object. Navigator 6 added one more feature, called the directories bar — a framelike device that can be opened or hidden from the left edge of the browser window. At the same time, however, NN6+/Mozilla browsers no longer permit hiding and showing the browser window’s scroll bars. Chrome objects have but one property: visible. Reading this Boolean value (possible without signed scripts) lets you inspect the visitor’s browser window for the elements currently engaged. Changing the visibility of these items on the fly alters the relationship between the inner and outer dimensions of the browser window. If you must carefully size a window to display content, you should adjust the chrome elements before sizing the window. But before you start changing chrome visibility before the eyes of your page visitors, weigh the decision carefully. Experienced users have fine-tuned the look of their browser windows to just the way they like them. If you mess with that look, you may anger your visitors. Fortunately, changes you make to a chrome element’s visibility are not stored to the user’s preferences. However, the changes you make survive an unloading of the
758
Chapter 27: Window and Frame Objects windowObject.directories page. If you change the settings, be sure that you first save the initial settings and restore them with an onunload event handler.
Tip The Macintosh menu bar is not part of the browser’s window chrome. Therefore, its visibility cannot be adjusted from a script.
Example In Listing 27-6, you can experiment with the look of a browser window with any of the chrome elements turned on or off. To run this script, you must either sign the scripts or turn on codebase principals (see Chapter 49, ‘‘Security and Netscape Signed Scripts,’’ on the CD-ROM). Java must also be enabled to use the signed script statements. As the page loads, it stores the current state of each chrome element. One button for each chrome element triggers the toggleBar() function. This function inverts the visible property for the chrome object passed as a parameter to the function. Finally, the Restore button returns the visibility properties to their original settings. Notice that the restore() function is also called by the onunload event handler for the document. LISTING 27-6
Chapter 27: Window and Frame Objects windowObject.external We list the document property here primarily for completeness. Each window object contains a single document object. The value of the document property is the document object, which is not a displayable value. Instead, you use the document property as you build references to properties and methods of the document and to other objects contained by the document, such as a form and its elements. To load a different document into a window, use the location object (see Chapter 28, ‘‘Location and History Objects’’). The document object is described in detail in Chapter 29, ‘‘Document and Body Objects.’’ Related Item: document object
event Event Value: Object
Read/Write
Compatibility: WinIE4+, MacIE4+, NN+, Moz+, Safari 1+, Opera+, Chrome+ IE4+ treats the event object as a property of the window object. The W3C DOM passes an instance of the Event object as an argument to event handler functions. The connection with the window object is relatively inconsequential because all action involving the event object occurs in event handler functions. The only difference is that the object can be treated as a more global object when one event handler function invokes another. Instead of having to pass the event object parameter to the next function, functions can access the event object directly (with or without the window. prefix in the reference). For complete details about the event object in all browsers, see Chapter 32, ‘‘Event Objects.’’ Related Item: event object
external Value: Object
Read-Only
Compatibility: WinIE4+, MacIE-, NN-, Moz+, Safari-, Opera-, ChromeThe external property is useful only when the browser window is a component in another application. The property provides a gateway between the current browser window and the application that acts as a host to the browser window component. With WinIE4+ acting as a component to the host operating system, the external property can be used to access several methods that influence behaviors outside the browser. Perhaps the three most useful methods to regular web-page scripters are AddDesktopComponent(), AddFavorite(), and NavigateAndFind(). The first two methods display the same kind of alert dialog box that users get after making these choices from the browser or desktop menus, so that you won’t be able to sneak your web site onto desktops or Favorites listings without the visitor’s approval. IE7 and Firefox2+ allow AddSearchProvider() for installing search plug-ins. As with the first two methods, an alert is displayed asking the user permission to install the search plug-in. You can find information about OpenSearch and the format for the XML file passed to the method at http://www.opensearch.org/Specifications/OpenSearch/1.1. Table 27-2 describes the parameters for these methods.
761
Part IV: Document Objects Reference windowObject.frameElement TABLE 27-2
Popular window.external Object Methods Method
Description
AddDesktopComponent("URL", Adds a web site or image to the Active Desktop (if turned "type"[, left, top, width, height]) on in the user’s copy of Windows). The type parameter value is either website or image. Dimensional parameters (optional) are all integer values. AddFavorite("URL"[, "title"])
Adds the specified URL to the user’s Favorites list. The optional title string parameter is how the URL should be listed in the menu (if missing, the URL appears in the list).
AddSearchProvider("URL")
Adds the search provider, specified in the URL with an OpenSearchDescription XML file.
NavigateAndFind("URL", "findString", "target")
Navigates to the URL in the first parameter and opens the page in the target frame (an empty string opens in the current frame). The findString is text to be searched for on that page and highlighted when the page loads.
Example The first example asks the user whether it is okay to add a web site to the Active Desktop. If Active Desktop is not enabled, the user is given the choice of enabling it at this point: external.AddDesktopComponent("http://www.nytimes.com","website", 200, 100, 400, 400);
In the next example, the user is asked to approve the addition of a URL to the Favorites list. The user can follow the normal procedure for filing the item in a folder in the list: external.AddFavorite("http://www.dannyg.com/support/update13.html", "JSBible 6 Support Center");
The final example assumes that a user makes a choice from a select list of items. The onchange event handler of the select list invokes the following function to navigate to a fictitious page and locate listings for a chosen sports team on the page: function locate(list) { var choice = list.options[list.selectedIndex].value; external.NavigateAndFind("http://www.collegesports.net/scores.html", choice, "scores"); }
Chapter 27: Window and Frame Objects windowObject.frames If the current window exists as a result of a or tag, the window’s frameElement property returns a reference to the hosting element. As is made clear in the discussion about the frame element object later in this chapter, a reference to a frame or iframe element object provides access to the properties that echo the attributes of the HTML element object. For a window that is not part of a frameset, the frameElement property returns null. The convenience of this property becomes apparent when a single document is loaded into multiple framesets. A script in the document can still refer to the containing frame element, even when the ID of the element changes from one frameset to another. The frameset element is also accessible via the parentElement property of the frameElement property: var frameSetObj = self.frameElement.parentElement;
A reference to the frameset element opens possibilities for adjusting frame sizes. Related Items: frame, iframe objects
frames Value: Array
Read-Only
Compatibility: WinIE3+, MacIE3+, NN2+, Moz+, Safari+, Opera+, Chrome+ In a multiframe window, the top or parent window contains any number of separate frames, each of which acts as a full-fledged window object. The frames property (note the plural use of the word as a property name) plays a role when a statement must reference an object located in a different frame. For example, if a button in one frame is scripted to load a document in another frame, the button’s event handler must be able to tell JavaScript precisely where to display the new HTML document. The frames property assists in that task. To use the frames property to communicate from one frame to another, it should be part of a reference that begins with the parent or top property. This lets JavaScript make the proper journey through the hierarchy of all currently loaded objects to reach the desired object. To find out how many frames are currently active in a window, use this expression: parent.frames.length
This expression returns a number indicating how many frames the parent window defines. This value does not, however, count further nested frames, should a third generation of frame be defined in the environment. In other words, no single property exists that you can use to determine the total number of frames in the browser window if multiple generations of frames are present. The browser stores information about all visible frames in a numbered (indexed) array, with the first frame (that is, the topmost tag defined in the framesetting document) as number 0: parent.frames[0]
Therefore, if the window shows three frames (whose indexes are frames[0], frames[1], and frames[2], respectively), the reference for retrieving the title property of the document in the second frame is parent.frames[1].document.title
This reference is a road map that starts at the parent window and extends to the second frame’s document and its title property. Other than the number of frames defined in a parent window and each
763
Part IV: Document Objects Reference windowObject.frames frame’s name (top.frames[i].name), no values from the frame definitions are directly available from the frame object via scripting until you get to IE4 and NN6/Moz/W3C (see the frame element object later in this chapter). In these browsers, individual frame element objects have several properties that reveal tag attributes. Using index values for frame references is not always the safest tactic, however, because your frameset design may change over time, in which case the index values will also change. Instead, you should take advantage of the name attribute of the tag, and assign a unique, descriptive name to each frame. A value you assign to the name attribute is also the name that you use for target attributes of links in order to force a linked page to load in a frame other than the one containing the link. You can use a frame’s name as an alternative to the indexed reference. For example, in Listing 27-7, two frames are assigned distinctive names. To access the title of a document in the JustAKid2 frame, the complete object reference is parent.JustAKid2.document.title
with the frame name (case sensitive) substituting for the frames[1] array reference. Or, in keeping with JavaScript flexibility, you can use the object name in the array index position: parent.frames["JustAKid2"].document.title
The supreme advantage to using frame names in references is that no matter how the frameset structure may change over time, a reference to a named frame will always find that frame, even though its index value (that is, its position in the frameset) may change.
Example Listing 27-7 and Listing 27-8 demonstrate how JavaScript treats values of frame references from objects inside a frame. The same document is loaded into each frame. A script in that document extracts information about the current frame and the entire frameset. LISTING 27-7
Framesetting Document for Listing 27-8 window.frames property
A call to determine the number (length) of frames returns 0, from the point of view of the current frame referenced. That’s because each frame here is a window that has no nested frames within it. But add the parent property to the reference, and the scope zooms out to take into account all frames generated by the parent window’s document.
764
Chapter 27: Window and Frame Objects windowObject.history LISTING 27-8
Showing Various Window Properties Window Revealer II function gatherWindowData() { var msg = ""; msg += "
From the point of view of this frame:"; msg += "window.frames.length: " + window.frames.length + ""; msg += "window.name: " + window.name + "
"; msg += "
From the point of view of the framesetting i document:"; msg += "parent.frames.length: " + parent.frames.length + ""; msg += "parent.frames[0].name: " + parent.frames[0].name + "
The last statement in the example shows how to use the array syntax (brackets) to refer to a specific frame. All array indexes start with 0 for the first entry. Because the document asks for the name of the first frame (parent.frames[0]), the response is JustAKid1 for both frames. Related Items: frame, frameset objects; window.parent, window.top properties
fullScreen Values: Boolean
Read-Only
Compatibility: WinIE-, MacIE-, NN7.1+, Moz1.4+, Safari-, Opera-, ChromeThe intent of the fullScreen property is to indicate whether the browser is in full-screen mode, which can be set in Mozilla browsers through the Full Screen command in the View menu. Unfortunately, the property isn’t reliable (as of Mozilla 1.8.1) and always returns false, regardless of the browser’s actual full-screen setting.
Part IV: Document Objects Reference windowObject.innerHeight (See the discussion of the history object in Chapter 28, ‘‘Location and History Objects.’’)
Compatibility: WinIE-, MacIE-, NN4+, Moz+, Safari+, Opera+, Chrome+ NN4+/Moz/WebKit- and Presto-based browers let scripts adjust the height and width of any window, including the main browser window, by setting properties. This adjustment can be helpful if your page shows itself best with the browser window sized to a particular height and width. Rather than relying on the user to size the browser window for optimum viewing of your page, you can dictate the size of the window (although the user can always resize the main window manually). And because you can examine the operating system of the visitor via the navigator object (see Chapter 42), you can size a window to adjust for the differences in font and form element rendering on different platforms. Supporting browsers provide two different points of reference for measuring the height and width of a window: inner and outer. Both are measured in pixels. The inner measurements are that of the active document area of a window (sometimes known as a window’s content region). If the optimum display of your document depends on the document display area being a certain number of pixels high and/or wide, the innerHeight and innerWidth properties are the ones to set. By contrast, the outer measurements reference the outside boundary of the entire window, including whatever chrome is showing in the window: scroll bars, status bar, and so on. Setting the outerHeight and outerWidth is generally done in concert with a reading of screen object properties (see Chapter 42). Perhaps the most common use of the outer properties is to set the browser window to fill the available screen area of the visitor’s monitor. A more efficient way of modifying both outer dimensions of a window is with the window. resizeTo() method, which is also available in IE4+. The method takes pixel width and height (as integer values) as parameters, thus accomplishing a window resizing in one statement. Be aware that resizing a window does not adjust the location of a window. Therefore, just because you set the outer dimensions of a window to the available space returned by the screen object, you can’t count on the window suddenly filling the available space on the monitor. Application of the window.moveTo() method is necessary to ensure that the top-left corner of the window is at screen coordinates 0,0. Despite the freedom that these properties afford the page author, Netscape and Mozilla-based browsers have built in a minimum size limitation for scripts that are not cryptographically signed. You cannot set these properties such that the outer height and width of the window is smaller than 100 pixels on a side. This limitation is to prevent an unsigned script from setting up a small or nearly invisible window that monitors activity in other windows. With signed scripts, however, windows can be made smaller than 100×100 pixels, with the user’s permission. IE4+ maintains a smaller minimum size to prevent resizing a window to zero size.
Caution Users may dislike your scripts messing with their browser window sizes and positions. NN7+/Moz/WebKit- and Presto-based browsers do not allow scripts to resize windows unless the script is signed.
766
Chapter 27: Window and Frame Objects windowObject.innerHeight
Example In Listing 27-9, several buttons let you see the results of setting the innerHeight, innerWidth, outerHeight, and outerWidth properties. Safari ignores scripted adjustments to these properties, whereas Mozilla users can set preferences that prevent scripts from moving and resizing windows.
Part IV: Document Objects Reference windowObject.location LISTING 27-9
(continued)
JavaScript: jsb27-09.js // store original outer dimensions as page loads var originalWidth = window.outerWidth; var originalHeight = window.outerHeight; alert("original dimensions: \nwindow.outerWidth=" + window.outerWidth + ". \nwindow.outerHeight =" + window.outerHeight + ". \nwindow.innerWidth = " + window.innerWidth + ". \nwindow.outerHeight = " + window.outerHeight); // generic function to set inner dimensions function setInner(width, height) { window.innerWidth = width; window.innerHeight = height; } // generic function to set outer dimensions function setOuter(width, height) { window.outerWidth = width; window.outerHeight = height; } // restore window to original dimensions function restore() { window.outerWidth = originalWidth; window.outerHeight = originalHeight; }
Related Items: window.resizeTo(), window.moveTo() methods; screen object; navigator object
location Value: Object
Read/Write
Compatibility: WinIE3+, MacIE3+, NN2+, Moz+, Safari+, Opera+, Chrome+ (See the discussion of the location object in Chapter 28, ‘‘Location and History Objects.’’)
locationbar (See directories)
768
Chapter 27: Window and Frame Objects windowObject.netscape
name Value: String
Read/Write
Compatibility: WinIE3+, MacIE3+, NN2+, Moz+, Safari+, Opera+, Chrome+ All window objects can have names assigned to them. Names are particularly useful for working with frames, because a good naming scheme for a multiframe environment can help you determine precisely which frame you’re working with in references coming from other frames. The main browser window, however, has no name attached to it by default. Its value is an empty string. There aren’t many reasons to assign a name to the window, because JavaScript and HTML provide plenty of other ways to refer to the window object (the top property, the _top constant for target attributes, and the opener property from subwindows). If you want to attach a name to the main window, you can do so by setting the window.name property at any time. But be aware that because this is one window property whose life extends beyond the loading and unloading of any given document, chances are that your scripts would use the reference in only one document or frameset. Unless you restore the default empty string, your programmed window name will be present for any other document that loads later. Our suggestion in this regard is to assign a name in a window’s or frameset’s onload event handler and then reset it to empty in a corresponding onunload event handler:
You can see an example of this application in Listing 27-15, where setting a parent window name is helpful for learning the relationships between parent and child windows. Related Items: top property; window.open(), window.sizeToContent() methods
navigator Value: Object
Read-Only
Compatibility: WinIE4+, MacIE4+, NN6+, Moz+, Safari+, Opera+, Chrome+ Although the navigator object appears as a property of the window object only in modern browsers, this object has been around since the very beginning (see Chapter 42). In previous browsers, the navigator object was referenced as a stand-alone object. And because you can omit any reference to the window object for a window object’s properties, you can use the same windowless reference syntax for compatibility across all scriptable browsers (at least for the navigator object properties that exist across all browsers). That’s the way we recommend referring to the navigator object.
Example This book is littered with examples of using the navigator object, primarily for performing browser detection. You can find examples of specific navigator object properties in Chapter 42. Related Item: navigator object
Part IV: Document Objects Reference windowObject.offscreenBuffering Given its name, you might think that the netscape property somehow works in tandem with the navigator property, but this is not the case. The netscape property is unique to NN/Moz browsers and provides access to functionality that is specific to the Netscape family of browsers, such as the privilege manager.
Example The netscape property is commonly used as a means of accessing the NN/Moz-specific PrivilegeManager object to enable or disable security privileges. Following is an example of how this access is carried out: netscape.security.PrivilegeManager.enablePrivilege("UniversalBrowserRead");
offscreenBuffering Value: Boolean or string
Read/Write
Compatibility: WinIE4+, MacIE4+, NN-, Moz-, Safari 1.2+, Opera-, Chrome+ IE4+/Safari 1.2+ by default initially render a page in a buffer (a chunk of memory) before it is blasted to the video screen. You can control this behavior explicitly by modifying the window.offscreenBuffering property. The default value of the property is the string auto. You can also assign Boolean true or false to the property to override the normal automatic handling of this behavior.
Example If you want to turn off buffering for an entire page, include the following statement at the beginning of your script statements: window.offscreenBuffering = false;
onerror Value: Function
Read/Write
Compatibility: WinIE4+, MacIE4+, NN3+, Moz+, Safari-, Opera-, ChromeThe onerror property is an exception to this book’s rule of not describing event handlers as properties within object reference sections. The reason is that the onerror event brings along some special properties that are useful to control by setting the event handler property in scripts. Modern browsers (IE5+, NN4+, and W3C) are designed to prevent script errors from being intrusive if a user encounters a script error while loading or interacting with a page. But even the subtle hints about problems (messages or icons in the status bar) can be confusing for users who have no idea what JavaScript is. JavaScript lets you turn off the display of script error windows or messages as someone executes a script on your page. The question is: When should you turn off these messages? Script errors generally mean that something is wrong with your script. The error may be the result of a coding mistake or, conceivably, a bug in JavaScript (perhaps on a platform version of the browser that you haven’t been able to test). If such errors occur, often the script won’t continue to do what you intended. Hiding the script error from yourself during development would be foolhardy, because you’d never know whether unseen errors are lurking in your code. It can be equally dangerous to turn off error dialog boxes for users who may believe that the page is operating normally, when in fact it’s not. Some data values may not be calculated or displayed correctly.
770
Chapter 27: Window and Frame Objects windowObject.onerror That said, we can see some limited instances of when you may want to keep such dialog-box windows from appearing. For example, if you know for a fact that a platform-specific bug trips the error message without harming the execution of the script, you may want to prevent that error alert dialog box from appearing in the files posted to your web site. You should do this only after extensive testing to ensure that the script ultimately behaves correctly, even with the bug or error.
Note IE fires the onerror event handler only for runtime errors. This means that if you have a syntactical error in your script that trips the browser as the page loads, the onerror event doesn’t fire, and you cannot trap that error message. Moreover, if the user has the IE script debugger installed, any code you use to prevent browser error messages from appearing will not work.
When the browser starts, the window.onerror property is . In this state, all errors are reported via the normal JavaScript error window or message. To turn off error alerts, set the window.onerror property to invoke a function that does absolutely nothing: function doNothing() { return true; } window.onerror = doNothing;
To restore the error messages, reload the page. You can, however, also assign a custom function to the window.onerror property. This function then handles errors in a more friendly way under your script control. Whenever error messages are turned on (the default behavior), a script error (or Java applet or class exception) invokes the function assigned to the onerror property, passing three parameters:
Error message
URL of the document causing the error
Line number of the error
You can essentially trap for all errors and handle them with your own interface (or no user notification at all). The last statement of this function must be return true if you do not want the JavaScript script error message to appear. If you are using the NPAPI to communicate with a Java applet directly from your scripts, you can use the same scheme to handle any exception that Java may throw. A Java exception is not necessarily a mistake kind of error: Some methods assume that the Java code will trap for exceptions to handle special cases — for example, reacting to a user’s denial of access when prompted by a signed script dialog box. See Chapter 47, ‘‘Scripting Java Applets and Plug-Ins’’ (on the CD-ROM), for an example of trapping for a specific Java exception. Also, see Chapter 21, ‘‘Control Stuctures and Exception Handling,’’ for JavaScript exception handling introduced for W3C DOM–compatible browsers.
Example In Listing 27-10, one button triggers a script that contains an error. We added an error-handling function to process the error so that it opens a separate window and fills in a textarea form element (see Figure 27-4). A Submit button is also provided to mail the bug information to a support center email address — an example of how to handle the occurrence of a bug in your scripts.
771
Part IV: Document Objects Reference windowObject.onerror FIGURE 27-4
An example of a self-reporting error window.
LISTING 27-10
Controlling Script Errors HTML: jsb27-10.html Error Dialog Control Error Dialog Control
JavaScript: jsb27-10.js // function with invalid variable value function goWrong() { var x = fred;
772
Chapter 27: Window and Frame Objects windowObject.onerror } // turn off error dialogs function errOff() { window.onerror = doNothing; } // turn on error dialogs with hard reload function errOn() { window.onerror = handleError; } // assign default error handler window.onerror = handleError; // error handler when errors are turned off...prevents error dialog function doNothing() { return true; } function handleError(msg, URL, lineNum) { var errWind = window.open("","errors","height=270,width=400"); var wintxt = ""; wintxt += "An error has occurred on this page. " + "Please report it to Tech Support."; wintxt += ""; wintxt += ""; wintxt += "Error: " + msg + "\n"; wintxt += "URL: " + URL + "\n"; wintxt += "Line: " + lineNum + "\n"; wintxt += "Client: " + navigator.userAgent + "\n"; wintxt += "-----------------------------------------\n"; wintxt += "Please describe what you were doing when the error occurred:"; wintxt += ""; wintxt += ""; wintxt += ""; wintxt += ""; errWind.document.write(wintxt); errWind.document.close(); return true; }
We provide a button that performs a hard reload, which in turn resets the window.onerror property to its default value. With error dialog boxes turned off, the error handling function does not run. Related Items: location.reload() method; JavaScript exception handling (Chapter 21, ‘‘Control Structures and Exception Handling’’ ); debugging scripts (Chapter 48, ‘‘Debugging Scripts,’’ on the CD-ROM)
773
Part IV: Document Objects Reference windowObject.opener
opener Value: Window object reference
Read/Write
Compatibility: WinIE3+, MacIE3+, NN3+, Moz+, Safari+, Opera+, Chrome+ Many scripters make the mistake of thinking that a new browser window created with the window.open() method has a child-parent relationship similar to the one that frames have with their parents. That’s not the case at all. New browser windows, when created, have a very slim link to the window from whence they came: via the opener property. The purpose of the opener property is to provide scripts in the new window with a valid reference back to the original window. For example, the original window may contain some variable values or general-purpose functions that a new window at this web site wants to use. The original window may also have form elements whose settings are of value to the new window, or that get set by user interaction in the new window. Because the value of the opener property is a reference to a genuine window object, you can begin references with the property name. Or, you may use the more complete window.opener or self.opener reference. But then the reference must include some object or property of that original window, such as a window method or a reference to something contained by that window’s document. If a subwindow opens yet another subwindow, the chain is still valid, albeit one step longer. The third window can reach the main window with a reference that begins opener.opener....
It’s a good idea for the third window to store in a global variable the value of opener.opener while the page loads. Then, if the user closes the second window, the variable can be used to start a reference to the main window. When a script that generates a new window is within a frame, the opener property of the subwindow points to that frame. Therefore, if the subwindow needs to communicate with the main window’s parent or another frame in the main window, you have to very carefully build a reference to that distant object. For example, if the subwindow needs to get the checked property of a checkbox in a sister frame of the one that created the subwindow, the reference is opener.parent.sisterFrameName.document.formName.checkboxName.checked
It is a long way to go, indeed, but building such a reference is always a case of mapping out the path from where the script is, to where the destination is, step by step.
Example To demonstrate the importance of the opener property, take a look at how a new window can define itself from settings in the main window (see Listing 27-11). The doNew() function generates a small subwindow and loads the file in Listing 27-12 into the window. Notice the initial conditional statements in doNew() that make sure that if the new window already exists, it comes to the front, by invoking the new window’s focus() method.
774
Chapter 27: Window and Frame Objects windowObject.opener LISTING 27-11
Contents of a Main Window Document That Generates a Second Window HTML: jsb27-11.html Master of all Windows Select a color for a new window: Red Yellow Blue This field will be filled from an entry in another window:
JavaScript: jsb27-11.js var myWind; function doNew() { if (!myWind || myWind.closed) { myWind = window.open("jsb27-12.html","subWindow","height=200, i width=350,resizable"); } else { // bring existing subwindow to the front myWind.focus(); } }
775
Part IV: Document Objects Reference windowObject.opener LISTING 27-12
References to the opener Property HTML: jsb27-12.html New Window on the Block document.write("")
Type text here for the main window:
JavaScript: jsb27-12.js function getColor() { // shorten the reference colorButtons = self.opener.document.forms[0].color; // see which radio button is checked for (var i = 0; i < colorButtons.length; i++) { if (colorButtons[i].checked) { return colorButtons[i].value; } } return "white"; }
776
Chapter 27: Window and Frame Objects windowObject.pageYOffset In the getColor() function, the multiple references to the radio-button array can be very long. To simplify the references, the getColor() function starts by assigning the radio-button array to a variable we arbitrarily call colorButtons. That shorthand now stands in for lengthy references as we loop through the radio buttons to determine which button is checked, and retrieve its value property. A button in the second window simply fetches the title of the opener window’s document. Even if another document loads in the main window in the meantime, the opener reference still points to the main window: Its document object, however, will change. Finally, the second window contains a text input object. Enter any text there that you like and then either tab or click out of the field. The onchange event handler updates the field in the opener’s document (provided that the document is still loaded). Related Items: window.open(), window.focus() methods
outerHeight outerWidth (See innerHeight and innerWidth, earlier in this chapter)
pageXOffset pageYOffset Value: Integer
Read-Only
Compatibility: WinIE-, MacIE-, NN4+, Moz+, Safari+, Opera+, Chrome+ The top-left corner of the content (inner) region of the browser window is an important geographical point for scrolling documents. When a document is scrolled all the way to the top and flush left in the window (or when a document is small enough to fill the browser window without displaying scroll bars), the document’s location is said to be 0,0, meaning zero pixels from the top and zero pixels from the left. If you were to scroll the document, some other coordinate point of the document would be under that top-left corner. That measure is called the page offset, and the pageXOffset and pageYOffset properties let you read the pixel value of the document at the inner window’s top-left corner: pageXOffset is the horizontal offset, and pageYOffset is the vertical offset. The value of these measures becomes clear if you design navigation buttons in your pages to carefully control paging of content being displayed in the window. For example, you might have a two-frame page in which one of the frames features navigation controls and the other displays the primary content. The navigation controls take the place of scroll bars, which, for aesthetic reasons, are turned off in the display frame. Scripts connected to the simulated scrolling buttons can determine the pageYOffset value of the document, and then use the window.scrollTo() method to position the document precisely to the next logical division in the document for viewing. IE has corresponding values as body object properties: body.scrollLeft and body.scrollTop (see Chapter 29). Related Items: window.innerHeight, window.innerWidth, body.scrollLeft, body.scrollTop properties; window.scrollBy(), window.scrollTo() methods
777
Part IV: Document Objects Reference windowObject.parent
parent Value: Window object reference
Read-Only
Compatibility: WinIE3+, MacIE3+, NN2+, Moz+, Safari+, Opera+,Chrome+ The parent property (and the top property, discussed later in this section) comes into play primarily when a document is to be displayed as part of a multiframe window. The HTML documents that users see in the frames of a multiframe browser window are distinct from the document that specifies the frameset for the entire window. That document, though still in the browser’s memory (and appearing as the URL in the location field of the browser), is not otherwise visible to the user (except in source view). If scripts in your visible documents need to reference objects or properties of the frameset window, you can reference those frameset window items with the parent property. (Do not, however, expand the reference by preceding it with the window object, as in window.parent.propertyName, because this causes problems in early browsers.) In a way, the parent property seems to violate the object hierarchy because, from a single frame’s document, the property points to a level seemingly higher in precedence. If you didn’t specify the parent property, or instead specified the self property from one of these framed documents, the object reference is to the frame only, rather than to the outermost framesetting window object. A nontraditional but perfectly legal way to use the parent object is as a means of storing temporary variables. Thus, you could set up a holding area for individual variable values, or even an array of data. Then these values can be shared among all documents loaded into the frames, even when documents change inside the frames. You have to be careful, however, when storing data in the parent on the fly (that is, in response to user action in the frames). In early browsers, variables can revert to their default values (the values set by the parent’s own script) if the user resizes the window. A child window can also call a function defined in the parent window. The reference for such a function is parent.functionName([parameters])
At first glance, it may seem as though the parent and top properties point to the same framesetting window object. In an environment consisting of one frameset window and its immediate children, that’s true. But if one of the child windows was itself another framesetting window, you wind up with three generations of windows. From the point of view of the youngest child (for example, a window defined by the second frameset), the parent property points to its immediate parent, whereas the top property points to the first framesetting window in this chain. On the other hand, a new window created via the window.open() method has no parent–child relationship to the original window. The new window’s top and parent point to that new window. You can read more about these relationships in the ‘‘Frames’’ section earlier in this chapter.
Example To demonstrate how various window object properties refer to window levels in a multiframe environment, use your browser to load the Listing 27-13 document. It in turn sets each of two equal-size frames to the same document: Listing 27-14. This document extracts the values of several window properties, plus the document.title properties of two different window references.
778
Chapter 27: Window and Frame Objects windowObject.parent LISTING 27-13
Framesetting Document for Listing 27-14 The Parent Property Example self.name = "Framesetter";
Part IV: Document Objects Reference windowObject.personalbar LISTING 27-14
(continued)
document.write(gatherWindowData());
In the two frames, the references to the window and self object names return the name assigned to the frame by the frameset definition (JustAKid1 for the left frame, JustAKid2 for the right frame). In other words, from each frame’s point of view, the window object is its own frame. References to self.document.title refer only to the document loaded into that window frame. But references to the top and parent windows (which are one and the same in this example) show that those object properties are shared between both frames. A couple of other fine points are worth highlighting. First, the name of the framesetting window is set as Listing 27-13 loads, rather than in response to an onload event handler in the tag. The reason for this is that the name must be set in time for the documents loading in the frames to get that value. If we had waited until the frameset’s onload event handler, the name wouldn’t be set until after the frame documents had loaded. Second, we restore the parent window’s name to an empty string when the framesetting document unloads. This is to prevent future pages from getting confused about the window name. Related Items: window.frames, window.self, window.top properties
personalbar (See directories)
returnValue Value: Any data type
Read/Write
Compatibility: WinIE4+, MacIE5+, NN-, Moz+, Safari+, Opera-, ChromeScripts use the returnValue property in a document that loads into the originally IE-specific modal dialog box. A modal dialog box is generated via the showModalDialog() method, which returns whatever data has been assigned to the returnValue property of the dialog-box window before it closes. This is possible because script processing in the main window freezes while the modal dialog box is visible. As the dialog box closes, a value can be returned to the main window’s script right where the modal dialog box was invoked, and the main window’s script resumes executing statements.
Example See Listing 27-36 for the showModalDialog() method, for an example of how to get data back from a dialog box. Related Item: showModalDialog() method
780
Chapter 27: Window and Frame Objects windowObject.screenTop
screen Value: screen object
Read-Only
Compatibility: WinIE4+, MacIE4+, NN6+, Moz+, Safari+, Opera+, Chrome+ Although the screen object appears as a property of the window object in modern browsers, the screen object is also available in NN4 (see Chapter 42), but as a stand-alone object. Because you can omit any reference to the window object for a window object’s properties, the same windowless reference syntax can be used for compatibility with legacy browsers that support the screen object.
Example See Chapter 42 for examples of using the screen object to determine the video-monitor characteristics of the computer running the browser. Related Item: screen object
screenLeft screenTop Value: Integer
Read-Only
Compatibility: WinIE5+, MacIE-, NN-, Moz-, Safari 1.2+, Opera+, Chrome+ WinIE5+ originally provided the screenLeft and screenTop properties of the window object to let you read the pixel position (relative to the top-left 0,0 coordinate of the video monitor) of what Microsoft calls the client area of the browser window. The client area excludes most window chrome, such as the title bar, address bar, and the window-sizing bar. Therefore, when the browser window is maximized (meaning that no sizing bars are exposed), the screenLeft property of the window is 0, whereas the screenTop property varies, depending on the combination of toolbars the user has elected to display. For nonmaximized windows, if the window has been positioned so that the top and/or left parts of the client area are out of view, their property values will be negative integers. These two properties are read-only. You can position the browser window via the window.moveTo() and window.moveBy() methods, but these methods position the top-left
corner of the entire browser window, not the client area. IE browsers through version 7 do not provide properties for the position of the entire browser window.
Example Use The Evaluator (Chapter 4, ‘‘JavaScript Essentials’’) to experiment with the screenLeft and screenTop properties. Start with the browser window maximized (if you are using Windows). Enter the following property name in the top text box: window.screenLeft
Click the Evaluate button to see the current setting. Unmaximize the window, and drag it around the screen. Each time you finish dragging, click the Evaluate button again to see the current value. Do the same for window.screenTop. Related Items: window.moveTo(), window.moveBy() methods
781
Part IV: Document Objects Reference windowObject.screenX
screenX screenY Value: Integer
Read/Write
Compatibility: WinIE-, MacIE-, NN6+, Moz+, Safari 1.2+, Opera+, Chrome+ NN6+/Moz/W3C provide the screenX and screenY properties to read the position of the outer boundary of the browser window relative to the top-left coordinates (0,0) of the video monitor. The browser window includes the 4-pixels-wide window-sizing bars that surround Win32 windows. Therefore, when the WinNN6+ browser window is maximized, the value for both screenX and screenY is -4. NN/Moz/W3C do not provide the equivalent measures of the browser window client area as found in the screenLeft and screenTop properties of IE5+. You can, however, find out whether various toolbars are visible in the browser window (see window.directories). Although you can assign a value to either property, current versions of supporting browsers do not adjust the window position in response, if the user has set the preference that prevents window movement and resizing. Moving and resizing windows by script is considered by many web surfers to be unacceptable behavior.
Example Use The Evaluator (Chapter 4, ‘‘JavaScript Essentials’’) to experiment with the screenX and screenY properties. Start with the browser window maximized (if you are using Windows). Enter the following property name in the top text box: window.screenY
Click the Evaluate button to see the current setting. Unmaximize the window, and drag it around the screen. Each time you finish dragging, click the Evaluate button again to see the current value. Do the same for window.screenY. Related Items: window.moveTo(), window.moveBy() methods
scrollbars (See directories)
scrollMaxX scrollMaxY Value: Integer
Read/Write
Compatibility: WinIE-, MacIE-, NN7.1+, Moz1.4+, Safari-, Opera-, ChromeThe NN7.1+/Moz1.4+ scrollMaxX and scrollMaxY properties let you determine the maximum horizontal and vertical scrolling extents of a window. Scrolling is possible only if the window displays scroll bars along the desired axis. Values are pixel integers. Related Items: scrollX, scrollY properties
Chapter 27: Window and Frame Objects windowObject.self The NN6+/Mozilla/Safari scrollX and scrollY properties let you determine the horizontal and vertical scrolling of a window. Scrolling is possible only if the window displays scroll bars along the desired axis. Values are pixel integers. Although the IE DOM does not provide similar properties for the window, the same information can be derived from the body.scrollLeft and body.scrollTop properties.
Example Use The Evaluator (Chapter 4, ‘‘JavaScript Essentials’’) to experiment with the scrollX and scrollY properties. Enter the following property in the top text box: window.scrollY
Now manually scroll the page down so that you can still see the Evaluate button. Click the button to see how far the window has scrolled along the y-axis. Related Items: body.scrollLeft, body.scrollTop properties
self Value: Window object reference
Read-Only
Compatibility: WinIE3+, MacIE3+, NN2+, Moz+, Safari+, Opera+, Chrome+ Just as the window object reference is optional, so is the self property when the object reference points to the same window as the one containing the reference. In what may seem to be an unusual construction, the self property represents the same object as the window. For instance, to obtain the title of the document in a single-frame window, you can use any of the following three constructions: window.document.title self.document.title document.title
Although self is a property of a window, you should not combine the references within a single-frame window script (for example, don’t begin a reference with window.self, which has been known to cause numerous scripting problems). Specifying the self property, though optional for single-frame windows, can help make an object reference crystal clear to someone reading your code (and to you, for that matter). Multiple-frame windows are where you need to pay particular attention to this property. JavaScript is pretty smart about references to a statement’s own window. Therefore, you can generally omit the self part of a reference to a same-window document element. But when you intend to display a document in a multiframe window, complete references (including the self prefix) to an object make it much easier on anyone who reads or debugs your code to track who is doing what to whom. You are free to retrieve the self property of any window. The value that comes back is a window object reference.
Example Listing 27-15 uses the same operations as Listing 27-5 but substitutes the self property for all window object references. The application of this reference is entirely optional, but it can be helpful for reading and debugging scripts if the HTML document is to appear in one frame of a multiframe window — especially if other JavaScript code in this document refers to documents
783
Part IV: Document Objects Reference windowObject.sidebar in other frames. The self reference helps anyone reading the code know precisely which frame was being addressed. When testing, remember that even though modern browsers support the status property, some of them do not display scripted status-bar text associated with links, in order to prevent link spoofing. LISTING 27-15
Using the self Property self Property self.defaultStatus = "Welcome to my Website."; self Property
Microsoft
Mozilla
Related Items: window.frames, window.parent, window.top properties
sidebar (See appCore)
status Value: String
Read/Write
Compatibility: WinIE3+, MacIE3+, NN2+, Moz+, Safari+, Opera+, ChromeAt the bottom of the browser window is a status bar. Part of that bar includes an area that normally discloses the document loading progress or the URL of a link that the mouse is pointing to at any given instant. You can control the temporary content of that field by assigning a text string to the window object’s status property. You should adjust the status property only in response to events that have a temporary effect, such as a link or image map area object’s onmouseover event handler. When the status property is set in this situation, it overrides any other setting in the status bar. If the user then moves the mouse pointer away from the object that changes the status bar, the bar returns to its default setting (which may be empty on some pages). To prevent link spoofing, however, not all modern browsers display scripted status-bar text associated with links.
784
Chapter 27: Window and Frame Objects windowObject.status Use this window property as a friendlier alternative to displaying the URL of a link as a user rolls the mouse around the page. For example, if you’d rather use the status bar to explain the nature of the destination of a link, put that text into the status bar in response to the onmouseover event handler. But be aware that experienced web surfers like to see URLs down there. Therefore, consider creating a hybrid message for the status bar that includes a friendly description followed by the URL in parentheses. In multiframe environments, you can set the window.status property without having to worry about referencing the individual frame.
Example In Listing 27-16, the status property is set in a handler embedded in the onmouseover attribute of two HTML link tags. Notice that the handler requires a return true statement (or any expression that evaluates to return true) as the last statement of the handler. This statement is required; otherwise, the status message will not display in all browsers. When testing, remember that even though modern browsers support the status property, some of them do not display scripted status-bar text associated with links, in order to prevent link spoofing. LISTING 27-16
Links with Custom Status-Bar Messages window.status Property window.status Property Home
Mozilla
As a safeguard against platform-specific anomalies that affect the behavior of onmouseover event handlers and the window.status property, you should also include an onmouseout event handler for links and client-side image map area objects. Such onmouseout event handlers should set the status property to an empty string. This setting ensures that the status-bar message returns to the defaultStatus setting when the pointer rolls away from these objects. If you want to write a generalizable function that handles all window status changes, you can do so, but word the onmouseover attribute carefully so that the event handler evaluates to return true. Listing 27-17 shows such
785
Part IV: Document Objects Reference windowObject.status an alternative. Again, when testing, remember that some modern browsers do not display scripted status-bar text associated with links, in order to prevent link spoofing. LISTING 27-17
Handling Status Message Changes Generalizable window.status Property function showStatus(msg) { window.status = msg; return true; } Generalizable window.status Property Home
Mozilla
Notice how the event handlers return the results of the showStatus() method to the event handler, allowing the entire handler to evaluate to return true. One final example of setting the status bar (shown in Listing 27-18) also demonstrates how to create a simple scrolling banner in the status bar. LISTING 27-18
msg = "Welcome to my world..."; delay = 150; timerId; maxCount = 0; currCount = 1;
function scrollMsg() { // set the number of times scrolling message is to run if (maxCount == 0) { maxCount = 3 * msg.length; } window.status = msg; // keep track of how many characters have scrolled currCount++; // shift first character of msg to end of msg msg = msg.substring (1, msg.length) + msg.substring (0, 1); // test whether we’ve reached maximum character count if (currCount >= maxCount) { timerID = 0; // zero out the timer window.status = ""; // clear the status bar return; // break out of function } else { // recursive call to this function timerId = setTimeout("scrollMsg()", delay); } }
Because the status bar is being set by a stand-alone function (rather than by an onmouseover event handler), you do not have to append a return true statement to set the status property. The scrollMsg() function uses more advanced JavaScript concepts, such as the window.setTimeout() method (covered later in this chapter) and string methods (covered in
787
Part IV: Document Objects Reference windowObject.statusbar Chapter 15, ‘‘The String Object’’). To speed the pace at which the words scroll across the status bar, reduce the value of delay. Many web surfers (including us) don’t care for these scrollers that run forever in the status bar. Rolling the mouse over links disturbs the banner display. Use scrolling bars sparingly or design them to run only a few times after the document loads.
Tip Setting the status property with onmouseover event handlers has had checkered results along various implementations in Navigator. A script that sets the status bar is always in competition against the browser itself, which uses the status bar to report loading progress. When a hot spot on a page is at the edge of a frame, many times the onmouseout event fails to fire, preventing the status bar from clearing itself. Be sure to torture-test any such implementations before declaring your page ready for public access.
Related Items: window.defaultStatus property; onmouseover, onmouseout event handlers; link object
statusbar toolbar (See locationbar)
top Value: Window object reference
Read-Only
Compatibility: WinIE3+, MacIE3+, NN2+, Moz+, Safari+, Opera+, Chrome+ The window object’s top property refers to the topmost window in a frameset object hierarchy. For a single-frame window, the reference is to the same object as the window itself (including the self and parent properties), so do not include window as part of the reference. In a multiframe window, the top window is the one that defines the first frameset (in case of nested framesets). Users don’t ever really see the top window in a multiframe environment, but the browser stores it as an object in its memory. The reason is that the top window has the road map to the other frames (in case one frame should need to reference an object in a different frame), and its child frames can call upon it. Such a reference looks like this: top.functionName([parameters])
For more about the distinction between the top and parent properties, see the in-depth discussion about scripting frames at the beginning of this chapter. See also the example of the parent property for listings that demonstrate the values of the top property. Related Items: window.frames, window.self, window.parent properties
Chapter 27: Window and Frame Objects windowObject.alert() Listing the window property as a separate property may be more confusing than helpful. The window property is the same object as the window object. You do not need to use a reference that begins with window.window. Although the window object is assumed for many references, you can use window as part of a reference to items in the same window or frame as the script statement that makes that reference. You should not, however, use window as a part of a reference involving items higher up in the hierarchy (top or parent).
Methods alert("message") Returns: Nothing Compatibility: WinIE3+, MacIE3+, NN2+, Moz+, Safari+, Opera+, Chrome+ An alert dialog box is a modal window that presents a message to the user with a single OK button to dismiss the dialog box. As long as the alert dialog box is showing, no other application or window can be made active. The user must dismiss the dialog box before proceeding with any more work in the browser. The single parameter to the alert() method can be a value of any data type, including representations of some unusual data types whose values you don’t normally work with in JavaScript (such as complete objects). This makes the alert dialog box a handy tool for debugging JavaScript scripts. Any time you want to monitor the value of an expression, use that expression as the parameter to a temporary alert() method in your code. The script proceeds to that point and then stops to show you the value. (See Chapter 48 for more tips on debugging scripts.) What is often disturbing to application designers is that all JavaScript-created modal dialog boxes (via the alert(), confirm(), and prompt() methods) identify themselves as being generated by JavaScript or the browser. The purpose of this identification is to act as a security precaution against unscrupulous scripters who might try to spoof system or browser alert dialog boxes, inviting a user to reveal passwords or other private information. These identifying words cannot be overwritten or eliminated by your scripts. You can simulate a modal dialog-box window in a cross-browser fashion with regular browser windows, but it is not as robust as a genuine modal window, which you can create in IE4+, and some of the other modern browsers, via the window.showModalDialog() method. Because the alert() method is of a global nature (that is, no particular frame in a multiframe environment derives any benefit from laying claim to the alert dialog box), a common practice is to omit all window object references from the statement that calls the method. Restrict the use of alert dialog boxes in your HTML documents and site designs. The modality of the windows is disruptive to the flow of a user’s navigation around your pages. Communicate with users via forms or by writing to separate document window frames. Of course, alert boxes can still be very handy as a quick debugging aid.
Example The parameter for the example in Listing 27-19 is a concatenated string. It joins two fixed strings and the value of the browser’s navigator.appName property. Loading this document causes the alert dialog box to appear, as shown in several configurations in Figure 27-5. The JavaScript Alert line cannot be deleted from the dialog box in earlier browsers, while the title bar can’t be changed in later browsers.
789
Part IV: Document Objects Reference windowObject.back() LISTING 27-19
Displaying an Alert Dialog Box window.alert() Method window.alert() Method alert("You are running the " + navigator.appName + " browser.");
FIGURE 27-5
Results of the alert() method in Listing 27-19 in Firefox and Internet Explorer.
Related Items: window.confirm(), window.prompt() methods
back() forward() Returns: Nothing Compatibility: WinIE+, MacIE-, NN4+, Moz+, Safari+, Opera+, Chrome+ The purpose of the window.back() and window.forward() methods that began in NN4 is to offer a scripted version of the global back and forward navigation buttons while allowing the history object to control navigation strictly within a particular window or frame — as it should. Even though IE now supports these window methods, they did not catch on (and the window object is out of the scope of the W3C DOM Level 2), so you are better off staying with the history object’s
790
Chapter 27: Window and Frame Objects windowObject.clearTimeout() methods for navigating browser history. For more information about version compatibility and about back and forward navigation, see the history object in Chapter 28. Related Items: history.back(), history.forward(), history.go() methods
clearInterval(intervalIDnumber) Returns: Nothing Compatibility: WinIE4+, MacIE4+, NN4+, Moz+, Safari+, Opera+, Chrome+ Use the window.clearInterval() method to turn off an interval loop action started with the window.setInterval() method. The parameter is the ID number returned by the setInterval() method. A common application for the JavaScript interval mechanism is animation of an object on a page. If you have multiple intervals running, each has its own ID value in memory. You can turn off any interval by its ID value. As soon as an interval loop stops, your script cannot resume that interval: It must start a new one, which generates a new ID value.
Example See Listing 27-33 and Listing 27-34 later in this chapter for an example of how setInterval() and clearInterval() are used together on a page. Related Items: window.setInterval(), window.setTimeout(), window.clearTimeout() methods
clearTimeout(timeoutIDnumber) Returns: Nothing Compatibility: WinIE3+, MacIE3+, NN2+, Moz+, Safari+, Opera+, Chrome+ Use the window.clearTimeout() method in concert with the window.setTimeout() method, as described later in this chapter, when you want your script to cancel a timer that is waiting to run its expression. The parameter for this method is the ID number that the window.setTimeout() method returns when the timer starts ticking. The clearTimeout() method cancels the specified timeout. A good practice is to check your code for instances where user action may negate the need for a running timer — and to stop that timer before it goes off.
Example The page in Listing 27-20 features one text box and two buttons. One button starts a countdown timer coded to last 1 minute (easily modifiable for other durations); the other button interrupts the timer at any time while it is running. When the minute is up, an alert dialog box lets you know. LISTING 27-20
A Countdown Timer HTML: jsb27-20.html
continued
791
Part IV: Document Objects Reference windowObject.clearTimeout() LISTING 27-20
(continued)
Count Down Timer
JavaScript: jsb27-20.js var running = false; var endTime = null; var timerID = null; function startTimer() { running = true; now = new Date(); now = now.getTime(); // change last multiple for the number of minutes endTime = now + (1000 * 60 * 1); showCountDown(); } function showCountDown() { var now = new Date(); now = now.getTime(); if (endTime - now 0) { scrollJump = -scrollJump; } parent.display.scrollBy(0, scrollJump); if (parent.display.pageYOffset 12) ? theHour - 12 : theHour); theTime += ((theMin < 10) ? ":0" : ":") + theMin; theTime += (theHour >= 12) ? " pm" : " am"; theTime += ((flasher) ? " " : "*"); flasher = !flasher; window.status = theTime; // recursively call this function every second to keep timer going timerID = setTimeout("updateTime()",1000); } Status Bar Clock
In this function, the setTimeout() method works in the following way: When the current time (including the flasher status) appears in the status bar, the function waits approximately 1 second
831
Part IV: Document Objects Reference windowObject.showHelp() (1,000 milliseconds) before calling the same function again. You don’t have to clear the timerID value in this application because JavaScript does it for you every time the 1,000 milliseconds elapse. A logical question to ask is whether this application should be using setInterval() instead of setTimeout(). This is a case in which either one does the job. Using setInterval() here would require that the interval process start outside the updateTime() function, because you need only one process running that repeatedly calls updateTime(). It would be a cleaner implementation instead of the numerous timeout processes spawned by Listing 27-35. On the other hand, the application would not run in legacy browsers, as Listing 27-35 does. That’s likely not a problem at this point in time, but this application remains a decent example of the setTimeout() function. To demonstrate passing parameters, you can modify the updateTime() function to add the number of times it gets invoked to the display in the status bar. For that to work, the function must have a parameter variable so that it can catch a new value each time it is invoked by setTimeout()’s expression. For all browsers, the function would be modified as follows (unchanged lines are represented by the ellipsis): function updateTime(i) { //... window.status = theTime + " (" + i + ")"; // pass updated counter value with next call to this function timerID = setTimeout("updateTime(" + i+1 + ")",1000); }
If you were running this exclusively in NN4+/Moz, you could use its more convenient way of passing parameters to the function: timerID = setTimeout(updateTime, 1000, i+1);
In either case, the onload event handler would also have to be modified to get the ball rolling with an initial parameter: onload = "updateTime(0)";
Related Items: window.clearTimeout(), window.setInterval(), window.clearInterval() methods
showHelp("URL",["contextID"]) Returns: Nothing Compatibility: WinIE4+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe IE-specific showHelp() method lets a script open a Winhelp window with a particular .hlp file. This method is specific to Win32 operating systems. If your Winhelp file has context identifiers specified in various places, you can pass the ID as an optional second parameter. This lets the call to showHelp() navigate to the particular area of the .hlp file that applies to a specific element on the page. See the Microsoft Visual Studio authoring environment for details on building Winhelp files.
832
Chapter 27: Window and Frame Objects windowObject.showModalDialog()
showModalDialog("URL"[, arguments][, features]) showModelessDialog("URL"[, arguments][, features]) Returns: returnValue (modal) or window object (modeless) Compatibility: WinIE4+, MacIE4+, NN-, Moz+, Safari 2.01+, Opera-, Chrome+ IE, Safari, Chrome, and Mozilla-based browsers such as Firefox, provide methods for opening a modal dialog-box window, which always stays in front of the main browser window, while making the main window inaccessible to the user. In WinIE5, Microsoft added the modeless type of dialog box, which is not supported by Safari, Chrome and Mozilla-based browsers such as Firefox. The modeless type of dialog box also stays in front but allows user access to whatever can be seen in the main window. You can load any HTML page or image that you like into the dialog-box window by providing a URL as the first parameter. Optional parameters let you pass data to a dialog box and give you considerable control over the look of the window. A similar type of dialog-box window is available in NN/Moz via the window.openDialog() method. The windows generated by both methods are (almost) full-fledged window objects, with some extra properties that are useful for what these windows are intended to do. Perhaps the most important property is the window.dialogArgument property. This property lets a script read the data that is passed to the window via the second parameter of both showModalDialog() and showModelessDialog(). Passed data can be in any valid JavaScript data type, including objects and arrays. Displaying a modal dialog box has some ramifications for scripts. In particular, script execution in the main window halts at the statement that invokes the showModalDialog() method as long as the modal dialog box remains visible. Scripts are free to run in the dialog-box window during this time. The instant the user closes the dialog box, execution resumes in the main window. A call to show a modeless dialog box, on the other hand, does not halt processing because scripts in the main page or dialog-box window are allowed to communicate live with the other window.
Retrieving dialog-box data To send data back to the main window’s script from a modal dialog-box window, a script in the dialog-box window can set the window.returnValue property to any JavaScript value. It is this value that gets assigned to the variable receiving the returned value from the setModelDialog() method, as shown in the following example: var specifications = window.showModalDialog("preferences.html");
The makeup and content of the returned data are in the hands of your scripts. No data is automatically returned for you. Because a modeless dialog box coexists with your live main page window, returning data is not as straightforward as for a modal dialog box. The second parameter of the showModelessDialog() method takes on a special task that isn’t exactly the same as passing parameters to the dialog box. Instead, if you define a global variable or a function in the main window’s script, pass a reference to that variable or function as the second parameter to display the modeless dialog box. A script in the modeless dialog box can then point to that reference as the way to send data back to the main window before the dialog box closes (or when a user clicks something, such as an Apply button). This
833
Part IV: Document Objects Reference windowObject.showModalDialog() mechanism even allows for passing data back to a function in the main window. For example, say that the main window has a function defined as the following: function receivePrefsDialogData(a, b, c) { // statements to process incoming values // }
Then pass a reference to this function when opening the window: dlog = showModelessDialog("prefs.html", receivePrefsDialogData);
A script statement in the dialog-box window’s document can pick up that reference so that other statements, such as a function for an Apply button’s onclick event handler, can use it: var returnFunc = window.dialogArguments; //... function apply(form) { returnFunc(form.color.value, form.style.value, form.size.value); }
Although this approach seems to block ways of getting parameters to the dialog box when it opens, you can always reference the dialog box in the main window’s script and set form or variable values directly: dlog = showModelessDialog("prefs.html", receivePrefsDialogData); dlog.document.forms[0].userName.value = GetCookie("userName");
Be aware that a dialog-box window opened with either of these methods does not maintain a connection to the originating window via the opener property. The opener property for both dialog-box types is undefined.
Dialog-box window features Both methods provide an optional third property that lets you specify visible features of the dialog-box window. Omitting the property sets all features to their default values. All parameters are to be contained by a single string, and each parameter’s name–value pair is in the form of CSS attribute:value syntax. Table 27-5 lists all the window features available for the two window styles. If you are designing for backward compatibility with IE4, you are restricted to the modal dialog box and a subset of features, as noted in the table. All values listed as Boolean take only the following four values: yes, no, 1, and 0. The CSS-type of syntax for these features lets you thread multiple features together by separating each pair with a semicolon within the string. For example: var dlogData = showModalDialog("prefs.html", defaultData, "dialogHeight:300px; dialogWidth:460px; help:no");
Although they are not explicitly listed among the window features, scroll bars are normally displayed in the window if the content exceeds the size assigned or available to the dialog box. If you don’t want scroll bars to appear, have your dialog-box document’s script set the document.body.scroll property to false as the page opens.
834
Chapter 27: Window and Frame Objects windowObject.showModalDialog() TABLE 27-5
IE Dialog-Box Window Features Feature
Type
Default
Description
center
Boolean
yes
Whether to center dialog box (overridden by dialogLeft and/or dialogTop).
dialogHeight
Length
Varies
Outer height of the dialog-box window. IE4 default length unit is em; IE5+/Moz/Safari/Chrome is pixel (px).
dialogLeft
Integer
Varies
Pixel offset of dialog box from left edge of screen.
dialogTop
Integer
Varies
Pixel offset of dialog box from top edge of screen.
dialogWidth
Length
Varies
Outer width of the dialog-box window. IE4 default length unit is em; IE5+/Moz/Safari/Chrome is pixel (px).
edge
String
raised | sunken
Border style (IE only).
resizable
Boolean
no
Dialog box is resizable.
scroll
Boolean
yes
Display scrollbars
status
Boolean
Varies
Display status bar at window bottom (IE5+/Safari/Chrome only). Default is yes for untrusted dialog box, no for trusted dialog box.
Dialog-box cautions A potential user problem to watch for is that typically, a dialog-box window does not open until the HTML file for the dialog box has loaded. Therefore, if there is substantial delay before a complex document loads, the user does not see any action indicating that something is happening. You may want to experiment with setting the cursor style sheet property and restoring it when the dialog box’s document loads.
Example To demonstrate the two styles of dialog boxes, we have implemented the same functionality (setting some session visual preferences) for both modal and modeless dialog boxes. This tactic shows you how to pass data back and forth between the main page and both styles of dialog-box windows. The first example demonstrates how to use a modal dialog box. In the process, data is passed into the dialog-box window, and values are returned. Listing 27-36 is the HTML and scripting for the main page. A button’s onclick event handler invokes a function that opens the modal dialog box. The dialog box’s document (see Listing 27-37) contains several form elements for entering a user name and selecting a few color styles for the main page. Data from the dialog box is fashioned into an array to be sent back to the main window. That array is initially assigned to a local variable, prefs, as the dialog box closes. If the user cancels the dialog box, the returned value is an empty string, so nothing more in getPrefsData() executes. But when
835
Part IV: Document Objects Reference windowObject.showModalDialog() the user clicks OK, the array comes back. Each of the array items is read and assigned to its respective form value or style property. These values are also preserved in the global currPrefs array. This allows the settings to be sent to the modal dialog box (as the second parameter to showModalDialog()) the next time the dialog box is opened.
LISTING 27-36
Main Page for showModalDialog() HTML: jsb27-36.html window.setModalDialog() Method window.setModalDialog() Method Welcome, .!
Use this button to set style preferences for this page: Preferences
JavaScript: jsb27-36.js var currPrefs = new Array(); var nameHolder; function getPrefsData() { var prefs = showModalDialog("jsb27-37.html", currPrefs, "dialogWidth:400px; dialogHeight:300px;"); if (prefs) { if (prefs["name"]) { if (nameHolder.textContent == "friend") { nameHolder.textContent = prefs["name"]; } else { //IE nameHolder.innerText = prefs["name"]; } currPrefs["name"] = prefs["name"]; }
The dialog box’s document, shown in Listing 27-37, is responsible for reading the incoming data (and setting the form elements accordingly) and assembling form data for return to the main window’s script. Notice when you load the example that the title element of the dialog box’s document appears in the dialog-box window’s title bar. When the page loads into the dialog-box window, the init() function examines the window.dialogArguments property. If it has any data, the data is used to preset the form elements to mirror the current settings of the main page. A utility function, setSelected(), preselects the option of a select element to match the current settings. Buttons at the bottom of the page are explicitly positioned to be at the bottom-right corner of the window. Each button invokes a function to do what is needed to close the dialog box. In the case of the OK button, the handleOK() function sets the window.returnValue property to the data
837
Part IV: Document Objects Reference windowObject.showModalDialog() that comes back from the getFormData() function. This latter function reads the form element values and packages them in an array using the form elements’ names as array indices. This helps keep everything straight back in the main window’s script, which uses the index names, and therefore is not dependent upon the precise sequence of the form elements in the dialog-box window. LISTING 27-37
Document for the Modal Dialog Box HTML: jsb27-37.html User Preferences Web Site Preferences
Enter your first name:
Select a background color: Beige Antique White Goldenrod Lime Powder Blue Slate Gray
Select a text color: Black White Navy Blue Dark Orange Sea Green Teal
JavaScript: jsb27-37.js // Close the dialog function closeme() { window.close(); } // Handle click of OK button function handleOK() { window.returnValue = getFormData(); closeme(); } // Handle click of Cancel button function handleCancel() { window.returnValue = ""; closeme(); } // Generic function converts form element name-value pairs // into an array function getFormData() { var form = document.prefs; var returnedData = new Array(); // Harvest values for each type of form element for (var i = 0; i < form.elements.length; i++)
continued
839
Part IV: Document Objects Reference windowObject.showModalDialog() LISTING 27-37
(continued)
{ if (form.elements[i].type == "text") { returnedData[form.elements[i].name] = form.elements[i].value; } else if (form.elements[i].type.indexOf("select") != -1) { returnedData[form.elements[i].name] = form.elements[i].options[form.elements[i].selectedIndex].value; } else if (form.elements[i].type == "radio") { returnedData[form.elements[i].name] = form.elements[i].value; } else if (form.elements[i].type == "checkbox") { returnedData[form.elements[i].name] = form.elements[i].value; } else { continue; } } return returnedData; } // Initialize by setting form elements from passed data function init() { if (window.dialogArguments) { var args = window.dialogArguments; var form = document.prefs; if (args["name"]) { form.name.value = args["name"]; } if (args["bgColor"]) { setSelected(form.bgColor, args["bgColor"]); } if (args["textColor"]) { setSelected(form.textColor, args["textColor"]); } if (args["h1Size"]) { setSelected(form.h1Size, args["h1Size"]); }
840
Chapter 27: Window and Frame Objects windowObject.showModalDialog() } } // Utility function to set a SELECT element to one value function setSelected(select, value) { for (var i = 0; i < select.options.length; i++) { if (select.options[i].value == value) { select.selectedIndex = i; break; } } return; } // Utility function to accept a press of the // Enter key in the text field as a click of OK function checkEnter() { if (window.event.keyCode == 13) { handleOK(); } }
One last convenience feature of the dialog-box window is the onkeypress event handler in the text box. The function it invokes looks for the Enter key. If that key is pressed while the box has focus, the same handleOK() function is invoked, as though the user had clicked the OK button. This feature makes the dialog box behave as though the OK button is an automatic default, just as in real dialog boxes. You should observe several important structural changes that were made to turn the modal approach into a modeless one. Listing 27-38 shows a version of the main window modified for use with a modeless dialog box. Another global variable, prefsDlog, is initialized to eventually store the reference to the modeless window returned by the showModelessWindow() method. The variable gets used to invoke the init() function inside the modeless dialog box, but also as a condition in an if construction surrounding the generation of the dialog box. The reason this is needed is to prevent multiple instances of the dialog box from being created (the button is still alive while the modeless window is showing). The dialog box won’t be created again as long as there is a value in prefsDlog and the dialog-box window has not been closed (picking up the window.closed property of the dialog-box window). The showModelessDialog() method’s second parameter is a reference to the function in the main window that updates the main document. As you see in a moment, that function is invoked from the dialog box when the user clicks the OK or Apply button.
841
Part IV: Document Objects Reference windowObject.showModelessDialog() LISTING 27-38
Main Page for showModelessDialog() HTML: jsb27-38.html window.setModelessDialog() Method window.setModelessDialog() Method Welcome, !
Use this button to set style preferences for this page: Preferences
JavaScript: jsb27-38.js var currPrefs = new Array(); var prefsDlog; function getPrefsData() { if (!prefsDlog || prefsDlog.closed) { prefsDlog = showModelessDialog("jsb27-39.html", setPrefs, "dialogWidth:400px; dialogHeight:300px"); prefsDlog.init(currPrefs); } } function setPrefs(prefs) { if (prefs["bgColor"]) { document.body.style.backgroundColor = prefs["bgColor"]; currPrefs["bgColor"] = prefs["bgColor"]; } if (prefs["textColor"]) { document.body.style.color = prefs["textColor"]; currPrefs["textColor"] = prefs["textColor"]; } if (prefs["h1Size"])
Changes to the dialog-box window document for a modeless version (see Listing 27-39) are rather limited. A new button is added to the bottom of the screen for an Apply button. As in many dialog-box windows you see in Microsoft products, the Apply button lets current settings in dialog boxes be applied to the current document, but without closing the dialog box. This approach makes experimenting with settings easier. The Apply button invokes a handleApply() function, which works the same as handleOK(), except that the dialog box is not closed. But these two functions communicate back to the main window differently from a modal dialog box. The main window’s processing function is passed as the second parameter of showModelessDialog() and is available as the window.dialogArguments property in the dialog-box window’s script. That function reference is assigned to a local variable in both functions, and the remote function is invoked, passing the results of the getFormData() function as parameter values back to the main window. LISTING 27-39
Document for the Modeless Dialog Box HTML: jsb27-39.html User Preferences Web Site Preferences
Enter your first name:
continued
843
Part IV: Document Objects Reference windowObject.showModelessDialog() LISTING 27-39
(continued)
Select a background color: Beige Antique White Goldenrod Lime Powder Blue Slate Gray
Select a text color: Black White Navy Blue Dark Orange Sea Green Teal
Select "Welcome" heading font point size: 12 14 18 24 32 48
OK Cancel Apply
JavaScript: jsb27-39.js // Close the dialog function closeme() { window.close(); } // Handle click of OK button function handleOK() { var returnFunc = window.dialogArguments; returnFunc(getFormData()); closeme(); } // Handle click of Apply button function handleApply() { var returnFunc = window.dialogArguments; returnFunc(getFormData()); } // Handle click of Cancel button function handleCancel() { window.returnValue = ""; closeme(); } // Generic function converts form element name-value pairs // into an array function getFormData() { var form = document.prefs; var returnedData = new Array(); // Harvest values for each type of form element for (var i = 0; i < form.elements.length; i++) { if (form.elements[i].type == "text") { returnedData[form.elements[i].name] = form.elements[i].value; } else if (form.elements[i].type.indexOf("select") != -1) { returnedData[form.elements[i].name] = form.elements[i].options[form.elements[i].selectedIndex].value;
continued
845
Part IV: Document Objects Reference windowObject.showModelessDialog() LISTING 27-39
(continued)
} else if (form.elements[i].type == "radio") { returnedData[form.elements[i].name] = form.elements[i].value; } else if (form.elements[i].type == "checkbox") { returnedData[form.elements[i].name] = form.elements[i].value; } else { continue; } } return returnedData; } // Initialize by setting form elements from passed data function init(currPrefs) { if (currPrefs) { var form = document.prefs; if (currPrefs["name"]) { form.name.value = currPrefs["name"]; } if (currPrefs["bgColor"]) { setSelected(form.bgColor, currPrefs["bgColor"]); } if (currPrefs["textColor"]) { setSelected(form.textColor, currPrefs["textColor"]); } if (currPrefs["h1Size"]) { setSelected(form.h1Size, currPrefs["h1Size"]); } } } // Utility function to set a SELECT element to one value function setSelected(select, value) { for (var i = 0; i < select.options.length; i++) { if (select.options[i].value == value) { select.selectedIndex = i;
846
Chapter 27: Window and Frame Objects windowObject.sizeToContent() break; } } return; } // Utility function to accept a press of the // Enter key in the text field as a click of OK function checkEnter() { if (window.event.keyCode == 13) { handleOK(); } }
The biggest design challenge you probably face with respect to these windows is deciding between a modal and modeless dialog-box style. Some designers insist that modality has no place in a graphical user interface; others say that there are times when you need to focus the user on a very specific task before any further processing can take place. That’s where a modal dialog box makes perfect sense. Related Item: window.open() method
sizeToContent() Returns: Nothing Compatibility: WinIE-, MacIE-, NN6+, Moz+, Safari-, Opera-, ChromeThe NN6+/Moz window.sizeToContent() method can be a valuable aid in making sure that a window (especially a subwindow) is sized for the optimum display of the window’s content. But you must be cautious with this method, or it will do more harm than good. Invoking the sizeToContent() method resizes the window so that all content is visible. Concerns about variations in OS-specific rendering become a thing of the past. Naturally, you should perform this action only on a window whose content occupies, at the most, a space smaller than the smallest video monitor running your code (typically 640×480 pixels, but conceivably much smaller for future versions of the browser used on handheld computers). You can get the user in trouble, however, if you invoke the method twice on the same window that contains the resizing script. This action can cause the window to expand to a size that may exceed the pixel size of the user’s video monitor. Successive invocations fail to cinch up the window’s size to fit its content again. Multiple invocations are safe, however, on subwindows when the resizing script statement is in the main window.
Example Use The Evaluator (Chapter 4, ‘‘JavaScript Essentials’’) in NN6+/Moz to try the sizeToContent() method. Assuming that you are running The Evaluator from the Chap13 directory on the CD-ROM (or the directory copied as is to your hard disk), you can open a subwindow with one of the other files in the directory and then size the subwindow. Enter the following statement in the top text box: a = window.open("jsb13-02.html","")
847
Part IV: Document Objects Reference windowObject.stop() You might, depending on where you installed the CD-ROM, have to alter the path in the above statement to something like this: a = window.open("../../Chap13/lst13-02.htm","")
The file will open, depending on the browser version and your browser configuration settings, in either a new tab or a new subwindow. Enter the following statement in the top text box: a.sizeToContent()
The resized window (if a new tab was opened) or subwindow is at the minimum recommended width for a browser window and at a height tall enough to display the little bit of content in the document. As with any method that changes the size of the browser window, problems arise in browsers such as Firefox 2 that support tabbed browsing where multiple pages are opened as different tabs within the same browser instance. In a tabbed browser, it is impossible to resize the window of one page without altering all others. It’s certainly still possible to open multiple browser instances to resolve this problem, but the default response to window.open() is to open a new tab, not a new browser window. Related Item: window.resizeTo() method
stop() Returns: Nothing Compatibility: WinIE-, MacIE-, NN4+, Moz+, Safari+, Opera+, ChromeThe NN/Moz original stop() method offers a scripted equivalent of clicking the Stop button in the toolbar. The availability of this method allows you to create your own toolbar on your page and hide the toolbar (in the main window with signed scripts, or in a subwindow). For example, if you have an image representing the Stop button in your page, you can surround it with a link whose action stops loading, as in the following:
A script cannot stop its own document from loading, but it can stop the loading of another frame or window. Similarly, if the current document dynamically loads a new image or a multimedia MIME type file as a separate action, the stop() method can halt that process. Even though the stop() method is a window method, it is not tied to any specific window or frame: Stop means stop. Related Items: window.back(), window.find(), window.forward(), window.home(), window.print() methods
Event handlers onafterprint onbeforeprint Compatibility: WinIE5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeEach of these event handlers fires after the user has clicked the OK button in IE’s Print dialog box. This goes for printing that is invoked manually (via menus and browser shortcut buttons) and the window.print() method.
848
Chapter 27: Window and Frame Objects windowObject.onbeforeunload() Although printing is usually WYSIWYG, it is conceivable that you may want the printed version of a document to display more, or less, of the document than is showing at that instant. For example, you may have a special copyright notice that you want appended to the end of a page whenever it goes to the printer. In that case, the element with that content can have its display style sheet property set to none when the page loads. Before the document is sent to the printer, a script needs to adjust that style property to display the element as a block item; after printing, have your script revert the setting to none. Immediately after the user clicks the OK button in the Print dialog box, the onbeforeprint event handler fires. As soon as the page is sent to the printer or spooler, the onafterprint event handler fires.
Example The following script fragment assumes that the page includes a div element whose style sheet includes a setting of display:none as the page loads. Somewhere in the head, the print-related event handlers are set as properties: function showPrintCopyright() { document.all.printCopyright.style.display = "block"; } function hidePrintCopyright() { document.all.printCopyright.style.display = "none"; } window.onbeforeprint = showPrintCopyright; window.onafterprint = hidePrintCopyright;
onbeforeunload Compatibility: WinIE4+, MacIE5+, NN-, Moz+, Safari+, Opera-, Chrome+ Any user or scripted action that normally forces the current page to be unloaded or replaced causes the onbeforeunload event handler to fire. Unlike the onunload event handler, however, onbeforeunload is a bit better behaved when it comes to allowing complex scripts to finish before the actual unloading takes place. Moreover, you can assign a string value to the event.returnValue property in the event handler function. That string becomes part of a message in an alert window that gives the user a chance to stay on the page. If the user agrees to stay, the page does not unload, and any action that caused the potential replacement is canceled.
Example The simple page in Listing 27-40 shows you how to give the user a chance to stay on the page. LISTING 27-40
Using the onbeforeunload Event Handler onbeforeunload Event Handler
continued
849
Part IV: Document Objects Reference windowObject.onerror() LISTING 27-40
(continued)
function verifyClose() { return "We really like you and hope you will stay longer."; } onbeforeunload Event Handler
Use this button to navigate to the previous page: Go Back
Related Item: onunload event handler
onerror Compatibility: WinIE4+, MacIE4+, NN3+, Moz+, Safari-, Opera-, Chrome(See the discussion of the window.onerror property earlier in this chapter.)
onhelp Compatibility: WinIE4+, MacIE4+, NN-, Moz-, Safari-, Opera-, ChromeThe generic onhelp event handler, discussed in Chapter 26, also fires when the user activates the context-sensitive help within a modal or modeless dialog box. In the latter case, a user can click the Help icon in the dialog box’s title bar, at which time the cursor changes to a question mark. The user can then click any element in the window. At that second click, the onhelp event handler fires, and the event object contains information about the element clicked (the event.srcElement is a reference to the specific element), allowing a script to supply help about that element. To prevent the browser’s built-in help window from appearing, the event handler must evaluate to return false (IE4+) or set the event.returnValue property to false (IE5+).
Example The following script fragment can be used to provide context-sensitive help within a dialog box. Help messages for only two form elements are shown here, but in a real application, you could easily add more messages. function showHelp() { switch (event.srcElement.name)
850
Chapter 27: Window and Frame Objects windowObject.onload() { case "bgColor" : alert("Choose a color for the main window\’s background."); break; case "name" : alert("Enter your first name for a friendly greeting."); break; default : alert("Make preference settings for the main page styles."); } event.returnValue = false; } window.onhelp = showHelp;
Because this page’s help focuses on form elements, the switch construction cases are based on the name properties of the form elements. For other kinds of pages, the id properties may be more appropriate. Related Items: event object (Chapter 32, ‘‘Event Objects’’); switch construction (Chapter 21, ‘‘Control Structures and Exception Handling’’)
onload Compatibility: WinIE3+, MacIE3+, NN2+, Moz+, Safari+, Opera+, Chrome+ The onload event handler fires in the current window at the end of the document loading process (after all text and image elements have been transferred from the source file server to the browser, and after all plug-ins and Java applets have loaded and started running). At that point, the browser’s memory contains all the objects and script components in the document that the browser can possibly know about. The onload handler is an attribute of a tag for a single-frame document, or of the tag for the top window of a multiple-frame document. When the handler is an attribute of a tag, the event triggers only after all frames defined by that frameset have completely loaded. Use either of the following scenarios to insert an onload handler into a document the old way: [body content]
851
Part IV: Document Objects Reference windowObject.onresize() Alternatively, you can bind an event listener to the window object using the W3C addEventListener() method. Chapter 32 explains the modern cross-browser event-handling technique. This handler has a special capability when it’s part of a frameset definition: The handler won’t fire until the onload event handlers of all child frames in the frameset have fired. Therefore, if some initialization scripts depend on components existing in other frames, trigger them from the frameset’s onload event handler. This brings up a good general rule of thumb for writing JavaScript: Scripts that execute during a document’s loading should contribute to the process of generating the document and its objects. To act immediately on those objects, design additional functions that are called by the onload event handler for that window. The type of operations suited for an onload event handler are those that can run quickly and without user intervention. Users shouldn’t be penalized by having to wait for considerable postloading activity to finish, before they can interact with your pages. At no time should you present a modal dialog box as part of an onload handler. Users who design macros on their machines to visit sites unattended may get hung up on a page that automatically displays an alert, confirm, or prompt dialog box. On the other hand, an operation such as setting the window.defaultStatus property is a perfect candidate for an onload event handler, as is initializing event handlers as properties of element objects in the page.
Note Browsers equipped with pop-up window blockers ignore all window.open() method calls in onload event handler functions.
Related Items: onunload event handler; window.defaultStatus property
onresize Compatibility: WinIE4+, MacIE4+, NN4+, Moz+, Safari+, Opera+, Chrome+ If a user resizes a window, the action causes the onresize event handler to fire for the window object. When you assign a function to the event (for example, window.onresize = handleResizes), the NN/Moz event object conveys width and height properties that reveal the outer width and height of the entire window. A window resize should not reload the document such that an onload event handler fires (although some early Navigator versions did fire the extra event). Related Item: event object (Chapter 32, ‘‘Event Objects’’)
onscroll Compatibility: WinIE4+, MacIE4+, NN7+, Moz+, Safari 1.3+, Opera+, Chrome+ The onscroll event handler fires for the body element object as the result of manual scrolling of the document (via scroll bars or navigation keyboard keys) and scripted scrolling via the doScroll() method, via the scrollIntoView() method, or by adjusting the scrollTop and/or scrollLeft properties of the body element object. For manual scrolling and scrolling by doScroll(), the event seems to fire twice in succession. Moreover, the event.srcElement property is null even when the body element is handling the onscroll event handler.
Example Listing 27-41 is a highly artificial demonstration of what can be a useful tool for some page designs. Consider a document that occupies a window or frame but that you don’t want scrolled, even by accident with a mouse wheel. (Be aware that the onscroll event is not fired if the user scrolls the page
852
Chapter 27: Window and Frame Objects windowObject.onunload() with a mouse wheel in Safari and Chrome in some versions of Windows, but is fired on the Mac.) If scrolling of the content would destroy the appearance or value of the content, you want to make sure that the page always zips back to the top. The onscroll event handler in Listing 27-41 does just that. Notice that the event handler is set as a property of the window object. LISTING 27-41
Preventing a Page from Scrolling onscroll Event Handler addEvent(window, "scroll", zipBack); //window.onscroll = zipBack; function zipBack() { window.scroll(0,0); } onscroll Event Handler This page always zips back to the top if you try to scroll it.
Related Items: scrollBy(), scrollByLines(), scrollByPages() methods
onunload Compatibility: WinIE3+, MacIE3+, NN2+, Moz+, Safari+, Opera-, Chrome+ An unload event reaches the current window just before a document is cleared from view. The most common ways windows are cleared are when new HTML documents are loaded into them, when the user clicks the back button or the reload button, or when the user does the reload keyboard shortcut, when a script begins writing new HTML on the fly for the window or frame. Be aware that in Safari the unload event is not fired when closing the tab/browser in some versions of Windows. Limit your use of the onunload event handler to quick operations that do not inhibit the transition from one document to another. Do not invoke any methods that display dialog boxes. You specify onunload event handlers in the same places in an HTML document as the onload handlers:
853
Part IV: Document Objects Reference frameObject as a tag attribute for a single-frame window or as a tag attribute for a multiframe window. Both onload and onunload event handlers can appear in the same or tag without causing problems. The onunload event handler merely stays safely tucked away in the browser’s memory, waiting for the unload event to arrive for processing as the document gets ready to clear the window. One caution about the onunload event handler: Even though the event fires before the document goes away, don’t burden the event handler with time-consuming tasks, such as generating new objects or submitting a form. The document will probably go away before the function completes, leaving the function looking for objects and values that no longer exist. The best defense is to keep your onunload event handler processing to a minimum.
Note Browsers equipped with pop-up window blockers ignore all window.open() method calls in onunload event handler functions.
Related Item: onload event handler
frame Element Object For HTML element properties, methods, and event handlers, see Chapter 26, ‘‘Generic HTML Element Objects.’’ Properties
Chapter 27: Window and Frame Objects frameObject.borderColor
Syntax Accessing properties or methods of a frame element object from a frameset: (IE4+) document.all.frameID. property | method([parameters]) (IE5+/W3C) document.getElementById("frameID"). property | method([parameters])
Accessing properties or methods of a frame element from a frame document: (IE4+) parent.document.all.frameID. property | method([parameters]) (IE5+/W3C) parent.document.getElementById("frameID"). property | method([parameters])
About this object As noted in the opening section of this chapter, a frame element object is distinct from the frame object that acts as a window object in a document hierarchy. The frame element object is available to scripts only when all HTML elements are exposed in the object model. Because the frame element object is an HTML element, it shares the properties, methods, and event handlers of all HTML elements, as described in Chapter 26. By and large, you access the frame element object to set or modify an attribute value in the tag. If so, you simplify matters if you assign an identifier to the id attribute of the tag. Your tag still needs a name attribute if your scripts refer to frames through the original object model (a parent.frameName reference). Although there is no law against using the same identifier for both name and id attributes, using different names to prevent potential conflict with references in browsers that recognize both attributes is best. To modify the dimensions of a frame, you must go to the frameset element object that defines the cols and rows attributes for the frameset. These properties can be modified on the fly in modern browsers.
Properties allowTransparency Value: Boolean
Read/Write
Compatibility: WinIE6+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe allowTransparency property indicates whether the frame’s background is transparent. This property applies primarily to the iframe object, because framesets don’t have background colors or images to show through a transparent frame.
borderColor Value: Hexadecimal triplet or color name string
Part IV: Document Objects Reference frameObject.contentDocument If a frame displays a border (as determined by the frameborder attribute of the frame element, or border attribute of the frameset element), it can have a color set separately from the rest of the frames. The initial color (if different from the rest of the frameset) is usually set by the bordercolor attribute of the tag. After that, scripts can modify settings as needed. Modifying a single frame’s border can be risky at times, depending on your color combinations. In practice, different browsers appear to follow different rules when it comes to negotiating conflicts or defining just how far a single frame’s border extends into the border space. Color changes to individual frame borders do not always render. Verify your designs on as many browsers and operating system variations as you can to test your combinations.
Example Although you may experience problems changing the color of a single frame border, the W3C DOM syntax would look like the following if the script were inside the framesetting document: document.getElementById("contentsFrame").borderColor = "red";
The IE-only version would be document.all["contentsFrame"].borderColor = "red";
These examples assume that the frame name arrives to a script function as a string. If the script is executing in one of the frames of the frameset, add a reference to parent in the preceding statements. Related Items: frame.frameBorder, frameset.frameBorder properties
contentDocument Value: document object reference
Read-Only
Compatibility: WinIE8+, MacIE-, NN6+, Moz+, Safari+, Opera+, Chrome+ The contentDocument property of a frame element object is nothing more than a reference to the document contained by that frame. This property bridges the gap between the frame element object and the frame object. Both of these objects contain the same document object, but from a scripting point of view, references most typically use the frame object to reach the document inside a frame, whereas the frame element is used to access properties equated with the frame tag’s attributes. But if your script finds that it has a reference to the frame element object, you can use the contentDocument property to get a valid reference to the document and, therefore, any other content of the frame.
Example A framesetting document script might be using the ID of a frame element to read or adjust one of the element properties, and then need to perform some action on the content of the page through its document object. You can get the reference to the document object via a statement such as the following: var doc = document.getElementById("Frame3").contentDocument;
Then your script can, for example, dive into a form in the document: var val = doc.mainForm.entry.value;
856
Chapter 27: Window and Frame Objects frameObject.frameBorder Related Items: contentWindow property; document object
contentWindow Value: document object reference
Read-Only
Compatibility: WinIE5.5+, MacIE-, NN7+, Moz1.0.1+, Safari+, Opera+, Chrome+ The contentWindow property of a frame element object is simply a reference to the window generated by that frame. This property provides access to the frame’s window, which can then be used to reach the document inside the frame.
Example You can get the reference to the window object associated with a frame via a statement such as the following: var win = document.getElementById("Frame3").contentWindow;
Related Item: window object
frameBorder Value: yes | no | 1 | 0 as strings
Read/Write
Compatibility: WinIE4+, MacIE4+, NN6+, Moz+, Safari+, Opera+, Chrome+ The frameBorder property offers scripted access to a frame element object’s frameborder attribute setting. Except for IE, none of the browsers we tested responded well to modifying this property after the page has loaded. Values for the frameBorder property are strings that substitute for Boolean values. Value yes or 1 means that the border is (supposed to be) turned on; no or 0 (supposedly) turns off the border. There is no consistent default behavior among the browsers.
Example The default value for the frameBorder property is yes. You can use this setting to create a toggle script (which, unfortunately, does not change the border’s appearance in IE). The W3C-compatible version looks like the following: function toggleFrameScroll(frameID) { var theFrame = document.getElementById(frameID); if (theFrame.frameBorder == "yes") { theFrame.frameBorder = "no"; } else { theFrame.frameBorder = "yes"; } }
Related Items: frameset.frameBorder properties
857
Part IV: Document Objects Reference frameObject.height
height width Value: Integer
Read-Only
Compatibility: WinIE4+, MacIE4+, NN-, Moz-, Safari+, Opera-, Chrome+ These two properties enable you to retrieve the height and width of a frame element object. These values are not necessarily the same as document.body.clientHeight and document.body.clientWidth, because the frame dimensions include chrome associated with the frame, such as scroll bars. These values are read-only. If you need to modify the dimensions of a frame, do so via the frameset element object’s rows and/or cols properties. Reading integer values for a frame’s height and width properties is much easier than trying to parse the rows and cols string properties.
Example The following fragment assumes a frameset defined with two frames set up as two columns within the frameset. The statements here live in the framesetting document. They retrieve the current width of the left frame and increase the width of that frame by 10 percent. Syntax shown here is for the W3C DOM, but can easily be adapted to IE-only terminology. var frameWidth = document.getElementById("leftFrame").width; document.getElementById("mainFrameset").cols = (Math.round(frameWidth * 1.1)) + ",*";
Notice that the numeric value of the existing frame width is first increased by 10 percent and then concatenated to the rest of the string property assigned to the frameset’s cols property. The asterisk after the comma means that the browser should figure out the remaining width and assign it to the right frame. Related Item: frameset object
longDesc Value: URL string
Read/Write
Compatibility: WinIE6+, MacIE5+, NN6+, Moz+, Safari+, Opera+, Chrome+ The longDesc property is the scripted equivalent of the longdesc attribute of the tag. This HTML 4 attribute is intended to provide browsers a URL to a document that contains a long description of the element. Future browsers can use this feature to provide information about the frame for visually impaired site visitors.
marginHeight marginWidth Value: Integer
Read/Write
Compatibility: WinIE6+, MacIE5+, NN6+, Moz+, Safari+, Opera+, Chrome+ Browsers tend to insert content within a frame automatically by adding a margin between the content and the edge of the frame. These values are represented by the marginHeight (top and bottom edges) and marginWidth (left and right edges) properties. Although the properties are not read-only, changing the values after the frameset has loaded does not alter the appearance of the
858
Chapter 27: Window and Frame Objects frameObject.scrolling document in the frame. If you need to alter the margin(s) of a document inside a frame, adjust the document.body.style margin properties. Also be aware that although the default values of these properties are empty (meaning when no marginheight or marginwidth attributes are set for the tag), margins are built into the page. The precise pixel count of those margins varies with operating system. Related Item: style object (Chapter 38, ‘‘Style Sheet and Style Objects’’)
name Value: String
Read/Write
Compatibility: WinIE4+, MacIE4+, NN6+, Moz+, Safari+, Opera+, Chrome+ The name property is the identifier associated with the frame for use as a reference. Scripts can reference the frame through the name property (for example, top.frames["myFrame"]), which is typically assigned via the name attribute.
noResize Value: Boolean
Read/Write
Compatibility: WinIE6+, MacIE5+, NN6+, Moz+, Safari+, Opera+, Chrome+ Web designers commonly fix their framesets so that users cannot resize the frames (by dragging any divider border between frames). The noResize property lets you read and adjust that behavior of a frame after the page has loaded. For example, during some part of the interaction with a user on a page, you may allow the user to modify the frame size manually while in a certain mode. Or you may grant the user one chance to resize the frame. When the onresize event handler fires, a script sets the noResize property of the frame element to false. If you turn off resizing for a frame, all edges of the frame become nonresizable, regardless of the noResize value setting of adjacent frames. Turning off resizability has no effect on the ability of scripts to alter the sizes of frames via the frameset element object’s cols or rows properties.
Example The following statement turns off the ability for a frame to be resized: parent.document.getElementById("myFrame1").noResize = true;
Because of the negative nature of the property name, it may be difficult to keep the logic straight (setting noResize to true means that resizability is turned off). Keep a watchful eye on your Boolean values. Related Items: frameset.cols, frameset.rows properties
scrolling Value: yes | no | 1 | 0 as strings
Read/Write
Compatibility: WinIE6+, MacIE5+, NN6+, Moz+, Safari+, Opera+, Chrome+ The scrolling property lets scripts turn scroll bars on and off inside a single frame of a frameset. By default, scrolling is turned on unless overridden by the scroll attribute of the tag. Values for the scrolling property are strings that substitute for Boolean values. Value yes or 1 means that scroll bars are visible (provided that there is more content than can be viewed without
859
Part IV: Document Objects Reference frameObject.scrolling scrolling); no or 0 hides scroll bars in the frame. IE also recognizes (and sets as default) the auto value.
Note Although this property is read/write, changing its value by script does not alter a frame’s appearance in WinIE, Mozilla browsers, or Safari.
Example Listing 27-42 produces a frameset consisting of eight frames. The content for the frames is generated by a script within the frameset (via the fillFrame() function). Event handlers (onclick) in the body of each frame invoke the toggleFrameScroll() function. Both ways of referencing the frame element object are shown, with the IE-only version commented out. In the toggleFrameScroll() function, the if condition checks whether the property is set to something other than no. This allows the condition to evaluate to true if the property is set to either auto (the first time) or yes (as set by the function). Note that the scroll bars don’t disappear from the frames in IE, NN6+, Safari, Opera, or Chrome. LISTING 27-42
Controlling the frame.scrolling Property frame.scrolling Property function toggleFrameScroll(frameID) { // IE5+/W3C version var theFrame = document.getElementById(frameID); if (theFrame.scrolling != "no") { theFrame.scrolling = "no"; } else { theFrame.scrolling = "yes"; } } // generate content for each frame function fillFrame(frameID) { var page = ""; page += "
This frame has the ID of:
" + frameID + "."; page += ""; return page; }
src Value: URL string
Read/Write
Compatibility: WinIE6+, MacIE5+, NN6+, Moz+, Safari+, Opera+, Chrome+ The src property of a frame element object offers an additional way of navigating to a different page within a frame (meaning other than assigning a new URL to the location.href property of the frame object). For backward compatibility with older browsers, however, continue using location.href for scripted navigation. Remember that the src property belongs to the frame element object, not the window object it represents. Therefore, references to the src property must be via the element’s ID and/or node hierarchy.
Example For best results, use fully formed URLs as values for the src property, as shown here: parent.document.getElementById("mainFrame").src = "http://www.dannyg.com";
Relative URLs and javascript: pseudo-URLs will also work most of the time. Related Item: location.href property
861
Part IV: Document Objects Reference framesetObject
frameset Element Object For HTML element properties, methods, and event handlers, see Chapter 26, ‘‘Generic HTML Element Objects.’’ Properties
Syntax Accessing properties or methods of a frameset element object from a frameset: (IE4+) document.all.framesetID. property | method([parameters]) (IE5+/W3C) document.getElementById("framesetID"). property | method([parameters])
Accessing properties or methods of a frameset element from a frame document: (IE4+) parent.document.all.framesetID. property | method([parameters]) (IE5+/W3C) parent.document.getElementById("framesetID"). property | method([parameters])
About this object The frameset element object is the script-accessible equivalent of the element generated via the tag. This element is different from the parent (window-type) object of the original object model. A frameset element object has properties and methods that impact the HTML element; by contrast, the window object referenced from documents inside frames via the parent or top window references, contains a document and all the content that goes along with it. When framesets are nested in side one another, a node parent–child relationship exists between containing and contained framesets. For example, consider the following skeletal nested frameset structure:
862
Chapter 27: Window and Frame Objects framesetObject.border
When writing scripts for documents that go inside any of the frames of this structure, references to the framesetting window and frames are a flatter hierarchy than the HTML signifies. A script in any frame references the framesetting window via the parent reference; a script in any frame references another frame via the parent.frameName reference. In other words, the window objects of the frameset defined in a document are all siblings, and have the same parent. Such is not the case when viewing the preceding structure from the perspective of W3C node terminology. Parent–child relationships are governed by the nesting of HTML elements, irrespective of whatever windows get generated by the browser. Therefore, frame2 has only one sibling: frame3. Both of those share one parent: innerFrameset. Both innerFrameset and frame1 are children of outerFrameset. If your script were sitting on a reference to frame2, and you wanted to change the cols property of outerFrameset, you would have to traverse two generations of nodes: frame2Ref.parentNode.parentNode.cols = "40%,60%";
What might confuse matters ever more in practice is that a script belonging to one of the frames must use window object terminology to jump out of the current window object to the frameset that generated the frame window for the document. In other words, there is no immediate way to jump directly from a document to the frame element object that defines the frame in which the document resides. The document’s script accesses the node hierarchy of its frameset via the parent.document reference. But this reference is to the document object that contains the entire frameset structure. Fortunately, the W3C DOM provides the getElementById() method to extract a reference to any node nested within the document. Thus, a document inside one of the frames can access the frame element object just as though it were any element in a typical document (which it is): parent.document.getElementById("frame2")
No reference to the containing frameset element object is necessary. To make that column width change from a script inside one of the frame windows, the statement would be parent.document.getElementById("outerFrame").cols = "40%,60%";
The inner frameset is equally accessible by the same syntax.
Properties border Value: Integer
Read/Write
Compatibility: WinIE4+, MacIE4+, NN-, Moz-, Safari-, Opera-, ChromeThe border property of a frameset element object lets you read the thickness (in pixels) of the borders between frames of a frameset. If you do not specify a border attribute in the frameset’s tag, the property is empty, rather than reflecting the actual border thickness applied by default.
863
Part IV: Document Objects Reference framesetObject.borderColor
Example Even though the property is read/write, changing the value does not change the thickness of the border you see in the browser. If you need to find the thickness of the border, a script reference from one of the frame’s documents would look like the following: var thickness = parent.document.all.outerFrameset.border;
Related Item: frameset.frameBorder property
borderColor Value: Hexadecimal triplet or color name string
Read/Write
Compatibility: WinIE4+, MacIE4+, NN-, Moz-, Safari-, Opera-, ChromeThe borderColor property lets you read the value of the color assigned to the bordercolor attribute of the frameset’s tag. Although the property is read/write, changing the color by script does not alter the border colors rendered in the browser window. Attribute values set as color names are returned as hexadecimal triplets when you read the property value.
Example To retrieve the current color setting in a frameset, a script reference from one of the frame’s documents would look like the following: var borderColor = parent.document.all.outerFrameset.borderColor;
Related Items: frame.borderColor, frameset.frameBorder properties
cols rows Value: String
Read/Write
Compatibility: WinIE4+, MacIE4+, NN6+, Moz+, Safari+, Opera+, Chrome+ The cols and rows properties of a frameset element object let you read and modify the sizes of frames after the frameset has loaded. These two properties are defined in the W3C DOM. Values for both properties are strings, which may include percent symbols or asterisks. Therefore, if you are trying to increase or decrease the size of a frame column or row gradually, you must parse the string for the necessary original values before performing any math on them (or, in IE4+, use the frame element object’s height and width properties to gauge the current frame size in pixels). Adjusting these two properties lets you modify the frameset completely, including adding or removing columns or rows in the frameset grid. Because a change in the frameset structure could impact scripts by changing the size of the frames array associated with the parent window or unloading documents that contain needed data, be sure to test your scripts with both states of your frameset. If you want to remove a frame from a frameset view, you might be safer to specify the size of zero for that particular row or column in the frameset. Of course, a size of zero still leaves a 1-pixel frame, but it is essentially invisible if borders are not turned on and the 1-pixel frame has the same background color as the other frames. Another positive byproduct of this technique is that you can restore the other frame with its document state identical from when it was hidden. When you have nested framesets defined in a single document, be sure to reference the desired frameset element object. One object may be specifying the columns, and another (nested) one
864
Chapter 27: Window and Frame Objects framesetObject.borderColor specifies the rows for the grid. Assign a unique ID to each frameset element so that references can be reliably directed to the proper object.
Example Listings 27-43, 27-44, and 27-45 show the HTML for a frameset and two of the three documents that go into the frameset. The final document is an HTML version of the U.S. Bill of Rights, which is serving here as a content frame for the demonstration. The frameset listing (see Listing 27-43) shows a three-frame setup. Down the left column is a table of contents (see Listing 27-44). The right column is divided into two rows. In the top row is a simple control (see Listing 27-45) that hides and shows the table-of-contents frame. As the user clicks the hot spot of the control (located inside a span element), the onclick event handler invokes the toggleTOC() function in the frameset. LISTING 27-43
Frameset and Script for Hiding/Showing a Frame Hide/Show Frame Example var origCols; function toggleTOC() { if (origCols) { showTOC(); } else { hideTOC(); } } function hideTOC() { var frameset = document.getElementById("outerFrameset"); origCols = frameset.cols; frameset.cols = "0,*"; } function showTOC() { if (origCols) { document.getElementById("outerFrameset").cols = origCols; origCols = null; } }
continued
865
Part IV: Document Objects Reference framesetObject.borderColor LISTING 27-43
(continued)
When a user clicks the hot spot to hide the frame, the script copies the original cols property settings to a global variable. The variable is used in showTOC() to restore the frameset to its original proportions. This allows a designer to modify the HTML for the frameset without also having to dig into scripts to hard-wire the restored size. LISTING 27-44
Table of Contents Frame Content Table of Contents body { background-color:#EEEEEE; } Table of Contents
Article I
Article II
Article III
Article IV
Article V
Article
Article
Article
Article
Article
VI VII VIII IX X
LISTING 27-45
Control Panel Frame Control Panel span { text-decoration:underline; cursor:pointer; }
Table of Contents
Related Item: frame object
frameBorder Value: yes | no | 1 | 0 as strings
Read/Write
Compatibility: WinIE4+, MacIE4+, NN-, Moz-, Safari-, Opera-, ChromeThe frameBorder property offers scripted access to a frameset element object’s frameborder attribute setting. IE4+ does not respond well to modifying this property after the page has loaded. Values for the frameBorder property are strings that substitute for Boolean values. Value yes or 1 means that the border is (supposed to be) turned on; no or 0 turns off the border.
867
Part IV: Document Objects Reference framesetObject.frameSpacing
Example The default value for the frameBorder property is yes. You can use this setting to create a toggle script (which, unfortunately, does not change the appearance in IE). The IE5+ version looks like the following: function toggleFrameScroll(framesetID) { var theFrameset = document.getElementById(framesetID); if (theFrameset.frameBorder == "yes") { theFrameset.frameBorder = "no"; } else { theFrameset.frameBorder = "yes"; } }
Related Item: frame.frameBorder property
frameSpacing Value: Integer
Read/Write
Compatibility: WinIE4+, MacIE4+, NN-, Moz-, Safari-, Opera-, ChromeThe frameSpacing property of a frameset element object lets you read the spacing (in pixels) between frames of a frameset. If you do not specify a framespacing attribute in the frameset’s tag, the property is empty, rather than reflecting the actual border thickness applied by default (usually 2).
Example If you need to change the spacing, a script reference would look like the following: document.getElementById("outerFrameset").frameSpacing = "10";
Related Item: frameset.border property
iframe Element Object For HTML element properties, methods, and event handlers, see Chapter 26, ‘‘Generic HTML Element Objects.’’ Properties
Syntax Accessing properties or methods of an iframe element object from a containing document: (IE4+) document.all.iframeID. property | method([parameters]) (IE4+/NN6) window.frames["iframeName"]. property | method([parameters]) (IE5+/W3C) document.getElementById("iframeID"). property | method([parameters])
Accessing properties of methods of an iframe element from a document inside the iframe element: (IE4+) parent.document.all.iframeID. property | method([parameters]) (IE5+/W3C) parent.document.getElementById("iframeID"). property | method([parameters])
About this object An iframe element allows HTML content from a separate source to be loaded within the body of another document. In some respects, the NN4 layer element was a precursor to the iframe concept, but unlike the layer, an iframe element is not inherently positionable. It is positionable the same way as any other HTML element: by assigning positioning attributes to a style sheet associated with the iframe. Without explicit positioning, an iframe element appears in the body of a
869
Part IV: Document Objects Reference iframeObject.align document in the normal source-code order of elements. Unlike a frame of a frameset, an iframe can be placed arbitrarily in the middle of any document. If the iframe changes size under script control, the surrounding content moves out of the way or cinches up. What truly sets the iframe apart from other HTML elements is its ability to load and display external HTML files and, with the help of scripts, have different pages loaded into the iframe without disturbing the rest of the content of the main document. Pages loaded into the iframe can also have scripts and any other features that you may like to put into an HTML document (including XML, in IE for Windows). The iframe element has a rich set of attributes that lets the HTML author control the look, size (height and width), and, to some degree, behavior of the frame. Most of these attributes are accessible to scripts as properties of an iframe element object. It is important to bear in mind that an iframe element is in many respects like a frame element, especially when it comes to window kinds of relationships. If you plant an iframe element in a document of the main window, that element shows up in the main window’s object model as a frame, accessible via common frames terminology: window.frames[i] window.frames[frameName]
Within that iframe frame object is a document and all its contents. All references to the document objects inside the iframe must flow through the portal of the iframe frame. Conversely, scripts in the document living inside an iframe can communicate with the main document via the parent reference. Of course, you cannot replace the content of the main window with another HTML document (using location.href, for instance) without destroying the iframe that was in the original document.
Properties align Value: String
Read/Write
Compatibility: WinIE4+, MacIE4+, NN6+, Moz+, Safari+, Opera+, Chrome+ The align property governs how an iframe element aligns itself with respect to surrounding content on the page. Two of the possible values (left and right) position the iframe along the left and right edge (respectively) of the iframe’s containing element (usually the body). Just as with an image, when an iframe is floated along the left and right edges of a container, other content wraps around the element. Table 27-6 shows all possible values and their meanings. As your script changes the value of the align property, the page automatically reflows the content to suit the new alignment.
Example The default setting for an iframe alignment is baseline. A script can shift the iframe to be flush with the right edge of the containing element as follows: document.getElementById("iframe1").align = "right";
870
Chapter 27: Window and Frame Objects iframeObject.contentDocument TABLE 27-6
Values of the align Property Value
Description
absbottom
Aligns the bottom of the iframe with the imaginary line that extends along character descenders of surrounding text
absmiddle
Aligns the middle of the iframe with the center point between the surrounding text’s top and absbottom
baseline
Aligns the bottom of the iframe with the baseline of surrounding text
bottom
Aligns the bottom of the iframe with the bottom of the surrounding text
left
Aligns the iframe flush with left edge of the containing element
middle
Aligns the imaginary vertical center line of surrounding text with the same for the iframe element
right
Aligns the iframe flush with the right edge of the containing element
texttop
Aligns the top of the iframe element with the imaginary line that extends along the tallest ascender of surrounding text
top
Aligns the top of the iframe element with the surrounding element’s top
Related Items: iframe.hspace, iframe.vspace properties
allowTransparency Value: Boolean
Read/Write
Compatibility: WinIE6+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe allowTransparency property indicates whether the frame’s background is transparent. By setting this property to true, you allow a background color or image to show through the transparent frame.
contentDocument Value: document object reference
Read-Only
Compatibility: WinIE8+, MacIE-, NN6+, Moz+, Safari+, Opera+, Chrome+ The contentDocument property of an iframe element object is nothing more than a reference to the document contained by that frame. If your script finds that it has a reference to an iframe element object, you can use the contentDocument property to get a valid reference to the document and, therefore, any other content of the frame.
Example A document script might be using the ID of an iframe element to read or adjust one of the element properties; then it needs to perform some action on the content of the page through its
871
Part IV: Document Objects Reference iframeObject.contentWindow document object. You can get the reference to the document object via a statement such as the
following: var doc = document.getElementById("Frame3").contentDocument;
Then your script can, for example, dive into a form in the document: var val = doc.mainForm.entry.value;
Related Items: contentWindow property; document object
contentWindow Value: document object reference
Read-Only
Compatibility: WinIE5.5+, MacIE-, NN7+, Moz1.0.1+, Safari+, Opera+, Chrome+ The contentWindow property of an iframe element object serves as a reference to the window object generated by the frame. You can then use this window object as a means of accessing the document object and any document elements. Related Items: contentDocument property; window object
frameBorder (See frame.frameBorder() and frameset.frameBorder())
frameSpacing (See frameset.frameSpacing())
height width Value: Integer
Read/Write
Compatibility: WinIE4+, MacIE4+, NN6+, Moz+, Safari+, Opera+, Chrome+ The height and width properties provide access to the height and width of the iframe object, and allow you to alter the size of the frame. Both properties are specified in pixels.
hspace vspace Value: Integer
Read/Write
Compatibility: WinIE4+, MacIE4+, NN-, Moz-, Safari-, Opera-, ChromeThese IE-specific properties allow for margins to be set around an iframe element. In general, hspace and vspace properties (and their HTML attributes) have been replaced by CSS margins and padding. These properties and their attributes are not recognized by any W3C standard (including HTML 4). Values for these properties are integers representing the number of pixels of padding between the element and surrounding content. The hspace value assigns the same number of pixels to the left and
872
Chapter 27: Window and Frame Objects iframeObject.scrolling right sides of the element; the vspace value is applied to both the top and bottom edges. Scripted changes to these values have no effect in WinIE5+. Related Item: style.padding property
longDesc Value: URL string
Read/Write
Compatibility: WinIE6+, MacIE5+, NN6+, Moz+, Safari+, Opera+, Chrome+ The longDesc property is the scripted equivalent of the longdesc attribute of the tag. This HTML 4 attribute is intended to provide browsers a URL to a document that contains a long description of the element. Future browsers can use this feature to provide information about the frame for visually impaired site visitors.
marginHeight marginWidth Value: Integer
Read/Write
Compatibility: WinIE4+, MacIE4+, NN6+, Moz+, Safari+, Opera+, Chrome+ Browsers tend to insert content within a frame automatically by adding a margin between the content and the edge of the frame. These values are represented by the marginHeight (top and bottom edges) and marginWidth (left and right edges) properties. Although the properties are not read-only, changing the values after the frameset has loaded does not alter the appearance of the document in the frame. If you need to alter the margin(s) of a document inside a frame, adjust the document.body.style margin properties. Also be aware that although the default values of these properties are empty (that is, when no marginheight or marginwidth attributes are set for the tag), margins are built into the page. The precise pixel count of those margins varies with different operating systems. Related Item: style object (Chapter 38, ‘‘Style Sheet and Style Objects’’)
name Value: String
Read/Write
Compatibility: WinIE4+, MacIE4+, NN6+, Moz+, Safari+, Opera+, Chrome+ The name property is the identifier associated with the frame for use as a reference. Scripts can reference the frame through the name property (for example, window.frames["myIframe"]), which is typically assigned via the name attribute.
Part IV: Document Objects Reference iframeObject.src The scrolling property lets scripts turn scroll bars on and off inside an iframe element. By default, scrolling is turned on unless overridden by the scroll attribute of the tag. Values for the scrolling property are strings that substitute for Boolean values. Value yes or 1 means that scroll bars are visible (provided that there is more content than can be viewed without scrolling); no or 0 hides scroll bars in the frame. IE4+ also recognizes (and sets as default) the auto value.
Example The following toggleIFrameScroll() function accepts a string of the iframe element’s ID as a parameter, and switches between on and off scroll bars in the iframe. The if condition checks whether the property is set to something other than no. This test allows the condition to evaluate to true if the property is set to either auto (the first time) or yes (as set by the function). function toggleFrameScroll(frameID) { // IE5 & NN6 version var theFrame = document.getElementById(frameID); if (theFrame.scrolling != "no") { theFrame.scrolling = "no"; } else { theFrame.scrolling = "yes"; } }
Related Item: frame.scrolling property
src Value: URL string
Read/Write
Compatibility: WinIE4+, MacIE4+, NN6+, Moz+, Safari+, Opera+, Chrome+ The src property of an iframe element object offers an additional way of navigating to a different page within an inline frame (that is, other than assigning a new URL to the location.href property of the frame object). Remember that the src property belongs to the iframe element object, not the window object it represents. Therefore, references to the src property must be via the element’s ID and/or node hierarchy.
Example For best results, use fully formed URLs as values for the src property, as shown here: document.getElementById("myIframe").src = "http://www.dannyg.com";
Relative URLs and javascript: pseudo-URLs also work most of the time. Related Item: location.href property
874
Chapter 27: Window and Frame Objects popupObject
popup Object Properties
Methods
document
hide()
isOpen
show()
Event Handlers
Syntax Creating a popup object: var popupObj = window.createPopup()
Accessing properties or methods of a popup object from a document in the window that created the pop-up: popupObj.property | method([parameters])
About this object A popup object is a chromeless window space that overlaps the window whose document generates the pop-up. A pop-up also appears in front of any dialog boxes. Unlike the dialog-box windows generated via showModalDialog() and showModelessDialog() methods, your scripts must not only create the window, but also put content in it, and then define where on the screen, and how big, it will be. Because the pop-up window IE creates is a window and not a dialog box, there is no exact W3C equivalent. However, with the ability to add and delete elements to the node tree using the W3C DOM, you can achieve the same type of functionality. See Chapter 25, ‘‘Document Object Model Essentials,’’ for more information. Because the pop-up window has no chrome (title bar, resize handles, and so on), you should populate its content with a border and/or background color so that it stands out from the main window’s content. The following statements reflect a typical sequence of creating, populating, and showing a popup object: var popup = window.createPopup(); var popupBody = popup.document.body; popupBody.style.border = "solid 2px black"; popupBody.style.padding = "5px"; popupBody.innerHTML = "
Here is some text in a popup window
"; popup.show(200,100, 200, 50, document.body);
Note As handy as it may be, in a strict W3C approach to JavaScript, you wouldn’t use the innerHTML property, because it isn’t officially part of the W3C standard. However, it is often too powerful a convenience property to ignore, as much of the code throughout this book is a testament. The book does show the W3C node manipulation alternative to innerHTML in some examples. Refer to Chapter 29 for a thorough explanation and examples of the W3C alternative to innerHTML.
875
Part IV: Document Objects Reference popupObject.document The pop-up window that IE creates is, in fact, a window, but only from the point of view of the document that it contains. In other words, although the number of properties and methods for the popup object is small, the parentWindow property of the document inside the pop-up points to a genuine window property. Even so, be aware that this pop-up does not appear as a distinct window among those listed in the Windows Taskbar. If a user clicks outside the pop-up or switches to another application, the pop-up disappears, and you must reinvoke the show() method by script (complete with dimension and position parameters) to force the pop-up to reappear. When you assign content to a pop-up, you are also responsible for making sure that the content fits the size of the pop-up you specify. If the content runs past the rectangular space (body text word wraps within the pop-up’s rectangle), no scroll bars appear.
Compatibility: WinIE5.5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeUse the document property as a gateway to the content of a pop-up window. This property is the only access point available from the script that creates the pop-up, to the pop-up itself. The most common application of this property is to set document properties governing the content of the pop-up window. For example, to give the pop-up a border (because the pop-up itself has no window chrome), the script that creates the window can assign values to the style property of the document in the pop-up window, as follows: myPopup.document.body.style.border = "solid 3px gray";
Be aware that the document object of a pop-up window may not implement the full flexibility you’re used to with primary window document objects. For example, you are not allowed to assign a URL to the document.URL property in a pop-up window.
Example Use The Evaluator (Chapter 4, ‘‘JavaScript’’) to experiment with the popup object and its properties. Enter the following statements in the top text box. The first statement creates a pop-up window whose reference is assigned to the a global variable. Next, a reference to the body of the pop-up’s document is preserved in the b variable for the sake of convenience. Further statements work with these two variables. a = window.createPopup() b = a.document.body b.style.border = "solid 2px black" b.style.padding = "5px" b.innerHTML = "
Here is some text in a popup window
" a.show(200,100, 200, 50, document.body)
See the description of the show() method for details on the parameters. Related Item: document object
876
Chapter 27: Window and Frame Objects popupObject.show()
isOpen Value: Boolean
Read-Only
Compatibility: WinIE5.5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeWhile a pop-up window is visible, its isOpen property returns true; otherwise, the property returns false. Because any user action in the browser causes the pop-up to hide itself, the property is useful only for script statements that are running on their own after the pop-up is made visible.
Example Use The Evaluator (Chapter 4, ‘‘JavaScript Essentials’’) to experiment with the isOpen property. Enter the following statements in the top text box. The sequence begins with a creation of a simple pop-up window, whose reference is assigned to the a global variable. Note that the final statement is actually two statements, designed so that the second statement executes while the pop-up window is still open. a = window.createPopup(); a.document.body.innerHTML = "
Here is a popup window
"; a.show(200,100, 200, 50, document.body); alert("Popup is open:" + a.isOpen);
If you then click in the main window to hide the pop-up, you will see a different result if you enter the following statement in the top text box by itself: alert("Popup is open:" + a.isOpen);
Related Item: popup.show() method
Methods hide() show(left, top, width, height[, positioningElementRef]) Returns: Nothing Compatibility: WinIE5.5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeAfter you have created a popup object with the window.createPopup() method and populated it with content, you must explicitly show the window via the show() method. If the window is hidden because a user clicked the main browser window somewhere, the show() method (and all its parameters) must be invoked again. To have a script hide the window, invoke the hide() method for the popup object. The first four parameters of the show() method are required; they define the pixel location and size of the pop-up window. By default, the coordinate space for the left and top parameters is the video display. Thus, a left and top setting of zero places the pop-up in the top-left corner of the video screen. But you can define a different coordinate space by adding an optional fifth parameter. This parameter must be a reference to an element on the page. To confine the coordinate space to the content region of the browser window, specify the document.body object as the positioning element reference.
877
Part IV: Document Objects Reference popupObject.show()
Example Listing 27-46 demonstrates the show() and hide() methods for a popup object. A click of the button on the page invokes the selfTimer() function, which acts as the main routine for this page. The goal is to produce a pop-up window that self-destructs 5 seconds after it appears. Along the way, a message in the pop-up counts down the seconds. A reference to the pop-up window is preserved as a global variable called popup. After the popup object is created, the initContent() function stuffs the content into the pop-up by way of assigning style properties, and some innerHTML, for the body of the document that is automatically created when the pop-up is generated. A span element is defined so that another function later on can modify the content of just that segment of text in the pop-up. Notice that the assignment of content to the pop-up is predicated on the pop-up window’s having been initialized (by virtue of the popup variable’s having a value assigned to it) and that the pop-up window is not showing. Although invoking initContent() under any other circumstances is probably impossible, the validation of the desired conditions is good programming practice. Back in selfTimer(), the popup object is displayed. Defining the desired size requires some trial and error to make sure that the pop-up window comfortably accommodates the text that is put into the pop-up in the initContent() function. With the pop-up window showing, now is the time to invoke the countDown() function. Before the function performs any action, it validates that the pop-up has been initialized and is still visible. If a user clicks the main window while the counter is counting down, this changes the value of the isOpen property to false, and nothing inside the if condition executes. This countDown() function grabs the inner text of the span and uses paresInt() to extract just the integer number (using base 10 numbering, because we’re dealing with zero-leading numbers that can potentially be regarded as octal values). The condition of the if construction decreases the retrieved integer by one. If the decremented value is zero, the time is up, and the pop-up window is hidden with the popup global variable returned to its original, null value. But if the value is other than zero, the inner text of the span is set to the decremented value (with a leading zero), and the setTimeout() method is called upon to reinvoke the countDown() function in 1 second (1,000 milliseconds). LISTING 27-46
Hiding and Showing a Pop-Up HTML: jsb27-46.html popup Object
878
Chapter 27: Window and Frame Objects popupObject.show()
JavaScript: jsb27-46.js var popup; function initContent() { if (popup && !popup.isOpen) { var popBody = popup.document.body; popBody.style.border = "solid 3px red"; popBody.style.padding = "10px"; popBody.style.fontSize = "24pt"; popBody.style.textAlign = "center"; var bodyText = "
This popup will self-destruct in "; bodyText += "05"; bodyText += " seconds..."; popBody.innerHTML = bodyText; } } function countDown() { if (popup && popup.isOpen) { var currCount = parseInt(popup.document.all.counter.innerText, 10); if (--currCount == 0) { popup.hide(); popup = null; } else { popup.document.all.counter.innerText = "0" + currCount; setTimeout("countDown()", 1000); } } } function selfTimer() { popup = window.createPopup(); initContent(); popup.show(200,200,400,100,document.body); setTimeout("countDown()", 1000); }
879
Part IV: Document Objects Reference popupObject.show() The hide() method here is invoked by a script that is running while the pop-up window is showing. Because a pop-up window automatically goes away if a user clicks the main window, it is highly unlikely that the hide() method would ever be invoked by itself in response to user action in the main window. If you want a script in the pop-up window to close the pop-up, use parentWindow.close().
Related Items: popup.isOpen property; window.createPopup() method
880
Location and History Objects
N
ot all objects in the document object model (DOM) are things you can see in the content area of the browser window. Each browser window or frame maintains a bunch of other information about the page you are currently visiting and where you have been. The URL of the page you see in the window is called the location, and browsers store this information in the location object. As you surf the Web, the browser stores the URLs of your past pages in the history object. You can manually view what that object contains by looking in the browser menu for the item that enables you to jump back to a previously visited page. This chapter is all about these two nearly invisible, but important, objects. These objects are not only valuable to your browser, but also valuable to snoopers who might want to write scripts to see what URLs you’re viewing in another frame, or the URLs of other sites you’ve visited in the past dozen mouse clicks. As a result, security restrictions built into browsers limit access to some of these objects’ properties (unless you use signed scripts in NN4+/Moz). For older browsers, these properties simply are not available from a script.
IN THIS CHAPTER Loading new pages and other media types via the location object Security restrictions across frames Navigating through the browser history under script control
location Object Properties
Methods
Event Handlers
hash
assign()
None
host
reload()
hostname
replace()
href pathname
881
Part IV: Document Objects Reference locationObject Properties
Methods
Event Handlers
port protocol search
Syntax Loading a new document into the current window: [window.]location.href = "URL";
Accessing location object properties or methods: [window.]location.property | method([parameters])
About this object In its place one level below window-style objects in the original document object hierarchy, the location object represents information about the URL of any currently open window, or of a specific frame. To display the URL of the current web page, you can reference the location object like this: document.write(location.href);
In this example, the href property evaluates to the URL, which is written to the current page in its entirety. The location object also allows you to access individual parts of the URL, as you will see in a moment. When you reference the location object in the framesetting document of a multiple-frame window, the location is given as the parent window’s URL, which appears in the Location (or Address) field of the browser. Each frame also has a location associated with it, although you may not see any overt reference to the frame’s URL in the browser. To get URL information about a document located in another frame, the reference to the location object must include the window frame reference. For example, if you have a window consisting of two frames, Table 28-1 shows the possible references to the location objects for all frames comprising the web presentation.
Note Scripts cannot alter the URL displayed in the browser’s Location/Address box. For security and privacy reasons, that text box cannot display anything other than the URL of a current page or URL in transit.
Most properties of a location object deal with network-oriented information. This information involves various data about the physical location of the document on the network, including the host server, the protocol being used, and other components of the URL. Given a complete URL for a typical World Wide Web page, the window.location object assigns property names to various segments of the URL, as shown here: http://www.example.com:80/promos/newproducts.html#giantGizmo
882
Chapter 28: Location and History Objects locationObject Property
Location Object References in a Two-Frame Browser Window Reference
Description
location (or window.location)
URL of frame displaying the document that runs the script statement containing this reference
parent.location
URL information for parent window that defines the
parent.frames[0].location
URL information for first visible frame
parent.frames[1].location
URL information for second visible frame
parent.otherFrameName.location
URL information for another named frame in the same frameset
The window.location object is handy when a script needs to extract information about the URL, perhaps to obtain a base reference on which to build URLs for other documents to be fetched as the result of user action. This object can eliminate a nuisance for web authors who develop sites on one machine and then upload them to a server (perhaps at an Internet service provider) with an entirely different directory structure. By building scripts to construct base references from the directory location of the current document, you can construct the complete URLs for loading documents. You don’t have to change the base reference data manually in your documents as you shift the files from computer to computer or from directory to directory. To extract the segment of the URL and place it in the enclosing directory, use the following: var baseRef = location.href.substring(0,location.href.lastIndexOf("/") + 1);
Caution Security alert: To allay fears of Internet security breaches and privacy invasions, scriptable browsers prevent your script in one frame from retrieving location object properties from other frames whose domain and server are not your own (unless you use signed scripts in NN4+/Moz or the user has set the IE browser to trust your site). This restriction puts a damper on many scripters’ well-meaning designs and aids for web watchers and visitors. If you attempt such property accesses, however, you receive an ‘‘access denied’’ (or similar) security warning dialog box.
883
Part IV: Document Objects Reference locationObject.hash Setting the value of some location properties is the preferred way to control which document gets loaded into a window or frame. Though you may expect to find a method somewhere in JavaScript that contains a plain-language Go or Open word (to simulate what you see in the browser menu bar), you point your browser to another URL by setting the window.location.href property to that URL, as in: window.location.href = "http://www.dannyg.com/";
The equals assignment operator (=) in this kind of statement is a powerful weapon. In fact, setting the location.href object to a URL of a different MIME type, such as one of the variety of sound and video formats, causes the browser to load those files into the plug-in or helper application designated in your browser’s settings. The location.assign() method was originally intended for internal use by the browser, but it is available for scripters (although I don’t recommend using it for navigation). Internet Explorer’s object model includes a window.navigate() method that also loads a document into a window, but you can’t use it for cross-browser applications. Two other methods complement the location object’s capability to control navigation. One method is the script equivalent of clicking Reload; the other method enables you to replace the current document’s entry in the history with that of the next URL of your script’s choice.
Properties hash Value: String
Read/Write
Compatibility: WinIE3+, MacIE3+, NN2+, Moz+, Safari+, Opera+, Chrome+ The hash mark (#) is a URL convention that directs the browser to an anchor located in the document. Any name you assign to an anchor (with the ... tag pair) becomes part of the URL after the hash mark. A location object’s hash property is the name of the anchor part of the current URL (which consists of the hash mark and the name). If you have written HTML documents with anchors and directed links to navigate to those anchors, you have probably noticed that although the destination location shows the anchor as part of the URL (for example, in the Location field), the window’s anchor value does not change as the user manually scrolls to positions in the document where other anchors are defined. An anchor appears in the URL only when the window has navigated there as part of a link or in response to a script that adjusts the URL. Just as you can navigate to any URL by setting the window.location.href property, you can navigate to another hash in the same document by adjusting only the hash property of the location without the hash mark (as shown in the following example). Listing 28-1 demonstrates how to use the hash property to access the anchor part of a URL. When you load the script in Listing 28-1, adjust the height of the browser window so that only one section is visible at a time. When you click a button, the script navigates to the next logical section in the progression and eventually takes you back to the top. The page won’t scroll any farther than the bottom
884
Chapter 28: Location and History Objects locationObject.hash of the document. Therefore, an anchor near the bottom of the page may not appear at the top of the browser window. LISTING 28-1
A Document with Anchors location.hash Property function goNextAnchor(where) { window.location.hash = where; } Top Section 1 Section 2 Section 3
885
Part IV: Document Objects Reference locationObject.host
Note The property assignment event handling technique used in the previous example and throughout the chapter is a deliberate simplification to make the code more readable. It is generally better to use the more modern approach of binding events using the addEventListener() (NN6+/Moz/W3C) or attachEvent() (IE5+) methods. A modern cross-browser event handling technique is explained in detail in Chapter 32, ‘‘Event Objects.’’ Several other chapters use the modern technique extensively.
Anchor names are passed as parameters with each button’s onclick event handler. Instead of going through the work of assembling a window.location value in the function by appending a literal hash mark and the value for the anchor, here we simply modify the hash property of the current window’s location. This is the preferred, cleaner method. If you attempt to read back the window.location.hash property in an added line of script, however, the window’s actual URL probably will not have been updated yet, and the browser will appear to be giving your script false information. To prevent this problem in subsequent statements of the same function, construct the URLs of those statements from the same variable values you use to set the window.location.hash property; don’t rely on the browser to give you the values you expect. Related Item: location.href property
host Value: String
Read/Write
Compatibility: WinIE3+, MacIE3+, NN2+, Moz+, Safari+, Opera+, Chrome+ The location.host property describes both the hostname and port of a URL. The port is included in the value only when the port is an explicit part of the URL. If you navigate to a URL that does not display the port number in the Location field of the browser, the location.host property returns the same value as the location.hostname property. As with the location.hostname property, the location.host property will likely come up blank for pages that you open from your local hard drive (localhost) in some browsers — for example, IE and WebKit browsers such as Chrome. Use the location.host property to extract the hostname:port part of the URL of any document loaded in the browser. This capability may be helpful for building a URL to a specific document that you want your script to access on-the-fly. Use the documents in Listing 28-2, Listing 28-3, and Listing 28-4 as tools to help you learn the values that the various window.location properties return. In the browser, open the file for Listing 28-2. This file creates a two-frame window. The left frame contains a temporary placeholder (see Listing 28-4) that displays some instructions. The right frame has a document (see Listing 28-3) that enables you to load URLs into the left frame and get readings on three different windows available: the parent window (which creates the multiframe window), the left frame, and the right frame. LISTING 28-2
Frameset for the Property Picker
886
Chapter 28: Location and History Objects locationObject.host window.location Properties
LISTING 28-3
Property Picker Property Picker var isNav = (typeof netscape != "undefined") ? true : false; function fillLeftFrame() { newURL = prompt("Enter the URL of a document to show in the left frame:",""); if (newURL != null && newURL != "") { parent.frames[0].location = newURL; } } function showLocationData(form) { for (var i = 0; i 5) { alert("My, my, you\’ve been busy. You have visited " + histCount + " pages so far."); } else { alert("You have been to " + histCount + " Web pages this session."); }
902
Chapter 28: Location and History Objects historyObject.forward() }
Related Items: None
Methods back() forward() Returns: Nothing Compatibility: WinIE3+, MacIE3+, NN2+, Moz+, Safari+, Opera+, Chrome+ Although the names might lead you to believe that these methods mimic the buttons on a browser’s toolbar, they do not. The history.back() method is window/frame specific, meaning that if you direct successive back() methods to a frame within a frameset, the method is ignored when it reaches the first document to be loaded into that frame. The Back button and the window.back() method unload the frameset and continue taking you back through the browser’s global history. If you deliberately lead a user to a dead end in your web site, you should make sure that the HTML document provides a way to navigate back to a recognizable spot. Because you can easily create a new window that has no toolbar or menu bar (non-Macintosh browsers), you may end up stranding your users because they have no way of navigating out of a cul-de-sac in such a window. A button in your document should give the user a way back to the last location. Unless you need to perform some additional processing prior to navigating to the previous location, you can simply place this method as the parameter to the event handler attribute of a button definition. To guarantee compatibility across all browsers, direct this method at the parent document when it’s used from within a frameset. Less likely to be scripted than the history.back() action is the method that performs the opposite action: navigating forward one step in the browser’s history list. The only time you can confidently use the history.forward() method is in balancing the use of the history.back() method in the same script — where your script closely keeps track of how many steps the script heads in either direction. Use the history.forward() method with extreme caution, and only after performing extensive user testing on your web pages to make sure that you’ve covered all user possibilities. Similar to navigating backward via history.back(), forward progress when using history.forward() extends only through the history listing for a given window or frame, not the entire browser history list. Listing 28-12 and Listing 28-13 provide a little workshop in which you can test the behavior of a variety of forms of backward and forward navigation in different browsers.
903
Part IV: Document Objects Reference historyObject.forward() LISTING 28-12
Navigation Lab Frameset Back and Forward
LISTING 28-13
Navigation Lab Control Panel Lab Controls Load a series of documents into the right frame by clicking some of these links (make a note of the sequence you click on):
Listing 28-1 Listing 28-5 Listing 28-9
Click on the various buttons below to see the results in this frameset:
history.back() and history.forward() for righthand frame:
history.back() for this frame:
history.back() for parent:
904
Chapter 28: Location and History Objects historyObject.go Related Items: history.go() method
go(relativeNumber | "URLOrTitleSubstring") Returns: Nothing Compatibility: WinIE3+, MacIE3+, NN2+, Moz+, Safari+, Opera+, Chrome+ Use the history.go() method to script navigation within the history list currently stored in the browser. If you elect to use a URL as a parameter, however, that precise URL must already exist in the history listing. Therefore, do not regard this method as an alternative to setting the window.location object to a brand-new URL. For navigating n steps in either direction along the history list, use the relativeNumber parameter of the history.go() method. This number is an integer value that indicates which item in the list to use, relative to the current location. For example, if the current URL is at the top of the list (that is, the Forward button in the toolbar is dimmed), you need to use the following method to jump to the URL two items backward in the list: history.go(-2);
In other words, the current URL is the equivalent of history.go(0) (a method that reloads the window). A positive integer indicates a jump that many items forward in the history list. Thus, history.go(-1) is the same as history.back(), whereas history.go(1) is the same as history.forward(). Alternatively, you can specify one of the URLs or document titles stored in the browser’s history list (titles appear in the Go/View menu). As security and privacy concerns have increased over time, this variant of the go() method has been reined in. It’s best not to use the string parameter in your scripting; in fact, none of the current browser versions support this variant. Like most other history methods, your script finds it difficult to manage the history list or the current URL’s spot in the queue. That fact makes it even more difficult for your script to determine intelligently how far to navigate in either direction, or to which specific URL or title matches it should jump. Use this method only for situations in which your web pages are in strict control of the user’s activity (or for designing scripts for yourself that automatically crawl around sites according to a fixed regimen). When you give the user control over navigation, you have no guarantee that the history list will be what you expect, and any scripts you write that depend on a history object will likely break. In practice, this method mostly performs a soft reload of the current window using the 0 parameter.
Tip If you are developing a page for all scriptable browsers, be aware that the reloading of a page with history.go(0) in IE often returns to the server to reload the page rather than reloading from the cache.
Listing 28-14 contains sample code that demonstrates how to navigate the history list via the go() method. Fill in either the number or text field of the page in Listing 28-14, and then click the associated button. The script passes the appropriate kind of data to the go() method. Unless you are using an older browser version, using the matching string text box and its button will do nothing. Be sure to use negative numbers for visiting a page earlier in the history.
905
Part IV: Document Objects Reference historyObject.go
Note
Mozilla browsers respond only to the integer offset approach to using the history.go() method.
LISTING 28-14
Navigating to an Item in History history.go() Method function doGoNum(form) { window.history.go(parseInt(form.histNum.value)); } function doGoTxt(form) { window.history.go(form.histWord.value); } Calling the history.go() method: Enter a number (+/-):
Enter either a word found in a document title in your history, or a word in a document URL in your history (remember, this will only work if your browser version is older):
Related Items: history.back(), history.forward(), location.reload() methods
906
Document and Body Objects
U
ser interaction is a vital aspect of client-side JavaScript scripting, and most of the communication between script and user takes place by way of the document object and its components. Understanding the scope of the document object within each of the object models you support is key to implementing successful cross-browser applications. Review the document object’s place within the original object hierarchy. Figure 29-1 shows that the document object is a pivotal point for a large percentage of objects. In the W3C DOM, the document object plays an even more important role as the container of all element objects delivered with the page: The document object is the root of the entire document tree. In fact, the document object and all that it contains is so big that we have divided its discussion into many chapters, each focusing on related object groups. This chapter looks at the document object and body object (which have conceptual relationships), whereas each of the succeeding chapters in this part of the book details objects contained by the document object.
907
IN THIS CHAPTER Accessing arrays of objects contained by the document object Writing new document content to a window or frame Using the body element for IE window measurements
Part IV: Document Objects Reference documentObject FIGURE 29-1
The basic document object model hierarchy. window frame self top parent history
Syntax Accessing document object properties or methods: [window.]document.property | method([parameters])
910
Event Handlers
Chapter 29: Document and Body Objects documentObject
About this object A document object encompasses the totality of what exists inside the content region of a browser window or window frame (excluding toolbars, status lines, and so on). The document is a combination of the content and interface elements that make the web page worth visiting. In modern browsers the document object also serves as the root node of a page’s hierarchical tree of nodes — that from which all other nodes grow. Because the document object isn’t explicitly represented in an HTML document by tags or any other notation, the original designers of JavaScript and object models decided to make the document object the portal to many settings that were represented in HTML as belonging to the body element. Therefore, the body element’s tag contains attributes for document-wide attributes, such as background color (bgcolor) and link colors in various states (alink, link, and vlink). The original designers decided to have the body element also serve as an HTML container for forms, links, and anchors. The document object, therefore, assumed a majority of the role of the body element. But even then, the document object became the most convenient place to bind some properties that extend beyond the body element, such as the title element and the URL of the link that referred the user to the page. When viewed within the context of the HTML source code, the original document object is somewhat schizophrenic. Even so, the document object has worked well as the basis for references to original object model objects, such as forms, images, and applets. This, of course, was before every HTML element, including the body element, was exposed as an object through modern object models. Amazingly, even with the IE4+ object model and W3C DOM — both of which treat the body element as an object separate from the document object — script compatibility with the original object model is quite easily accomplished. The document object has assumed a new schizophrenia, splitting its personality between the original object model and the one that places the document object at the root of the hierarchy, quite separate from the body element object it contains. The object knows which face to put on based on the rest of the script syntax that follows it. This means that quite often there are multiple ways to achieve the same reference. For example, you can use the following statement in all scriptable browsers to get the number of form objects in a document: document.forms.length
In IE4+, you can also use document.tags["form"].length
And in the W3C DOM as implemented in IE5+ and NN6+/Moz/Safari/Opera/Chrome, you can use document.getElementsByTagName("form").length
Modern browsers provide a generic approach to accessing elements (getElementsByTagName() method in the W3C DOM) to meet the requirements of object models that expose every HTML (and XML) element as an object. Promoting the body element to the ranks of exposed objects presented its own challenges to the new object model designers. The body element is the true owner of some properties that the original document object had to take on by default. Most properties that belonged to the original document object were renamed in their transfer to the body element. For example, the original document.alinkColor property is the body.aLink property in the modern model. But the bgColor property has not been renamed. For the sake of code compatibility, modern browsers recognize both properties, even though the W3C DOM has removed the old versions of the properties
911
Part IV: Document Objects Reference documentObject.activeElement for the newly conceived document object. Considering the fact that modern browsers are now prevalent, you should be able to stick with the new properties from here on.
Properties activeElement Value: Object reference
Read-Only
Compatibility: WinIE4+, MacIE4+, NN-, Moz+, Safari+, Opera+, Chrome+ Originally just in IE4+, a script can examine the document.activeElement property to see which element currently has focus. The value returned is an element object reference. You can use any of the properties and methods listed in Chapter 26 to find out more about the object. Although the element used to generate a mouse or keyboard event will most likely have focus, don’t rely on the activeElement property to find out which element generated an event. The IE event.srcElement property is far more reliable.
Example Use The Evaluator (see Chapter 4, ‘‘JavaScript Essentials’’) with IE4+ to experiment with the activeElement property. Type the following statement into the top text box: document.activeElement.value
After you press the Enter key, the Results box shows the value of the text box you just typed into (the very same expression you just typed). But if you then click the Evaluate button, you will see the value property of that button object appear in the Results box. Related Item: event.srcElement property
alinkColor bgColor fgColor linkColor vlinkColor Value: Hexadecimal triplet or color name string
Mostly Read/Write
Compatibility: WinIE3+, MacIE3+, NN2+, Moz+, Safari+, Opera+, Chrome+ These five properties are the script equivalent of the tag attributes of the same name (although the property names are case-sensitive). All five settings can be read via the document .body object in modern browsers. Values for all color properties can be either the common HTML hexadecimal triplet value (for example, "#00FF00") or any of the standard color names.
Example We select some color values at random to plug into three settings of the group of ugly colors for Listing 29-1. The smaller window displays a dummy button so that you can see how its display contrasts with color settings. Notice that the script sets the colors of the smaller window by rewriting the entire window’s HTML code. After changing colors, the script displays the color values in the original window’s textarea. Even though some colors are set with the color constant values, properties come
912
Chapter 29: Document and Body Objects documentObject.vlinkColor back in the hexadecimal triplet values. You can experiment to your heart’s content by changing color values in the listing. Every time you change the values in the script, save the HTML file and reload it in the browser. LISTING 29-1
Tweaking the Color of Page Elements Color Me // may be blocked at load time by browser popup blockers var newWindow = window.open("","","height=150,width=300"); function defaultColors() { return "bgcolor=’#c0c0c0’ vlink=’#551a8b’ link=’#0000ff’"; } function uglyColors() { return "bgcolor=’yellow’ vlink=’pink’ link=’lawngreen’"; } function showColorValues() { var result = ""; result += "bgColor: " + newWindow.document.bgColor + "\n"; result += "vlinkColor: " + newWindow.document.vlinkColor + "\n"; result += "linkColor: " + newWindow.document.linkColor + "\n"; document.forms[0].results.value = result; } // dynamically writes contents of another window function drawPage(colorStyle) { // work around popup blockers if (!newWindow || newWindow.closed) { newWindow = window.open("","","height=150,width=300"); } var thePage = ""; thePage += "Color SamplerJust so you can see the variety of items and colors, here\’s a link, and here is another link you can use on-line to visit and see how its color differs from the standard link."; thePage += ""; thePage += ""; thePage += ""; newWindow.document.write(thePage); newWindow.document.close(); showColorValues(); } // the following works properly only in Windows Navigator function setColors(colorStyle) { if (colorStyle == "default") { document.bgColor = "#c0c0c0"; } else { document.bgColor = "yellow"; } } // bind the event handlers function addEvent(elem, evtType, func) { if (elem.addEventListener) { elem.addEventListener(evtType, func, false); } else if (elem.attachEvent) { elem.attachEvent("on" + evtType, func); } else { elem["on" + evtType] = func; } } addEvent(window, "load", function() { addEvent(document.getElementById("default1"), "click", function(evt) {drawPage("default")}); addEvent(document.getElementById("weird1"), "click", function(evt) {drawPage("ugly")});
914
Chapter 29: Document and Body Objects documentObject.anchors[] addEvent(document.getElementById("default2"), "click", function(evt) {setColors("default")}); addEvent(document.getElementById("weird2"), "click", function(evt) {setColors("ugly")}); }); Try the two color schemes on the document in the small window.
These buttons change the current document.
Note The examples in this chapter take advantage of the modern approach to event handling, which involves the addEventListener() (NN6+/Moz/W3C) and attachEvent() (IE5+) methods. This event-handling technique is explained in detail in Chapter 32, ‘‘Event Objects.’’
Related Items: body.aLink, body.bgColor, body.link, body.text, body.vLink properties
anchors[] Value: Array of anchor objects
Read-Only
Compatibility: WinIE3+, MacIE3+, NN2+, Moz+, Safari+, Opera+, Chrome+ Anchor objects (described in Chapter 30, ‘‘Link and Anchor Objects’’) are points in an HTML document marked with tags. Anchor objects are referenced in URLs by a hash value between the page URL and anchor name. Like other object properties that contain a list of nested objects, the document.anchors property delivers an indexed array of anchors in a document. Use the array references to pinpoint a specific anchor for retrieving any anchor property. Anchor arrays begin their index counts with 0: The first anchor in a document, then, has the reference document.anchors[0]. And, as is true with any built-in array object, you can find out how many entries the array has by checking the length property. For example: alert("This document has " + document.anchors.length + " anchors.");
915
Part IV: Document Objects Reference documentObject.anchors[] The document.anchors property is read-only. To script navigation to a particular anchor, assign a value to the window.location or window.location.hash object, as described in the location object discussion in Chapter 28, ‘‘Location and History Objects.’’
Example In Listing 29-2, we append an extra script to Listing 28-1 to demonstrate how to extract the number of anchors in the document. The document dynamically writes the number of anchors found in the document. You will not likely ever need to reveal such information to users of your page, and the document.anchors property is not one that you will call frequently. The object model defines it automatically as a document property while defining actual anchor objects. LISTING 29-2
Using Anchors to Navigate Through a Page document.anchors Property function goNextAnchor(where) { window.location.hash = where; } // bind the event handlers function addEvent(elem, evtType, func) { if (elem.addEventListener) { elem.addEventListener(evtType, func, false); } else if (elem.attachEvent) { elem.attachEvent("on" + evtType, func); } else { elem["on" + evtType] = func; } } addEvent(window, "load", function() { addEvent(document.getElementById("next1"), "click", function(evt) {goNextAnchor("sec1")}); addEvent(document.getElementById("next2"), "click", function(evt) {goNextAnchor("sec2")}); addEvent(document.getElementById("next3"), "click", function(evt) {goNextAnchor("sec3")}); addEvent(document.getElementById("next4"), "click",
916
Chapter 29: Document and Body Objects documentObject.applets[] function(evt) {goNextAnchor("start")}); }); Top Section 1 Section 2 Section 3
document.write("There are " + document.anchors.length + " anchors defined for this document")
Related Items: anchor, location objects; document.links property
applets[] Value: Array of applet objects
Read-Only
Compatibility: WinIE3+, MacIE3+, NN2+, Moz+, Safari+, Opera+, Chrome+ The applets property refers to Java applets defined in a document by the tag. An applet is not officially an object in the document until the applet loads completely. Most of the work you do with Java applets from JavaScript takes place through the methods and variables defined inside the applet. Although you can reference an applet according to its indexed array position within the applets array, you will more likely use the applet object’s name in the reference to avoid any confusion.
917
Part IV: Document Objects Reference documentObject.baseURI
Example The document.applets property is defined automatically as the browser builds the object model for a document that contains applet objects. You will rarely access this property, except to determine how many applet objects a document has, as in this example: var numApplets = document.applets.length;
Related Item: applet object
baseURI Value: String
Read-Only
Compatibility: WinIE-, MacIE-, NN7+, Moz+, Safari+, Opera+, Chrome+ The baseURI property reveals the absolute base URI of the document. You can check the base URI of a document in the Evaluator (see Chapter 4, ‘‘JavaScript Essentials’’) by entering the following: document.baseURI
Related Item: document.documentURI property
bgColor (See alinkColor)
body Value: body element object
Read/Write
Compatibility: WinIE4+, MacIE4+, NN6+, Moz+, Safari+, Opera+, Chrome+ The document.body property is a shortcut reference to the body element object in modern object models. As you can see in the discussion of the body element object later in this chapter, that object has many key properties that govern the look of the entire page. Because the document object is the root of all references within any window or frame, the document.body property is easier to use to get to the body properties than the longer references normally used to access HTML element objects in both the IE4+ and W3C object models.
Example Use The Evaluator (see Chapter 4, ‘‘JavaScript Essentials’’) to examine properties of the body element object. First, to prove that the document.body is the same as the element object that comes back from longer references, enter the following statement into the top text box with either IE5+, NN6+/Moz, or some other W3C browser: document.body == document.getElementsByTagName("body")[0]
Next, check out the body object’s property listings later in this chapter and enter the listings into the top text box to review their results. For example: document.body.bgColor document.body.tagName
918
Chapter 29: Document and Body Objects documentObject.characterSet The main point to take from this example is that the document.body reference provides a simpler and more direct means of accessing a document’s body object without having to use the getElementsByTagName() method. Related Item: body element object
charset Value: String
Read/Write
Compatibility: WinIE4+, MacIE4+, NN-, Moz-, Safari+, Opera+, Chrome+ The charset property reveals the character set originally used by the browser (IE4+) to render the current document (the NN6+/Moz version of this property is called characterSet). You can find possible values for this property at ftp://ftp.isi.edu/in-notes/iana/assignments/character-sets
Each browser and operating system has its own default character set. Values may also be set through a tag.
Example Use The Evaluator (Chapter 4, ‘‘JavaScript Essentials’’) to experiment with the charset property. To see the default setting applied to the page, enter the following statement into the top text box: document.charset
If you are running IE5+ for Windows and you enter the following statement, the browser will apply a different character set to the page: document.charset = "iso-8859-2"
If your version of Windows does not have that character set installed in the system, the browser may ask permission to download and install the character set. Related Items: characterSet, defaultCharset properties
characterSet Value: String
Read/Write
Compatibility: WinIE-, MacIE-, NN6+, Moz+, Safari+, Opera+, Chrome+ The characterSet property reveals the character set used by the browser to render the current document (the IE version of this property is called charset). You can find possible values for this property at http://www.iana.org/assignments/character-sets
Each browser and operating system has its own default character set. Values may also be set through a tag.
919
Part IV: Document Objects Reference documentObject.compatMode
Example Use The Evaluator (Chapter 4, ‘‘JavaScript Essentials’’) to experiment with the characterSet property in NN6+/Moz. To see the default setting applied to the page, enter the following statement into the top text box: document.characterSet
Related Item: charset property
compatMode Value: String
Read-Only
Compatibility: WinIE6+, MacIE6+, NN7+, Moz+, Safari+, Opera+, Chrome+ The compatMode property reveals the compatibility mode for the document, as determined by the DOCTYPE element’s content. The value for this property can be one of the following string constants: BackCompat or CSS1Compat. The default setting for the compatMode property is BackCompat, which means that the document is not W3C standards-compliant; in other words, the document is in Quirks mode. Otherwise the document is in Strict mode and is W3C standards-compliant. By standards-compliant I’m referring to the CSS1 standard.
Example You may find it useful to check the compatibility mode of a document in order to carry out processing specific to one of the modes. Following is an example of how you might branch to carry out processing for backward-compatible documents: if (document.compatMode == "BackCompat") { // perform backward compatible processing }
Related Items: Standards Compatibility Modes (see Chapter 4, ‘‘JavaScript Essentials’’)
contentType Value: String
Read-Only
Compatibility: WinIE-, MacIE-, NN7+, Moz+, Safari-, Opera-, ChromeThe contentType property holds the content type (MIME type) of the document. For a normal HTML document, the value of this property is text/html.
cookie Value: String
Read/Write
Compatibility: WinIE3+, MacIE3+, NN2+, Moz+, Safari+, Opera+, Chrome+ The cookie mechanism in a web browser lets you store small pieces of information on the client computer in a reasonably secure manner. In other words, when you need some tidbit of information to persist at the client level while either loading diverse HTML documents or moving from one session to another, the cookie mechanism saves the day. The cookie is commonly used as a means to store the username and password you enter into a password-protected web site. The first time you enter this
920
Chapter 29: Document and Body Objects documentObject.cookie information into a form, the server-side form processing program has the browser write the information back to a cookie on your hard disk (usually after encrypting the password). Rather than bothering you to enter the username and password the next time you access the site, the server searches the cookie data stored for that particular server and extracts the username and password for automatic validation processing behind the scenes. Other applications of the cookie include storing user preferences and information about the user’s previous visit to the site. Preferences may include font styles or sizes and whether the user prefers viewing content inside a frameset or not. As shown in Chapter 57, ‘‘Application: Intelligent ‘Updated’ Flags’’ (on the CD-ROM), a time stamp of the previous visit can allow a coded HTML page to display highlighted images next to content that has changed since the user’s last visit, even if you have updated the page several times in the interim. Rather than hard-wiring new flags for your last visit, the scripts highlight what’s new for the visitor.
The cookie file Allowing some foreign server program to read from and write to your hard disk may give you pause, but browser cookie mechanisms don’t just open up your drive’s directory for the world to see (and to corrupt). Instead, the cookie mechanism provides access to a type of text file (Internet Explorer) or just one special text file (browsers other than IE) located in a platform-specific spot on your drive. In Mozilla-based browsers, for example, the cookie file is named cookies.txt and is located in a directory (whose name ends in .slt) within the browser’s profile area. In Windows, that location is C:\\Windows\Application Data\Mozilla\Profiles\[profilename]\; in Mac OSX, the location is [user]/Library/Mozilla/Profiles/[profilename]/. Internet Explorer for Windows uses a different filing system: all cookies for each domain are saved in a domain-specific file inside the C:\\Windows\Temporary Internet Files\ directory. Filenames begin with Cookie: and include the username and domain of the server that wrote the cookie. Safari cookies are recorded in an XML file named Cookies.plist within the [user]/Library/Cookies/ directory. Opera cookies are recorded in a binary file named cookies4.dat within the [user]\Application Data\Opera\Opera directory. Google Chrome cookies are recorded in a SQLite database file named Cookies within the [user]\Local Settings\Application Data\Google\Chrome\User Data\Default directory. Be aware that if you are testing with Google Chrome, your code will not work unless the files are coming from an HTTP server. Chrome intentionally disables cookies on file:/// documents. A cookie file is a text file. If curiosity drives you to open a cookie file, we recommend that you do so only with a copy saved in another directory or folder. Any alteration to the existing file can mess up whatever valuable cookies are stored there for sites you regularly visit. The data format for cookie files differs across browsers, in line with the different methodologies used for filing cookies. Inside the Mozilla file (after a few comment lines warning you not to manually alter the file) are lines of tab-delimited text. Each return-delimited line contains one cookie’s information. The cookie file is just like a text listing of a database. In each of the IE cookie files, the same data points are stored for a cookie as for Mozilla, but the items are in a return-delimited list. The structure of these files is of no importance to scripting cookies, because all browsers utilize the same syntax for reading and writing cookies through the document.cookie property.
Note As you experiment with browser’s cookies, you will be tempted to look into the cookie file after a script writes some data to the cookie. The cookie file usually will not contain the newly written data, because in most browsers cookies are transferred to disk only when the user quits the browser; conversely, the cookie file is read into the browser’s memory when it is launched. While you read, write, and delete cookies during a browser session, all activity is performed in memory (to speed up the process) to be saved later.
921
Part IV: Document Objects Reference documentObject.cookie
A cookie record Among the fields of each cookie record are the following (not necessarily in this order):
Domain of the server that created the cookie
Information on whether you need a secure HTTP connection to access the cookie
Pathname of URL(s) capable of accessing the cookie
Expiration date of the cookie
Name of the cookie entry
String data associated with the cookie entry
Note that cookies are domain-specific. In other words, if one domain creates a cookie, another domain cannot access it through the browser’s cookie mechanism behind your back. That reason is why it’s generally safe to store what we call throwaway passwords (the username/password pairs required to access some free registration-required sites) in cookies. Moreover, sites that store passwords in a cookie usually do so as encrypted strings, making it more difficult for someone to hijack the cookie file from your unattended PC and figure out what your personal password scheme may be. Cookies also have expiration dates. Because some browsers may allow no more than a fixed number of cookies (1000 in Firefox), the cookie file can get pretty full over the years. Therefore, if a cookie needs to persist past the current browser session, it should have an expiration date established by the cookie writer. Browsers automatically clean out any expired cookies. Not all cookies have to last beyond the current session, however. In fact, a scenario in which you use cookies temporarily while working your way through a web site is quite typical. Many shopping sites employ one or more temporary cookie records to behave as the shopping cart for recording items you intend to purchase. These items are copied to the order form at checkout time. But after you submit the order form to the server, that client-side data has no particular value. As it turns out, if your script does not specify an expiration date, the browser keeps the cookie fresh in memory without writing it to the cookie file. When you quit the browser, that cookie data disappears as expected.
JavaScript access Scripted access to cookies from JavaScript is limited to setting the cookie (with a number of optional parameters) and getting the cookie data (but with none of the parameters). The original object model defines cookies as properties of documents, but this description is somewhat misleading. If you use the default path to set a cookie (that is, the current directory of the document whose script sets the cookie in the first place), all documents in that same server directory have read and write access to the cookie. A benefit of this arrangement is that if you have a scripted application that contains multiple documents, all documents served from the same directory can share the cookie data. Modern browsers, however, impose a limit of 20 named cookie entries (that is, one name/value pair) for any domain. If your cookie requirements are extensive, you need to fashion ways of concatenating cookie data. (We do this in the Decision Helper application in Chapter 58 on the CD-ROM.)
Saving cookies To write cookie data to the cookie file, you use a simple JavaScript assignment operator with the document.cookie property. But the formatting of the data is crucial to achieving success. Here is the syntax for assigning a value to a cookie (optional items are in brackets; placeholders for data you supply are in italics): document.cookie = "cookieName=cookieData [; expires=timeInGMTString]
922
Chapter 29: Document and Body Objects documentObject.cookie [; path=pathName] [; domain=domainName] [; secure]"
Let’s examine each of the properties individually.
Name/Data Each cookie must have a name and a string value (even if that value is an empty string). Such name/value pairs are fairly common in HTML, but they look odd in an assignment statement. For example, if you want to save the string ‘‘Fred’’ to a cookie named ‘‘userName,’’ the JavaScript statement is document.cookie = "userName=Fred";
If the browser sees no existing cookie in the current domain with this name, it automatically creates the cookie entry for you; if the named cookie already exists, the browser replaces the old data with the new data. Retrieving the document.cookie property at this point yields the following string: userName=Fred
You can omit all the other cookie-setting properties, in which case the browser uses default values, as explained in a following section. For temporary cookies (those that don’t have to persist beyond the current browser session), the name/value pair is usually all you need. The entire name/value pair must be a single string with no semicolons, commas, or character spaces. To take care of spaces between words, preprocess the value with the JavaScript encodeURIComponent() function, which URI-encodes the spaces as %20 — and then be sure to convert the value to restore the human-readable spaces (through decodeURIComponent()) when you retrieve the cookie later. You cannot save a JavaScript array or object to a cookie. But with the help of the Array.join() method, you can convert an array to a string; use String.split() to re-create the array after reading the cookie at a later time.
Expires Expiration dates, when supplied, must be passed as Greenwich Mean Time (GMT) strings (see Chapter 17, ‘‘The Date Object,’’ about time data). To calculate an expiration date based on today’s date, use the JavaScript Date object as follows: var exp = new Date(); var oneYearFromNow = exp.getTime() + (365 * 24 * 60 * 60 * 1000); exp.setTime(oneYearFromNow);
Since the getTime() and setTime() methods operate in milliseconds, the year you’re adding to the current date must be converted to milliseconds. After making the calculation, the date is converted to the accepted GMT string format: document.cookie = "userName=Fred; expires=" + exp.toGMTString();
In the cookie file, the expiration date and time is stored as a numeric value (in seconds), but to set it, you need to supply the time in GMT format. You can delete a cookie before it expires by setting the
923
Part IV: Document Objects Reference documentObject.cookie named cookie’s expiration date to a time and date earlier than the current time and date. The safest expiration parameter is expires=Thu, 01-Jan-70 00:00:01 GMT;
Omitting the expiration date signals to the browser that this cookie is temporary. The browser never writes it to the cookie file and forgets it when you quit the browser.
Path For client-side cookies, the default path setting (the current directory) is usually the best choice. You can, of course, create a duplicate copy of a cookie with a separate path (and domain) so that the same data is available to a document located in another area of your site (or the Web).
Domain To help synchronize cookie data with a particular document (or group of documents), the browser matches the domain of the current document with the domain values of cookie entries in the cookie file. Therefore, if you were to display a list of all cookie data contained in a document.cookie property, you would get back all the name-value cookie pairs from the cookie file whose domain parameter matches that of the current document. Unless you expect the document to be replicated in another server within your domain, you can usually omit the domain parameter when saving a cookie. Default behavior automatically supplies the domain of the current document to the cookie file entry. Be aware that a domain setting must have at least two periods, such as .google.com .hotwired.com
Or, you can write an entire URL to the domain, including the http:// protocol.
SECURE If you omit the SECURE parameter when saving a cookie, you imply that the cookie data is accessible to any document or server-side program from your site that meets the other domain- and path-matching properties. For client-side scripting of cookies, you should omit this parameter when saving a cookie.
Retrieving cookie data Cookie data retrieved through JavaScript arrives as one string, which contains the whole name-data pair. Even though the cookie file stores other parameters for each cookie, you can retrieve only the name-data pairs through JavaScript. Moreover, when two or more (up to a maximum of 20) cookies meet the current domain criteria, these cookies are also lumped into that string, delimited by a semicolon and space. For example, a document.cookie string may look like this: userName=Fred; password=NikL2sPacU
In other words, you cannot treat named cookies as objects. Instead, you must parse the entire cookie string, extracting the data from the desired name-data pair.
924
Chapter 29: Document and Body Objects documentObject.cookie When you know that you’re dealing with only one cookie (and that no more will ever be added to the domain), you can customize the extraction based on known data, such as the cookie name. For example, with a cookie name that is seven characters long, you can extract the data with a statement such as this: var data = decodeURIComponent(document.cookie.substring (7,document.cookie.length));
The first parameter of the substring() method includes the equal sign to separate the name from the data; this is where the 7 comes from in the code. This example works with single cookies only because it assumes that the cookie starts at the beginning of the cookie file, which may not be the case if the file contains multiple cookies. A better approach to cookie extraction is to create a general-purpose function that can work with single- or multiple-entry cookies. For example: function getCookieData(labelName) { var labelLen = labelName.length; // read cookie property only once for speed var cookieData = document.cookie; var cLen = cookieData.length; var i = 0; var cEnd; while (i < cLen) { var j = i + labelLen; if (cookieData.substring(i,j) == labelName) { cEnd = cookieData.indexOf(";",j); if (cEnd == -1) { cEnd = cookieData.length; } return decodeURIComponent(cookieData.substring(j+1, cEnd)); } i++; } return ""; }
Calls to this function pass the label name of the desired cookie as a parameter. The function parses the entire cookie string, chipping away any mismatched entries (through the semicolons) until it finds the cookie name. If all of this cookie code still makes your head hurt, you can turn to a set of functions devised by experienced JavaScripter and web site designer Bill Dortch of hIdaho Design. His cookie functions provide generic access to cookies that you can use in all of your cookie-related pages. Listing 29-3 shows Bill’s cookie functions, which include a variety of safety nets for date calculation bugs that appeared in some legacy versions of Netscape Navigator. The code is updated with modern URL encoding and decoding methods. Don’t be put off by the length of the listing: Most of the lines are comments.
925
Part IV: Document Objects Reference documentObject.cookie LISTING 29-3
Bill Dortch’s Cookie Functions Cookie Functions // // Cookie Functions -- "Night of the Living Cookie" Version (25-Jul-96) // // Written by: Bill Dortch, hIdaho Design // The following functions are released to the public domain. // // This version takes a more aggressive approach to deleting // cookies. Previous versions set the expiration date to one // millisecond prior to the current time; however, this method // did not work in Netscape 2.02 (though it does in earlier and // later versions), resulting in "zombie" cookies that would not // die. DeleteCookie now sets the expiration date to the earliest // usable date (one second into 1970), and sets the cookie’s value // to null for good measure. // // Also, this version adds optional path and domain parameters to // the DeleteCookie function. If you specify a path and/or domain // when creating (setting) a cookie**, you must specify the same // path/domain when deleting it, or deletion will not occur. // // The FixCookieDate function must now be called explicitly to // correct for the 2.x Mac date bug. This function should be // called *once* after a Date object is created and before it // is passed (as an expiration date) to SetCookie. Because the // Mac date bug affects all dates, not just those passed to // SetCookie, you might want to make it a habit to call // FixCookieDate any time you create a new Date object: // // var theDate = new Date(); // FixCookieDate (theDate); // // Calling FixCookieDate has no effect on platforms other than // the Mac, so there is no need to determine the user’s platform // prior to calling it. // // This version also incorporates several minor coding improvements. // // **Note that it is possible to set multiple cookies with the same // name but different (nested) paths. For example: // // SetCookie ("color","red",null,"/outer"); // SetCookie ("color","blue",null,"/outer/inner");
926
Chapter 29: Document and Body Objects documentObject.cookie // // However, GetCookie cannot distinguish between these and will return // the first cookie that matches a given name. It is therefore // recommended that you *not* use the same name for cookies with // different paths. (Bear in mind that there is *always* a path // associated with a cookie; if you don’t explicitly specify one, // the path of the setting document is used.) // // Revision History: // // "JavaScript Bible 6th Edition" Version (28-July-2006) // - Replaced deprecated escape()/unescape() functions with // encodeURI() and decodeURI() functions // // "Toss Your Cookies" Version (22-Mar-96) // - Added FixCookieDate() function to correct for Mac date bug // // "Second Helping" Version (21-Jan-96) // - Added path, domain and secure parameters to SetCookie // - Replaced home-rolled encode/decode functions with // new (then) escape/unescape functions // // "Free Cookies" Version (December 95) // // // For information on the significance of cookie parameters, // and on cookies in general, please refer to the official cookie // spec, at: // // http://www.netscape.com/newsref/std/cookie_spec.html // //****************************************************************** // // "Internal" function to return the decoded value of a cookie // function getCookieVal (offset) { var endstr = document.cookie.indexOf (";", offset); if (endstr == -1) { endstr = document.cookie.length; } return decodeURI(document.cookie.substring(offset, endstr)); } // // // // // //
Function to correct for 2.x Mac date bug. Call this function to fix a date object prior to passing it to SetCookie. IMPORTANT: This function should only be called *once* for any given date object! See example at the end of this document.
continued
927
Part IV: Document Objects Reference documentObject.cookie LISTING 29-3
(continued)
function FixCookieDate (date) { var base = new Date(0); var skew = base.getTime(); // dawn of (Unix) time - should be 0 if (skew > 0) { // Except on the Mac - ahead of its time date.setTime (date.getTime() - skew); } } // // Function to return the value of the cookie specified by "name". // name - String object containing the cookie name. // returns - String object containing the cookie value, or null if // the cookie does not exist. // function GetCookie (name) { var arg = name + "="; var alen = arg.length; var clen = document.cookie.length; var i = 0; while (i < clen) { var j = i + alen; if (document.cookie.substring(i, j) == arg) { return getCookieVal (j); } i = document.cookie.indexOf(" ", i) + 1; if (i == 0) { break; } } return null; } // // // // // // // // // // //
928
Function to create or update a cookie. name - String object containing the cookie name. value - String object containing the cookie value. May contain any valid string characters. [expires] - Date object containing the expiration data of the cookie. If omitted or null, expires the cookie at the end of the current session. [path] - String object indicating the path for which the cookie is valid. If omitted or null, uses the path of the calling document.
Chapter 29: Document and Body Objects documentObject.cookie // [domain] - String object indicating the domain for which the cookie // is valid. If omitted or null, uses the domain of the calling // document. // [secure] - Boolean (true/false) value indicating whether cookie // transmission requires a secure channel (HTTPS). // // The first two parameters are required. The others, if supplied, must // be passed in the order listed above. To omit an unused optional // field, use null as a place holder. For example, to call SetCookie // using name, value and path, you would code: // // SetCookie ("myCookieName", "myCookieValue", null, "/"); // // Note that trailing omitted parameters do not require a placeholder. // // To set a secure cookie for path "/myPath", that expires after the // current session, you might code: // // SetCookie (myCookieVar, cookieValueVar, null, "/myPath", null, // true); // function SetCookie (name,value,expires,path,domain,secure) { document.cookie = name + "=" + encodeURIComponent (value) + ((expires) ? "; expires=" + expires.toGMTString() : "") + ((path) ? "; path=" + path : "") + ((domain) ? "; domain=" + domain : "") + ((secure) ? "; secure" : ""); } // Function to delete a cookie. (Sets expiration date to start of epoch) // name String object containing the cookie name // path String object containing the path of the cookie to delete. // This MUST be the same as the path used to create the // cookie, or null/omitted if // no path was specified when creating the cookie. // domain - String object containing the domain of the cookie to // delete. This MUST be the same as the domain used to // create the cookie, or null/omitted if no domain was // specified when creating the cookie. // function DeleteCookie (name,path,domain) { if (GetCookie(name)) { document.cookie = name + "=" + ((path) ? "; path=" + path : "") + ((domain) ? "; domain=" + domain : "") + "; expires=Thu, 01-Jan-70 00:00:01 GMT"; } } continued
929
Part IV: Document Objects Reference documentObject.cookie LISTING 29-3
(continued)
// // Examples // var expdate = new Date (); FixCookieDate (expdate); // Correct for Mac date bug (call only once) expdate.setTime (expdate.getTime() + (24 * 60 * 60 * 1000)); // 24 hrs SetCookie ("ccpath", "http://www.hidaho.com/colorcenter/", expdate); SetCookie ("ccname", "hIdaho Design ColorCenter", expdate); SetCookie ("tempvar", "This is a temporary cookie."); SetCookie ("ubiquitous", "This cookie will work anywhere in this i domain",null,"/"); SetCookie ("paranoid", "This cookie requires secure i communications",expdate,"/",null,true); SetCookie ("goner", "This cookie must die!"); document.write (document.cookie + ""); DeleteCookie ("goner"); document.write (document.cookie + ""); document.write ("ccpath = " + GetCookie("ccpath") + ""); document.write ("ccname = " + GetCookie("ccname") + ""); document.write ("tempvar = " + GetCookie("tempvar") + "");
Extra batches You may design a site that needs more than 20 cookies for a given domain. For example, in a shopping site, you never know how many items a customer may load into the shopping cart cookie. Because each named cookie stores plain text, you can create your own text-based data structures to accommodate multiple pieces of information per cookie. (But also watch out for a practical limit of 2,000 characters per name/value pair within the 4,000 character maximum for any domain’s combined cookies.) The trick is determining a delimiter character that won’t be used by any of the data in the cookie. In Decision Helper (in Chapter 58), for example, we use a period to separate multiple integers stored in a cookie. With the delimiter character established, you must then write functions that concatenate these ‘‘subcookies’’ into single cookie strings and extract them on the other side. It’s a bit more work, but well worth the effort, to have the power of persistent data on the client.
Example Experiment with the last group of statements in Listing 29-3 to create, retrieve, and delete cookies. You can also experiment with The Evaluator by assigning a name/value pair string to document.cookie, and then examining the value of the cookie property. Related Items: String object methods (see Chapter 15, ‘‘The String Object’’)
930
Chapter 29: Document and Body Objects documentObject.designMode
defaultCharset Value: String
Read/Write
Compatibility: WinIE4+, MacIE4+, NN-, Moz-, Safari+, Opera-, Chrome+ The defaultCharset property reveals the character set used by the browser to render the current document. You can find possible values for this property at http://www.iana.org/assignments/character-sets
Each browser and operating system has its own default character set. Values may also be set through a tag. The difference between the defaultCharset and charset properties is not clear, especially because both are read/write (although modifying the defaultCharset property has no visual effect on the page). However, if your scripts temporarily modify the charset property, you can use the defaultCharset property to return to the original character set: document.charset = document.defaultCharset;
Example Use The Evaluator (Chapter 4, ‘‘JavaScript Essentials’’) to experiment with the defaultCharset property. To see the default setting applied to the page, enter the following statement into the top text box: document.defaultCharset
Related Items: charset, characterSet properties
defaultView Value: window or frame object reference
Read-Only
Compatibility: WinIE-, MacIE-, NN6+, Moz+, Safari+, Opera+, Chrome+ The defaultView property returns a reference to the object serving as the viewer for the document. The viewer is responsible for rendering the document, and in Mozilla the object returned in the defaultView property is the window or frame object that contains the document. This W3C DOM Level 2 property provides access to the computed CSS values being applied to any HTML element (through the document.defaultView.getComputedStyle() method). Related Items: window and frame properties; window.getComputedStyle() method
designMode Value: String
Read/Write
Compatibility: WinIE5+, MacIE-, NN7.1, Moz1.4+, Safari+, Opera+, Chrome+ The designMode property is applicable for IE only when WinIE5+ technology is being used as a component in another application. The property controls whether the browser module is being used for HTML editing. Modifying the property from within a typical HTML page in the IE5+ browser has no effect. But on the Mozilla side, the property can be used to turn an iframe element’s document object into an HTML editable document. Visit http://www.mozilla.org/editor for current details and examples.
931
Part IV: Document Objects Reference documentObject.doctype
doctype Value: DocumentType object reference
Read-Only
Compatibility: WinIE+, MacIE5+, NN6+, Moz+, Safari+, Opera+, Chrome+ The doctype property comes from the W3C Core DOM and returns a DocumentType object — a representation of the Document Type Definition (DTD) information for the document. The DocumentType object (if one is explicitly defined in the source code) is the first child node of the root document node (and is thus a sibling to the HTML element). In IE, this property is only supported in XML documents; HTML documents always return null. Table 29-1 shows the typical DocumentType object property list and values for a generic HTML page. Future DOM specifications will allow these properties to be read/write. Related Items: Node object (see Chapter 25, ‘‘Document Object Model Essentials’’)
Example Take a look at the document.doctype object by entering the following line of code in the bottom text field of the Evaluator web page (see Chapter 4): document.doctype
If you pay close attention you’ll notice that the publicId property is actually set to -//W3C// DTD HTML 4.01 Transitional//EN, which is different from the value shown in Table 29-1. This reveals the fact that the Evaluator page declares itself as an HTML 4.01 document.
932
Chapter 29: Document and Body Objects documentObject.domain
documentElement Value: HTML or XML element object reference
Read-Only
Compatibility: WinIE5+, MacIE5+, NN6+, Moz+, Safari+, Opera+, Chrome+ The documentElement property returns a reference to the HTML (or XML) element object that contains all of the content of the current document. The naming of this property is a bit misleading, because the root document node is not an element, but its only child node is the HTML (or XML) element for the page. At best, you can think of this property as providing scripts with an element face to the document object and document node associated with the page currently loaded in the browser. The document.documentElement object represents the html element for a page, whereas docoument.body represents the body element. This explains why document.body is a child of the document.documentElement object.
Example Use The Evaluator (Chapter 4, ‘‘JavaScript Essentials’’) to examine the behavior of the documentElement property. In IE5+/W3C, enter the following statement into the top text field: document.documentElement.tagName
The result is HTML, as expected. Related Item: ownerDocument property (see Chapter 26, ‘‘Generic HTML Element Objects’’)
documentURI Value: String
Read-Only
Compatibility: WinIE-, MacIE-, NN8+, Moz1.7+, Safari+, Opera+, Chrome+ The documentURI property contains the location of the document. This is the W3C DOM Level 3 equivalent of the non-W3C DOM location.href property. Use The Evaluator (Chapter 4) to view the document URI by entering the following: document.documentURI
Related Item: document.baseURI property
domain Value: String
Read/Write
Compatibility: WinIE4+, MacIE4+, NN3+, Moz+, Safari+, Opera+, Chrome+ Security restrictions can get in the way of sites that have more than one server at their domain. Because some objects, especially the location object, prevent access to properties of other servers displayed in other frames, legitimate access to those properties is blocked. For example, it’s not uncommon for popular sites to have their usual public access site on a server named something such as www.popular.com. If a page on that server includes a front end to a site search engine located at search.popular.com, visitors who use browsers with these domain restrictions security restrictions are denied access.
933
Part IV: Document Objects Reference documentObject.embeds[] To guard against that eventuality, a script in documents from two servers can instruct the browser to think both servers are the same. In the preceding example, you would set the document.domain property in both documents to popular.com. Without specifically setting the property, the default value includes the server name as well, thus causing a mismatch between hostnames. Before you start thinking that you can spoof your way into other servers, be aware that you can set the document.domain property only to servers with the same domain (following the two-dot rule) as the document doing the setting. Therefore, documents originating only from xxx.popular.com can set their document.domain properties to popular.com server. Related Items: window.open() method; window.location object; security (see Chapter 49, ‘‘Security and Netscape Signed Scripts’’ on the CD-ROM)
embeds[] Value: Array of embed element objects
Read-Only
Compatibility: WinIE4+, MacIE4+, NN3+, Moz+, Safari+, Opera+, Chrome+ Although now supplanted by the tag, the tag used to be the markup that loaded data requiring a plug-in application to play or display. The document.embeds property is an array of embed element objects within the document: var count = document.embeds.length;
Related Item: embed element object (see Chapter 44, ‘‘Embedded Objects’’)
expando Value: Boolean
Read/Write
Compatibility: WinIE4+, MacIE4+, NN-, Moz-, Safari-, Opera-, ChromeMicrosoft calls any custom property that is not a native property of the document object an expando property. By default, most objects in recent generations of browsers allow scripts to add new properties of objects as a way to temporarily store data without explicitly defining global variables. For example, if you want to maintain an independent counter of how often a function is invoked, you can create a custom property of the document object and use it as the storage facility: document.counter = 0;
IE4+ enables you to control whether the document object is capable of accepting expando properties. The default value of the document.expando property is true, thus allowing custom properties. But the potential downside to this permissiveness, especially during the page construction phase, is that a misspelled native property name is gladly accepted by the document object. You may not be aware of why the title bar of the browser window doesn’t change when you assign a new string to the document.Title property (which, in the case-sensitive world of JavaScript, is distinct from the native document.title property).
Example Use The Evaluator (Chapter 4, ‘‘JavaScript Essentials’’) to experiment with the document .expando property in IE4+. Begin by proving that the document object can normally accept custom properties. Type the following statement into the top text field: document.spooky = "Boo!"
934
Chapter 29: Document and Body Objects documentObject.fileSize This property is now set and stays that way until the page is either reloaded or unloaded. Now freeze the document object’s properties with the following statement: document.expando = false
If you try to add a new property, such as the following, you receive an error: document.happy = "tra la"
Interestingly, even though document.expando is turned off, the first custom property is still accessible and modifiable. Related Item: prototype property of custom objects (see Chapter 23, ‘‘Function Objects and Custom Objects’’)
Compatibility: WinIE4+, MacIE4+, NN-, Moz-, Safari-, Opera-, ChromeThese three IE-specific properties return information about the file that holds the current document. The first two properties (not implemented in MacIE) reveal the dates on which the current document’s file was created and modified. For an unmodified file, its creation and modified dates are the same. The fileSize property reveals the number of bytes of the file. Date values returned for the first two properties are in a format similar to mm/dd/yyyy. Note, however, that the values contain only the date and not the time. In any case, you can use the values as the parameter to a new Date() constructor function. You can then use date calculations for such information as the number of days between the current day and the most recent modification. Not all servers may provide the proper date or size information about a file, or in a format that IE can interpret. Test your implementation on the deployment server to ensure compatibility. Also, be aware that these properties can be read-only for a file that is loaded in the browser. JavaScript by itself cannot get this information about files that are on the server, but not loaded into the browser.
Example Listing 29-4 dynamically generates several pieces of content relating to the creation and modification dates of the file, as well as its size. More importantly, the listing demonstrates how to turn a value returned by the file date properties into a genuine date object that can be used for date calculations. In the case of Listing 29-4, the calculation is the number of full days between the creation date and the day someone views the file. Notice that the dynamically generated content is added very simply through the innerText properties of carefully located span elements in the body content.
935
Part IV: Document Objects Reference documentObject.fileSize LISTING 29-4
Displaying File Information for a Web Page fileCreatedDate and fileModifiedDate Properties function fillInBlanks() { var created = document.fileCreatedDate; var modified = document.fileModifiedDate; document.getElementById("created").innerText = created; document.getElementById("modified").innerText = modified; var createdDate = new Date(created).getTime(); var today = new Date().getTime(); var diff = Math.floor((today - createdDate) / (1000*60*60*24)); document.getElementById("diff").innerText = diff; document.getElementById("size").innerText = document.fileSize; } // bind the event handlers function addEvent(elem, evtType, func) { if (elem.addEventListener) { elem.addEventListener(evtType, func, false); } else if (elem.attachEvent) { elem.attachEvent("on" + evtType, func); } else { elem["on" + evtType] = func; } } addEvent(window, "load", function() { fillInBlanks(); }); fileCreatedDate and fileModifiedDate Properties
This file ( bytes) was created on and most recently modified on .
936
Chapter 29: Document and Body Objects documentObject.forms[]
It has been days since this file was created.
Related Item: lastModified property
forms[] Value: Array
Read-Only
Compatibility: WinIE3+, MacIE3+, NN2+, Moz+, Safari+, Opera+, Chrome+ As we show in Chapter 34, ‘‘Form and Related Objects,’’ which is dedicated to the form object, an HTML form (anything defined inside a ... tag pair) is a JavaScript object unto itself. You can create a valid reference to a form according to its name (assigned through a form’s name attribute). For example, if a document contains the following form definition: input item definitions
then your scripts can refer to the form object by name: document.phoneData
However, a document object also tracks its forms in another way: as an array of form objects. The first item of a document.forms array is the form that loaded first (it was foremost from the top of the HTML code). If your document defines one form, the forms property is an array one entry in length; with three separate forms in the document, the array is three entries long. Use standard array notation to reference a particular form from the document.forms array. For example, the first form in a document (the zeroth entry of the document.forms array) is referenced as document.forms[0]
Any of the form object’s properties or methods are available by appending the desired property or method name to the reference. For example, to retrieve the value of an input text field named homePhone from the second form of a document, the reference you use is document.forms[1].homePhone.value
One advantage to using the document.forms property for addressing a form object or element instead of the actual form name is that you may be able to generate a library of generalizable scripts that know how to cycle through all available forms in a document and then hunt for a form that has some special element and property. The following script fragment (part of a repeat loop described more
937
Part IV: Document Objects Reference documentObject.forms[] fully in Chapter 21, ‘‘Control Structures and Exception Handling’’) uses a loop-counting variable (i) to help the script check all forms in a document: for (var i = 0; i < document.forms.length; i++) { if (document.forms[i]. ... ) { statements } }
One more variation on forms array references enables you to substitute the name of a form (as a string) for the forms array index. For example, the form named phoneData can be referenced as: document.forms["phoneData"]
If you take a lot of care in assigning names to objects, you will likely prefer the document .formName style of referencing forms. In this book, you see both indexed array and form name style references. The advantage of using name references is that even if you redesign the page and change the order of forms in the document, references to the named forms will still be valid, whereas the index numbers of the forms will have changed. Also see the discussion in Chapter 34, ‘‘Form and Related Objects,’’ of the form object and how to pass a form’s data to a function.
Example The document in Listing 29-5 is set up to display an alert dialog box that simulates navigation to a particular music site, based on the selected status of the blues check box. The user input here is divided into two forms: one form with the check box and the other form with the button that does the navigation. A block of copy fills the space in between. Clicking the bottom button (in the second form) triggers the function that fetches the checked property of the blues check box by using the document.forms[i] array as part of the address. LISTING 29-5
A Simple Form Example document.forms example function goMusic() { if (document.forms[0].bluish.checked) { alert("Now going to the Blues music area..."); } else { alert("Now going to the Rock music area..."); } }
938
Chapter 29: Document and Body Objects documentObject.frames[] // bind the event handlers function addEvent(elem, evtType, func) { if (elem.addEventListener) { elem.addEventListener(evtType, func, false); } else if (elem.attachEvent) { elem.attachEvent("on" + evtType, func); } else { elem["on" + evtType] = func; } } addEvent(window, "load", function() { addEvent(document.getElementById("visit"), "click", goMusic); }); Check here if you’ve got the blues. M o r e C o p y
Related Item: form object (see Chapter 34, ‘‘Form and Related Objects’’)
Part IV: Document Objects Reference documentObject.height The document.frames property is similar to the window.frames property, but its association with the document object may seem a bit illogical at times. The objects contained by the array returned from the property are window objects, which means they are the window objects of any defined frame elements (from a framesetting document) or iframe elements (from a plain HTML document). Distinguishing the window objects from the iframe element objects is important. Window objects have different properties and methods from the frame and iframe element objects. The latter’s properties typically represent the attributes for those element’s tags. If a document contains no iframe elements, the document.frames array length is zero. Although you can access an individual frame object through the typical array syntax (for example, document.frames[0]), you can also use alternate syntax that Microsoft provides for collections of
objects. The index number can also be placed inside parentheses, as in: document.frames(0)
Moreover, if the frames have values assigned to their name attributes, you can use the name (in string form) as a parameter: document.frames("contents")
And if the collection of frames has more than one frame with the same name, you must take special care. Using the duplicated name as a parameter forces the reference to return a collection of frame objects that share that name. Or, you can limit the returned value to a single instance of the duplicate-named frames by specifying an optional second parameter indicating the index. For example, if a document has two iframe elements with the name contents, a script could reference the second window object as: document.frames("contents", 1)
For the sake of cross-browser compatibility, my preference for referencing frame window objects is through the window.frames property.
Example See Listings 27-7 and 27-8 for examples of using the frames property with window objects. Related Item: window.frames property
height width Value: Integer
Read-Only
Compatibility: WinIE-, MacIE-, NN4+, Moz+, Safari+, Opera-, Chrome+ The height and width properties provide the pixel dimensions of the content within the current window (or frame). If the document’s content is smaller than the size of the browser’s content region, the dimensions returned by these properties include the blank space to the right or bottom edges of the content area of the window. But if the content extends beyond the viewable edges of the content region, the dimensions include the unseen content as well. The corresponding measures in Internet Explorer are the document.body.scrollHeight and document.body.scrollWidth properties. These IE properties are also supported by most modern browsers.
940
Chapter 29: Document and Body Objects documentObject.images[]
Example Use The Evaluator (Chapter 4, ‘‘JavaScript Essentials’’) to examine the height and width properties of that document. Enter the following statement into the top text box and click the Evaluate button: "height=" + document.height + "; width=" + document.width
Resize the window so that you see both vertical and horizontal scroll bars in the browser window and click the Evaluate button again. If either or both numbers get smaller, the values in the Results box are the exact size of the space occupied by the document. But if you expand the window to well beyond where the scroll bars are needed, the values extend to the number of pixels in each dimension of the window’s content region. Related Items: document.body.scrollHeight, document.body.scrollWidth properties
images[] Value: Array
Read-Only
Compatibility: WinIE4+, MacIE3+, NN3+, Moz+, Safari+, Opera+, Chrome+ With images treated as first-class objects, beginning with NN3 and IE4, it’s only natural for a document to maintain an array of all the image tags defined on the page (just as it does for links and anchors). The primary importance of having images as objects is that you can modify their content (the source file associated with the rectangular space of the image) on-the-fly. You can find details about the image object in Chapter 31, ‘‘Image, Area, Map, and Canvas Objects.’’ Use image array references to pinpoint a specific image for the retrieval of any image property, or for assigning a new image file to its src property. Image arrays begin their index counts with 0: The first image in a document has the reference document.images[0]. And, as with any array object, you can find out how many images the array contains by checking the length property. For example: var imageCount = document.images.length;
Images can also have names, so if you prefer, you can refer to the image object by its name, as in var imageLoaded = document.imageName.complete;
or var imageLoaded = document.images[imageName].complete;
The document.images array is a useful guide to knowing whether a browser supports swappable images. Any browser that treats an img element as an object always forms a document.images array in the page. If no images are defined in the page, the array is still there, but its length is zero. The array’s existence, however, is the clue about image object compatibility. Because the document.images array evaluates to an array object when present, the expression can be used as a conditional expression for branching to statements that involve image swapping: if (document.images) { // image swapping or precaching here }
Browsers that don’t have this property (legacy and, potentially, mobile) evaluate document .images as undefined, and thus the condition is treated as a false value.
941
Part IV: Document Objects Reference documentObject.implementation
Example The document.images property is defined automatically as the browser builds the object model for a document that contains image objects. See the discussion about the Image object in Chapter 31, for reference examples. Related Item: Image object (see Chapter 31, ‘‘Image, Area, Map, and Canvas Objects’’)
implementation Value: Object
Read-Only
Compatibility: WinIE6+, MacIE5+, NN6+, Moz+, Safari+, Opera+, Chrome+ The Core W3C DOM defines the document.implementation property as an avenue to let scripts find out what DOM features (that is, modules of the DOM standard) are implemented for the current environment. Although the object returned by the property (a DOMImplementation object) has no properties, it has a method, hasFeature(), which lets scripts find out, for example, whether the environment supports HTML or just XML. The first parameter of the hasFeature() method is the feature in the form of a string. The second parameter is a string form of the version number. The method returns a Boolean value. The ‘‘Conformance’’ section of the W3C DOM specification governs the module names. (The standard also allows browser-specific features to be tested through the hasFeature() method.) Module names include strings such as HTML, XML, MouseEvents, and so on. Version numbering for W3C DOM modules corresponds to the W3C DOM level. Thus, the version for the XML DOM module in DOM Level 2 is known as 2.0. Note that versions refer to DOM modules and not, for example, the separate HTML standard.
Example Use The Evaluator (Chapter 4, ‘‘JavaScript Essentials’’) to experiment with the document .implementation.hasFeature() method. Enter the following statements one at a time into the top text field and examine the results: document.implementation.hasFeature("HTML","1.0") document.implementation.hasFeature("HTML","2.0") document.implementation.hasFeature("HTML","3.0") document.implementation.hasFeature("CSS","2.0") document.implementation.hasFeature("CSS2","2.0")
Feel free to try other values. For some reason, as of version 7, Internet Explorer returns false for some features that it indeed supports, such as CSS 2.0. In other words, it’s probably not a good idea to place a lot of trust in the IE results of the hasFeature() method, at least for the time being.
inputEncoding Value: String
Read-Only
Compatibility: WinIE-, MacIE-, NN-, Moz1.8+, Safari+, Opera-, Chrome+ The input encoding of a document is the character encoding that is in effect at the time when the document is parsed. For example, ISO-8859-1 is a common character encoding that you may see reported by the inputEncoding property.
942
Chapter 29: Document and Body Objects documentObject.lastModified
lastModified Value: Date string
Read-Only
Compatibility: WinIE3+, MacIE3+, NN2+, Moz+, Safari+, Opera+, Chrome+ Every disk file maintains a modified time stamp, and most (but not all) servers are configured to expose this information to a browser accessing a file. This information is available by reading the document.lastModified property. If your server supplies this information to the client, you can use the value of this property to present this information for readers of your web page. The script automatically updates the value for you, rather than requiring you to hand-code the HTML line every time you modify the home page. Be aware that if you are testing with Safari or Google Chrome, your code will not work unless the files are coming from an HTTP server. If the value returned to you displays itself as a date in 1969, it means that you are positioned somewhere west of GMT, or Greenwich Mean Time (some number of time zones west of GMT at 1 January 1970), and the server is not providing the proper data when it serves the file. Sometimes server configuration can fix the problem, but not always. The returned value is not a date object, but rather a straight string consisting of the time and date, as recorded by the document’s file system. The format of the string varies from browser to browser and version to version. You can, however, usually convert the date string to a JavaScript date object and use the date object’s methods to extract selected elements for recompilation into readable form. Listing 29-6 shows an example. Even local file systems don’t necessarily provide the correct data for every browser to interpret. But put that same file on a UNIX or Windows web server, and the date appears correctly when accessed through the Net.
Example Experiment with the document.lastModified property with Listing 29-6. But also be prepared for inaccurate readings depending on the location of the file. LISTING 29-6
Putting a Time Stamp on a Page Time Stamper GiantCo Home Page update = new Date(document.lastModified); theMonth = update.getMonth() + 1; theDate = update.getDate();
continued
943
Part IV: Document Objects Reference documentObject.layers[] LISTING 29-6
As noted at great length in the Date object discussion in Chapter 17, you should be aware that date formats vary greatly from country to country. Some of these formats use a different order for date elements. When you hard-code a date format, it may take a form that is unfamiliar to other users of your page. Related Item: Date object (see Chapter 17, ‘‘The Date Object’’)
layers[] Value: Array
Read-Only
Compatibility: WinIE-, MacIE-, NN4, Moz-, Safari-, Opera-, ChromeThe layer object is the NN4 way of exposing positioned elements to the object model. Thus, the document.layers property is an array of positioned elements in the document. The layer object and document.layers property are orphaned in NN4, and their importance is all but gone now that Mozilla has taken over. Chapter 43 includes several examples of how to carry out similar functionality as the document.layers property using the standard W3C DOM. Related Item: layer object (see Chapter 43, ‘‘Positioned Objects’’)
linkColor (See alinkColor)
links[] Value: Array
Read-Only
Compatibility: WinIE3+, MacIE3+, NN2+, Moz+, Safari+, Opera+, Chrome+ The document.links property is similar to the document.anchors property, except that the objects maintained by the array are link objects — items created with tags. Use the array references to pinpoint a specific link for retrieving any link property, such as the target window specified in the link’s HTML definition. Link arrays begin their index counts with 0: The first link in a document has the reference document.links[0]. And, as with any array object, you can find out how many entries the array has by checking the length property. For example: var linkCount = document.links.length;
944
Chapter 29: Document and Body Objects documentObject.URL Entries in the document.links property are full-fledged location objects, which means you have the same properties available to each member of the links[] array as you do in the location object.
Example The document.links property is defined automatically as the browser builds the object model for a document that contains link objects. You rarely access this property, except to determine the number of link objects in the document. Related Items: link object; document.anchors property
location URL Value: String
Read/Write and Read-Only (see text)
Compatibility: WinIE4+, MacIE4+, NN3+, Moz+, Safari+, Opera+, Chrome+ The document.URL property is similar to the window.location property. A location object, you may recall from Chapter 28, ‘‘Location and History Objects,’’ consists of a number of properties regarding the document currently loaded in a window or frame. Assigning a new URL to the location object (or location.href property) tells the browser to load the page from that URL into the frame. The document.URL property, on the other hand, is simply a string (read-only in Navigator, Mozilla, and Safari) that reveals the URL of the current document. The value may be important to your script, but the property does not have the object power of the window.location object. You cannot change (assign another value to) this property value because a document has only one URL: its location on the Net (or your hard disk) where the file exists, and what protocol is required to get it. This may seem like a fine distinction, and it is. The reference you use (window.location object or document.URL property) depends on what you are trying to accomplish specifically with the script. If the script is changing the content of a window by loading a new URL, you have no choice but to assign a value to the window.location object. Similarly, if the script is concerned with the component parts of a URL, the properties of the location object provide the simplest avenue to that information. To retrieve the URL of a document in string form (whether it is in the current window or in another frame), you can use either the document.URL property or the window.location.href property.
Note The document.URL property replaces the old document.location property, which is still supported in most browsers.
Example HTML documents in Listings 29-7 through 29-9 create a test lab that enables you to experiment with viewing the document.URL property for different windows and frames in a multiframe environment. Results are displayed in a table, with an additional listing of the document.title property to help you identify documents being referred to. The same security restrictions that apply to retrieving window.location object properties also apply to retrieving the document.URL property from another window or frame.
945
Part IV: Document Objects Reference documentObject.URL LISTING 29-7
A Simple Frameset for the URL Example document.URL Reader
LISTING 29-8
Showing Location Information for Different Contexts URL Property Reader function fillTopFrame() { newURL=prompt("Enter the URL of a document to show in the top frame:",""); if (newURL != null && newURL != "") { top.frames[0].location = newURL; } } function showLoc(item) { var windName = item.value; var theRef = windName + ".document"; item.form.dLoc.value = decodeURIComponent(eval(theRef + ".URL")); item.form.dTitle.value = decodeURIComponent(eval(theRef + ".title")); } // bind the event handlers function addEvent(elem, evtType, func) { if (elem.addEventListener) {
946
Chapter 29: Document and Body Objects documentObject.URL elem.addEventListener(evtType, func, false); } else if (elem.attachEvent) { elem.attachEvent("on" + evtType, func); } else { elem["on" + evtType] = func; } } addEvent(window, "load", function() { addEvent(document.getElementById("opener"), "click", fillTopFrame); addEvent(document.getElementById("parent"), "click", function(evt) {showLoc(document.getElementById("parent"));}); addEvent(document.getElementById("upper"), "click", function(evt) {showLoc(document.getElementById("upper"));}); addEvent(document.getElementById("this"), "click", function(evt) {showLoc(document.getElementById("this"));}); }); Click the "Open URL" button to enter the location of an HTML document to display in the upper frame of this window. Select a window or frame to view each document property values.
Parent window Upper frame This frame
document.URL:
document.title:
continued
947
Part IV: Document Objects Reference documentObject.media LISTING 29-8
(continued)
LISTING 29-9
A Placeholder Page for the URL Example Opening Placeholder Initial place holder. Experiment with other URLs for this frame (see below).
Related Items: location object; location.href, URLUnencoded properties
media Value: String
Read/Write
Compatibility: WinIE5.5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe document.media property indicates the output medium for which content is formatted. The property actually returns an empty string as of IE7, but the intention appears to be to provide a way to use scripting to set the equivalent of the CSS2 @media rule (one of the so-called at rules because of the at symbol). This style sheet rule allows browsers to assign separate styles for each type of output device on which the page is rendered (for example, perhaps a different font for a printer versus the screen). In practice, however, this property is not modifiable, at least through IE8. Related Items: None
mimeType Value: String
Read-Only
Compatibility: WinIE5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeAlthough this property is readable in WinIE5+, its value is not, strictly speaking, a MIME type, at least not in traditional MIME format. Moreover, the results are inconsistent between IE versions 5, 6,
948
Chapter 29: Document and Body Objects documentObject.plugins[] 7, and 8. Perhaps this property will be of more use in an XML, rather than an HTML, document environment. In any case, this property in no way exposes supported MIME types in the current browser.
nameProp Value: String
Read-Only
Compatibility: WinIE6+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe nameProp property returns a string containing the title of the document, which is the same as document.title. If the document doesn’t have a title, nameProp contains an empty string. Related Item: title property
namespaces[] Value: Array of namespace objects
Read-Only
Compatibility: WinIE5.5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeA namespace object can dynamically import an XML-based IE Element Behavior. The namespaces property returns an array of all namespace objects defined in the current document. Related Items: None
parentWindow Value: window object reference
Read-Only
Compatibility: WinIE4+, MacIE4+, NN-, Moz-, Safari-, Opera+, ChromeThe document.parentWindow property returns a reference to the window object containing the current document. The value is the same as any reference to the current window.
Example To prove that the parentWindow property points to the document’s window, you can enter the following statement into the top text field of The Evaluator (see Chapter 4, ‘‘JavaScript Essentials’’): document.parentWindow == self
This expression evaluates to true only if both references are of the same object. Related Item: window object
plugins[] Value: Array
Read-Only
Compatibility: WinIE4+, MacIE4+, NN4+, Moz+, Safari+, Opera+, Chrome+ The document.plugins property returns the same array of embed element objects that you get from the document.embeds property. This property has been deprecated in favor of document.embeds. Related Item: document.embeds property
949
Part IV: Document Objects Reference documentObject.protocol
protocol Value: String
Read/Write
Compatibility: WinIE4+, MacIE4+, NN-, Moz-, Safari-, Opera-, ChromeThe IE-specific document.protocol property returns the plain-language version of the protocol that was used to access the current document. For example, if the file is accessed from a web server, the property returns Hypertext Transfer Protocol. This property differs from the location.protocol property, which returns the portion of the URL that includes the often more cryptic protocol abbreviation (for example, http:). As a general rule, you want to hide all of this stuff from a web application user.
Example If you use The Evaluator (Chapter 4, ‘‘JavaScript Essentials’’) to test the document.protocol property, you will find that it displays File Protocol in the results because you are accessing the listing from a local hard disk or CD-ROM. However, if you upload the Evaluator web page to a web server and access it from there, you will see the expected Hypertext Transfer Protocol result. Related Item: location.protocol property
referrer Value: String
Read-Only
Compatibility: WinIE3+, MacIE3+, NN2+, Moz+, Safari+, Opera+, Chrome+ When a link from one document leads to another, the second document can, under JavaScript control, reveal the URL of the document containing the link. The document.referrer property contains a string of that URL. This feature can be a useful tool for customizing the content of pages based on the previous location the user was visiting within your site. A referrer contains a value only when the user reaches the current page through a link. Any other method of navigation (such as through the history, bookmarks, or by manually entering a URL) sets this property to an empty string.
Caution The document.referrer property usually returns an empty string unless the files are retrieved from a web server.
Example This demonstration requires two documents (and you’ll need to access the documents from a web server). The first document, in Listing 29-10, simply contains one line of text as a link to the second document. In the second document, shown in Listing 29-11, a script verifies the document from which the user came through a link. If the script knows about that link, it displays a message relevant to the experience the user had at the first document. Also try opening Listing 29-11 in a new browser window from the Open File command in the File menu to see how the script won’t recognize the referrer.
950
Chapter 29: Document and Body Objects documentObject.scripts[] LISTING 29-10
An Example Referrer Page document.referrer Property 1 Visit my sister document
LISTING 29-11
Determining the Referrer when a Page Is Visited Through a Link document.referrer Property 2 alert(document.referrer.length + " : " + document.referrer); if (document.referrer.length > 0 && document.referrer.indexOf("jsb29-10.html") != -1) { document.write("How is my brother document?"); } else { document.write("Hello, and thank you for stopping by."); }
Part IV: Document Objects Reference documentObject.security Originally IE-specific, the document.scripts property returns an array of all script element objects in the current document. You can reference an individual script element object to read not only the properties it shares with all HTML element objects (see Chapter 26, ‘‘Generic HTML Element Objects’’), but also script-specific properties, such as defer, src, and htmlFor. The actual scripting is accessible through either the innerText or text properties for any script element object. Although the document.scripts array is read-only, many properties of individual script element objects are modifiable. Adding or removing script elements impacts the length of the document.scripts array. Don’t forget, too, that if your scripts need to access a specific script element object, you can assign an id attribute to it and reference the element directly. This property is the same as the W3C browser expression document .getElementsByTagName("script"), which returns an array of the same objects.
Example You can experiment with the document.scripts array in The Evaluator (Chapter 4, ‘‘JavaScript Essentials’’). For example, you can see that only one script element object is in the Evaluator page if you enter the following statement into the top text field: document.scripts.length
If you want to view all of the properties of that lone script element object, enter the following statement into the bottom text field: document.scripts[0]
Among the properties are both innerText and text. If you assign an empty string to either property, the scripts are wiped out from the object model, but not from the browser. The scripts disappear because after they were loaded, they were cached outside of the object model. Therefore, if you enter the following statement into the top field: document.scripts[0].text = ""
the script contents are gone from the object model, yet subsequent clicks of the Evaluate and List Properties buttons (which invoke functions of the script element object) still work. Related Item: script element object (Chapter 40, ‘‘HTML Directive Objects’’)
security Value: String
Read-Only
Compatibility: WinIE5.5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe security property reveals information about a security certificate, if one is associated with the current document. Related Items: none
selection Value: Object
Read-Only
Compatibility: WinIE4+, MacIE4+, NN-, Moz-, Safari-, Opera+, ChromeThe document.selection property returns a selection object whose content is represented in the browser window as a body text selection. That selection can be explicitly performed by the
952
Chapter 29: Document and Body Objects documentObject.title user (by clicking and dragging across some text) or created under script control through the WinIE TextRange object (see Chapter 33). Because script action on a selection (for example, finding the next instance of selected text) is performed through the TextRange object, converting a selection to a TextRange object using the document.selection.createRange() method is common practice. See the selection object in Chapter 33 for more details.
Be aware that you cannot script interaction with text selections through user interface elements, such as buttons. Clicking a button gives focus to the button and deselects the selection. Use other events, such as document.onmouseup to trigger actions on a selection.
Example Refer to Listings 26-36 and 26-44 in Chapter 26 to see the document.selection property in action for script-controlled copying and pasting (WinIE only). Related Items: selection, TextRange objects
strictErrorChecking Value: String
Read-Only
Compatibility: WinIE-, MacIE-, NN-, Moz1.8+, Safari-, Opera-, ChromeThe strictErrorChecking property reveals the error-checking mode for the document. More specifically, if the property is set to true (the default), exceptions and errors related to DOM operations are reported. Otherwise, DOM-related exceptions may not be thrown, and errors may not be reported.
styleSheets[] Value: Array
Read-Only
Compatibility: WinIE4+, MacIE4+, NN6+, Moz+, Safari+, Opera+, Chrome+ The document.styleSheets array consists of references to all style element objects in the document. Not included in this array are style sheets that are assigned to elements by way of the style attribute inside a tag, or linked in through link elements. See Chapter 38 for details about the styleSheet object. Related Item: styleSheet object (see Chapter 38, ‘‘Style Sheet and Style Objects’’)
title Value: String
Read-Only and Read/Write
Compatibility: WinIE3+, MacIE3+, NN2+, Moz+, Safari+, Opera+, Chrome+ A document’s title is the text that appears between the ... tag pair in an HTML document’s head portion. The title usually appears in the title bar of the browser window in a single-frame presentation, or in a tabbed pane within a multi-paned browser window. Only the title of the topmost framesetting document appears as the title of a multiframe window. Even so, the title property for an individual document within a frame is available through scripting. For example, if two frames are available (UpperFrame and LowerFrame), a script in the document occupying the LowerFrame frame can reference the title property of the other frame’s document, such as this: parent.UpperFrame.document.title
953
Part IV: Document Objects Reference documentObject.URL The document.title property is a holdover from the original document object model. HTML elements in recent browsers have an entirely different application of the title property (see Chapter 26). In modern browsers (IE4+/W3C/Moz/Safari/Opera/Chrome), you should address the document’s title by way of the title element object directly. Related Items: history object
URL (See location)
URLUnencoded Value: String
Read-Only
Compatibility: WinIE5.5+, MacIE-, NN-, Moz+, Safari+, Opera+, Chrome+ The document.URL property returns a URL-encoded string, meaning that non-alphanumeric characters in the URL are converted to URL-friendly characters (for example, a space becomes %20). You can always use the decodeURI() function on the value returned by the document.URL property, although in IE the URLUnencoded property does that for you. If there are no URL-encoded characters in the URL, then both properties return identical strings. Related Items: document.URL property
Compatibility: WinIE-, MacIE-, NN-, Moz1.8+, Safari+, Opera-, Chrome+ These three properties reveal information about the document as it pertains to XML. More specifically, they convey the XML encoding of the document, whether or not the document is a standalone XML document, and the XML version number of the document, respectively. If any of the property values cannot be determined, their values remain null.
Chapter 29: Document and Body Objects documentObject.close() In Navigator 4 only, the natural propagation of an event is downward from the window object, through the document object, and eventually reaching its target. For example, if you click a button, the click event first reaches the window object; then it goes to the document object; if the button is defined within a layer, the event also filters through that layer; eventually (in a split second) the event reaches the button, where an onclick event handler is ready to act on that click. Event capture with different syntax has been standardized in the W3C DOM and is implemented in W3C browsers, such as Firefox and Camino (Mozilla). More specifically, the W3C event capture model introduces the concept of an event listener, which enables you to bind an event handler function to an event. See the addEventListener() method in Chapter 26 for the W3C counterpart to the NN4 captureEvents() method. Also, see Chapter 32 for more details on the combination of event capture and event bubbling in the W3C DOM.
clear() Returns: Nothing Compatibility: WinIE3+, MacIE3+, NN2+, Moz+, Safari+, Opera+, Chrome+ Ever since NN2, the document.clear() method was intended to clear the current document from the browser window. This method is quite impractical, because you typically need some further scripts to execute after you clear the document, but if the scripts are gone, nothing else happens. In practice, the document.clear() method never did what it was supposed to do (and in earlier browsers easily caused browser crashes). We strongly recommend against using document.clear(), even in preparation for generating a new page’s content with document.write(). The document.write() method clears the original document from the window before adding new content. If you truly want to empty a window or frame, then use document.write() to write a blank HTML document or to load an empty HTML document from the server. Related Items: document.close(), document.write(), document.writeln() methods
close() Returns: Nothing Compatibility: WinIE3+, MacIE3+, NN2+, Moz+, Safari+, Opera+, Chrome+ Whenever a layout stream is opened to a window through the document.open() method or through either of the document writing methods (which also open the layout stream), you must close the stream after the document is written. This causes the Layout:Complete and Done messages to appear in the status line (although you may experience some bugs in the status message on some platforms). The document-closing step is very important to prepare the window for the next potential round of replenishment with new script-assembled HTML. If you don’t close the document, subsequent writing is appended to the bottom of the document. Some or all of the data specified for the window won’t display properly until you invoke the document.close() method, especially when images are being drawn as part of the document stream. A common symptom is the momentary appearance and then disappearance of the document parts. If you see such behavior, look for a missing document.close() method after the last document.write() method.
955
Part IV: Document Objects Reference documentObject.createAttribute()
Fixing the Sticky Wait Cursor From time to time, various browsers fail to restore the cursor to normal after document.write() and document.close() (and some other content-modifying scripts). The cursor stubbornly remains in the wait mode, or the progress bar keeps spinning when, in truth, all processing has been completed. Albeit ugly, one workaround that we have found effective is to force an extra document.close() via a javascript: pseudo-URL (just adding another document.close() to your script doesn’t do the trick). For use within a frameset, the javascript: URL must be directed to the top of the frameset hierarchy, whereas the document.close() method is aimed at the frame that had its content changed. For example, if the change is made to a frame named content, create a function, such as the following: function recloseDoc() { top.location.href = "javascript:void (parent.content.document.close())"; } If you place this function in the framesetting document, scripts that modify the content frame can invoke this script after any operation that prevents the normal cursor from appearing.
Example Before you experiment with the document.close() method, be sure you understand the document.write() method described later in this chapter. After that, make a separate set of the three documents for that method’s example (Listings 29-14 through 29-16 in a different directory or folder). In the takePulse() function listing, comment out the document.close() statement, as shown here: msg += "
Make it a great day!"; parent.frames[1].document.write(msg); //parent.frames[1].document.close();
Now try the pages on your browser. You see that each click of the upper button appends text to the bottom frame, without first removing the previous text. The reason is that the previous layout stream was never closed. The document thinks that you’re still writing to it. Also, without properly closing the stream, the last line of text may not appear in the most recently written batch. Related Items: document.open(), document.clear(), document.write(), document.writeln() methods
createAttribute("attributeName") Returns: Attribute object reference Compatibility: WinIE6+, MacIE5+, NN6+, Moz+, Safari+, Opera+, Chrome+ The document.createAttribute() method generates an attribute node object (formally known as an Attr object in W3C DOM terminology) and returns a reference to the newly created object. Invoking the method assigns only the name of the attribute, so it is up to your script to assign a value to the object’s nodeValue property and then plug the new attribute into an existing element through
956
Chapter 29: Document and Body Objects documentObject.createDocumentFragment() that element’s setAttributeNode() method (described in Chapter 26). The following sequence generates an attribute that becomes an attribute of a table element: var newAttr = document.createAttribute("width"); newAttr.nodeValue = "80%"; document.getElementById("myTable").setAttributeNode(newAttr);
Attributes do not always have to be attributes known to the HTML standard, because the method also works for XML elements, which have custom attributes.
Example To create an attribute and inspect its properties, enter the following text into the top text box of The Evaluator (Chapter 4, ‘‘JavaScript Essentials’’): a = document.createAttribute("author")
Now enter a into the bottom text box to inspect the properties of an Attr object. Related Items: setAttributeNode() method (see Chapter 26, ‘‘Generic HTML Element Objects’’)
createCDATASection("data") Returns: CDATA section object reference Compatibility: WinIE-, MacIE5, NN7+, Moz+, Safari+, Opera+, Chrome+ The document.createCDATASection() method generates a CDATA section node for whatever string you pass as the parameter. The value of the new node becomes the string that you pass.
createComment("commentText") Returns: Comment object reference Compatibility: WinIE6+, MacIE5+, NN6+, Moz+, Safari+, Opera+, Chrome+ The document.createComment() method creates an instance of a comment node. Upon creation, the node is in memory and available to be inserted into the document via any node’s appendChild() or insertBefore() method. Related Items: appendChild(), insertBefore() methods
createDocumentFragment() Returns: Document fragment object reference Compatibility: WinIE6+, MacIE5+, NN6+, Moz+, Safari+, Opera+, Chrome+ The document.createDocumentFragment() method creates an instance of an empty document fragment node. This node serves as a holder that can be used to assemble a sequence of nodes in memory. After creating and assembling nodes into the document fragment, the entire fragment can be inserted into the document tree. A document fragment is particularly helpful when your scripts assemble an arbitrary sequence of element and text nodes. By providing a parent node for all content within, the fragment node supplies the necessary parent node context for W3C DOM node methods, such as appendChild(), during the content assembly process. If you then append or insert the document fragment node to an
957
Part IV: Document Objects Reference documentObject.createElement() element in the rendered document tree, the fragment wrapper disappears, leaving just its content in the desired location in the document. Therefore, a typical usage pattern for a document fragment is to begin by creating an empty fragment node (through the createDocumentFragment() method), populate it at will with newly created element or text nodes or both, and then use the appropriate node method on a document tree’s element to append, insert, or replace, using the fragment node as the source material. Related Items: None
createElement("tagName") createElementNS("namespaceURI", "tagName") Returns: Element object reference Compatibility: WinIE4+, MacIE4+, NN6+, Moz+, Safari+, Opera+, Chrome+ The document.createElement() and document.createElementNS() methods generate an element object for whatever HTML (or XML) tag name you pass as the parameter. An object created in this manner is not officially part of the current document node tree because it has not yet been placed into the document. But these methods are the way you begin assembling an element object that eventually gets inserted into the document. The createElementNS() method is identical to createElement(), except that the latter method accepts an extra parameter that you use to pass a namespace URI for the element. Additionally, the tag name that you specify when creating an element via createElementNS() must be a qualified name. Note, however, that createElementNS() is not supported in Internet Explorer through version 8. The returned value is a reference to the object. Properties of that object include all properties (set to default values) that the browser’s object model defines for that element object. Your scripts can then address the object through this reference to set the object’s properties. Typically, you do this before the object is inserted into the document, especially because otherwise read-only properties can be modified before the element is inserted into the document. After the object is inserted into the document, the original reference (for example, a global variable used to store the value returned from the createElement() method) still points to the object, even while it is in the document and being displayed for the user. To demonstrate this effect, consider the following statements that create a simple paragraph element containing a text node: var newText = document.createTextNode("Four score and seven years ago..."); var newElem = document.createElement("p"); newElem.id = "newestP"; newElem.appendChild(newText); document.body.appendChild(newElem);
At this point, the new paragraph is visible in the document. But you can now modify, for example, the style of the paragraph by addressing either the element in the document object model or the variable that holds the reference to the object you created: newElem.style.fontSize = "20pt";
or document.getElementById("newestP").style.fontSize = "20pt";
The two references are inextricably connected and always point to the exact same object. Therefore, if you want to use a script to generate a series of similar elements (for example, a bunch of li list item
958
Chapter 29: Document and Body Objects documentObject.createEventObject() elements), then you can use createElement() to make the first one and set all properties that the items have in common. Then use cloneNode() to make a new copy, which you can then treat as a separate element (and probably assign unique IDs to each element). When scripting in the W3C DOM environment, you may rely on document.createElement() frequently to generate new content for a page or portion thereof (unless you prefer to use the convenience innerHTML property to add content in the form of strings of HTML). In a strict W3C DOM environment, creating new elements is not a matter of assembling HTML strings, but rather creating genuine element (and text node) objects.
Example Chapter 26, ‘‘Generic HTML Element Objects,’’ contains numerous examples of the document .createElement() method in concert with methods that add or replace content to a document. See Listings 26-10, 26-21, 26-22, 26-28, 26-29, and 26-31. Related Item: document.createTextNode() method
createEvent("eventType") Returns: Event object reference Compatibility: WinIE-, MacIE-, NN6+, Moz+, Safari+, Opera+, Chrome+ The document.createEvent() method creates an instance of a W3C DOM Event object of the specified event category. Upon creation, the generic event must be initialized as a particular event type, and any other relevant properties set for the event. After successfully initializing the event, you can fire it through a call to the dispatchEvent() method. Event types recognized by Mozilla are KeyEvents, MouseEvents, MutationEvents, and UIEvents. Beginning with Mozilla 1.7.5, the following additional types may also be used: Event, KeyboardEvent, MouseEvent, MutationEvent, MutationNameEvent, TextEvent, UIEvent. The process of initializing each of these event types requires its own series of parameters in the associated initEvent() method. See Chapter 32 for more details.
Example Following is an example of how you might create an event, initialize it to a specific event type, and send it to a given element: var evt = document.createEvent("MouseEvents"); evt.initEvent("mouseup", true, true); document.getElementById("myButton").dispatchEvent(evt);
Related Items: createEventObject() method; W3C DOM event object (see Chapter 32, ‘‘Event Objects’’)
createEventObject([eventObject]) Returns: event object Compatibility: WinIE5.5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe IE-specific createEventObject() method creates an event object, which can then be passed as a parameter to the fireEvent() method of any element object. The event object created by this event is just like an event object created by a user or system action.
959
Part IV: Document Objects Reference documentObject.createNSResolver() An optional parameter enables you to base the new event on an existing event object. In other words, the properties of the newly created event object pick up all the properties of the event object passed as a parameter, which then enables you to modify properties of your choice. If you provide no parameter to the method, then you must fill the essential properties manually. For more about the properties of an event object, see Chapter 32.
Example See the discussion of the fireEvent() method in Chapter 26 for an example of the sequence to follow when creating an event to fire on an element. Related Items: createEvent() method; fireEvent() method (see Chapter 26); event object (see Chapter 32)
createNSResolver(nodeResolver) Returns: XPath namespace resolver object reference Compatibility: WinIE-, MacIE-, NN7+, Moz+, Safari+, Opera+, Chrome+ The createNSResolver() method is used in the context of XPath to alter a node so that it can resolve namespaces. This is necessary as part of the evaluation of an XPath expression. The only parameter is the node that is to serve as the basis for the namespace resolver. Related Item: evaluate() method
createRange() Returns: Range object reference Compatibility: WinIE-, MacIE-, NN6+, Moz+, Safari+, Opera+, Chrome+ The document.createRange() method creates an empty W3C DOM Range object with the boundary points of the range collapsed to the point before the first character of the rendered body text. Related Item: Range object
createStyleSheet(["URL"[, index]]) Returns: styleSheet object reference Compatibility: WinIE4+, MacIE4, NN-, Moz-, Safari-, Opera-, ChromeThe IE-specific createStyleSheet() method creates a styleSheet object, a type of object that includes style element objects as well as style sheets that are imported into a document through the link element. Thus, you can dynamically load an external style sheet even after a page has loaded. Unlike the other create methods entering W3C DOM usage, the createStyleSheet() method not only creates the style sheet, but it inserts the object into the document object model immediately. Thus, any style sheet rules that belong (or are assigned to) that object take effect on the page right away. If you’d rather create a style sheet and delay its deployment, you should use the createElement() method and element object assembly techniques. If you don’t specify any parameters to the method in WinIE, an empty styleSheet object is created. It is assumed that you will then use styleSheet object methods, such as addRule() to add the details to the style sheet. To link in an external style sheet file, assign the file’s URL to
960
Chapter 29: Document and Body Objects documentObject.createStyleSheet() the first parameter of the method. The newly imported style sheet is appended to the end of the document.styleSheets array of styleSheet objects. An optional second parameter lets you specify precisely where in the sequence of style sheet elements the newly linked style sheet should be inserted. A style sheet rule for any given selector is overridden by a style sheet for the same selector that appears later in the sequence of style sheets in a document.
Example Listing 29-12 demonstrates adding an internal and external style sheet to a document. For the internal addition, the addStyle1() function invokes document.createStyleSheet() and adds a rule governing the p elements of the page. In the addStyle2() function, an external file is loaded. That file contains the following two style rules: h2 {font-size:20pt; color:blue;} p {color:blue;}
Notice that by specifying a position of zero for the imported style sheet, the addition of the internal style sheet always comes afterward in styleSheet object sequence. Thus, except when you deploy only the external style sheet, the red text color of the p elements override the blue color of the external style sheet. If you remove the second parameter of the createStyleSheet() method in addStyle2(), the external style sheet is appended to the end of the list. If it is the last style sheet to be added, the blue color prevails. Repeatedly clicking the buttons in this example continues to add the style sheets to the document. LISTING 29-12
Creating and Applying Style Sheets document.createStyleSheet() Method function addStyle1() { var newStyle = document.createStyleSheet(); newStyle.addRule("P", "font-size:16pt; color:red"); } function addStyle2() { var newStyle = document.createStyleSheet("jsb29-12.css",0); } // bind the event handlers function addEvent(elem, evtType, func) { if (elem.addEventListener) { elem.addEventListener(evtType, func, false);
continued
961
Part IV: Document Objects Reference documentObject.createTextNode() LISTING 29-12
Lorem ipsum dolor sit amet, consectetaur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim adminim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
Section 2
Duis aute irure dolor in reprehenderit involuptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deseruntmollit anim id est laborum.
Related Item: styleSheet object (see Chapter 38, ‘‘Style Sheet and Style Objects’’)
createTextNode("text") Returns: Object Compatibility: WinIE5+, MacIE5+, NN6+, Moz+, Safari+, Opera+, Chrome+ A text node is a W3C DOM object that contains body text without any HTML (or XML) tags, but is usually contained by (meaning, is a child of) an HTML (or XML) element. Without the IE innerText convenience property for modifying the text of an element, the W3C DOM relies on the node hierarchy of a document (Mozilla exceeds the W3C DOM by providing an innerHTML
962
Chapter 29: Document and Body Objects documentObject.createTreeWalker() property, which you can use to replace text in an element). To insert or replace text inside an HTML element in the W3C DOM way, you create the text node and then use methods of the parent element (for example, appendChild(), insertBefore(), and replaceChild(), all described in Chapter 26) to modify the document’s content. To generate a fresh text node, use document.createTextNode(). The sole parameter of the createTextNode() method is a string whose text becomes the nodeValue of the text node object returned by the method. You can also create an empty text node (passing an empty string) and assign a string to the nodeValue of the object later. As soon as the text node is present in the document object model, scripts can simply change the nodeValue property to modify the text of an existing element. For more details on the role of text nodes in the W3C DOM, see Chapter 25, ‘‘Document Object Model Essentials.’’
Example Although Chapters 25 and 26 (Listing 26-21, for instance) provide numerous examples of the createTextNode() method at work, using The Evaluator is instructive to see just what the method generates in IE5+/W3C. You can use one of the built-in global variables of The Evaluator to hold a reference to a newly generated text node by entering the following statement into the top text field: a = document.createTextNode("Hello")
The Results box shows that an object was created. Now, look at the properties of the object by entering a into the bottom text field. The precise listings of properties varies between IE5+ and W3C browsers, but the W3C DOM properties that they share in common indicate that the object is a node type 3 with a node name of #text. No parents, children, or siblings exist yet because the object created here is not part of the document hierarchy tree until it is explicitly added to the document. To see how insertion works, enter the following statement into the top text field to append the text node to the myP paragraph: document.getElementById("myP").appendChild(a)
The word Hello appears at the end of the simple paragraph lower on the page. Now you can modify the text of that node either through the reference, from the point of view of the containing p element, or through the global variable reference for the newly created node: document.getElementById("myP").lastChild.nodeValue = "Howdy"
or a.nodeValue = "Howdy"
Related Item: document.createElement() method
createTreeWalker(rootNode, whatToShow, filterFunction, entityRefExpansion) Returns: TreeWalker object reference Compatibility: WinIE-, MacIE-, NN7+, Moz1.4+, Safari+, Opera+, Chrome+ The document.createTreeWalker() method creates an instance of a TreeWalker object that can be used to navigate the document tree. The first parameter to the method indicates the node in
963
Part IV: Document Objects Reference documentObject.elementFromPoint() the document that is to serve as the root node of the tree. The second parameter is an integer constant that specifies one of several built-in filters for selecting nodes to be included in the tree. Following are the possible acceptable values for this parameter: NodeFilter.SHOW_ALL
NodeFilter.SHOW_ATTRIBUTE
NodeFilter.SHOW_CDATA_SECTION
NodeFilter.SHOW_COMMENT
NodeFilter.SHOW_DOCUMENT
NodeFilter.SHOW_DOCUMENT_FRAGMENT
NodeFilter.SHOW_DOCUMENT_TYPE
NodeFilter.SHOW_ELEMENT
NodeFilter.SHOW_ENTITY
NodeFilter.SHOW_ENTITY_REFERENCE
NodeFilter.SHOW_NOTATION
NodeFilter.SHOW_PROCESSING_INSTRUCTION
NodeFilter.SHOW_TEXT
The third parameter to the createNodeIterator() method is a reference to a filter function that can filter nodes even further than the whatToShow parameter. This function must accept a single node and return an integer value based upon one of the following constants: NodeFilter.FILTER_ACCEPT, NodeFilter.FILTER_REJECT, or NodeFilter.FILTER_SKIP. The idea is that you code the function to perform a test on each node and return an indicator value that lets the node iterator know whether or not to include the node in the tree. Your function doesn’t loop through nodes. The TreeWalker object mechanism repetitively invokes the function as needed to look for the presence of whatever characteristic you wish to use as a filter. The final parameter to the method is a Boolean value that determines whether or not the content of entity reference nodes should be treated as hierarchical nodes. This parameter applies primarily to XML documents. Related Items: TreeWalker object
elementFromPoint(x, y) Returns: Element object reference Compatibility: WinIE4+, MacIE4+, NN-, Moz+, Safari+, Opera+, Chrome+ Originally IE-specific, the elementFromPoint() method returns a reference to whatever element object occupies the point whose integer coordinates are supplied as parameters to the method. The coordinate plane is that of the document, whose top-left corner is at point 0,0. This coordinate plane can be very helpful in interactive designs that need to calculate collision detection between positioned objects or mouse events. When more than one object occupies the same point (for example, one element is positioned atop another), the element with the highest z-index value is returned. A positioned element always wins when placed atop a normal body-level element. And if multiple overlapping positioned elements have the same z-index value (or none by default), the element that comes last in the source code order is returned for the coordinate that they share in common.
Example Listing 29-13 is a document that contains many different types of elements, each of which has an ID attribute assigned to it. The onmouseover event handler for the document object invokes a
964
Chapter 29: Document and Body Objects documentObject.elementFromPoint() function that finds out which element the cursor is over when the event fires. Note that the event coordinates are event.clientX and event.clientY, which use the same coordinate plane as the page for their point of reference. As you roll the mouse over every element, its ID appears on the page. Some elements, such as br and tr, occupy no space in the document, so you cannot get their IDs to appear. On a typical browser screen size, a positioned element rests atop one of the paragraph elements so that you can see how the elementFromPoint() method handles overlapping elements. If you scroll the page, the coordinates for the event and the page’s elements stay in sync.
LISTING 29-13
Tracking the Mouse as It Passes over Elements document.elementFromPoint() Method function replaceHTML(elem, text) { while(elem.firstChild) { elem.removeChild(elem.firstChild); } elem.appendChild(document.createTextNode(text)); } function showElemUnderneath(evt) { var elem elem = document.elementFromPoint(evt.clientX, evt.clientY); replaceHTML(document.getElementById("mySpan"), elem.id); } document.elementFromPoint() Method
Roll the mouse around the page. The coordinates of the mouse pointer are currently atop an element whose ID is: "".
Cell A1
Cell B1
continued
965
Part IV: Document Objects Reference documentObject.evaluate() LISTING 29-13
(continued)
Cell A2
Cell B2
Section 1
Lorem ipsum dolor sit amet, consectetaur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim adminim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
Section 2
Duis aute irure dolor in reprehenderit involuptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deseruntmollit anim id est laborum.
Here is a positioned element.
Related Items: event.clientX, event.clientY properties; positioned objects (see Chapter 43, ‘‘Positioned Objects’’)
evaluate("expression", contextNode, resolver, type, result) Returns: XPath result object reference Compatibility: WinIE-, MacIE-, NN7+, Moz+, Safari+, Opera+, Chrome+ The document.evaluate() method evaluates an XPath expression and returns an XPath result object (XPathResult). The most important parameter to this method is the first one, which contains the actual XPath expression as a string. The second parameter is the context node to which the expression applies, whereas the third parameter is the namespace resolver (see the createNSResolver() method). The resolver parameter can be specified as null as long as there aren’t any namespace prefixes used within the expression. The type parameter determines the type of the result of the expression and is specified as one of the XPath result types, such as 0 for any type, 1 for number, 2 for string, and so forth. Finally, a reusable result object can be specified in the last parameter, which will then be modified and returned from the method as the result of the expression. Related Item: createNSResolver() method
Chapter 29: Document and Body Objects documentObject.execCommand() The execCommand() method is the JavaScript gateway to a set of commands that is outside of the methods defined for objects in the object model. A series of related methods (queryCommandEnable() and others) also facilitate management of these commands. The syntax for the execCommand() method requires at least one parameter, a string version of the command name. Command names are not case-sensitive. An optional second parameter is a Boolean flag to instruct the command to display any user interface artifacts that may be associated with the command. The default is false. For the third parameter, some commands require that an attribute value be passed for the command to work. For example, to set the font size of a text range, the syntax is myRange.execCommand("FontSize", true, 5);
The execCommand() method returns Boolean true if the command is successful; false if not successful. Some commands can return values (for example, finding out the font name of a selection), but those are accessed through the queryCommandValue() method. In Internet Explorer, most of these commands operate on body text selections that are TextRange objects. As described in Chapter 33, a TextRange object must be created under script control. But a TextRange object can be created in response to a user selecting some text in the document. Because a TextRange object is independent of the element hierarchy (indeed, a TextRange can spread across multiple nodes), it cannot respond to style sheet specifications. Thus, many of the commands that can operate on a TextRange object have to do with formatting or modifying the text. For a list of commands that work exclusively on TextRange objects, see the TextRange.execCommand() method in Chapter 33. Although many of the commands intended for the TextRange also work when invoked from the document object, in this section the focus is on those commands that have scope over the entire document. Table 29-2 lists those few commands that work with the document. Also listed are many commands that work exclusively on text selections in the document, whether the selections are made manually by the user or with the help of the TextRange object (see Chapter 33). Mozilla 1.4 and Safari 1.3 added a feature that allows scripts to turn an iframe element’s document object into an HTML editable document. Here is an example of how to center the selected text in an iframe with an ID of msg: document.getElementById("msg").contentDocument.execCommand("JustifyCenter");
Note that the contentDocument property is used to access the iframe as a document. Visit http://www.mozilla.org/editor for additional details and examples of the document.execCommand() method.
Example You can find many examples of the execCommand() method for the TextRange object in Chapter 33. But you can try out the document-specific commands in The Evaluator (see Chapter 4) in Internet Explorer if you like. Try each of the following statements in the top text box and click the Evaluate button: document.execCommand("Refresh") document.execCommand("SelectAll") document.execCommand("Unselect")
967
Part IV: Document Objects Reference documentObject.execCommand() TABLE 29-2
document.execCommand() Commands Command
Parameter
Description
BackColor
Color String
Encloses the current selection with a font element whose style attribute sets the background-color style to the parameter value.
CreateBookmark
Anchor String
Encloses the current selection (or text range) with an anchor element whose name attribute is set to the parameter value.
CreateLink
URL String
Encloses the current selection with an a element whose href attribute is set to the parameter value.
decreaseFontSize
none
Encloses the current selection with a small element.
Delete
none
Deletes the current selection from the document.
FontName
Font Face(s)
Encloses the current selection with a font element whose face attribute is set to the parameter value.
FontSize
Size String
Encloses the current selection with a font element whose size attribute is set to the parameter value.
foreColor
Color String
Encloses the current selection with a font element whose color attribute is set to the parameter value.
FormatBlock
Block Element String
Encloses the current selection with the specified block element. IE only supports the h1 through h6, address and pre block elements. Other browsers support all block elements.
increaseFontSize
none
Encloses the current selection with a big element.
Indent
None
Indents the current selection.
InsertHorizontalRule
Id String
Encloses the current selection in an hr element, whose id attribute is set to the parameter value.
InsertImage
Id String
Encloses the current selection in an img element, whose id attribute is set to the parameter value.
InsertParagraph
Id String
Encloses the current selection in an p element, whose id attribute is set to the parameter value.
JustifyCenter
None
Centers the current selection.
JustifyFull
None
Full-justifies the current selection.
JustifyLeft
None
Left-justifies the current selection.
JustifyRight
None
Right-justifies the current selection.
Outdent
None
Outdents the current selection.
968
Chapter 29: Document and Body Objects documentObject.getElementById() TABLE 29-2
(continued )
Command
Parameter
Description
Refresh
None
Reloads the page.
RemoveFormat
None
Removes formatting for the current selection.
SelectAll
None
Selects all text of the document.
UnBookmark
None
Removes anchor tags that surround the current selection.
Unlink
None
Removes link tags that surround the current selection.
Unselect
None
Deselects the current selection anywhere in the document.
All methods return true in the Results box. Because any way you can evaluate a statement in The Evaluator forces a body selection to become de-selected before the evaluation takes place, you can’t experiment this way with the selection-oriented commands. Related Items: queryCommandEnabled(), queryCommandIndterm(), queryCommandState(), queryCommandSupported(), queryCommandText(), queryCommandValue() methods
getElementById("elementID") Returns: Element object reference Compatibility: WinIE5+, MacIE5+, NN6+, Moz+, Safari+, Opera+, Chrome+ The document.getElementById() method is the W3C DOM syntax for retrieving a reference to any element in a document that has a unique identifier assigned to its id attribute. If the document contains more than one instance of an ID, the method returns a reference to the first element in source code order with that ID. Because this method is such an important avenue to writing references to objects that are to be modified under script control, you can see how important it is to assign unique IDs to elements. This method’s name is quite a finger twister for scripters, especially compared to the IE4+ convention of letting a reference to any element begin simply with the object’s ID. However, the getElementById() method is the modern way of acquiring an element’s reference for W3C DOM-compatible browsers, including IE. When you type this method, be sure to use a lowercase d as the last character of the method name. Unlike some other element-oriented methods (for example, getElementsByTagName()), which can be invoked on any element in a document, the getElementById() method works exclusively with the document object.
Example You can find many examples of this method in use throughout this book, but you can take a closer look at how it works by experimenting in The Evaluator (Chapter 4, ‘‘JavaScript Essentials’’). A number of elements in The Evaluator have IDs assigned to them, so that you can use the method to inspect the objects and their properties. Enter the following statements into both the top and bottom text
969
Part IV: Document Objects Reference documentObject.getElementsByName() fields of The Evaluator. Results from the top field are references to the objects; results from the bottom field are lists of properties for the particular object. document.getElementById("myP") document.getElementById("myEM") document.getElementById("myTitle") document.getElementById("myScript")
Related Item: getElementsByTagName() method (see Chapter 26, ‘‘Generic HTML Element Objects’’)
getElementsByName("elementName") Returns: Array Compatibility: WinIE5+, MacIE5+, NN6+, Moz+, Safari+, Opera+, Chrome+ The document.getElementsByName() method returns an array of references to objects whose name attribute is assigned the element name passed as the method’s attribute. Although other browsers recognize name attributes even for elements that don’t have them by default, IE does not. Therefore, for maximum cross-browser compatibility, use this method only to locate elements that have name attributes defined for them by default, such as form control elements. If the element does not exist in the document, the method returns an array of zero length. For the most part, you are best served by using IDs on elements and the getElementById() method to unearth references to individual objects. But some elements, especially the input element of type radio, use the name attribute to group elements together. In that case, a call to getElementsByName() returns an array of all elements that share the name — facilitating perhaps a for loop that inspects the checked property of a radio button group. Thus, instead of using the old-fashioned approach by way of the containing form object: var buttonGroup = document.forms[0].radioGroupName;
you can retrieve the array more directly: var buttonGroup = document.getElementsByName(radioGroupName);
In the latter case, you operate independently of the containing form object’s index number or name. This assumes, of course, that a group name is not shared elsewhere on the page, which would certainly lead to confusion.
Example Use The Evaluator (Chapter 4, ‘‘JavaScript Essentials’’) to test out the getElementsByName() method. All form elements in the upper part of the page have names associated with them. Enter the following statements into the top text field and observe the results: document.getElementsByName("output") document.getElementsByName("speed").length document.getElementsByName("speed")[0].value
You can also explore all of the properties of the text field by typing the following expression into the bottom field: document.getElementsByName("speed")[0]
970
Chapter 29: Document and Body Objects documentObject.open() Related Items: document.getElementsById(), getElementsByTagName() methods
importNode(node, deep) Returns: Node object reference Compatibility: WinIE-, MacIE-, NN7+, Moz+, Safari+, Opera+, Chrome+ The document.importNode() method imports a node from another document object into the current document object. A copy of the original node is made when the node is imported, meaning that the original node remains unchanged. The second parameter to the method is a Boolean value that determines whether or not the node’s entire subtree is imported (true) or just the node itself (false).
open(["mimeType"] [,"replace"]) Returns: Nothing Compatibility: WinIE3+, MacIE3+, NN2+, Moz+, Safari+, Opera+, Chrome+ Opening a document is different from opening a window. In the case of a window, you’re creating a new object, both on the screen and in the browser’s memory. Opening a document, on the other hand, tells the browser to get ready to accept some data for display in the window named or implied in the reference to the document.open() method. (For example, parent.frames[1] .document.open() may refer to a different frame in a frameset, whereas document.open() implies the current window or frame.) Therefore, the method name may mislead newcomers because the document.open() method has nothing to do with loading documents from the web server or hard disk. Rather, this method is a prelude to sending data to a window through the document.write() or document.writeln() methods. In a sense, the document.open() method merely opens the valve of a pipe; the other methods send the data down the pipe like a stream, and the document.close() method closes that valve as soon as the page’s data has been sent in full. The document.open() method is optional because a document.write() method that attempts to write to a closed document automatically clears the old document and opens the stream for a new one. Whether or not you use the document.open() method, be sure to use the document.close() method after all the writing has taken place. An optional parameter to the document.open() method enables you to specify the nature of the data being sent to the window. A MIME (Multipurpose Internet Mail Extension) type is a specification for transferring and representing multimedia data on the Internet (originally for mail transmission, but now applicable to all Internet data exchanges). You’ve seen MIME depictions in the list of helper applications in your browser’s preferences settings. A pair of data type names separated by a slash represents a MIME type (such as text/html and image/gif). When you specify a MIME type as a parameter to the document.open() method, you’re instructing the browser about the kind of data it is about to receive, so that it knows how to render the data. Common values that most browsers accept are: text/html text/plain image/gif image/jpeg image/xbm
971
Part IV: Document Objects Reference documentObject.queryCommandEnabled() If you omit the parameter, JavaScript assumes the most popular type, text/html — the kind of data you typically assemble in a script prior to writing to the window. The text/html type includes any images that the HTML references. Specifying any of the image types means that you have the raw binary representation of the image that you want to appear in the new document — possible, but unlikely. Another possibility is to direct the output of a write() method to a plug-in. For the mimeType parameter, specify the plug-in’s MIME type (for example, application/x-director for Shockwave). Again, the data you write to a plug-in must be in a form that it knows how to handle. The same mechanism also works for writing data directly to a helper application.
Note
IE accepts only the text/html MIME type parameter.
Modern browsers include a second, optional parameter to the method: replace. This parameter does for the document.open() method what the replace() method does for the location object. For document.open(), it means that the new document you are about to write replaces the previous document in the window or frame, with the end result that the replaced window or frame’s history is not recorded.
Example You can see an example of where the document.open() method fits in the scheme of dynamically creating content for another frame in the discussion of the document.write() method later in this chapter. Related Items: document.close(), document.clear(), document.write(), document.writeln() methods
queryCommandEnabled("commandName") queryCommandIndterm("commandName") queryCommandState("commandName") queryCommandSupported("commandName") queryCommandText("commandName") queryCommandValue("commandName") Returns: Various values Compatibility: WinIE4+, MacIE-, NN7.1, Moz1.3+, Safari+, Opera+, Chrome+ These six methods lend further support to the execCommand() method for document and TextRange objects. If you choose to use the execCommand() method to achieve some stylistic change on a text selection, you can use some of these query methods to make sure the browser supports the desired command and to retrieve any returned values. Table 29-3 summarizes the purpose and returned values for each of the query methods. Note that browser support for these seven methods is uneven. Because the execCommand() method cannot be invoked on a page while it is still loading, any such invocations that may collide with the loading of a page should check with queryCommandEnabled() prior to invoking the command. Validating that the browser version
972
Chapter 29: Document and Body Objects documentObject.recalc() running the script supports the desired command is also a good idea. Therefore, you may want to wrap any command call with the following conditional structure: if (document.queryCommandEnabled(commandName) && document.queryCommandSupported(commandName)) { // ... } TABLE 29-3
Query Commands queryCommand
Returns
Description
Enabled
Boolean
Reveals whether the document or TextRange object is in a suitable state to be invoked.
Indterm
Boolean
Reveals whether the command is in an indeterminate state.
CommandState
Boolean | null
Reveals whether the command has been completed (true), is still working (false), or is in an indeterminate state (null).
Supported
Boolean
Reveals whether the command is supported in the current browser.
Text
String
Returns any text that may be returned by a command.
Value
Varies
Returns whatever value (if any) is returned by a command.
When using a command to read information about a selection, use the queryCommandText() or queryCommandValue() methods to catch that information (recall that the execCommand() method itself returns a Boolean value regardless of the specific command invoked).
Example See the examples for these methods covered under the TextRange object in Chapter 33, ‘‘Body Text Objects.’’ Related Items: TextRange object (see Chapter 33); execCommand() method
recalc([allFlag]) Returns: Nothing Compatibility: WinIE5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeIE5 introduced the concept of dynamic properties. With the help of the setExpression() method of all elements and the expression() style sheet value, you can establish dependencies between object properties and potentially dynamic properties, such as a window’s size or a draggable element’s
973
Part IV: Document Objects Reference documentObject.releaseEvents() location. After those dependencies are established, the document.recalc() method causes those dependencies to be recalculated — usually in response to some user action, such as resizing a window or dragging an element. The optional parameter is a Boolean value. The default value, false, means that the recalculations are performed only on expressions for which the browser has detected any change since the last recalculation. If you specify true, however, all expressions are recalculated, whether they have changed or not. Mozilla 1.4 includes a feature that allows scripts to turn an iframe element’s document object into an HTML editable document. Part of the scripting incorporates the document.execCommand() and related methods. Visit http://www.mozilla.org/editor for current details and examples.
Example You can see an example of recalc() in Listing 26-32 for the setExpression() method. In that example, the dependencies are between the current time and properties of standard element objects. Related Items: getExpression(), removeExpression(), setExpression() methods (see Chapter 26, ‘‘Generic HTML Element Objects’’)
releaseEvents(eventTypeList) Returns: Nothing Compatibility: WinIE-, MacIE-, NN4+, Moz-, Safari-, Opera-, ChromeIn NN4+, as soon as you enable event capture for a particular event type in a document, that capture remains in effect until the page unloads or you specifically disable the capture. You can turn off event capture for each event via the releaseEvents() method. See Chapter 32, ‘‘Event Objects,’’ for more details on event capture and release. Related Items: captureEvents(), routeEvent() methods
routeEvent([eventObject]) Returns: Nothing Compatibility: WinIE-, MacIE-, NN4+, Moz-, Safari-, Opera-, ChromeIf you capture a particular event type in NN4, your script may need to perform some limited processing on that event before letting it reach its intended target. To let an event pass through the object hierarchy to its target, you use the routeEvent() method, passing as a parameter the event object being handled in the current function. See Chapter 32, ‘‘Event Objects,’’ for more details on event processing. Related Items: captureEvents(), releaseEvents() methods
Chapter 29: Document and Body Objects documentObject.writeln Both of these methods send text to a document for display in its window. The only difference between the two methods is that document.writeln() appends a carriage return to the end of the string it sends to the document. This carriage return is helpful for formatting source code when viewed through the browser’s source view window. For new lines in rendered HTML that is generated by these methods, you must still write a to insert a line break. A common, incorrect conclusion that many JavaScript newcomers make is that these methods enable a script to modify the contents of an existing document, which is not true. As soon as a document has loaded into a window (or frame), the only fully backward-compatible text that you can modify without reloading or rewriting the entire page is the content of text and textarea objects. In IE4+, you can modify HTML and text through the innerHTML, innerText, outerHTML, and outerText properties of any element. For W3C DOM–compatible browsers, you can modify an element’s text by setting its nodeValue or innerHTML properties. The preferred approach for modifying the content of a node involves strict adherence to the W3C DOM, which requires creating and inserting or replacing new elements, as described in Chapter 26, and demonstrated in examples throughout this chapter and the rest of the book. The two safest ways to use the document.write() and document.writeln() methods are to:
Write some or all of the page’s content by way of scripts embedded in the document
Send HTML code either to a new window or to a separate frame in a multiframe window
For the first case, you essentially interlace script segments within your HTML. The scripts run as the document loads, writing whatever scripted HTML content you like. This task is exactly what you did in script1.html in Chapter 3, ‘‘Selecting and Using Your Tools.’’ This task is also how you can have one page generate browser-specific HTML when a particular class of browser requires unique syntax. In the latter case, a script can gather input from the user in one frame and then algorithmically determine the layout and content destined for another frame. The script assembles the HTML code for the other frame as a string variable (including all necessary HTML tags). Before the script can write anything to the frame, it can optionally open the layout stream (to close the current document in that frame) with the parent.frameName.document.open() method. In the next step, a parent.frameName.document.write() method pours the entire string into the other frame. Finally, a parent.frameName.document.close() method ensures that the total data stream is written to the window. Such a frame looks just the same as if it were created by a source document on the server rather than on-the-fly in memory. The document object of that window or frame is a full citizen as a standard document object. You can, therefore, even include scripts as part of the HTML specification for one of these temporary HTML pages. After an HTML document (containing a script that is going to write via the write() or writeln() methods) loads completely, the page’s incoming stream closes automatically. If you then attempt to apply a series of document.write() statements, the first document.write() method completely removes all vestiges of the original document. That includes all of its objects and scripted variable values. Therefore, if you try to assemble a new page with a series of document.write() statements, the script and variables from the original page will be gone before the second document.write() statement executes. To get around this potential problem, assemble the content for the new screen as one string variable, and then pass that variable as the parameter to a single document.write() statement. Also be sure to include a document.close() statement in the next line of script. Assembling HTML in a script to be written via the document.write() method often requires skill in concatenating string values and nesting strings. A number of JavaScript String object shortcuts facilitate the formatting of text with HTML tags (see Chapter 15, ‘‘The String Object,’’ for details).
975
Part IV: Document Objects Reference documentObject.writeln If you are writing to a different frame or window, you are free to use multiple document.write() statements if you like. Whether your script sends lots of small strings via multiple document .write() methods, or assembles a larger string to be sent through one document.write() method, depends partly on the situation and partly on your own scripting style. From a performance standpoint, a fairly standard procedure is to do more preliminary work in memory and place as few I/O (input/output) calls as possible. On the other hand, making a difficult-to-track mistake is easier in string concatenation when you assemble longer strings. You should use the system that’s most comfortable for you. You may see another little-known way of passing parameters to these methods. Instead of concatenating string values with the plus (+) operator, you can also bring string values together by separating them with commas, in which case the strings appear to be arguments to the document.write() method. For example, the following two statements produce the same results: document.write("Today is " + new Date()); document.write("Today is ",new Date());
Neither form is better than the other, so use the one that feels more comfortable to your existing programming style.
Note Dynamically generating scripts requires an extra trick, especially in NN. The root of the problem is that if you try code such as document.write(""), the browser interprets the end script tag as the end of the script that is doing the writing. You have to trick the browser by separating the end tag into a couple of components. Escaping the forward slash also helps. For example, if you want to load a different .js file for each class of browser, the code looks similar to the following:
// variable ‘browserVer’ is a browser-specific string // and ‘page’ is the HTML your script is accumulating // for document.write() page += "";
Using the document.open(), document.write(), and document.close() methods to display images in a document requires some small extra steps. First, any URL assignments that you write via document.write() must be complete (not relative) URL references. Alternatively, you can write the tag for the dynamically generated page so that its href attribute value matches that of the file that is writing the page. The other image trick is to be sure to specify height and width attributes for every image, scripted or otherwise. Document-rendering performance is improved on all platforms, because the values help the browser lay out elements even before their details are loaded. In addition to the document.write() example that follows (see Listings 29-14 through 29-16), you can find fuller implementations that use this method to assemble images and bar charts in many of the applications in Chapters 52 through 61 on the CD-ROM. Because you can assemble any valid HTML as a string to be written to a window or frame, a customized, on-the-fly document can be as elaborate as the most complex HTML document that you can imagine.
Example The example in Listings 29-14 through 29-16 demonstrates several important points about using the document.write() and document.writeln() methods for writing to another frame. First is
976
Chapter 29: Document and Body Objects documentObject.writeln the fact that you can write any HTML code to a frame, and the browser accepts it as if the source code came from an HTML file somewhere. In the example, we assemble a complete HTML document, including basic HTML tags for completeness. LISTING 29-14
A Frameset for the Document Writing Example Writin’ to the doc
LISTING 29-15
Writing a Document Based upon User Input Document Write Controller function takePulse(form) { var msg = "On The Fly with " + form.yourName.value + ""; msg += "Good Day " + form.yourName.value + "!"; for (var i = 0; i < form.how.length; i++) { if (form.how[i].checked) { msg += form.how[i].value; break; } } msg += "Make it a great day!"; parent.Frame2.document.write(msg); parent.Frame2.document.close(); }
continued
977
Part IV: Document Objects Reference documentObject.writeln LISTING 29-15
(continued)
function getTitle() { alert("Lower frame document.title is now:" + parent.Frame2.document.title); } // bind the event handlers function addEvent(elem, evtType, func) { if (elem.addEventListener) { elem.addEventListener(evtType, func, false); } else if (elem.attachEvent) { elem.attachEvent("on" + evtType, func); } else { elem["on" + evtType] = func; } } addEvent(window, "load", function() { addEvent(document.getElementById("enter"), "click", function(evt) {takePulse(document.getElementById("enter").form) }); addEvent(document.getElementById("peek"), "click", getTitle); }); Fill in a name, and select how that person feels today. Then click "Write To Below" to see the results in the bottom frame. Enter your first name:
How are you today? Swell Pretty Good So-So
978
Chapter 29: Document and Body Objects documentObject.writeln
LISTING 29-16
A Placeholder Page for the Document Writing Example Placeholder
It is important to note that this example customizes the content of the document based on user input. This customization makes the experience of working with your web page feel far more interactive to the user — yet you’re doing it without any server-side programs. The second point we want to bring home is that the document created in the separate frame by the document.write() method is a genuine document object. In this example, the tag of the written document changes if you redraw the lower frame after changing the entry of the name field in the upper frame. If you click the lower button after updating the bottom frame, you see that the document.title property has, indeed, changed to reflect the tag written to the browser in the course of displaying the frame’s page. The fact that you can artificially create full-fledged, JavaScript document objects on the fly represents one of the most important powers of serverless CGI scripting (for information delivery to the user) with JavaScript. You have much to take advantage of here if your imagination is up to the task. Note that you can easily modify Listing 29-15 to write the results to the same frame as the document containing the field and buttons. Instead of specifying the lower frame: parent.frames[1].document.open(); parent.frames[1].document.write(msg); parent.frames[1].document.close();
The code simply can use: document.open(); document.write(msg); document.close();
This code would replace the form document with the results and not require any frames in the first place. Because the code assembles all of the content for the new document into one variable value, that data survive the one document.write() method.
979
Part IV: Document Objects Reference documentObject.onselectionchange The frameset document (see Listing 29-14) creates a blank frame by loading a blank document (see Listing 29-16). An alternative that we highly recommend is to have the framesetting document fill the frame with a blank document of its own creation. See the section ‘‘Blank frames’’ in Chapter 27, ‘‘Window and Frame Objects,’’ for further details about this technique. Related Items: document.open(); document.close(); document.clear() methods
Event handlers onselectionchange Compatibility: WinIE5.5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe onselectionchange event can be triggered by numerous user actions, although all of those actions occur on elements that are under the influence of the WinIE5.5+ edit mode. Related Item: oncontrolselect event handler
onstop Compatibility: WinIE5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe onstop event fires in WinIE5+ when the user clicks the browser’s Stop button. Use this event handler to stop potentially runaway script execution on a page, because the Stop button does not otherwise control scripts after a page has loaded. If you are having a problem with a runaway repeat loop during development, you can temporarily use this event handler to let you stop the script for debugging.
Example Listing 29-17 provides a simple example of an intentional infinitely looping script. In case you load this page into a browser other than IE5+, you can click the Halt Counter button to stop the looping. The Halt Counter button, as well as the onstop event handler, invokes the same function. LISTING 29-17
Stopping a Script Using the onstop Event Handler onStop Event Handler var counter = 0; var timerID; function startCounter() { document.forms[0].display.value = ++counter; //clearTimeout(timerID) timerID = setTimeout("startCounter()", 10); } function haltCounter()
Click the browser’s Stop button (in IE) to stop the script counter.
Related Items: Repeat loops (Chapter 21, ‘‘Control Structures and Exception Handling’’)
body Element Object Compatibility: WinIE4+, MacIE4+, NN6+, Moz+, Safari+, Opera+, Chrome+ For HTML element properties, methods, and event handlers, see Chapter 26, ‘‘Generic HTML Element Objects.’’
981
Part IV: Document Objects Reference
Properties
Methods
Event Handlers
alink
createControlRange()
onafterprint
background
createTextRange()
onbeforeprint
bgColor
doScroll()
onscroll
bgProperties bottomMargin leftMargin link noWrap rightMargin scroll scrollLeft scrollTop text topMargin vLink
Syntax Accessing body element object properties or methods: [window.] document.body.property | method([parameters])
About this object In object models that reveal HTML element objects, the body element object is the primary container of the content that visitors see on the page. The body contains all rendered HTML. This special place in the node hierarchy gives the body object some unique powers, especially in the IE object model. As if to signify the special relationship, both the IE and W3C object models provide the same shortcut reference to the body element: document.body. As a first-class HTML element object (as evidenced by the long lists of properties, methods, and event handlers covered in Chapter 26), you are also free to use other syntaxes to reach the body element. You are certainly familiar with several body element attributes that govern body-wide content appearance, such as link colors (in three states) and background (color or image). But IE and NN/Mozilla (and the W3C so far) have some very different ideas about the body element’s role in scripting documents. Many methods and properties that NN/Mozilla considers to be the domain of the window (for example, scrolling, inside window dimensions, and so forth), IE puts into the hands of the body element object. Therefore, whereas NN/Mozilla scrolls the window (and whatever it may contain), IE scrolls the body (inside whatever window it lives). And because the body element
982
Chapter 29: Document and Body Objects bodyObject.background fills the entire viewable area of a browser window or frame, that viewable rectangle is determined in IE by the body’s scrollHeight and scrollWidth properties, whereas NN4+/Moz features window.innerHeight and window.innerWidth properties. This distinction is important to point out because when you are scripting window- or document-wide appearance factors, you may have to look for properties and methods for the window or body element object, depending on your target browser(s).
Note Use caution when referencing the document.body object while the page is loading. The object may not officially exist until the page has completely loaded. If you need to set some initial properties through scripting, do so in response to the onload event handler located in the tag. Attempts at setting body element object properties in immediate scripts inside the head element may result in error messages about the object not being found.
Properties alink bgColor link text vLink Value: Hexadecimal triplet or color name string
Read/Write
Compatibility: WinIE4+, MacIE4+, NN6+, Moz+, Safari+, Opera+, Chrome+ The aLink, link, and vLink properties replaced the ancient document properties alinkColor, linkColor, and vlinkColor. The bgColor property is the same as the old document.bgColor property, while the text property replaced the document.fgColor property. These properties serve as the scripted equivalents of the HTML attributes for the body element — the new property names more closely align themselves with the HTML attributes than the old property names. We use past tense when referring to these properties because CSS has largely made them obsolete. Granted, they still work, but will likely fall into disuse as web developers continue to embrace style sheets as the preferred means of altering color in web pages. Link colors that are set through pseudo-class selectors in style sheets (as style attributes of the body element) must be accessed through the style property for the body object.
background Value: URL string
Read/Write
Compatibility: WinIE4+, MacIE4+, NN6+, Moz+, Safari+, Opera+, Chrome+ The background property enables you to set or get the URL for the background image (if any) assigned to the body element. A body element’s background image overlays the background color in case both attributes or properties are set. To remove an image from the document’s background, set the document.body.background property to an empty string. Similar to the properties that provide access to colors on the page, the background image in modern web pages should be set through style sheets, as opposed to the body.background property. In that case, you access the background programmatically through the style property of the body object.
983
Part IV: Document Objects Reference bodyObject.bgcolor
bgColor (See aLink)
bgProperties Value: String constant
Read/Write
Compatibility: WinIE4+, MacIE4+, NN-, Moz-, Safari-, Opera-, ChromeThe IE-specific bgProperties property is an alternative way of adjusting whether the background image should remain fixed when the user scrolls the document or scroll with the document. Initial settings for this behavior should be done through the background-attachment CSS attribute and modified under script control by way of the body element’s style.backgroundAttachment property. No matter which way you reference this property, the only allowable values are the string constants scroll (the default) or fixed.
Example Both of the following statements change the default behavior of background image scrolling in IE4+: document.body.bgProperties = "fixed";
or document.body.style.backgroundAttachment = "fixed";
The added benefit of using the style sheet version is that it also works in NN6+/Moz and other W3C browsers. Related Item: body.background property
Compatibility: WinIE4+, MacIE4+, NN-, Moz-, Safari-, Opera-, ChromeThe four IE-specific margin properties are alternatives to setting the corresponding four margin style sheet attributes for the body element (body.style.marginBottom, and so on). Style sheet margins represent blank space between the edge of an element’s content and its next outermost container. In the case of the body element, that container is an invisible document container. Of the four properties, only the one for the bottom margin may be confusing, if the content does not fill the vertical space of a window or frame. The margin value is not automatically increased to accommodate the extra blank space.
Example Both of the following statements change the default left margin in IE4+. The style sheet version has an added benefit — it also works in NN6+/Moz and other W3C browsers. document.body.leftMargin = 30;
984
Chapter 29: Document and Body Objects bodyObject.scroll and document.body.style.marginLeft = 30;
Related Item: style object
leftMargin (See bottomMargin)
link (See aLink)
noWrap Value: Boolean
Read/Write
Compatibility: WinIE4+, MacIE4+, NN-, Moz-, Safari-, Opera-, ChromeThe nowrap property enables you to modify the body element behavior normally set through the HTML nowrap attribute. Because the property name is a negative, the Boolean logic needed to control it can get confusing. The default behavior for a body element is for text to wrap within the width of the window or frame. This behavior occurs when the value of noWrap is its default value of false. By turning noWrap to true, a line of text continues to render past the right edge of the window or frame until the HTML contains a line break (or end of paragraph). If the text continues on past the right edge of the window, the window (or frame) gains a horizontal scroll bar (unless, of course, a frame is set to not scroll). By and large, users don’t like to scroll in any direction if they don’t have to. Unless you have a special need to keep single lines intact, let the default behavior rule the day.
Example To change the word-wrapping behavior from the default, the statement is: document.body.noWrap = true;
Related Items: None
rightMargin (See bottomMargin)
scroll Value: Constant string
Read/Write
Compatibility: WinIE4+, MacIE4+, NN-, Moz-, Safari-, Opera-, ChromeThe IE-specific scroll property provides scripted access to the IE-specific scroll attribute of a body element. By default, an IE body element displays a vertical scroll bar even if the height of the content does not warrant it; a horizontal scroll bar appears only when the content is forced to be wider than the window or frame. You can make sure that both scroll bars are hidden by setting the scroll attribute to no or changing it through a script. Possible values for this property are the constant strings yes and no.
985
Part IV: Document Objects Reference bodyObject.scrollLeft Except for frame attributes and NN4+/Moz-signed scripts, other browsers do not provide facilities for turning off scroll bars under script control. You can generate a new window (via the window.open() method) and specify that its scroll bars be hidden.
Example To change the scroll bar appearance from the default, the statement is: document.body.scroll = "no";
Related Items: window.scrollbars property; window.open() method
scrollLeft scrollTop Value: Integer
Read/Write
Compatibility: WinIE4+, MacIE4+, NN7+, Moz+, Safari+, Opera+, Chrome+ Even though the scrollLeft and scrollTop properties of the body object are the same as those for generic HTML element objects, they play an important role in determining the placement of positioned elements (described more fully in Chapter 43). Because the mouse event and element position properties tend to be relative to the visible content region of the browser window, you must take the scrolling values of the document.body object into account when assigning an absolute position. Values for both of these properties are integers representing pixels.
Example Listing 29-18 is an unusual construction that creates a frameset and the content for each of the two frames, all within a single HTML document. In the left frame of the frameset are two fields that are ready to show the pixel values of the right frame’s xOffset and yOffset properties. The content of the right frame is a 30-row table of fixed width (800 pixels). Mouse-click events are captured by the document level (see Chapter 32), allowing you to click any table or cell border, or outside the table, to trigger the showOffsets() function in the right frame. That function is a simple script that displays the page offset values in their respective fields in the left frame. LISTING 29-18
Determining Scroll Values Master of all Windows function leftFrame() { var output = "Body Scroll Values\n"; output += "body.scrollLeft:\n"; output += "body.scrollTop:\n"; output += "";
986
Chapter 29: Document and Body Objects bodyObject.createControlRange() return output; } function rightFrame() { var output = "\n"; output += "function showOffsets() {\n"; output += "parent.readout.document.forms[0].xOffset.value "; output += "= document.body.scrollLeft\n"; output += "parent.readout.document.forms[0].yOffset.value "; output += "= document.body.scrollTop\n}\n"; output += "document.onclick = showOffsets\n"; output += "Content Page\n"; output += "Scroll this frame and click on a table border to view "; output += "page offset values.\n"; output += "
"; var oneRow = "
Cell 1
Cell 2
Cell "; oneRow += "3
Cell 4
Cell 5"; for (var i = 1; i imageDB.length - 1) { gifIndex = 0; } document.selections.cached.selectedIndex = gifIndex; loadCached(document.selections); var timeoutID = setTimeout("checkTimer()",5000); } } // reset form controls to defaults on unload function resetSelects() { for (var i = 0; i < document.forms.length; i++) { for (var j = 0; j < document.forms[i].elements.length; j++) { if (document.forms[i].elements[j].type == "select-one") { document.forms[i].elements[j].selectedIndex = 0; } } } } // get things rolling function init() { loadIndividual(document.selections); loadCached(document.selections); setTimeout("checkTimer()",5000); } Image Object
Individually Loaded
Pre-cached
Image:
1020
Chapter 31: Image, Area, Map, and Canvas Objects imageObject.useMap
Select image:
Wires Keyboard Discs Cables
Bands Clips Lamp Erasers
Auto-cycle through pre-cached images
Related Items: img.lowsrc, img.nameProp properties
start Value: String
Read/Write
Compatibility: WinIE4-6, MacIE4+, NN-, Moz-, Safari-, Opera-, ChromeThe start property works in conjunction with video clips viewed through the img element in IE4+. By default, a clip starts playing (except on the Macintosh) when the image file opens. This follows the default setting of the start property: "fileopen". Another recognized value is "mouseover", which prevents the clip from running until the user rolls the mouse pointer atop the image. Related Items: img.dynsrc, img.loop properties
useMap Value: Identifier string
Read/Write
Compatibility: WinIE4+, MacIE4+, NN6+, Moz+, Safari+, Opera+, Chrome+ The useMap property represents the usemap attribute of an img element, pointing to the name assigned to the map element in the page (see Listing 31-6). This map element contains the details
1021
Part IV: Document Objects Reference imageObject.vspace about the client-side image map (described later in this chapter). The value for the useMap property must include the hash mark that defines an internal HTML reference on the page. If you need to switch between two or more image maps for the same img element (for example, you swap images or the user is in a different mode), you can define multiple map elements with different names. Then, change the value of the useMap property for the img element object to associate a different map with the image. Related Item: isMap property
vspace (See hspace)
width (See height)
x y Value: Integer
Read-Only
Compatibility: WinIE-, MacIE-, NN4, Moz1+, Safari1+, Opera-, Chrome+ A script can retrieve the x and y coordinates of an img element (the top-left corner of the rectangular space occupied by the image) via the x and y properties. These properties are read-only. They are generally not used, in favor of the offsetLeft and offsetTop properties of any element, which are also supported in IE. Related Items: img.offsetLeft, img.offsetTop properties; img.scrollIntoView(), window.scrollTo() methods
Event handlers onabort onerror Compatibility: WinIE4+, MacIE4+, NN3+, Moz-, Safari-, Opera-, ChromeYour scripts may need to be proactive when a user clicks the Stop button while an image loads or when a network or server problem causes the image transfer to fail. Use the onabort event handler to activate a function in the event of a user clicking the Stop button; use the onerror event handler for the unexpected transfer snafu. Be aware that while onerror works in all browsers, onabort does not. In practice, these event handlers don’t supply all the information you may like to have in a script, such as the filename of the image that’s loading at the time. If such information is critical to your scripts, the scripts need to store the name of a currently loading image to a variable before they set the image’s src property. You also don’t know the nature of the error that triggers an error event. You can treat such problems by forcing a scripted page to reload or by navigating to an entirely different spot in your web site.
Example Listing 31-4 includes an onabort event handler. If the images already exist in the cache, you must quit and relaunch the browser to try to stop the image from loading. In that example, we provide a
1022
Chapter 31: Image, Area, Map, and Canvas Objects imageObject.onload reload option for the entire page. How you handle the exception depends a great deal on your page design. Do your best to smooth over any difficulties that users may encounter.
onload Compatibility: WinIE3+, MacIE3+, NN2+, Moz+, Safari+, Opera+, Chrome+ An img object’s onload event handler fires when one of three actions occurs: an image’s lowsrc image finishes loading; in the absence of a lowsrc image specification, the src image finishes loading; or when each frame of an animated GIF (GIF89a format) appears. It’s important to understand that if you define a lowsrc file inside an tag, the img object receives no further word about the src image having completed its loading. If this information is critical to your script, verify the current image file by checking the src property of the Image object. Be aware, too, that an img element’s onload event handler may fire before the other elements on the page have completed loading. If the event handler function refers to other elements on the page, the function should verify the existence of other elements prior to addressing them. Quit and restart your browser, or clear your cache, to get the most from Listing 31-4. As the document first loads, the lowsrc image file (the picture of pencil erasers) loads ahead of the NASA image. (Recall that the lowsrc property is not supported by all browsers, so you won’t necessarily see the pencil erasers loaded ahead of the NASA image.) Again, we deliberately chose to load a large image directly from the NASA web site so that you would have more time to see the behavior of the onload event handler. When the erasers are loaded, the onload event handler writes ‘‘done’’ to the text field, even though the main image (the NASA image) is not loaded yet. LISTING 31-4
The Image onload Event Handler The Image onload Event Handler function loadIt(theImage,form) { if (document.images) { form.result.value = ""; document.images[0].lowsrc = "desk1.gif"; document.images[0].src = theImage; } } function checkLoad(form) { if (document.images) { form.result.value = document.images[0].complete; }
continued
1023
Part IV: Document Objects Reference areaObject LISTING 31-4
(continued)
} function signal() { if(confirm("You have stopped the image from loading. Do you want to try again?")) { location.reload(); } } The Image onload Event Handler Click the browser’s STOP button to invoke the onabort event handler
Related Items: img.src, img.lowsrc properties
area Element Object For HTML element properties, methods, and event handlers, see Chapter 26, ‘‘Generic HTML Element Objects.’’ Properties
alt coords hash host hostname href
1024
Methods
Event Handlers
Chapter 31: Image, Area, Map, and Canvas Objects areaObject Properties
Methods
Event Handlers
noHref pathname port protocol search shape target
Syntax Accessing area element object properties: (NN3+/IE4+) (IE4+) (IE4+) (IE5+/W3C) (IE5+/W3C)
About this object Document object models treat an image map area object as one of the link (a element) objects in a document (see the anchor object in Chapter 30, ‘‘Link and Anchor Objects’’). When you think about it, such treatment is not illogical at all because clicking a map area generally leads the user to another document or anchor location in the same document — a hyperlinked reference. Although the HTML definitions of links and map areas differ greatly, the earliest scriptable implementations of both kinds of objects had nearly the same properties and event handlers. Starting with IE4, NN6/Moz, and W3C-compatible browsers, all area element attributes are accessible as scriptable properties. Moreover, you can change the makeup of client-side image map areas by way of the map element object. The map element object contains an array of area element objects nested inside. You can remove, modify, or add to the area elements inside the map element. Client-side image maps are fun to work with, and they have been well documented in HTML references since Netscape Navigator 2 introduced the feature. Essentially, you define any number of areas within the image, based on shape and coordinates. Many graphics tools can help you capture the coordinates of images that you need to enter into the coords attribute of the tag.
Tip If one gotcha exists that trips up most HTML authors, it’s the tricky link between the and tags. You must assign a name to the ; in the tag, the usemap attribute requires a hash symbol (#) and the map name. If you forget the hash symbol, you can’t create a connection between the image and its map.
1025
Part IV: Document Objects Reference areaObject Listing 31-5 contains an example of a client-side image map that allows you to navigate through different geographical features of the Middle East. As you drag the mouse around an aerial image, certain regions cause the mouse pointer to change, indicating that there is a link associated with the region. Clicking a region results in an alert box indicating which region you clicked. LISTING 31-5
A Simple Client-Side Image Map Image Maps function show(msg) { window.status = msg; return true; } function go(where) { alert("We’re going to " + where + "!"); } function clearIt() { window.status = ""; return true; } Sinai and Vicinity
Properties alt Value: String
Read/Write
Compatibility: WinIE4+, MacIE4+, NN6+, Moz+, Safari+, Opera+, Chrome+ The alt property represents the alt attribute of an area. Internet Explorer displays the alt text in a tiny pop-up window (tool tip) above an area when you pause (hover) the mouse pointer over it. There is debate among web developers about Microsoft’s usage of tool tips for alt text, both in image maps and regular images. Future browsers may implement this attribute to provide additional information about the link associated with the area element. For the time being, Internet Explorer is the only mainstream browser to use the alt property in any noticeable way, although all the browsers recognize it. Related Item: title property
coords shape Value: String
Read/Write
Compatibility: WinIE4+, MacIE4+, NN6+, Moz+, Safari+, Opera+, Chrome+ The coords and shape properties control the location, size, and shape of the image hot spot governed by the area element. Shape values that you can use for this property control the format of the coords property values, as follows: Shape
Coordinates
Example
circ
center-x, center-y, radius
"30, 30, 20"
circle
center-x, center-y, radius
"30, 30, 20"
poly
x1, y1, x2, y2, . . .
"0, 0, 0, 30, 15, 30, 0, 0"
polygon
x1, y1, x2, y2, . . .
"0, 0, 0, 30, 15, 30, 0, 0"
rect
left, top, right, bottom
"10, 20, 60, 40"
rectangle
left, top, right, bottom
"10, 20, 60, 40"
1027
Part IV: Document Objects Reference areaObject.hash The default shape for an area is a rectangle. Related Items: None
hash host hostname href pathname port protocol search target (See corresponding properties of the link object in Chapter 30, ‘‘Link and Anchor Objects.’’)
noHref Value: Boolean
Read/Write
Compatibility: WinIE4+, MacIE4+, NN6+, Moz+, Safari+, Opera+, Chrome+ The noHref property is used to enable or disable a particular area within a map. The values of the property may be true, which means an area is enabled, or false to prevent the area from serving as a link within the map. The actual behavior in any of the browsers may be unpredictable, so test carefully.
shape (See coords)
map Element Object For HTML element properties, methods, and event handlers, see Chapter 26, ‘‘Generic HTML Element Objects.’’ Properties
Methods
Event Handlers
onscroll†
areas[] name † See
Chapter 29
Syntax Accessing map element object properties: (IE4+) (IE5+/W3C)
Chapter 31: Image, Area, Map, and Canvas Objects mapObject.areas[]
About this object The map element object is an invisible HTML container for all area elements, each of which defines a ‘‘hot’’ region for an image. Client-side image maps associate links (and targets) to rectangular, circular, or polygonal regions of the image. By far, the most important properties of a map element object are the areas array and, to a lesser extent, the name. It is unlikely that you will change the name of a map. (It is better to define multiple map elements with different names, and then assign the desired name to an img element object’s useMap property.) But you can use the areas array to change the makeup of the area objects inside a given client-side map.
Properties areas[] Value: Array of area element objects
Read/Write
Compatibility: WinIE4+, MacIE4+, NN6+, Moz+, Safari+, Opera+, Chrome+ Use the areas array to iterate through all area element objects within a map element. Whereas Mozilla-based and WebKit-based browsers adhere closely to the document node structure of the W3C DOM, IE4+ provides more direct access to the area element objects nested inside a map. If you want to rewrite the area elements inside a map, you can clear out the old ones by setting the length property of the areas array to zero. Then assign area element objects to slots in the array to build that array. Listing 31-6 demonstrates how to use scripting to replace the area element objects inside a map element. The scenario is that the page loads with one image of a computer keyboard. This image is linked to the keyboardMap client-side image map, which specifies details for three hot spots on the image. If you then switch the image displayed in that img element, scripts change the useMap property of the img element object to point to a second map that has specifications more suited to the desk lamp in the second image. Roll the mouse pointer atop the images, and view the URLs associated with each area in the status bar (for this example, the URLs do not lead to other pages). Another button on the page, however, invokes the makeAreas() function (not supported by MacIE5), which creates four new area element objects and (through DOM-specific pathways) adds those new area specifications to the image. If you roll the mouse atop the image after the function executes, you can see that the URLs now reflect those of the new areas. Also note the addition of a fourth area, whose status bar message appears in Figure 31-2. LISTING 31-6
Modifying area Elements On-the-Fly map Element Object // generate area elements on-the-fly function makeAreas()
continued
1029
Part IV: Document Objects Reference mapObject.areas[] LISTING 31-6
(continued)
{ document.getElementById("myIMG").src = "desk3.gif"; // build area element objects var area1 = document.createElement("area"); area1.href = "Script-Made-Shade.html"; area1.shape = "polygon"; area1.coords = "52,28,108,35,119,29,119,8,63,0,52,28"; var area2 = document.createElement("area"); area2.href = "Script-Made-Base.html"; area2.shape = "rect"; area2.coords = "75,65,117,87"; var area3 = document.createElement("area"); area3.href = "Script-Made-Chain.html"; area3.shape = "polygon"; area3.coords = "68,51,73,51,69,32,68,51"; var area4 = document.createElement("area"); area4.href = "Script-Made-Emptyness.html"; area4.shape = "rect"; area4.coords = "0,0,50,120"; // stuff new elements into MAP child nodes var mapObj = document.getElementById("lamp_map"); while (mapObj.childNodes.length) { mapObj.removeChild(mapObj.firstChild); } mapObj.appendChild(area1); mapObj.appendChild(area2); mapObj.appendChild(area3); mapObj.appendChild(area4); // workaround NN6 display bug document.getElementById("myIMG").style.display = "inline"; } function changeToKeyboard() { document.getElementById("myIMG").src = "cpu2.gif"; document.getElementById("myIMG").useMap = "#keyboardMap"; } function changeToLamp() { document.getElementById("myIMG").src = "desk3.gif"; document.getElementById("myIMG").useMap = "#lampMap"; } map Element Object
1030
Chapter 31: Image, Area, Map, and Canvas Objects mapObject.areas[]
FIGURE 31-2
Scripts created a special client-side image map for the image.
1031
Part IV: Document Objects Reference mapObject.name Related Items: area element object
name Value: String
Read/Write
Compatibility: WinIE4+, MacIE4+, NN6+, Moz+, Safari+, Opera+, Chrome+ A relationship between the image map and the image needs to be created. We do this with the value of the name property for an image map: it matches the value of the corresponding image’s useMap property. Related Item: useMap property of the corresponding image
canvas Element Object For HTML element properties, methods, and event handlers, see Chapter 26, ‘‘Generic HTML Element Objects.’’ Properties
About this object A canvas is a relatively new construct that enables you to create a rectangular region on a page that can be drawn to programmatically through JavaScript. Relative to a web page, a canvas appears as an image since it occupies a rectangular space. Unlike images, however, canvas content is generated programmatically using a series of methods defined on the canvas object. Support for canvases first appeared in the Safari browser in version 1.3, and then spread to Mozilla browsers in Mozilla version 1.8, which corresponds to Firefox 1.5. While the current version of IE does not natively support this object, there are third-party libraries that allow you to use this object in IE. Canvas objects are created and positioned on the page using the tag, which supports only two unique attributes: width and height. After the canvas is created, the remainder of the work associated with creating a canvas graphic falls to JavaScript code. You’ll typically want to create a special draw function that takes on the task of drawing to the canvas, upon the page loading. The job of the draw function is to use the methods of the canvas object to render the canvas graphic. Listing 31-7 contains a skeletal page for placing a basic canvas with a border. Notice that there is a draw() function that is ready to receive the code for rendering the canvas graphic.
LISTING 31-7
A Skeletal Canvas canvas Object
continued
1033
Part IV: Document Objects Reference canvasObject LISTING 31-7
(continued)
function draw() { // Draw some stuff } canvas { border: 1px solid black; } canvas Object
Listing 31-8 contains a more interesting canvas example that builds on the skeletal page by adding some actual canvas drawing code. The properties and methods in the canvas object provide you with the capability to do some amazing things, so consider this example a rudimentary scratching of the canvas surface. LISTING 31-8
A Canvas Containing a Simple Chart canvas Object function draw() { var canvas = document.getElementById(’chart’); if (canvas.getContext) { var context = canvas.getContext(’2d’); context.lineWidth = 20; // First bar context.strokeStyle = "red"; context.beginPath(); context.moveTo(20, 90); context.lineTo(20, 10); context.stroke(); // Second bar context.strokeStyle = "green"; context.beginPath(); context.moveTo(50, 90);
Figure 31-3 shows this canvas example in action, which involves the display of a simple bar chart. The thing to keep in mind is that this bar chart is being rendered programmatically using vector graphics, which is quite powerful. This example reveals a few more details about how canvases work. Notice that you must first obtain a context in order to perform operations on the canvas. (In reality, you perform graphics operations on a canvas context, not the canvas element itself.) The job of a context is to provide you with a virtual surface on which to draw. You obtain a canvas context by calling the getContext() method on the canvas object and specifying the type of context; currently, only the 2d (two-dimensional) context is supported in browsers. When you have a context, canvas drawing operations are carried out relative to the context. You are then free to tinker with stroke and fill colors, create paths and fills, and do most of the familiar graphical things that go along with vector drawing. You can find a more complete tutorial and examples dedicated to drawing with the canvas element at http://developer.mozilla.org/en/docs/Canvas_tutorial.
Part IV: Document Objects Reference canvasObject.globalAlpha FIGURE 31-3
A simple bar chart created using a vector canvas.
The fillStyle property sets the fill for the brush used in filling a region of a canvas is with a color or pattern. Although you can create gradients and other interesting patterns for use in filling shapes, the most basic usage of the fillStyle property is creating a solid color fill by setting the property to an HTML-style color (#RRGGBB). All fill operations that follow the fillStyle setting will use the new fill style.
Example Setting a fill color simply involves assigning an HTML-style color to the fillStyle property: context.fillStyle = "#FF00FF";
Related Item: strokeStyle property
globalAlpha Value: Float
Read/Write
Compatibility: WinIE-, MacIE-, NN-, Moz1.8+, Safari1.3+, Opera+, Chrome+ The globalAlpha property is a floating-point property that establishes the transparency (or opacity, depending on how you think about it) of the content drawn on a canvas. Acceptable
1036
Chapter 31: Image, Area, Map, and Canvas Objects canvasObject.lineWidth values for this property range from 0.0 (fully transparent) to 1.0 (fully opaque). The default setting is 1.0, which means that all canvases initially have no transparency.
Example To set the transparency of a canvas to 50 percent transparency, set the globalAlpha property to 0.5: context.globalAlpha = 0.5;
Related Item: None
globalCompositeOperation Value: String
Read/Write
Compatibility: WinIE-, MacIE-, NN-, Moz1.8+, Safari1.3+, Opera+, Chrome+ The globalCompositeOperation property determines how the canvas appears in relation to background content on a web page. This is a powerful property because it can dramatically affect the manner in which canvas content appears with respect to any underlying web page content. The default setting is source-over, which means opaque areas of the canvas are displayed, but transparent areas are not. Other popular settings include copy, lighter, and darker, among others.
Example If you want a canvas to always fully cover the background web page, regardless of any transparent areas it may have, you should set the globalCompositeOperation property to copy: context.globalCompositeOperation = "copy";
Compatibility: WinIE-, MacIE-, NN-, Moz1.8+, Safari1.3+, Opera+, Chrome+ These properties all impact the manner in which lines are drawn on a canvas. The lineCap property determines the appearance of line end points (butt, round, or square). Similar to lineCap is the lineJoin property, which determines how lines are joined to each other (bevel, miter, or round). By default, lines terminate with no special end point (butt) and are joined cleanly with no special joint graphic (miter). The lineWidth property establishes the width of lines and is expressed as an integer value greater than 0 in the canvas coordinate space. When a line is drawn, its width appears centered over the line coordinates.
Example You’ll often want to change the lineWidth property to get different effects when assembling a canvas graphic. Here’s an example of setting a wider line width (10 in this case): context.lineWidth = 10;
1037
Part IV: Document Objects Reference canvasObject.miterLimit Related Items: miterLimit, strokeStyle properties
miterLimit Value: Float
Read/Write
Compatibility: WinIE-, MacIE-, NN-, Moz1.8+, Safari1.3+, Opera+, Chrome+ The miterLimit property is a floating-point value that determines more specifically how lines are joined together. The miterLimit property works in conjunction with the lineJoin property to cleanly and consistently join lines in a path. Related Item: lineJoin property
Compatibility: WinIE-, MacIE-, NN-, Moz1.8+, Safari1.3+, Opera+, Chrome+ These properties all work in conjunction to establish a shadow around canvas content. The shadowBlur property determines the width of the shadow itself, whereas shadowColor sets the color of the shadow as an HTML-style RGB value (#RRGGBB). Finally, the shadowOffsetX and shadowOffsetY properties specify exactly how far the shadow is offset from a graphic. The shadowBlur, shadowOffsetX, and shadowOffsetY properties are all expressed in units of the canvas coordinate space.
Example The following code creates a shadow that is 5 units wide, light gray in color (#BBBBBB), and offset 3 units in both the X and Y directions: context.shadowBlur = 5; context.shadowColor = "#BBBBBB"; context.shadowOffsetX = 3; context.shadowOffsetY = 3;
Related Item: None
strokeStyle Value: String
Read/Write
Compatibility: WinIE-, MacIE-, NN-, Moz1.8+, Safari1.3+, Opera+, Chrome+ The strokeStyle property controls the style of strokes used to draw on the canvas. You are free to set the stroke style to a gradient or pattern using more advanced canvas features, but the simpler approach is to just set a solid colored stroke as an HTML-style color value (#RRGGBB). The default stroke style is a solid black stroke.
1038
Chapter 31: Image, Area, Map, and Canvas Objects canvasObject.arc()
Example To change the stroke style to a solid green brush, set the strokeStyle property to the color green: context.strokeStyle = "#00FF00";
Related Item: fillStyle property
Methods arc(x, y, radius, startAngle, endAngle, clockwise) arcTo(x1, y1, x2, y2, radius) bezierCurveTo(cp1x, cp1y, cp2x, cp2y, x, y) quadraticCurveTo(cpx, cpy, x, y) Returns: Nothing Compatibility: WinIE-, MacIE-, NN-, Moz1.8+, Safari1.3+, Opera+, Chrome+ These methods are all responsible for drawing curves in one way or another. If you have any experience with drawing vector graphics, then you’re probably familiar with the difference between arcs, Bezier curves, and quadratic curves. The arc() method draws a curved line based upon a center point, a radius, and start and end angles. You can think of this method as tracing the curve of a circle from one angle to another. The angles are expressed in radians, not degrees, so you’ll probably need to convert degrees to radians: var radians = (Math.PI / 180) * degrees;
The last argument to arc() is a Boolean value that determines whether or not the arc is drawn in the clockwise (true) or counterclockwise (false) direction. The arcTo() method draws an arc along a curve based upon tangent lines of a circle. This method is not implemented in Mozilla until version 1.8.1. Finally, the bezierCurveTo() and quadraticCurveTo() methods draw a curved line based upon arguments relating to Bezier and quadratic curves, respectively, which are a bit beyond this discussion. To learn more about Bezier and quadratic curves, check out en.wikipedia.org/wiki/Be ´zier_curve.
beginPath() closePath() Returns: Nothing Compatibility: WinIE-, MacIE-, NN-, Moz1.8+, Safari1.3+, Opera+, Chrome+ These two methods are used to manage paths. Call the beginPath() method to start a new path, into which you can then add shapes. When you’re finished, call closePath() to close up the path. The only purpose of closePath() is to close a subpath that is still open, meaning that you want to finish connecting an open shape back to its start. If you’ve created a path that is already closed,
1039
Part IV: Document Objects Reference canvasObject.clip() there is no need to call the closePath() method. Listing 31-8 contains a good example of where the closePath() method is unnecessary because the bar shapes don’t need to be closed.
clip() Returns: Nothing Compatibility: WinIE-, MacIE-, NN-, Moz1.8+, Safari1.3+, Opera+, Chrome+ The clip() method recalculates the clipping path based upon the current path and the clipping path that already exists. Subsequent drawing operations rely on the newly calculated clipping path.
createLinearGradient(x1, y1, x2, y2) createRadialGradient(x1, y1, radius1, x2, y2, radius2) createPattern(image, repetition) Returns: Gradient object reference, pattern object reference (createPattern()) Compatibility: WinIE-, MacIE-, NN-, Moz1.8+, Safari1.3+, Opera+, Chrome+ These methods are used to create special patterns and gradients for fill operations. A linear gradient is specified as a smooth color transition between two coordinates, whereas a radial gradient is specified based upon two circles with similar radii. You set the actual color range of a gradient by calling the addColorStop() method on the gradient object returned from the createLinearGradient() and createRadialGradient() methods. The addColorStop() method accepts a floating-point offset and a string color value as its only two arguments. The createPattern() method is used to create a fill pattern based upon an image. You provide an image object and a repetition argument for how the image is tiled when filling a region. Repetition options include repeat, repeat-x, repeat-y, and no-repeat.
drawImage(image, x, y) drawImage(image, x, y, width, height) drawImage(image, srcX, srcY, srcWidth, srcHeight, destX, destY, destWidth, destHeight) Returns: Nothing Compatibility: WinIE-, MacIE-, NN-, Moz1.8+, Safari1.3+, Opera+, Chrome+ These drawImage() methods all draw an image to the context. The difference between them has to do with if and how the image is scaled as it is drawn. The first version draws the image at a coordinate with no scaling, whereas the second version scales the image to the specified target width and height. Finally, the third version enables you to draw a portion of the image to a target location with a scaled width and height.
fill() fillRect(x, y, width, height) clearRect(x, y, width, height) Returns: Nothing
1040
Chapter 31: Image, Area, Map, and Canvas Objects canvasObject.rotate() Compatibility: WinIE-, MacIE-, NN-, Moz1.8+, Safari1.3+, Opera+, Chrome+ These methods are used to fill and clear areas. The fill() method fills the area within the current path, whereas the fillRect() method fills a specified rectangle independent of the current path. The clearRect() method is used to clear (erase) a rectangle.
getContext(contextID) Returns: Context object reference Compatibility: WinIE-, MacIE-, NN-, Moz1.8+, Safari1.3+, Opera+, Chrome+ The getContext() method operates on a canvas element object, not a context, and is used to obtain a context for further graphical operations. You must call this method to obtain a context before you can draw to a canvas since all of the canvas drawing methods are actually called relative to a context, not a canvas. For the standard two-dimensional canvas context, specify "2d" as the sole parameter to the method.
lineTo(x, y) moveTo(x, y) Returns: Nothing Compatibility: WinIE-, MacIE-, NN-, Moz1.8+, Safari1.3+, Opera+, Chrome+ These two methods are used to draw lines and adjust the stroke location. The moveTo() method simply moves the current stroke location without adding anything to the path. The lineTo() method, on the other hand, draws a line from the current stroke location to the specified point. It’s worth pointing out that drawing a line with the lineTo() method only adds a line to the current path; the line doesn’t actually appear on the canvas until you call the stroke() method to carry out the actual drawing of the path.
rect(x, y, width, height) Returns: Nothing Compatibility: WinIE-, MacIE-, NN-, Moz1.8+, Safari1.3+, Opera+, Chrome+ The rect() method adds a rectangle to the current path. Similar to other drawing methods, the rectangle is actually just added to the current path, which isn’t truly visible until you render it using the stroke() method.
restore() save() Returns: Nothing Compatibility: WinIE-, MacIE-, NN-, Moz1.8+, Safari1.3+, Opera+, Chrome+ It’s possible to save and restore the state of the graphic context, in which case you can make changes and then return to a desired state. The context state includes information such as the clip region, line width, fill color, and so forth. Call the save() and restore() methods to save and restore the context state.
1041
Part IV: Document Objects Reference canvasObject.scale()
rotate(angle) scale(x, y) translate(x, y) Returns: Nothing Compatibility: WinIE-, MacIE-, NN-, Moz1.8+, Safari1.3+, Opera+, Chrome+ All of the drawing operations that you perform on a canvas are expressed in units relative to the coordinate system of the canvas. These three methods enable you to alter the canvas coordinate system by rotating, scaling, or translating its origin. Rotating the coordinate system affects how angles are expressed in drawing operations that involve angles. Scaling the coordinate system impacts the relative size of units expressed in the system. And finally, translating the coordinate system alters the location of the origin, which affects where positive and negative values intersect on the drawing surface.
stroke() strokeRect(x, y, width, height) Returns: Nothing Compatibility: WinIE-, MacIE-, NN-, Moz1.8+, Safari1.3+, Opera+, Chrome+ Most of the drawing operations on a canvas impact the current path, which you can think of as a drawing you’ve committed to memory but have yet to put on paper. You render a path to the canvas by calling the stroke() method. If you want to draw a rectangle to the canvas without dealing with the current path, call the strokeRect() method.
1042
Event Objects
P
rior to version 4 browsers, user and system actions — events — were captured predominantly by event handlers defined as attributes inside HTML tags. For instance, when a user clicked a button, the clickevent triggered the onclick event handler in the tag. That handler may invoke a separate function or perform some inline JavaScript script. Even so, the events themselves were rather dumb: Either an event occurred or it didn’t. Where an event occurred (that is, the screen coordinates of the pointer at the moment the mouse button was clicked) and other pertinent event tidbits (for example, whether a keyboard modifier key was pressed at the same time) were not part of the equation — until version 4 browsers, that is. While remaining fully backward compatible with the event handler mechanism of old, version 4 browsers had the first event model that turn events into first-class objects whose properties automatically carry a lot of relevant information about the event when it occurs. These properties are fully exposed to scripts, allowing pages to respond more intelligently about what the user does with the page and its elements. Another new aspect of version 4 event models was the notion of ‘‘event propagation.’’ It was possible to have an event processed by an object higher up the element containment hierarchy whenever it made sense to have multiple objects share one event handler. That the event being processed carried along with it information about the intended target, plus other golden information nuggets, made it possible for event handler functions to be smart about processing the event without requiring an event handler call to pass all kinds of target-specific information. Unfortunately, the joy of this newly found power is tempered by the forces of object model incompatibility. Event object models are clearly divided along two fronts:
The IE4+ model
The model adopted by the W3C DOM Level 2, as implemented in NN6+/Moz and Gecko-, WebKit-, and Presto-based browsers
1043
IN THIS CHAPTER The ‘‘life’’ of an event object Event support in different browser generations Retrieving information from an event
Part IV: Document Objects Reference
Many of these distinctions are addressed in the overviews of the object models in Chapter 26, ‘‘Generic HTML Element Objects.’’ In this chapter, you find out more about the actual event objects that contain all the ‘‘goodies.’’ Where possible, cross-browser concerns are addressed.
Why ‘‘Events’’? Graphical user interfaces are more difficult to program than the ‘‘old-fashioned’’ command-line interface. With a command-line or menu-driven system, users were intentionally restricted in the types of actions they could take at any given moment. The world was very modal, primarily as a convenience to programmers who led users through rigid program structures. That all changes in a graphical user interface, such as Windows, Mac OS, XWindow System, or any other derived from the pioneering work of the Xerox Star system. The challenge for programmers is that a good user interface in this realm must make it possible for users to perform all kinds of actions at any given moment: roll the mouse, click a button, type a key, select text, choose a pull-down menu item, and so on. To accommodate this, a program (or, better yet, the operating system) must be on the lookout for any possible activity coming from all input ports, whether it be the mouse, keyboard, or network connection. A common methodology to accomplish this at the operating system level is to look for any kind of event, whether it comes from user action or some machine-generated activity. The operating system or program then looks up how it should process each kind of event. Such events, however, must have some smarts about them so that the program knows what, and where on the screen, the event is.
What an event knows (and when it knows it) Although the way to reference an event object varies a bit among the three event models, the one concept they all share is that an event object is created the instant the event action occurs. For instance, if you click a button, an event object is created in the browser’s memory. As the object is created, the browser assigns values to the object’s properties — properties that reflect numerous characteristics of that specific event. For a click event, that information includes the coordinates of the click, and which mouse button was used to generate the event. To be even more helpful, the browser does some quick calculations to determine that the coordinates of the click event coincide with the rectangular space of a button element on the screen. Therefore, the event object has as one of its properties a reference to the ‘‘screen thing’’ that you clicked on. Most event object properties are read-only (in some even models, all the properties are), because an event object is like a snapshot of an event action. If the event model were to allow modification of event properties, performing both potentially useful and potentially unfriendly actions would be possible. For example, how frustrating would it be to a user to attempt to type into a text box, only for a keystroke to be modified after the actual key press and a totally different character to appear in the text box? On the other hand, perhaps it may be useful in some situations to make sure that anything typed into a text box is converted to uppercase characters, no matter what is typed. Each event model brings its own philosophy to the table in this regard. For example, the IE4+ event model allows keyboard character events to be modified by script; the W3C DOM event model does not. Perhaps the most important aspect of an event object to keep in mind is that it exists only as long as scripts process the event. An event can trigger an event handler — usually a function. That function, of course, can invoke other functions. As long as statements are still executing in response to the event handler, the event object and all its properties are still ‘‘alive’’ and available to your scripts. But after the last script statement runs, the event object reverts to an empty object.
1044
Chapter 32: Event Objects
The reason an event object has such a brief life is that there can be only one event object at a time. In other words, no matter how complex your event handler functions are, or how rapidly events fire, they are executed serially (for experienced programmers: there is one execution thread). The operating system buffers events that start to bunch up on each other. Except in rare cases in which the buffer gets full and events are not recorded, event handlers are executed in the order in which the events occur.
The static Event object Up to this point, the discussion has been about the event object (with a lowercase ‘‘e’’), which is one instance of an event, with all the properties associated with that specific event action. In the W3C DOM event model, there is also a static Event object (with an uppercase ‘‘E’’) that includes additional subcategories within it. These subcategories are all covered later in this chapter, but they are introduced here to illustrate the contrast between the event and Event objects. The former, as you’ve seen, is a transient object with details about a specific event action; the latter serves primarily as a holder of event-related constant values that scripts can use. The static Event object is always available to scripts inside any window or frame. For a list of all Event object properties in NN6+/Moz and Gecko-, WebKit-, and Presto-based browsers, use The Evaluator (see Chapter 4, ‘JavaScript Essentials’): enter Event into the bottom text box (also check out the KeyEvent object in NN6+/Moz). The static Event object also turns out to be the object from which event objects are cloned. Thus, the static Event object has a number of properties and methods that apply to (are inherited by) the event objects created by event actions. These relationships are more important in the W3C DOM event model, which builds upon the DOM’s object-oriented tendencies to implement the event model.
Event Propagation Prior to version 4 browsers, an event fired on an object. If an event handler was defined for that event and that object, the handler executed; if there was no event handler, the event just disappeared into the ether. Newer browsers, however, send events on a longer ride, causing them to propagate through the document object models. As you know by now, two propagation models exist, one for each of the event models in use today: IE4+ and W3C DOM, as implemented in NN6+/Moz and Gecko-, WebKit-, and Presto-based browsers. It’s also worth mentioning the event model that is unique to NN4, which served as a third model prior to NN4 succumbing to modern browsers. The NN4 event model has historical relevance because it aids in understanding the latter two models. Conceptually, the NN4 and IE4+ propagation models are diametrically opposite each other — any NN4 event propagates inward toward the target, whereas an IE event starts at the target and propagates outward. But the W3C DOM model manages to implement both models simultaneously, albeit with all new syntax so as not to step on the older models. At the root of all three models is the notion that every event has a target. For user-initiated actions, this is fairly obvious. If you click a button or type in a text box, that button is the target of your mouse-related event; the text box is the target of your keyboard event. System-generated events are not so obvious, such as the onload event that fires after a page finishes loading. In all event models, this event fires on the window object. What distinguishes the event propagation models is how an event reaches its target, and what, if anything, happens to the event after it finishes executing the event handler associated with the target.
NN4-only event propagation Although NN4 has given way to newer browsers, its propagation model initiated some concepts that are found in the modern W3C DOM event propagation model. The name for the NN4 model is event capture.
1045
Part IV: Document Objects Reference
In NN4, all events propagate from the top of the document object hierarchy (starting with the window object) downward to the target object. For example, if you click a button in a form, the click event passes through the window and document (and, if available, layer) objects before reaching the button (the form object is not part of the propagation path). This propagation happens instantaneously, so that there is no performance penalty by this extra journey. The event that passes through the window, document, and layer objects is a fully formed event object, complete with all properties relevant to that event action. Therefore, if the event were processed at the window level, one of the event object’s properties is a reference to the target object, so that the event handler scripts at the window level can find out information, such as the name of the button, and even get a reference to its enclosing form. By default, event capture is turned off. To instruct the window, document, or layer object levels to process that passing click object, requires turning on event capture for the window, document, and/or layer object.
Enabling NN4 event capture All three objects just mentioned — window, document, and layer — have a captureEvents() method. You use this method to enable event capture at any of those object levels. The method requires one or more parameters, which are the event types (as supplied by Event object constants) that the object should capture, while letting all others pass untouched. For example, if you want the window object to capture all keypress events, you include the following statement in a script that executes as the page loads: window.captureEvents(Event.KEYPRESS);
Defining event handlers in the intended targets is also a good idea, even if they are empty (for example, onkeypress="") to help NN4 generate the event in the first place. If you want the window to capture multiple event types, string the event type constants together, separated by the pipe character: window.captureEvents(Event.KEYPRESS | Event.CLICK);
Now you must assign an action to the event, at the window’s level, for each event type. More than likely, you have defined functions to execute for the event. Assign a function reference to the event handler by setting the handler property of the window object: window.onkeypress = processKeyEvent; window.onclick = processClickEvent;
Hereafter, if a user clicks a button or types into a field inside that window, the events are processed by their respective window-level event handler functions.
Turning off event capture As soon as you enable event capture for a particular event type in a document, that capture remains in effect until the page unloads or you specifically disable the capture. You can turn off event capture for each event via the window, document, or layer releaseEvents() method. The releaseEvents() method takes the same kind of parameters — Event object type constants — as the captureEvents() method. The act of releasing an event type simply means that events go directly to their intended targets without stopping elsewhere for processing, even if an event handler for the higher-level object
1046
Chapter 32: Event Objects
is still defined. And because you can release individual event types based on parameters set for the releaseEvents() method, other events being captured are not affected by the release of others.
Passing events toward their targets If you capture a particular event type in NN4, your script may need to perform some limited processing on that event before letting it reach its intended target. For example, perhaps you want to do something special if a user clicks an element with the Shift meta key pressed. In that case, the function that handles the event at the document level inspects the event’s modifiers property to determine if the Shift key was pressed at the time of the event. If the Shift key was not pressed, you want the event to continue on its way to the element that the user clicked. To let an event pass through the object hierarchy to its target, you use the routeEvent() method, passing as a parameter the event object being handled in the current function. A routeEvent() method does not guarantee that the event will reach its intended destination, because another object in between may have event capturing for that event type turned on and will intercept the event. That object, too, can let the event pass through with its own routeEvent() method. In some cases, your scripts need to know if an event that is passed onward by the routeEvent() method activated a function that returns a value. This knowledge is especially valuable if your event must return a true or false value to let an object know if it should proceed with its default behavior (for example, whether a link should activate its href attribute URL or cancel after the event handler evaluates to return true or return false). When a function is invoked by the action of a routeEvent() method, the return value of the destination function is passed back to the routeEvent() method. That value, in turn, can be returned to the object that originally captured the event.
Event traffic cop The last scenario is one in which a higher-level object captures an event and directs the event to a particular object elsewhere in the hierarchy. For example, you could have a document-level event handler function direct every click event whose modifiers property indicates that the Alt key was pressed, to a Help button object whose own onclick event handler displays a help panel (perhaps showing an otherwise hidden layer). You can redirect an event to any object via the handleEvent() method. This method works differently from the others described in this chapter, because the object reference of this method is the reference of the object to handle the event (with the event object being passed as a parameter, such as one of the other methods). As long as the target object has an event handler defined for that event, it will process the event as if it had received the event directly from the system (even though the event object’s target property may be some other object entirely).
IE4+ event propagation IE’s event propagation model is called event bubbling, since events ‘‘bubble’’ upward from the target object through the HTML element containment hierarchy. It’s important to distinguish between the old-fashioned document object hierarchy (followed in the NN4 event capture model) and the more modern notion of HTML element containment — a concept that carries over to the W3C DOM as well. A good way to demonstrate the effect of event bubbling — a behavior that is turned on by default — is to populate a simple document with lots of event handlers to see which ones fire and in
1047
Part IV: Document Objects Reference
what order. Listing 32-1 has onclick event handlers defined for a button inside a form, the form itself, and other elements and objects, all the way up the hierarchy to the window. LISTING 32-1
Event Bubbling Demonstration Event Bubbles function init() { window.onclick = winEvent document.onclick = docEvent; document.body.onclick = docBodEvent; } function winEvent() { alert("Event is now at the window object level."); } function docEvent() { alert("Event is now at the document object level."); } function docBodEvent() { alert("Event is now at the BODY element."); } Event Bubbles
You can try this listing in IE4+ and even NN6+/Moz , Safari, Opera, or Chrome because W3C DOM browsers also observe event bubbling. But you will notice differences in the precise propagation among WinIE4+, MacIE4+, and W3C DOM browsers. But notice that after you click the button in Listing 32-1, the event first fires at the target: the button. Then the event bubbles upward through the HTML containment to fire at the enclosing form element, next to the enclosing body element, and so on. Where the differences occur are after the body element. Table 32-1 shows the objects for which event handlers are defined in Listing 32-1, and to which objects the click event bubbles in the three classes of browsers.
1048
Chapter 32: Event Objects
Despite the discrepancies in Table 32-1, events do bubble through the most likely HTML containers that come to mind. The object level with the most global scope, and that works in all browser categories shown in the table, is the document object.
Preventing IE event bubbling Because bubbling occurs by default, there are times when you may prefer to prevent an event from bubbling up the hierarchy. For example, if you have one handler at the document level whose job is to deal with the click event from a related series of buttons, any other object that receives click events will allow those events to bubble upward to the document level unless the bubbling is cancelled. Having the event bubble up could conflict with the document-level event handler. TABLE 32-1
Event Bubbling Variations for Listing 32-1 Event Handler Location
WinIE4+/Opera
MacIE4+
NN6+/Moz/Safari/Chrome
button
Yes
Yes
Yes
form
Yes
Yes
Yes
body
Yes
Yes
Yes
HTML
Yes
No
Yes
document
Yes
Yes
Yes
window
No
No
Yes
Each event object in IE has a property called cancelBubble. The default value of this property is false, which means that the event bubbles to the next outermost container that has an event handler for that event. But if, in the execution of an event handler, that property is set to true, the event does not bubble up any higher when the processing of that handler finishes its job. Therefore, to stop an event from bubbling beyond the current event handler, include the following statement somewhere in the handler function: event.cancelBubble = true;
You can prove this to yourself by modifying the page in Listing 32-1 to cancel bubbling at any level. For example, if you change the event handler of the form element to include a statement that cancels bubbling, the event goes no further than the form in IE (while the WebKit engine and recent versions of the Mozilla/Gecko engine support some of the IE syntax, the syntax is different for NN6+/Moz browsers, as discussed later in this chapter):
Preventing IE event default action In the days when events were almost always bound to elements by way of attributes in tags, the technique to block the event’s default action was to make sure the event handler evaluated to
1049
Part IV: Document Objects Reference
return false. This is how, for instance, a form element’s onsubmit event handler could prevent
the form from carrying out the submission if client-side form validation failed. To enhance that capability — especially when events are bound by other means, such as object element properties — IE’s event object includes a returnValue property. Assign false to this property in the event handler function to block the element’s default action to the event: event.returnValue = false;
This way of blocking default actions in IE is often more effective than the old return false technique.
Redirecting events Starting with IE5.5, you can redirect an event to another element, but with some limitations. The mechanism that makes this possible is the fireEvent() method of all HTML element objects (see Chapter 26). This method isn’t so much redirecting an event as causing a brand-new event to be fired. But you can pass most of the properties of the original event object with the new event by specifying a reference to the old event object as the optional second parameter to the fireEvent() method. The big limitation in this technique, however, is that the reference to the target element gets lost in this hand-off to the new event. The srcElement property of the old event gets overwritten with a reference to the object that is the target of the call to fireEvent(). For example, consider the following onclick event handler function for a button inside a form element: function buttonEvent() { event.cancelBubble = true; document.body.fireEvent("onclick", event); }
By cancelling event bubbling, the event does not propagate upward to the enclosing form element. Instead, the event is explicitly redirected to the body element, passing the current event object as the second parameter. When the event handler function for the body element runs, its event object has information about the original event, such as the mouse button used for the click and the coordinates. But the event.srcElement property points to the document.body object. As the event bubbles upward from the body element, the srcElement property continues to point to the document.body object. You can see this at work in Listing 32-2 for IE5.5+. LISTING 32-2
Cancelling and Redirecting Events in IE5.5+ Event Cancelling & Redirecting // display alert with event object info function revealEvent(elem, evt)
1050
Chapter 32: Event Objects { var msg = "Event (from " + evt.srcElement.tagName + " at "; msg += event.clientX + "," + event.clientY + ") is now at the "; msg += elem + " element."; alert(msg); } function init() { document.onclick = docEvent; document.body.onclick = docBodEvent; } function docEvent() { revealEvent("document", event); } function docBodEvent() { revealEvent("BODY", event); } function buttonEvent(form) { revealEvent("BUTTON", event); // cancel if checked (IE4+) event.cancelBubble = form.bubbleCancelState.checked; // redirect if checked (IE5.5+) if (form.redirect.checked) { document.body.fireEvent("onclick", event); } } Event Cancelling & Redirecting
Button ‘main1’
Cancel Bubbling at BUTTON Redirect Event to BODY
Listing 32-2 is a modified version of Listing 32-1. Major additions are enhanced event handlers at each level so that you can see the tag name of the event that is regarded as the srcElement of the event, as well as the coordinates of the click event. With both check boxes unchecked, events bubble upward from the button, and the button element is then shown to be the original target all the
1051
Part IV: Document Objects Reference
way up the bubble hierarchy. If you check the Cancel Bubbling check box, the event goes no further than the button element, because that’s where event bubbling is turned off. If you then check the ‘‘Redirect Event to Body’’ check box, the original event is cancelled at the button level, but a new event is fired at the body element. But notice that by passing the old event object as the second parameter, the click location properties of the old event are applied to the new event directed at the body. This event then continues to bubble upward from the body. As a side note, if you uncheck the Cancel Bubbling check box but leave the Redirect Event box checked, you can see how the redirection is observed at the end of the button’s event handler, and that something special goes on. The original event is held aside by the browser while the redirected event bubbles upward. As soon as that event-processing branch finishes, the original bubbling propagation carries on with the form. Notice, though, that the event object still knows that it was targeted at the button element, and the other properties are intact. This means that for a time, two event objects were in the browser’s memory, but only one is ‘‘active’’ at a time. While the redirected event is propagating, the window.event object refers to that event object only.
Applying event capture WinIE 5 and later also provide a kind of event capture, which overrides all other event propagation. Intended primarily for temporary capture of mouse events, it is controlled not through the event object but via the setCapture() and releaseCapture() methods of all HTML element objects (described in Chapter 26). When you engage capture mode, all mouse events are directed to the element object that invoked the setCapture() method, regardless of the actual target of the event. This action facilitates such activities as element dragging, so that mouse events that might fire outside of the intended target (for example, when dragging the cursor too fast for the animation to track) continue to go to the target. When the drag mode is no longer needed, invoke the releaseCapture() method to allow mouse events to propagate normally.
W3C event propagation Yielding to arguments in favor of both NN4’s event capture and IE’s event bubbling, the W3C DOM group managed to assemble an event model that employs both propagation systems. Although forced to use new syntax so as not to conflict with older browsers, the W3C DOM propagation model works like the NN4 model for capture and like IE4+ for bubbling. In other words, an event bubbles by default, but you can also turn on event capture if you want. Thus, an event first trickles down the element containment hierarchy to the target; then it bubbles up through the reverse path. Event bubbling is on by default, just as in IE4+. To enable capture, you must apply a W3C DOM event listener to an object at some higher container. Use the addEventListener() method (see Chapter 26) for any visible HTML element or node. One of the parameters of the addEventListener() method determines whether the event listener function should be triggered while the event is bubbling or while it is captured. Listing 32-3 is a simplified example for NN6+/Moz/W3C that demonstrates how a click event aimed at a button can be both captured and allowed to bubble. Most event handling functions are assigned inside the init() function. Borrowing code from Listing 32-1, event handlers are assigned to the window, document, and body objects as property assignments. These are automatically treated as bubble-type event listeners. Next, two objects — document and form — are given capture-type event listeners for the click event. The document object event listener invokes the same function as the bubble-type event handler (the alert text includes some asterisks to remind you
1052
Chapter 32: Event Objects
that it is the same alert being displayed in both the capture and bubble phases of the event). For the form object, however, the capture-type event listener is directed to one function, while a bubble-type listener for the same object is directed at a separate function. In other words, the form object invokes one function as the event trickles down to the target, and another function when the event starts bubbling back up. Many of the event handler functions dynamically read the eventPhase property of the event object to reveal which phase of event propagation is in force at the instance the event handler is invoked (although an apparent bug reports the incorrect phase at the document object during event capture). LISTING 32-3
W3C Event Capture and Bubble W3C DOM Event Propagation function init() { // using old syntax to assign bubble-type event handlers window.onclick = winEvent; document.onclick = docEvent; document.body.onclick = docBodEvent; // turn on click event capture for two objects document.addEventListener("click", docEvent, true); document.forms[0].addEventListener("click", formCaptureEvent, true); // set event listener for bubble document.forms[0].addEventListener("click", formBubbleEvent, false); } function winEvent(evt) { alert("Event is now at the window object level (" + getPhase(evt) + ")."); } function docEvent(evt) { alert("Event is now at the **document** object level (" + getPhase(evt) + ")."); } function docBodEvent(evt) { alert("Event is now at the BODY level (" + getPhase(evt) + ")."); } function formCaptureEvent(evt) { alert("This alert triggered by FORM only on CAPTURE."); } function formBubbleEvent(evt) { alert("This alert triggered by FORM only on BUBBLE."); continued
1053
Part IV: Document Objects Reference
LISTING 32-3
(continued)
} // reveal event phase of current event object function getPhase(evt) { switch (evt.eventPhase) { case 1: return "CAPTURING"; break; case 2: return "AT TARGET"; break; case 3: return "BUBBLING"; break; default: return ""; } } W3C DOM Event Propagation
If you want to remove event capture after it has been enabled, use the removeEventListener() method on the same object as the event listener that was originally added (see Chapter 26). And, because multiple event listeners can be attached to the same object, specify the exact same three parameters to the removeEventListener() method that were applied to the addEventListener() method.
Preventing W3C event bubbling or capture Corresponding to the cancelBubble property of the IE4+ event object is an event object method in the W3C DOM. The method that prevents propagation in any event phase is the stopPropagation() method. Invoke this method anywhere within an event listener function. The current function executes to completion, but the event propagates no further.
1054
Chapter 32: Event Objects
Listing 32-4 extends the example of Listing 32-3 to include two check boxes that let you stop propagation at the form element in your choice of the capture or bubble phase.
LISTING 32-4
Preventing Bubble and Capture W3C DOM Event Propagation function init() { // using old syntax to assign bubble-type event handlers window.onclick = winEvent; document.onclick = docEvent; document.body.onclick = docBodEvent; // turn on click event capture for two objects document.addEventListener("click", docEvent, true); document.forms[0].addEventListener("click", formCaptureEvent, true); // set event listener for bubble document.forms[0].addEventListener("click", formBubbleEvent, false); } function winEvent(evt) { if (evt.target.type == "button") { alert("Event is now at the window object level i (" + getPhase(evt) + ")."); } } function docEvent(evt) { if (evt.target.type == "button") { alert("Event is now at the **document** object level i (" + getPhase(evt) + ")."); } } function docBodEvent(evt) { if (evt.target.type == "button") { alert("Event is now at the BODY level (" + getPhase(evt) + ")."); } } function formCaptureEvent(evt) continued
1055
Part IV: Document Objects Reference
LISTING 32-4
(continued)
{ if (evt.target.type == "button") { alert("This alert triggered by FORM only on CAPTURE."); if (document.forms[0].stopAllProp.checked) { evt.stopPropagation(); } } } function formBubbleEvent(evt) { if (evt.target.type == "button") { alert("This alert triggered by FORM only on BUBBLE."); if (document.forms[0].stopDuringBubble.checked) { evt.stopPropagation(); } } } // reveal event phase of current event object function getPhase(evt) { switch (evt.eventPhase) { case 1: return "CAPTURING"; break; case 2: return "AT TARGET"; break; case 3: return "BUBBLING"; break; default: return ""; } } W3C DOM Event Propagation Stop all propagation at FORM
1056
Chapter 32: Event Objects
Prevent bubbling past FORM
In addition to the W3C DOM stopPropagation() method, NN6+, Moz, Safari, Opera, and Chrome also support IE’s cancelBubble property for syntactical convenience.
Preventing W3C event default action The W3C DOM counterpart to IE’s returnValue property is the event object’s preventDefault() method. Invoke this method in an event handler function when you wish to block the element’s default action to the event: evt.preventDefault();
Redirecting W3C DOM events The mechanism for sending an event to an object outside the normal propagation pattern in W3C is similar to that of IE4+, although with different syntax and an important requirement. In place of the IE4+ fireEvent() method, NN6+/Moz and Gecko-, WebKit-, and Presto-based browsers use the W3C DOM dispatchEvent() method. The sole parameter of the method is an event object, but it cannot be an event object that is already propagating through the element hierarchy. Instead, you must create a new event object via a W3C DOM event object constructor (described later in this chapter). Listing 32-5 is the same as the IE4+ Listing 32-2, but with just a few modifications to run in the W3C event model. Notice that the dispatchEvent() method passes a newly created event object as its sole parameter. LISTING 32-5
Cancelling and Redirecting Events in the W3C DOM Event Cancelling & Redirecting // display alert with event object info function revealEvent(elem, evt) { var msg = "Event (from " + evt.target.tagName + " at "; msg += evt.clientX + "," + evt.clientY + ") is now at the "; msg += elem + " element."; alert(msg);
continued
1057
Part IV: Document Objects Reference
LISTING 32-5
(continued)
} function init() { document.onclick = docEvent; document.body.onclick = docBodEvent; } function docEvent(evt) { revealEvent("document", evt); } function docBodEvent(evt) { revealEvent("BODY", evt); } function buttonEvent(form, evt) { revealEvent("BUTTON", evt); // redirect if checked if (form.redirect.checked) { document.body.dispatchEvent(evt); } // cancel if checked if (form.bubbleCancelState.checked) { evt.stopPropagation(); } } Event Cancelling & Redirecting
Button ‘main1’
Cancel Bubbling at BUTTON Redirect Event to BODY
1058
Chapter 32: Event Objects
Referencing the event Object Just as there are two different event object models in today’s browsers, the way your scripts access those objects is divided into two camps: the IE way and the W3C way. We start with the simpler, IE way. In IE4+, the event object is accessible as a property of the window object: window.event
But, as you are well aware, the window part of references is optional, so your scripts can treat the event object as if it were a global reference: event.propertyName
Thus, any statement in an event handler function can access the event object without any special preparation or initializations. The situation is a bit more complicated in the W3C event model. In some cases you must explicitly pass the event object as a parameter to an event handler function, whereas in other cases, the event object is delivered as a parameter automatically. The difference depends on how the event handler function is bound to the object.
Binding Events Perhaps the most important facet of event handling in any script is binding an event to an element on the page. There are several different ways that you can carry out this event binding, and as you might expect, they aren’t all compatible across different browsers. Furthermore, some of the techniques are considered pass´e in the sense that they have been improved upon by more modern approaches. Following are the four main techniques that can be used to bind events to elements:
Assignment through tag attributes
Assignment through object properties
Attachment in IE
Event listeners in NN/Moz/W3C
The following sections explore these event binding options in more detail, with an emphasis on showing you how to craft a modern, cross-browser event binding function based upon the last two techniques listed.
Binding events through tag attributes Dating back to some of the earliest JavaScript-powered browsers, the original way of binding event handlers to objects is through an attribute in the element’s tag. To bind an event in this manner, you simply assign inline JavaScript code in the attribute of an element, as in the following:
1059
Part IV: Document Objects Reference
The attribute name is the name of the event being handled, and its value is inline JavaScript code that is executed upon the event firing. You can include multiple statements in the event attribute, as this code reveals:
For modern browsers that support the W3C event model (NN6+/Moz and Gecko, WebKit- and Presto-based browsers), if you intend to inspect properties of the event within the event handler function, you must specify the event object as a parameter by passing event as a parameter, as in:
This is the only time in the W3C model that you see an explicit reference to the event (lowercase e) object as if it were a global reference. This reference does not work in any other context — only as a parameter to an event handler function. If you have multiple parameters, the event reference can go in any order, but we tend to put it last:
The function definition that is bound to the element should therefore have a parameter variable in place to catch the event object parameter: function doSomething(widget, evt) {...}
You have no restrictions on how you name this parameter variable. In some examples of this book, you may see the variable assigned as event or, more commonly, evt. When working with cross-browser scripts, avoid using event as a parameter variable name so as not to interfere with the Internet Explorer window.event property. The good news is that binding an event through an event tag attribute works well across all browsers. The bad news is that it goes against the prevailing trend in web design, which is to separate HTML content from the code that makes it interactive. In other words, there is a concerted effort among web developers to clearly delineate JavaScript code from HTML code. This concept is closely related to the notion of separating content from presentation, which is afforded by style sheets. In this way, you could think of a web page as having three distinct components: HTML content, CSS, and JavaScript code. Keeping these three components as compartmentalized as possible results in cleaner, more manageable code.
Note You see many examples of event tag attribute binding throughout this book during demonstrations of various objects, properties, and methods. The usage is intentional because it is generally easier to understand the concepts under discussion when the events are bound closely to the elements.
The trick to maintaining a clean separation between JavaScript event binding and HTML code is to bind the events purely within script code as opposed to within attributes of HTML elements. The latter three event binding approaches mentioned earlier all offer this separation.
1060
Chapter 32: Event Objects
Binding events through object properties Dating back as far as NN3 and IE4, element objects have event properties that can be used to bind events by assignment. For every event that an element is capable of receiving and responding to, there is a suitably named property, in all lowercase. For example, the button element object has a property named onclick that corresponds to the onclick event. You can bind an event handler to a button element by assigning a function reference to the onclick property: document.forms[0].myButton.onclick = handleClick;
Note Although event properties should be specified in all lowercase (onclick), some browsers also recognize mixed case event names (onClick).
One catch to binding events as object properties is that at first glance it doesn’t appear to be possible to pass your own parameters to the invoked handler functions. W3C browsers pass an event object as the only parameter to event handler functions, and this doesn’t exactly leave room for you to include your own parameters. Without any further trickery, this means that your functions should receive the passed event object in a parameter variable: function doSomething(evt) {...}
Recall that the event object contains a reference to the object that was the target of the event. From that, you can access any properties of that object, such as the form object that contains a form control object. It is in fact perfectly possible to pass along your own parameters; it just takes an intermediary anonymous function to do the go-between work. For example, the following code demonstrates how to pass a single custom parameter along with the standard event object: document.forms[0].myButton.onclick = function(evt) {doSomething("Cornelius", evt);};
In this example, a name string is passed along as the first parameter to the event handler, whereas the event object (automatically passed to the anonymous function as its sole parameter, and assigned to the parameter variable evt) is routed along as the second parameter. The actual handler code would look something like this: function doSomething(firstName, evt) {...}
The evt parameter variable in the doSomething() event handler function acts as a reference to the event object for statements within the function. If you need to invoke other functions from there, you can pass the event object reference further along as needed. The event object retains its properties as long as the chain of execution triggered by the event action continues.
Binding events through IE attachments In IE5 Microsoft set out to establish a new means of binding events to elements through attachments, which were originally intended for use with IE behaviors (see Chapter 51, ‘‘Internet Explorer Behaviors,’’ on the CD-ROM). Eventually, the attachment approach to event binding expanded beyond
1061
Part IV: Document Objects Reference
behaviors and became the de facto IE standard for event binding. Seeing as how IE (as of version 8) still does not support the W3C approach to binding events, which you see in the next section, you should consider attachments the preferred way of handling events in IE for the foreseeable future. IE event attachments are managed through the attachEvent() and detachEvent() methods, which are supported by all element objects that are capable of receiving events. By using both of these methods, you can bind and unbind events throughout the course of an application as needed. The attachEvent() method takes the following form: elementReference.attachEvent("event", functionReference);
To put this form in perspective, the following is an example of binding an event using the attachEvent() method in IE: document.getElementById("myButton").attachEvent("onclick", doSomething);
The first parameter to the attachEvent() is the string name of the event, including the on prefix, as in "onclick". The second parameter is a reference to the event handler function for the event. One new power afforded by IE event attachment is the ability to attach the same event to the same element multiple times (presumably pointing to different event handler functions). Just remember that if you choose to bind multiple events of the same type to the same element, they will be processed in the reverse order that they were assigned. This means the first event added is processed last. Since the IE event model is predicated on the event object, which is a property of the window object, there is no event object passed into the event handler function. To access event properties, you simply access the window’s event object using either window.event or just event. The latter approach works because the window object is always assumed in client-side scripting. The upcoming section ‘‘event Object Compatibility’’ shows how to reconcile the IE window.event property and the W3C event event handler parameter. The IE event binding approach also offers the ability to unbind an event, which means the targeted element will no longer receive event notifications. You unbind an IE event by calling the detachEvent() method on the element, like this: document.getElementById("myButton").detachEvent("onclick", doSomething);
This example reveals how the detachEvent() method relies on the exact same syntax as attachEvent().
Binding events through W3C listeners The W3C approach to binding events is logically similar to IE event attachment in that it revolves around two methods: addEventListener() and removeEventListener(). These two methods give elements the ability to listen for events and then respond accordingly. Also similarly to the IE attachEvent() and detachEvent() methods, addEventListener() and removeEventListener() work as a pair for adding and removing event listeners, respectively. The addEventListener() method takes the following form: elementReference.addEventListener("eventType", functionReference, captureSwitch);
1062
Chapter 32: Event Objects
The following example should help to reveal the practical usage of the method: document.getElementById("myButton").addEventListener("click", doSomething, false);
Note how the event name is specified without the on prefix, which is different from the name used in IE event attachments. The other notable difference in W3C event listeners as compared to IE event attachments involves the third parameter to addEventListener(), captureSwitch, which determines whether the element should listen for the event during the capture phase of event propagation. Later in the chapter you learn about event propagation and how this parameter might be used to tweak the propagation of an event. For now, just know that the parameter is typically set to false. Similar to IE event attachments, you can add the same event listener to the same element multiple times. Unlike the IE approach, however, is the fact that W3C events added in this manner are processed in the same order that they were assigned. This means that the first event added is processed first. Another similarity the W3C event model has to IE event handling is the ability to unbind an event from an element. The W3C version of event unbinding involves the removeEventListener() method, which is demonstrated in this example: document.getElementById("myButton").removeEventListener("click", doSomething, false);
This example shows how the removeEventListener() method accepts the same parameters as addEventListener().
A cross-browser event binding solution Pulling together what you’ve learned about modern event handling, you know it must be possible to reconcile the IE and W3C approaches to event binding. In fact, it doesn’t take all that much extra code to bind events in a manner that cleanly attempts to use the latest event binding techniques while still gracefully falling back on an older technique (object properties) for legacy browsers. Following is a cross-browser function you can use to add an event binding to an element: function addEvent(elem, evtType, func) { if (elem.addEventListener) { elem.addEventListener(evtType, func, false); } else if (elem.attachEvent) { elem.attachEvent("on" + evtType, func); } else { elem["on" + evtType] = func; } }
Parameters for the function are a reference to the element, a string of the event type (that is, the version without the on prefix), and a reference to the function to be invoked when the event fires
1063
Part IV: Document Objects Reference
on the element. The addEvent() function first attempts to use the addEventListener() method on the supplied element, which satisfies modern W3C browsers (NN6+/Mozilla/Safari/Opera/ Chrome). If that fails, attachEvent() is tried, which accommodates modern IE browsers (IE5+). If that’s a bust, the function falls back on simply assigning the event handler function to the event object property, which works on the vast majority of browsers.
Note You could easily extend the addEvent() function to allow for the captureSwitch parameter of the addEventListener() method by adding a fourth parameter and passing it to addEventListener(), instead of passing false.
Of course, the addEvent() function has to get called in order to bind events for a page. The onload event provides a great opportunity for binding events but, as you know, it’s not a good idea to just call the addEvent() function in the onload HTML attribute. That would go against everything you’ve just learned. The trick is to first add an anonymous event handler for the onload event, and then carry out your other event bindings within that function. Here’s an example of how you might do this: addEvent(window, "load", function() { addEvent(document.getElementById("myButton"), "click", handleClick); addEvent(document.body, "mouseup", function(evt) {handleClick(evt);}); });
In case you need to unbind an event, here is a suitable cross-browser function for unbinding events: function removeEvent(elem, evtType, func) { if (elem.removeEventListener) { elem.removeEventListener(evtType, func, false); } else if (elem.detachEvent) { elem.detachEvent("on" + evtType, func); } else { elem["on" + evtType] = null; } }
event Object Compatibility Despite the incompatible ways that W3C DOM and IE event objects arrive at an event handler function, you can easily stuff the object into one variable that both browser types can use. For example, the following function fragment receives a W3C DOM event object but also accommodates the IE event object: function doSomething(evt)
1064
Chapter 32: Event Objects
{ evt = (evt) ? evt : ((window.event) ? window.event : null); if (evt) { // browser has an event to process ... } }
If an event object arrives as a parameter, it continues to be available as evt; but if not, the function makes sure that a window.event object is available and assigns it to the evt variable; finally, if the browser doesn’t know about an event object, the evt variable is made null. Processing continues only if evt contains an event object. That’s the easy part. The madness comes in the details: reading properties of the event object when the property names can vary widely across the two event object models. Sections later in this chapter provide specifics of each property and method of both event object models, but seeing an overview of the property terminology on a comparative basis is helpful. Table 32-2 lists the common information bits and actions you are likely to want from an event object, and the property or method names used in the event object models. TABLE 32-2
Common event Object Properties and Methods Property/Action
IE4+
W3C DOM
Target element
srcElement
target
Event type
type
type
X coordinate in element
offsetX
n/a†
Y coordinate in element
offsetY
n/a†
X coordinate on page
n/a†
pageX††
Y coordinate on page
n/a†
pageY††
X coordinate in window
clientX
clientX
Y coordinate in window
clientY
clientY
X coordinate on screen
screenX
screenX
Y coordinate on screen
screenY
screenY
Mouse button
button
button
Keyboard key
keyCode
keyCode
Shift key pressed
shiftKey
shiftKey
Alt key pressed
altKey
altKey
Ctrl key pressed
ctrlKey
ctrlKey
1065
Part IV: Document Objects Reference
TABLE 32-2
(continued )
Property/Action
IE4+
W3C DOM
fromElement
relatedTarget
Next Element
toElement
relatedTarget
Cancel bubbling
cancelBubble
stopPropagation()
Prevent default action
returnValue
preventDefault()
Previous Element
†
Value can be derived through calculations with other properties. an official W3C DOM property, but is supported in Mozilla, Safari, Opera, and Chrome.
†† Not
As you can see in Table 32-2, properties for the IE4+ and W3C event objects have a lot in common. Perhaps the most important incompatibility to overcome is referencing the element that is the intended target of the event. This, too, can be branched in your code to achieve a common variable that references the element. For example, embedded within the previous function fragment can be a statement, such as the following: var elem = (evt.target) ? evt.target : ((evt.srcElement) ? evt.srcElement : null);
Each event model has additional properties that are not shared by the other. Details about these are covered in the rest of this chapter.
Dueling Event Models Despite the sometimes widely divergent ways event object models treat their properties, accommodating a wide range of browsers for event manipulation is not difficult. In this section, you see two scripts that examine important event properties. The first script reveals which, if any, modifier keys are held down during an event; the second script extracts the codes for both mouse buttons and keyboard keys. Both scripts work with all modern browsers that have event objects.
Cross-platform modifier key check Listing 32-6 demonstrates branching techniques for examining the modifier key(s) being held down while an event fires. You can find details of the event object properties, such as modifiers and altKey, later in this chapter. To see the page in action, click a link, type into a text box, and click a button while holding down any combination of modifier keys. A series of four check boxes representing the four modifier keys is at the bottom. As you click or type, the check box(es) of the pressed modifier key(s) become checked. LISTING 32-6
Hold one or more modifier keys and click on this link while looking at the checkboxes to see which keys you are holding.
continued
1067
Part IV: Document Objects Reference
LISTING 32-6
(continued)
Enter some text with uppercase and lowercase letters (while looking at the checkboxes):
Alt Control Shift Meta
The script checks the event object property for each of three modifiers to determine which, if any, modifier keys are being pressed.
Cross-platform key capture To demonstrate keyboard events in both event capture models, Listing 32-7 captures the key character being typed into a text box, as well as the mouse button used to click a button. LISTING 32-7
Checking Events for Key and Mouse Button Pressed Button and Key Properties function checkWhich(evt) { evt = (evt) ? evt : ((event) ? event : null); if (evt) { var thingPressed = ""; var elem = (evt.target) ? evt.target : evt.srcElement; if (elem.type == "textarea") { thingPressed = (evt.charCode) ? evt.charCode : evt.keyCode; } else if (elem.type == "button") { thingPressed = (typeof evt.button !=
Mouse down atop this with either mouse button (if you have more than one).
Enter some text with uppercase and lowercase letters:
The codes displayed for each keyboard event are equivalent to the ASCII values of character keys. If you need the codes of other keys, the onkeydown and onkeyup event handlers provide Unicode values for any key that you press on the keyboard. See the charCode and keyCode property listings for event objects later in this chapter for more details.
1069
Part IV: Document Objects Reference
Event Types Although browsers prior to version 4 did not have an accessible event object, this is a good time to summarize the evolution of what in today’s browsers is known as the type property. The type property reveals the kind of event that generates an event object (the event handler name minus the ‘‘on’’). Object models in IE4+ and NN6+/W3C provide event handlers for virtually every HTML element, so that it’s possible, for example, to define an onclick event handler for not only a clickable button, but also for a p or even an arbitrary span element.
Older Browsers Earlier browsers tended to limit the number of event handlers for any particular element to just those that made sense for the kind of element it was. Even so, many scripters wanted more event handlers on more objects. But until that became a reality in IE4+ and NN6+/W3C, authors had to know the limits of the object models. Table 32-4 shows the event handlers available for objects within three generations of early browsers. Each column represents the version in which the event type was introduced. For example, the window object started out with four event types, and gained three more when NN4 was released. In contrast, the area object was exposed as an object for the first time in NN3, which is where the first event types for that object are listed. With the exception of the NN4 layer object, all objects shown in Table 32-4 have survived into the newer browsers, so that you can use these event handlers with confidence. Again, keep in mind that of the browsers listed in Table 32-4, only NN4 has an event object of any kind exposed to scripts.
TABLE 32-3
Event Types through the Early Ages Object
NN2/IE3
NN3
NN4
window
blur
dragdrop
focus
move
load
resize
unload layer
blur focus load mouseout mouseover mouseup
1070
Chapter 32: Event Objects
Object
NN2/IE3
NN3
NN4
link
click
mouseout
dblclick
mouseover
mousedown onmouseup
area
mouseout
click
mouseover image
abort error load
form
submit
reset
text, textarea, password blur
keydown
change
keypress
focus
keyup
select all buttons
click
mousedown mouseup
select
blur change focus
fileupload
blur focus select
Event types in IE4+ and NN6+/W3C By now you should have at least scanned the list of event handlers defined for elements in common, as shown in Chapter 26. This list of event types is enormous. A sizable number of the event types are unique to IE4, IE5, and IE5.5+, and in some cases, just the Windows version at that. If you compose pages for both IE4+ and NN6+/W3C, however, you need to know which event types these browser families and generations have in common. Event types for NN6+/Moz and Gecko-, WebKit-, and Presto-based browsers, are based primarily on the W3C DOM Level 2 specification, although they also include keyboard events, whose formal standards are still under development for DOM Level 3. Table 32-4 lists a common denominator of event types for modern browsers and the
objects that support them. Although not as long as the IE event list, the event types in Table 32-4 are the basic set you should get to know for all browsers.
About this object The IE4+ event object is a property of the window object. Its basic operation is covered earlier in this chapter. You can see a little of what the event object is about with the help of The Evaluator (see Chapter 4, ‘‘JavaScript Essentials’’). If you type event into the bottom text box, you can examine the properties of the event object for the event that triggers the function that displays the event object properties. If you press the Enter key in the text box, you see properties of the keypress event that caused the internal script to run; click the List Properties button to see the properties of the click event fired at the button. Hold down some of the modifier keys while clicking to see how this affects some of the properties. As you review the properties for the event object, make special note of the compatibility rating for each property. The list of properties for this object has grown over the evolution of the IE4+ event object model. Also, most properties are listed here as being read-only, which they were in IE4. But for IE5+, these properties are also Read/Write if the event is created artificially via methods, such as IE5.5+’s document.createEventObject() method. Event objects that are created by user or system action have very few properties that can be modified on the fly (to prevent your scripts from altering user actions). Notice, too, that some properties are the same as for the W3C DOM event object, as revealed in the compatibility ratings.
1074
Chapter 32: Event Objects eventObject.shiftLeft
Properties altKey ctrlKey shiftKey Value: Boolean
Read-Only
Compatibility: WinIE4+, MacIE4+, NN6+, Moz+, Safari+, Opera+, Chrome+ When an event object is created in response to a user or system action, these three properties are set based on whether their corresponding keys were being held down at the time — a Shift-click, for example. If the key was held down, the property is assigned a value of true; otherwise the value is false. Most commonly, you use expressions consisting of this property as if construction conditional statements. Because these are Boolean values, you can combine multiple properties in a single condition. For example, if you have a branch of a function that is to execute only if the event occurred with both the Shift and Control keys held down, the condition looks as the following: if (event.shiftKey && event.ctrlKey) { // statements to execute }
Conversely, you can take a more user-friendly approach to provide special processing if the user holds down any one of the three modifier keys: if (event.shiftKey || event.ctrlKey || event.altKey) { // statements to execute }
The rationale behind this approach is to offer perhaps some shortcut operation for users, but not force them to memorize a specific modifier key combination.
Example See Listing 32-6, where the values of these three properties are used to set the checked properties of corresponding check boxes for a variety of event types. Related Items: altLeft, ctrlLeft, shiftLeft properties
altLeft ctrlLeft shiftLeft Value: Boolean
Read-Only
Compatibility: WinIE5.5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeSome versions of Windows allow events to be modified by only the left-hand Alt, Ctrl, and Shift keys when using IE5.5+. For these modifiers to be recorded by the event object, focus must be on the document (body), and not in any form control. If the left-key version is false and the regular version is true, then your script knows that the right-hand key had been held down during the event. Related Items: altKey, ctrlKey, shiftKey properties
1075
Part IV: Document Objects Reference eventObject.behaviorCookie
behaviorCookie behaviorPart Value: Integer
Read-Only
Compatibility: WinIE6+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThese two properties are related to a Windows technology that Microsoft calls rendering behaviors. Unlike the behaviors discussed under the addBehavior() method in Chapter 26, rendering behaviors are written in C++ and provide services for custom drawing on your web page. For more details, consult the document ‘‘Implementing Rendering Behaviors’’ at http://msdn.microsoft.com/en-us/library/aa753628%28VS.85%29.aspx.
bookmarks boundElements dataFld qualifier reason recordset Value: See text
Array of ADO bookmarks (saved positions) for records within a recordset associated with the object that received the event.
boundElements Array
IE5
Array of element references for all elements bound to the same data set that was touched by the current event.
dataFld
String
IE5
Name of the data source column that is bound to a table cell that receives a cellchange event.
qualifier
String
IE5
Name of the data member associated with a data source that receives a data-related event. Available only if the data source object (DSO) allows multiple-named data members or a qualifier has been explicitly set via the datasrc attribute of the bound element. Read-write in IE5+.
reason
Integer
IE4
Set only from onDataSetComplete event, provides the result code of the data set loading (0=successful; 1=transfer aborted; 2=other error).
recordset
Object
IE4
Reference to the current recordset in a data source object.
1076
Chapter 32: Event Objects eventObject.button This group of event object properties is tied to using Data Binding in Windows versions of IE4+. Extensive details of Data Binding lie outside the scope of this book, but Table 32-5 provides a summary of these event object properties within that context (much of the terminology is used in Data Binding, but doesn’t affect other scripting). For more details, search for ActiveX Data Objects (ADO) at http://msdn.microsoft.com/en-us/library/default.aspx.
Note Although still supported in IE, Microsoft’s original ADO technology has given way to ADO.NET, which is designed for tighter integration with Microsoft’s .NET architecture. To learn more about the differences between the two technologies, visit http://msdn.microsoft.com/library/en-us/dndotnet/html /adonetprogmsdn.asp.
button Value: Integer
Read-Only
Compatibility: WinIE4+, MacIE4+, NN6+, Moz+, Safari+, Opera+, Chrome+ The button property reveals which button or buttons were pressed to activate a mouse event. If no mouse button is pressed to generate an event, this property is zero in IE. But integers 1 through 7 reveal single and multiple button presses, including the actions of three-button mice when they are recognized by the operating system. Integer values in IE correspond to buttons according to the following scheme: Value
Description
0
No button
1
Left (primary) button
2
Right button
3
Left and right buttons together
4
Middle button
5
Left and middle buttons together
6
Right and middle buttons together
7
Left, middle, and right buttons together
Mouse buttons other than the primary one are easier to look for in mousedown or mouseup events rather than in onclick events. Be aware that as the user works toward pressing multiple buttons, each press fires a mousedown event. Therefore, if the user presses the left button first, the mousedown event fires, with the event.button property bearing the 1 value; as soon as the right button is pressed, the mousedown event fires again, but this time with an event.button value of 3. If your script intends to perform special action with both buttons pressed, it should ignore and not perform any action for a single mouse button, because that one-button event will very likely fire in the process, disturbing the intended action. Exercise caution when scripting the event.button property for both IE4+ and NN6+/Moz/W3C. The W3C DOM event model defines different button values for mouse buttons (0, 1, and 2 for left, middle, and right) and no values for multiple buttons.
1077
Part IV: Document Objects Reference eventObject.cancelBubble
Example See Listing 32-7, where the event.button property is revealed in the status bar. Try pressing individual mouse buttons on, for example, the screen button. Then try combinations, watching the results very closely in the status bar. Related Items: None
cancelBubble Value: Boolean
Read/Write
Compatibility: WinIE4+, MacIE4+, NN6+, Moz+, Safari+, Opera+, Chrome+ The cancelBubble property (which sounds more as if it should be a method name) determines whether the current event object bubbles up any higher in the element containment hierarchy of the document. By default, this property is false, meaning that if the event is supposed to bubble, it will do so automatically. To prevent event bubbling for the current event, set the property to true anywhere within the event handler function. As an alternative, you can cancel bubbling directly in an element’s event handler attribute, as in the following: onclick="doButtonClick(this); event.cancelBubble = true"
Cancelling event bubbling works only for the current event. The very next event to fire will have bubbling enabled (provided the event bubbles).
Example See Listing 32-2 to see the cancelBubble property in action. Even though that listing has some features that apply to IE5.5+, the bubble cancelling demonstration works all the way back to IE4. Related Item: returnValue property
clientX clientY offsetX offsetY screenX screenY x y Value: Integer
Read/Write
Compatibility: WinIE4+, MacIE4+, NN6+, Moz+, Safari+, Opera+, Chrome+ An IE event object provides coordinates for an event in as many as four coordinate spaces: the element itself, the parent element of the event’s target, the viewable area of the browser window, and the entire video screen. Unfortunately, misleading values can be returned by some of the properties that correspond to these coordinate spaces, as discussed in this section. Note that no properties provide the explicit position of an event relative to the entire page, in case the user has scrolled the window. Starting with the innermost space — that of the element that is the target of the event — the offsetX and offsetY properties should provide pixel coordinates within the target element. This
is how, for example, you could determine the click point on an image, regardless of whether the
1078
Chapter 32: Event Objects eventObject.clientX image is embedded in the body or floating around in a positioned div. Windows versions through IE8 produce the correct values in most cases. But for some elements that are child elements of the body element, the vertical (y) value may be relative to the viewable window, rather than just the element itself. You can see an example of this when you work with Listing 32-8 and click the h1 or p elements near the top of the page. This problem does not affect MacIE, but there is another problem on Mac versions: If the page is scrolled away from its normal original position, the scrolled values are subtracted from the clientX and clientY values. This is an incompatibility bug, and you must take this error into account if you need click coordinates inside an element for a potentially scrolled page. This error correction must be done only for the Mac, because in Windows it works as is. Extending scope to the offset parent element of the event’s target, the x and y properties in IE5+ for Windows should return the coordinates for the event relative to the target’s offset parent element (the element that can be found via the offsetParent property). For most non-positioned elements, these values are the same as the clientX and clientY properties because, as discussed in a moment, the offset parent element has a zero offset with its parent, the body. Observe an important caution about the x and y properties: In WinIE4 and through MacIE5, the properties do not take into account any offset parent locations other than the body. Even in WinIE5+, this property can give false readings in some circumstances. By and large, these two properties should not be used. The next set of coordinates, clientX and clientY, are relative to the visible document area of the browser window. When the document is scrolled all the way to the top (or the document doesn’t scroll at all), these coordinates are the same as the coordinates on the entire page. But because the page can scroll ‘‘underneath’’ the viewable window, the coordinates on the page can change if the page scrolls. Also, in the Windows versions of IE, you can actually register mouse events that are up to 2 pixels outside of the body element, which is weird, but true. Therefore, in WinIE, if you click the background of the body, the event fires on the body element, but the clientX/clientY values will be 2 pixels greater than offsetX/offsetY (they’re equal in MacIE). Despite this slight discrepancy, you should rely on the clientX and clientY properties if you are trying to get the coordinates of an event that may be in a positioned element, but have those coordinates relative to the entire viewable window, rather than just the positioning context. Taking the page’s scrolling into account for an event coordinate is often important. After all, unless you generate a fixed-size window for a user, you don’t know how the browser window will be oriented. If you’re looking for a click within a specific region of the page, you must take page scrolling into account. The scrolling factor can be retrieved from the document.body.scrollLeft and document.body.scrollTop properties. When reading the clientX and clientY properties, be sure to add the corresponding scroll properties to get the position on the page: var coordX = event.clientX + document.body.scrollLeft; var coordY = event.clientY + document.body.scrollTop;
Do this in your production work without fail. Finally, the screenX and screenY properties return the pixel coordinates of the event on the entire video screen. These properties would be more useful if IE provided more window dimension properties. In any case, because mouse events fire only when the cursor is somewhere in the content region of the browser window, don’t expect to get the screen values of any place outside this region. If these descriptions seem confusing to you, you are not alone. Throw in a few bugs, and it may seem like quite a mess. But think how you may use event coordinates in scripts. By and large, you want to know one of two types of mouse event coordinates: within the element itself and within the page. Use the offsetX/offsetY properties for the former; use clientX/clientY (plus the scroll property values) for the latter. Although the coordinate properties are used primarily for mouse events, there is a little quirk that may let you determine if the user has resized the window via the maximize icon in the title bar
1079
Part IV: Document Objects Reference eventObject.clientX (on the Mac, this is called the zoom box) or the resize handle at the bottom-right corner of the screen. Mouse event coordinates are recorded in the event object for a resize event. In the case of the maximize icon, the clientY coordinate is a negative value (above the client space) and the clientX coordinate is within about 45 pixels of the previous width of the window (document.body.clientWidth). This, of course, happens after the window has resized, so it is not a way to prevent window resizing.
Example Listing 32-8 provides readings of all event coordinate properties in an interactive way. An onmousedown event handler triggers all event handling, and you can click the mouse anywhere on the page to see what happens. You see the tag of the element targeted by the mouse event to help you visualize how some of the coordinate properties are determined. An image is encased inside a positioned div element to help you see what happens to some of the properties when the event is targeted inside a positioned element. LISTING 32-8
IE4+ Event Coordinate Properties X and Y Event Properties (IE4+ Syntax) function checkCoords(evt) { evt = (evt) ? evt : ((window.event) ? window.event : null); if (evt) { var elem = (evt.target) ? evt.target : evt.srcElement; var form = document.forms[0]; form.srcElemTag.value = ""; form.clientCoords.value = evt.clientX + "," + evt.clientY; if (typeof document.body.scrollLeft != "undefined") { form.pageCoords.value = (evt.clientX + document.body.scrollLeft) + "," + (evt.clientY + document.body.scrollTop); } form.offsetCoords.value = evt.offsetX + "," + evt.offsetY; form.screenCoords.value = evt.screenX + "," + evt.screenY; form.xyCoords.value = evt.x + "," + evt.y; if (elem.offsetParent) { form.parElem.value = ""; } return false; } } function handleSize(evt)
Click on any element to see the coordinate values for the event object.
IE Mouse Event Coordinates:
srcElement:
clientX, clientY:
continued
1081
Part IV: Document Objects Reference eventObject.clientX LISTING 32-8
(continued)
...With scrolling:
offsetX, offsetY:
screenX, screenY:
x, y:
...Relative to:
Window Resize Coordinates:
clientX, clientY:
1082
Chapter 32: Event Objects eventObject.clientX
Here are some tasks to try in IE with the page that loads from Listing 32-8 to help you understand the relationships among the various pairs of coordinate properties:
1. Click the dot above the ‘‘i’’ on the ‘‘Click Here’’ button label. The target element is the button (input) element, whose offsetParent is a table cell element. The offsetY value is very low because you are near the top of the element’s own coordinate space. The client coordinates (and x and y), however, are relative to the viewable area in the window. If your browser window is maximized in Windows, the screenX and clientX values will be the same; the difference between screenY and clientY is the height of all the window chrome above the content region. With the window not scrolled at all, the client coordinates are the same with and without scrolling taken into account.
2. Jot down the various coordinate values and then scroll the page down slightly (clicking the scrollbar fires an event), and click the dot on the button again. The clientY value shrinks because the page has moved upward relative to the viewable area, making the measure between the top of the area smaller with respect to the button. The Windows version does the right thing with the offset properties, by continuing to return values relative to the element’s own coordinate space; the Mac, unfortunately, subtracts the scrolled amount from the offset properties.
3. Click the large image. The client properties perform as expected for both Windows and Mac, as do the screen properties. For Windows, the x and y properties correctly return the event coordinates relative to the img element’s offsetParent, which is the div element that surrounds it. Note, however, that the browser ‘‘sees’’ the div as starting 10 pixels to the left of the image. In WinIE5.5+, you can click within those 10 transparent pixels to the left of the image to click the div element. This padding is inserted automatically and impacts the coordinates of the x and y properties. A more reliable measure of the event inside the image is the offset properties. The same is true in the Macintosh version, as long as the page isn’t scrolled, in which case the scroll, just as in Step 2, affects the values above.
4. Click the top hr element under the heading. It may take a couple of tries to actually hit the element (you’ve made it when the hr element shows up in the srcElement box). This is to reinforce the way the client properties provide coordinates within the element itself (again, except on the Mac when the page is scrolled). Clicking at the very left end of the rule, you eventually find the 0,0 coordinate. Finally, if you are a Windows user, here are two examples to try to see some of the unexpected behavior of coordinate properties.
1. With the page not scrolled, click anywhere along the right side of the page, away from any text, so that the body element is srcElement. Because the body element theoretically fills the entire content region of the browser window, all coordinate pairs except for the screen coordinates should be the same. But offset properties are 2 pixels less than all the others. By and large, this difference won’t matter in your scripts, but you should be aware of this potential discrepancy if precise positioning is important. For inexplicable reasons, the offset properties are measured in a space that is inset 2 pixels from the left and top of the window. This is not the case in the Macintosh version, where all value pairs are the same from the body perspective.
1083
Part IV: Document Objects Reference eventObject.contentOverflow
2. Click the text of the h1 or p elements (just above and below the long horizontal rule at the top of the page). In theory, the offset properties should be relative to the rectangles occupied by these elements (they’re block elements, after all). But instead, they’re measured in the same space as the client properties (plus the 2 pixels). This unexpected behavior doesn’t have anything to do with the cursor being a text cursor, because if you click inside any of the text box elements, their offset properties are properly relative to their own rectangles. This problem does not afflict the Macintosh version. Many of these properties are also in the W3C DOM and are therefore supported in W3C DOM browsers. Unsupported properties display their values as undefined when you run Listing 32-8 in those browsers. You can see further examples of important event coordinate properties in action in the discussion of dragging elements around the IE page in Chapter 43, ‘‘Positioned Objects.’’ Related Items: fromElement, toElement properties
contentOverflow Value: Boolean
Read-Only
Compatibility: WinIE5.5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe value indicates whether page content has overflowed the current layout rectangle. This property is primarily used during printing as the basis for overflowing content from one page to another.
dataTransfer Value: Object
Read-Only
Compatibility: WinIE5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe dataTransfer property is a reference to the dataTransfer object. Use this object in drag-and-drop operations (that is, with drag-and-drop-related events) to control not only the data that gets transferred from the source to the target, but also to control the look of the cursor along the way. Table 32-6 lists the properties and methods of the dataTransfer object. The dataTransfer object acts as a conduit and controller of the data that your scripts need to transfer from one element to another in response to a user’s drag-and-drop action. You need to adhere to a well-defined sequence of actions triggered by a handful of event handlers. This means that the object is invoked on different instances of the event object as different events fire in the process of dragging and dropping. The sequence begins at the source element, where an ondragstart event handler typically assigns a value to the dropEffect property and uses the getData() method to explicitly capture whatever data regarding the source object gets transferred to the eventual target. For example, if you drag an image, the information being transferred may simply be the URL of the image — data that is extractable from the event.srcElement.src property of that event (the src property of the image, that is). At the target element(s), three event handlers must be defined: ondragenter, ondragover, and ondrop. Most commonly, the first two event handlers do nothing more than mark the element for a particular dropEffect (which must match the effectAllowed set at the source during the drag’s start) and set event.returnValue to false so the desired cursor is displayed. These actions are
1084
Chapter 32: Event Objects eventObject.dataTransfer also carried out in the ondrop event handler, but that is also the handler that does the processing of the destination action at the target element. This is when the dataTransfer object’s getData() method is invoked to pick up the data that has been ‘‘stored’’ away by getData() at the start of the drag. If you also want to make sure that the data is not picked up accidentally by another event, invoke the clearData() method to remove that data from memory.
TABLE 32-6
dataTransfer object Properties and Methods Property/Method
Returns
Description
dropEffect
String
An element that is a potential recipient of a drop action can use the ondragenter, ondragover, or ondrop event handler to set the cursor style to be displayed when the cursor is atop the element. Before this can work, the source element’s ondragstart event handler must assign a value to the event.effectAllowed property. Possible string values for both properties are copy, link, move, or none. These properties correspond to the Windows system cursors for the operations users typically do with files and in other documents. You must also cancel the default action (meaning set event.returnValue to false) for all of these drop element event handlers: ondragenter, ondragover, and ondrop.
effectAllowed
String
Set in response to an ondragstart event of the source element, this property determines which kind of drag-and-drop action will be taking place. Possible string values are copy, link, move, or none. This property value must match the dropEffect property value for the target element’s event object. Also, cancel the default action (meaning, set event.returnValue to false) in the ondragstart event handler.
clearData([format])
Nothing
Removes data in the clipboard. If no format parameters are supplied, all data are cleared. Data formats can be one or more of the following strings: Text, URL, File, HTML, Image.
getData(format)
String
Retrieves data of the specified format from the clipboard. The format is one of the following strings: Text, URL, File, HTML, Image. The clipboard is not emptied after you get the data, so it can be retrieved in several sequential operations.
setData(format, data)
Boolean
Stores string data in the clipboard. The format is one of the following strings: Text, URL, File, HTML, Image. For non-text data formats, the data must be a string that specifies the path or URL to the content. Returns true if the transfer to the clipboard is successful.
1085
Part IV: Document Objects Reference eventObject.fromElement Note that the style of dragging being discussed here is not the kind in which you see the source element actually moving on the screen (although you could script it that way). The intention is to treat drag-and-drop operations just as Windows does in, say, the Windows Explorer window or on the Desktop. To the user, the draggable component becomes encapsulated in the cursor. That’s why the properties of the dataTransfer object control the appearance of the cursor at the drop point as a way of conveying to the user the type of action that will occur with the impending drop. Apple implements the same behavior in Safari 2.
Example An extensive example of the dataTransfer property in action can be found in Listing 26-37 in the section for the ondrag event handler. Related Items: ondragend, ondragenter, ondragleave, ondragover, ondragstart, ondrop event handlers
fromElement toElement Value: Element object
Read-Only
Compatibility: WinIE4+, MacIE4+, NN-, Moz-, Safari+, Opera+, Chrome+ The fromElement and toElement properties allow an element to uncover where the cursor rolled in from or has rolled out to. These properties extend the power of the onmouseover and onmouseout event handlers by expanding their scope to outside the current element (usually to an adjacent element). When the onmouseover event fires on an element, the cursor had to be over some other element just beforehand. The fromElement property holds a reference to that element. Conversely, when the onmouseout event fires, the cursor is already over some other element. The toElement property holds a reference to that element.
Example Listing 32-9 provides an example of how the fromElement and toElement properties can reveal the life of the cursor action before and after it rolls into an element. When you roll the cursor to the center box (a table cell), its onmouseover event handler displays the text from the table cell from which the cursor arrived. LISTING 32-9
Using the toElement and fromElement Properties fromElement and toElement Properties .direction {background-color:#00FFFF; width:100; height:50; text-align:center;}
1086
Chapter 32: Event Objects eventObject.fromElement #main {background-color:#FF6666; text-align:center;} function showArrival(evt) { evt = (evt) ? evt : ((event) ? event : null); var direction = (event.fromElement.innerText) ? event.fromElement.innerText : "parts unknown"; status = "Arrived from: " + direction; } function showDeparture(evt) { evt = (evt) ? evt : ((event) ? event : null); var direction = (event.toElement.innerText) ? event.toElement.innerText : "parts unknown"; status = "Departed to: " + direction; } // bind the event handlers function addEvent(elem, evtType, func) { if (elem.addEventListener) { elem.addEventListener(evtType, func, false); } else if (elem.attachEvent) { elem.attachEvent("on" + evtType, func); } else { elem["on" + evtType] = func; } } addEvent(window, "load", function() { addEvent(document.getElementById("main"), "mouseover", function(evt) {showArrival(evt);}); addEvent(document.getElementById("main"), "mouseout", function(evt) {showDeparture(evt);}); }); fromElement and toElement Properties
Roll the mouse to the center box and look for arrival information in the status bar. Roll the mouse away from the center box and look for departure information in the status bar.
continued
1087
Part IV: Document Objects Reference eventObject.keyCode LISTING 32-9
(continued)
North
West
Roll
East
South
This is a good example to experiment with in the browser, because it also reveals a potential limitation. The element registered as the toElement or fromElement must fire a mouse event to register itself with the browser. If not, the next element in the sequence that registers itself is the one acknowledged by these properties. For example, if you roll the mouse into the center box, and then extremely quickly roll the cursor to the bottom of the page, you may bypass the South box entirely. The text that appears in the status bar is actually the inner text of the body element, which is the element that caught the first mouse event to register itself as the toElement for the center table cell. Related Item: srcElement property
keyCode Value: Integer
Read-Only
Compatibility: WinIE4+, MacIE4+, NN6+, Moz+, Safari+, Opera+, Chrome+ For keyboard events, the keyCode property returns an integer corresponding to the Unicode value of the character (for onkeypress events) or the keyboard character key (for onkeydown and onkeyup events). There is a significant distinction between these numbering code systems. If you want the Unicode values (the same as ASCII values for the Latin character set) for the key that a user pressed, get the keyCode property from the onkeypress event handler. For example, a lowercase ‘‘a’’ returns 97, whereas an uppercase ‘‘A’’ returns 65. Non-character keys, such as arrows, page navigation, and function keys, return a null value for the keyCode property during onkeypress events. In other words, the keyCode property for onkeypress events is more like a character code than a key code. To capture the exact keyboard key that the user presses, use either the onkeydown or onkeyup event handler. For these events, the event object captures a numeric code associated with a particular key on the keyboard. For the character keys, this varies with the language assigned as the
1088
Chapter 32: Event Objects eventObject.keyCode system language. Importantly, there is no distinction between uppercase or lowercase: The ‘‘A’’ key on the Latin keyboard returns a value of 65, regardless of the state of the Shift key. At the same time, however, the press of the Shift key fired its own onkeydown and onkeyup events, setting the keyCode value to 16. Other non-character keys — arrows, page navigation, function, and similar — have their own codes as well. This gets very detailed, and involves special key codes for the numeric keyboard keys that are different from their corresponding numbers along the top row of the alphanumeric keyboard.
Cross-Reference Be sure to see the extensive section on keyboard events in Chapter 26 for examples of how to apply the keyCode property in applications.
Example Listing 32-10 provides an additional play area to view the keyCode property for all three keyboard events while you type into a textarea. You can use this page later as an authoring tool to grab the precise codes for keyboard keys you may not be familiar with. LISTING 32-10
Displaying keyCode Property Values keyCode Property td {text-align:center} function showCode(which, evt) { evt = (evt) ? evt : ((event) ? event : null); if (evt) { document.forms[0].elements[which].value = evt.keyCode; } } function clearEm() { for (var i = 1; i < document.forms[0].elements.length; i++) { document.forms[0].elements[i].value = ""; } } // bind the event handlers
continued
1089
Part IV: Document Objects Reference eventObject.keyCode LISTING 32-10
The following are some specific tasks to try with the page to examine key codes (if you are not using a browser set for English, and a Latin-based keyboard, your results may vary):
1. Enter a lowercase a. Notice how the onkeypress event handler shows the code to be 97, which is the Unicode (and ASCII) value for the first of the lowercase letters of the Latin alphabet. But the other two events record just the key’s code: 65.
2. Type an uppercase A via the Shift key. If you watch closely, you see that the Shift key itself generates the code 16 for the onkeydown and onkeyup events. But the character key then shows the value 65 for all three events, because the ASCII value of the uppercase letter happens to match the keyboard key code for that letter.
3. Press and release the Down Arrow key (be sure the cursor still flashes in the textarea, because that’s where the keyboard events are being monitored). As a non-character key, it does not fire an onkeypress event. But it does fire the other events, and assigns 40 as the code for this key.
4. Poke around with other non-character keys. Some may produce dialog boxes or menus, but their key codes are recorded nonetheless. Note that not all keys on a Macintosh keyboard register with MacIE. Notice also that the keyCode property doesn’t work properly for the onkeypress event in Mozilla-based browsers. This is because Mozilla uses the charCode property for the onkeypress event instead of keyCode. You could make the code in the listing work for all modern browsers with the following modification in the showCode() function: if (evt) { var charCode = (evt.charCode) ? evt.charCode : evt.keyCode; document.forms[0].elements[which].value = charCode; }
Related Items: onkeydown, onkeypress, onkeyup event handlers
nextPage Value: String
Read-Only
Compatibility: WinIE5.5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe nextPage property is applicable only if your WinIE5.5+ page uses a TemplatePrinter behavior. Values of this property are one of the following strings: left, right, or an empty string.
propertyName Value: String
Read-Only
1091
Part IV: Document Objects Reference eventObject.repeat Compatibility: WinIE5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe propertyName property is filled only after an onpropertychange event fires. If a script modifies a property, the onpropertychange event handler fires, and the string name of the property is stuffed into the event.propertyName property. If the property happens to be a property of the style object associated with the element, the propertyName is the full property reference, as in style.backgroundColor.
Example See Listing 26-45 in the section about the onpropertychange event handler for an example of the values returned by this property. Related Item: onpropertychange event handler (Chapter 26, ‘‘Generic HTML Element Objects’’)
repeat Value: Boolean
Read-Only
Compatibility: WinIE5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe repeat property reveals for onkeydown events only whether the key is in repeat mode (as determined by the keyboard control panel settings in the system). With this information, you can prevent the automatic triggering of repeat mode from causing multiple characters from being recognized by the browser. This property can come in handy if users accidentally hold down a key too long. The following script fragment in an onkeydown event handler for a text box or textarea prevents multiple characters from appearing even if the system goes into repeat mode: if (event.repeat) { event.returnValue = false; }
By disabling the default action while in repeat mode, no further characters reach the text box until repeat mode goes away (with the press of another key). Related Item: onkeydown event handler
returnValue Value: Boolean
Read-Only
Compatibility: WinIE4+, MacIE4+, NN-, Moz-, Safari1.2+, Opera+, Chrome+ While IE4+ continues to honor the original way of preventing default action for an event handler (that is, having the last statement of the event handler evaluate to return false), the IE4+ event model provides a property that lets the cancellation of default action take place entirely within a function invoked by an event handler. By default, the returnValue property of the event object is true, meaning that the element processes the event after the scripted handler completes its job, just as if the script weren’t there. Normal processing, for example, is displaying a typed character, navigating to a link’s href URL upon being clicked, or submitting a form after the Submit button is clicked. But you don’t always want the default action to occur. For example, consider a text box that is supposed to allow only numbers to be typed in it. The onkeypress event handler can invoke a function that inspects each typed character. If the character is not a numeric character, it should not reach the
1092
Chapter 32: Event Objects eventObject.srcElement text box for display. The following validation function may be invoked from the onkeypress event handler of just such a text box: function checkIt() { var charCode = event.keyCode; if (charCode < 48 || charCode > 57) { alert("Please make sure entries are numerals only."); event.returnValue = false; } }
By using this event handler, the errant character won’t appear in the text box. Note that this property is not a substitute for the return statement of a function. If you need a value to be returned to the invoking statement, you can use a return statement in addition to setting the event.returnValue property.
Example You can find several examples of the returnValue property at work in Chapters 1 and 26. Specifically, refer to Listings 26-30, 26-33, 26-36, 26-37, 26-38, and 26-44. Moreover, many of the other examples in Chapter 26 can substitute the returnValue property way of cancelling the default action if the scripts were to be run exclusively on IE4+. Related Item: return statement (Chapter 23, ‘‘Function Objects and Custom Objects’’)
saveType Value: String
Read-Only
Compatibility: WinIE5.5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe saveType property is assigned a value only when an oncontentsave event is bound to a WinIE DHTML behavior file. For more information about behaviors, see http://msdn.microsoft .com/en-us/library/ms531079%28VS.85%29.aspx. Related Item: addBehavior() method
srcElement Value: Element object reference
Read-Only
Compatibility: WinIE4+, MacIE4+, NN-, Moz-, Safari1.2+, Opera+, Chrome+ The srcElement property is a reference to the HTML element object that is the original target of the event. Because an event may bubble up through the element containment hierarchy and be processed at any level along the way, having a property that points back to the element from which the event originated is comforting. After you have a reference to that element, you can read or write any properties that belong to that element or invoke any of its methods.
1093
Part IV: Document Objects Reference eventObject.srcElement
Example As a simplified demonstration of the power of the srcElement property, Listing 32-11 has but two event handlers defined for the body element, each invoking a single function. The idea is that the onmousedown and onmouseup events will bubble up from whatever their targets are, and the event handler functions will find out which element is the target and modify the color style of that element. An extra flair is added to the script in that each function also checks the className property of the target element. If the className is bold — a class name shared by three span elements in the paragraph — the stylesheet rule for that class is modified so that all items share the same color. Your scripts can do even more in the way of filtering objects that arrive at the functions to perform special operations on certain objects or groups of objects. Notice that the scripts don’t have to know anything about the objects on the page to address each clicked one individually. That’s because the srcElement property provides all of the specificity needed for acting on the target element.
LISTING 32-11
Using the srcElement Property srcElement Property .bold {font-weight:bold} .ital {font-style:italic} function highlight() { var elem = event.srcElement; if (elem.className == "bold") { document.styleSheets[0].rules[0].style.color = "red"; } else { elem.style.color = "#FFCC00"; } } function restore() { var elem = event.srcElement; if (elem.className == "bold") { document.styleSheets[0].rules[0].style.color = ""; } else {
Click on the bolded text, then click on the unbolded text. What do you see happen?
One event handler...
Can
Cover
Many
Objects
Lorem ipsum dolor sit amet, consectetaur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim adminim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
1095
Part IV: Document Objects Reference eventObject.srcFilter Related Items: fromElement, toElement properties
srcFilter Value: String
Read-Only
Compatibility: WinIE4+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeAccording to Microsoft, the srcFilter property should return a string of the name of the filter that was applied to trigger an onfilterchange event handler. While the property exists in the event object, its value is always null, at least through WinIE8. Related Items: onfilterchange event handler; style.filter object
srcUrn Value: String
Read-Only
Compatibility: WinIE5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeIf an event is fired in a WinIE behavior attached to an element, and the behavior has a URN identifier defined for it, the srcUrn property returns the string from the URN identifier. For more information about behaviors, see http://msdn.microsoft.com/enus/library/ms531079%28VS.85%29.aspx. Related Item: addBehavior() method
toElement (See fromElement)
type Value: String
Read-Only
Compatibility: WinIE4+, MacIE4+, NN4+, Moz+, Safari+, Opera+, Chrome+ You can find out what kind of event fired to create the current event object by way of the type property. The value is a string version of the event name — just the name of the event without the ‘‘on’’ prefix that is normally associated with event names in IE. This property can be helpful when you designate one event handler function to process different kinds of events. For example, both the onmousedown and onclick event handlers for an object can invoke one function. Inside the function, a branch is written for whether the type comes in as mousedown or click, with different processing for each event type. That is not to endorse such event handler function sharing, but for you to be aware of this power should your script constructions find the property helpful. This property and its values are fully compatible with the NN6+/Moz/W3C event models.
Example Use The Evaluator (Chapter 4, ‘‘JavaScript Essentials’’) to see values returned by the type property. Enter the following object name into the bottom text box and press Enter/Return: event
If necessary, scroll the Results box to view the type property, which should read keypress. Now click the List Properties button. The type changes to click. The reason for these types is that the
1096
Chapter 32: Event Objects eventObject.wheelData event object whose properties are being shown here is the event that triggers the function to show the properties. From the text box, an onkeypress event handler triggers that process; from the button, an onclick event handler does the job.
Related Items: All event handlers (Chapter 26, ‘‘Generic HTML Element Objects’’)
wheelData Value: Integer
Read-Only
Compatibility: WinIE5.5+, MacIE-, NN-, Moz-, Safari-, Opera-, ChromeThe wheelData property returns an integer indicating which direction the mouse wheel was rolled for an onmousewheel event. The values returned are typically either 120 or −120, with a positive value indicating that the mouse wheel was rolled toward the screen and a negative value indicating that the wheel was rolled the opposite direction.
About this object Although it is based largely on the event object as defined by the W3C DOM Level 2, the NN6+/Moz event object also carries forward several characteristics from the NN4 event object. A few properties are continued primarily for backward compatibility. But because future Mozilla development will likely forego the peculiarities of the NN4 DOM and event models, you should ignore these items (as highlighted below). Wherever possible, look forward and embrace the W3C DOM aspects of the event model. Safari, Opera, and Chrome, for example, implement a lot of the W3C DOM event model, but exclude all old NN4 properties. Although the NN6+/Moz event model provides a bubbling event propagation model just as IE4+ does the incompatibility of referencing event objects between the event models is still there. In the W3C DOM (as in NN4), an event object is explicitly passed as a parameter to event handler (or, rather, event listener) functions. But after you have a browser-specific event object assigned to a variable inside a function, a few important properties have the same names between the IE4+ and W3C DOM event models. If Microsoft adopts more of the W3C DOM event model in future versions of IE, the compatibility situation should improve. The event object discussed in this section is the instance of an event that is created as the result of a user or system event action. The W3C DOM includes an additional static Event object. Many of the properties of the static Event object are inherited by the event instances, so the detailed coverage of
1098
Chapter 32: Event Objects eventObject.shiftKey those shared properties is in this section because it is the event object you’ll be scripting for the most part. In many code fragments in the following detail sections, you will see references that begin with the evt reference. This assumes that the statement(s) resides inside a function that has assigned the incoming event object to the evt parameter variable: function myFunction(evt) {...}
As shown earlier in this chapter, you can equalize W3C DOM and IE4+ event object references when it is practical to do so because the scripts work on identical (or similar) event object properties. The results of this equalization are typically stored in the evt variable.
Compatibility: WinIE4+, MacIE4+, NN6+, Moz+, Safari+, Opera+, Chrome+ When an event object is created in response to a user or system action, these four properties are set based on whether their corresponding keys were being held down at the time — a Shift-click, for example. If the key was held down, the property is assigned a value of true; otherwise the value is false. The metaKey property corresponds to the Command key on the Macintosh keyboard but does not register for the Windows key on Wintel computers. Most commonly, you use expressions consisting of this property as if construction conditional statements. Because these are Boolean values, you can combine multiple properties in a single condition. For example, if you have a branch of a function that is to execute only if the event occurred with both the Shift and Control keys held down, the condition looks like the following: if (evt.shiftKey && evt.ctrlKey) { // statements to execute }
Conversely, you can take a more user-friendly approach to provide special processing if the user holds down any one of the four modifier keys: if (evt.shiftKey || evt.ctrlKey || evt.metaKey || evt.altKey) { // statements to execute }
The rationale behind this approach is to offer perhaps some shortcut operation for users, but not force them to memorize a specific modifier key combination.
1099
Part IV: Document Objects Reference eventObject.bubbles
Example See Listing 32-6, where the values of these properties are used to set the checked properties of corresponding check boxes for a variety of event types. Related Items: None
bubbles Value: Boolean
Read-Only
Compatibility: WinIE-, MacIE-, NN6+, Moz+, Safari+, Opera+, Chrome+ Not every event bubbles. For example, an onsubmit event propagates no further than the form object with which the event is associated. Events that do not bubble have their event object’s bubbles property set to false; all others have the property set to true. You use this property in the rare circumstance of a single event handler function processing a wide variety of events. You may want to perform special operations only on events that can bubble, and handle the others without special treatment. For this branch, you can use the property in an if conditional statement: if (evt.bubbles) { // special processing for bubble-able events }
You do not have to branch, however, just to cancel bubbling. A non-propagating event doesn’t mind if you tell it not to propagate. Related Item: cancelBubble property
button Value: Integer
Read-Only
Compatibility: WinIE4+, MacIE4+, NN6+, Moz+, Safari+, Opera8+, Chrome+ The button property reveals the button that was pressed to activate the mouse event. In the W3C DOM, the left (primary) button returns a value of 0. If the mouse is a three-button mouse, the middle button returns 1. The right button (on any multi-button mouse) returns a value of 2. Mouse buttons other than the primary one are easier to look for in mousedown or mouseup events, rather than onclick events. In the case of a user pressing multiple buttons, only the most recent button is registered. Exercise caution when scripting the button property across browsers. The respective event models define different button values for mouse buttons.
Example See Listing 32-7, where the button property is revealed in the status bar. Try pressing individual mouse buttons on, say, the screen button. Related Items: None
cancelable Value: Boolean
1100
Read-Only
Chapter 32: Event Objects eventObject.keyCode Compatibility: WinIE-, MacIE-, NN6+, Moz+, Safari+, Opera+, Chrome+ If an event is cancelable, then its default action can be prevented from occurring with the help of a script. Although most events are cancelable, some are not. The cancelable property lets you inquire about a particular event object to see if its event type is cancelable. Values for the property are Booleans. You may want to perform special operations only on events that are cancelable and handle the others without special treatment. For this branch, you can use the property in an if conditional statement: if (evt.cancelable) { // special processing for cancelable events }
You do not have to branch, however, just to prevent an event’s default action. A non-cancelable event doesn’t mind if you tell it to prevent the default action. Related Item: preventDefault() method
cancelBubble Value: Boolean
Read/Write
Compatibility: WinIE4+, MacIE4+, NN6+, Moz+, Safari+, Opera+, Chrome+ The cancelBubble property is a rare instance of an IE4+ event property being implemented in NN6+/Moz and Gecko-, WebKit-, and Presto-based browsers, even though the property is not defined in the W3C DOM. The property operates the same as in IE4+ in that it determines whether the current event object bubbles up any higher in the element containment hierarchy of the document. By default, this property is false, meaning that if the event is supposed to bubble, it will do so automatically. To prevent event bubbling for the current event, set the property to true anywhere within the event handler function. Cancelling event bubbling works only for the current event. The very next event to fire will have bubbling enabled (provided the event bubbles). If you are trying to migrate your code as much as possible to the W3C DOM, use the stopPropagation() method instead of cancelBubble. For cross-browser compatibility, however, cancelBubble is a safe bet.
Example See Listing 32-2 to see the cancelBubble property in action in an IE environment. Even though that listing has some features that apply to WinIE5.5+, the bubble cancelling demonstration works all the way back to IE4. Related Item: stopPropagation() method
Part IV: Document Objects Reference eventObject.keyCode The W3C DOM event object model clearly distinguishes between the Unicode character attached to the alphanumeric keys of the keyboard and the code attached to each of the keyboard keys (regardless of character). To inspect the character of a key, use the onkeypress event to create the event object, and then look at the event object’s charCode property. This is the property that returns 97 for ‘‘a’’ and 65 for ‘‘A’’ because it’s concerned with the character associated with the key action. This property’s value is zero for onkeydown and onkeyup events. In contrast, the keyCode property is filled with a non-zero value only from onkeydown and onkeyup events (onkeypress sets the property to zero) when alphanumeric keys are pressed; for most other non-character keys, all three events fill the keyCode property. Through this property you can look for non-character keys, such as arrows, page navigation, and function keys. For the character keys, there is no distinction between uppercase and lowercase: The ‘‘A’’ key on the Latin keyboard returns a value of 65, regardless of the state of the Shift key. At the same time, however, the press of the Shift key fires its own onkeydown and onkeyup events, setting the keyCode value to 16 (except in Safari, which does not register modifier keys in this way). Other non-character keys — arrows, page navigation, function, and similar — have their own codes as well. This gets very detailed, and involves special key codes for the numeric keyboard keys that are different from their corresponding numbers along the top row of the alphanumeric keyboard.
Cross-Reference Be sure to see the extensive section on keyboard events in Chapter 26, ‘‘Generic HTML Element Objects,’’ for examples of how to apply the keyCode property in applications.
Example Listing 32-12 provides a play area to view the charCode and keyCode properties for all three keyboard events while you type into a textarea. You can use this later as an authoring tool to grab the precise codes for keyboard keys you may not be familiar with. LISTING 32-12
Displaying charCode and keyCode Property Values charCode and keyCode Properties td {text-align:center} function showCode(which, evt) { document.forms[0].elements[which + "Char"].value = evt.charCode; document.forms[0].elements[which + "Key"].value = evt.keyCode; } function clearEm() { for (var i = 1; i < document.forms[0].elements.length; i++)
Part IV: Document Objects Reference eventObject.clientX LISTING 32-12
(continued)
Here are some specific tasks to try with the page in NN6+/Moz to examine key codes (if you are not using a browser set for English and a Latin-based keyboard, your results may vary):
1. Enter a lowercase a. Notice how the onkeypress event handler shows the charCode to be 97, which is the Unicode (and ASCII) value for the first of the lowercase letters of the Latin alphabet. But the other two event types record just the key’s code: 65.
2. Type an uppercase A via the Shift key. If you watch closely, you see that the Shift key, itself, generates the key code 16 for the onkeydown and onkeyup events. But the character key then shows the value 65 for all three events (until you release the Shift key), because the ASCII value of the uppercase letter happens to match the keyboard key code for that letter.
3. Press and release the Down Arrow key (be sure the cursor still flashes in the textarea, because that’s where the keyboard events are being monitored). As a non-character key, all three events stuff a value into the keyCode property, but zero into charCode. The keyCode value for this key is 40.
4. Poke around with other non-character keys. Some may produce dialog boxes or menus, but their key codes are recorded nonetheless. Related Items: onkeydown, onkeypress, onkeyup event handlers
Chapter 32: Event Objects eventObject.clientX The W3C DOM event object borrows mouse coordinate properties from both the NN4 and the IE4+ event models. If you have worked with event coordinates in these other browsers, you have nothing new to learn for W3C DOM-compatible browsers. Like the IE4+ event object, the W3C DOM event object’s clientX and clientY properties are the coordinates within the viewable content region of the window. These values are relative to the window space, not the document. But unlike IE4+, you don’t have to calculate the position of the coordinates within the document because another pair of NN/Moz properties, pageX and pageY, provide that information automatically. If the page has not scrolled, the values of the client and page coordinates are the same. Because it is usually more important to know an event’s coordinates with respect to the document than the window, the pageX and pageY properties are used most often. Another NN/Moz property pair, layerX and layerY, borrow terminology from the now defunct layer schemes of NN4, but the properties can still be quite valuable nonetheless. These coordinates are measured relative to the positioning context of the element that received the event. For regular, unpositioned elements in the body part of a document, that positioning context is the body element. Thus, for those elements, the values of the page and layer coordinates will be the same. But if you create a positioned element, the coordinate space is measured from the top-left corner of that space. Thus, if you are using the coordinates to assist in scripted dragging of positioned elements, you can confine your scope to just the positioned element. One coordinate system missing from the NN6+/Moz repertoire, but present in Safari, is that of the target element itself (comparable to the offsetX and offsetY properties of IE4+). These values, however, can be calculated in NN/Moz by subtracting from the page coordinate properties the offsetLeft and offsetTop properties of both the target element and its positioning context. For example, if you want to get the coordinates of a mouse event inside an image, the event handler can calculate those values as follows: var clickOffsetX = evt.pageX - evt.target.offsetLeft – document.body.offsetLeft; var clickOffsetY = evt.pageY - evt.target.offsetTop – document.body.offsetTop;
The last set of coordinate properties, screenX and screenY, provide values relative to the entire video display. Of all these properties, only the client and screen coordinates are defined in the W3C DOM Level 2 standard. Keep in mind that in most W3C DOM–compatible browsers, event targets include text nodes inside elements. Because nodes do not have all the properties of elements (for example, they have no offset properties signifying their location in the document), you may sometimes have to go to the target node’s parent node to get an element object whose offset properties provide the necessary page geography. This matters, of course, only if your scripts need to concern themselves with mouse events on text.
Example You can see the effects of the coordinate systems and associated NN6+/Moz properties with the page in Listing 32-13. You can view coordinate values for all four measuring systems, as well as some calculated value. Two clickable objects are provided so that you can see the differences between an object not in any layer and an object residing within a layer (although anything you see is clickable, including text nodes). Figure 32-1 shows the results of a click inside the positioned layer. One of the calculated fields applies window scrolling values to the client coordinates. But, as you will see, these calculated values are the same as the more convenient page coordinates. The other calculated field shows the coordinates relative to the rectangular space of the target element. Notice in the
1105
Part IV: Document Objects Reference eventObject.clientX code that if the nodeType of the target indicates a text node, that node’s parent node (an element) is used for the calculation.
Chapter 32: Event Objects eventObject.clientX else { elem["on" + evtType] = func; } } addEvent(window, "load", function() { addEvent(document.body, "mousedown", function(evt) {checkCoords(evt);}); }); X and Y Event Properties (NN6+/Moz)
Click on the button and in the DIV/image to see the coordinate values for the event object.
NN6 Mouse Event Coordinates:
target:
57) {
1120
Chapter 32: Event Objects eventObject.stopPropagation() alert("Please make sure entries are numbers only."); evt.preventDefault(); } }
This way, the errant character won’t appear in the text box. Invoking the preventDefault() method in NN6+/Moz and Gecko-, WebKit-, and Presto-based browsers, is the equivalent of assigning true to event.returnValue in IE5+. Related Item: cancelable property
stopPropagation() Returns: Nothing Compatibility: WinIE-, MacIE-, NN6+, Moz+, Safari+, Opera+, Chrome+ Use the stopPropagation() method to stop events from trickling down or bubbling up further through the element containment hierarchy. A statement in the event listener function that invokes the following is all that is needed: evt.stopPropagation();
As an alternative, you can cancel bubbling directly in an element’s event handler attribute, as in the following: onclick="doButtonClick(this); event.stopPropagation()"
If you are writing cross-browser scripts, you also have the option of using the cancelBubble property, which is compatible with IE4+. Related Items: bubbles, cancelBubble properties
1121
Part V Appendixes IN THIS PART Appendix A JavaScript and Browser Objects Quick Reference
Appendix B What’s on the CD-ROM
JavaScript and Browser Objects Quick Reference
1125
Part V: Appendixes
JavaScript and Browser Objects Quick Reference String constructor length prototype
try { statements to test } catch (errorInfo) { statements if exception occurs in try block } [finally { statements to run, exception or not }] throw value
Number
*All properties and methods are of the static Math object.
prototype constructor descriptionE fileNameM lineNumberM message name numberE
21
if (condition) { statementsIfTrue }
*Method of the static Date object.
*Returns array with properties: index, input, [0],...[n].
Operators Comparison == Equals === Strictly equals != Does not equal !== Strictly does not equal > Is greater than >= Is greater than or equal to < Is less than >>= Zero fill by value &= Bitwise AND by value |= Bitwise OR by value ^= Bitwise XOR by value []= Destructuring assignment Boolean && || !
AND OR NOT
Bitwise & | ^ ~ > >>>
Bitwise AND Bitwise OR Bitwise XOR Bitwise NOT Left shift Right shift Zero fill right shift
Miscellaneous , Series delimiter delete Property destroyer in Item in object instanceof Instance of new Object creator this Object self-reference ?: Conditional operator typeof Value type void Return no value
Appendix A JavaScript Bible, 7th Edition by Danny Goodman How to Use This Quick Reference This guide contains quick reference info for the core JavaScript language and browser object models starting with IE 5.5, Mozilla, and Safari. Numbers in the upper right corners of object squares are chapter numbers in which the object is covered in detail.
Each term is supported by all baseline browsers unless noted with a superscript symbol indicating browser brand and version: E—Internet Explorer M—Mozilla S—Safari O—Opera C—Google Chrome For example, M1.4 means the term is supported only by Mozilla 1.4 or later; E means the terms is supported only by Internet Explorer.
† checkbox, radio †† button, checkbox, radio ††† text, password, hidden †††† text, password, hidden, file
textarea
36
createTextRange()E select()
form length multiple name options[] options[i].defaultSelected options[i].index options[i].selected options[i].text options[i].value selectedIndex size type value
addImport(”url”[, index])E cssRulesMSO9C addRule(”selector”,“spec”[, index])ESC cssTextE deleteRule(index)MSOC disabled insertRule(”rule”, index)MSOC hrefEMSO9C E removeRule(index)ESC id importsE media ownerNodeMSOC ownerRuleMSOC owningElementE pagesE parentStyleSheetEMS readOnlyE rulesESC title type
he accompanying Windows–Macintosh CD-ROM contains additional chapters that include many more JavaScript examples, an electronic version of the Quick Reference shown in Appendix A for printing, a complete, searchable version of the entire book, and the Adobe Reader.
System Requirements To derive the most benefit from the example listings, you should have a Mozilla-based browser (for example, Firefox 3.6+, -, or Camino 2+), Internet Explorer 8+, a WebKit-based browser (for example, Safari 4+, or Google Chrome 5+) or a Presto-based browser (for example, Opera 10+) installed on your computer. Although many scripts run in these and other browsers, several scripts demonstrate features that are available on only a limited range of browsers. To write scripts, you can use a simple text editor, word processor, or dedicated HTML editor. To use the Adobe Reader (version 7.0), you need the following:
For Windows XP Pro/Home, or Windows XP Table PC Edition, you should be using a Pentium computer with 128 MB of RAM and 90 MB of hard disk space.
Macintosh users require a PowerPC G3, G4, or G5 processor, OS X v10.2.8 or later, at least 128 MB of RAM, and 110 MB of disk space.
Disc Contents When you view the contents of the CD-ROM, you will see files tailored for your operating system. The contents include the following items.
1133
Part V: Appendixes
JavaScript listings for text editors Starting with Part III of the book, almost all example listings are on the CD-ROM in the form of complete HTML files, which you can load into a browser to see the JavaScript item in operation. A directory called Listings contains the example files, with nested folders named for each chapter. The name of each HTML file is keyed to the listing number in the book. For example, the file for Listing 26-1 is named jsb26-01.html. Note that no listing files are provided for the tutorial chapters of Part II, because you are encouraged to enter HTML and scripting code manually. For your convenience, the _index.html file in the Listings folder provides a front-end table of contents to the HTML files for the book’s program listings. Open that file from your browser whenever you want to access the program listing files. If you intend to access that index page frequently, you can bookmark it in your browser(s). Using the index file to access the listing files can be very important in some cases, because several individual files must be opened within their associated framesets to work properly. Accessing the files through the _index.html file ensures that you open the frameset. The _index.html file also shows browser compatibility ratings for all the listings. This saves you time from opening listings that are not intended to run on your browser. To examine and modify the HTML source files, open them from your favorite text editor program (for Windows editors, be sure to specify the .html file extension in the Open File dialog box). You can open all example files directly from the CD-ROM, but if you copy them to your hard drive, access is faster and you will be able to experiment with modifying the files more readily. Copy the folder named Listings from the CD-ROM to any location on your hard drive.
Printable version of the JavaScript and Browser Object Quick Reference from Appendix A If you like the quick reference in Appendix A, you can print it out with the help of the Adobe Reader, included with the CD-ROM.
Adobe Reader The Adobe Reader is a helpful program that enables you to view the Quick Reference from Appendix A and the searchable version of this book, both of which are in PDF format on the CD-ROM. To install and run Adobe Reader, follow these steps:
For Windows 1. Navigate to the Adobe_Reader folder on the CD-ROM. 2. In the Adobe_Reader folder, double-click the lone executable file and follow the instructions presented on-screen for installing Adobe Acrobat Reader.
For Macintosh 1. Open the Adobe_Reader folder on the CD-ROM. 2. In the Adobe_Reader folder, double-click the Adobe Reader disk image icon; this will mount the disk image on your computer. Then open the mounted image and copy the Adobe Reader folder to the Applications directory of your computer.
1134
Appendix B: What’s on the CD-ROM
PDF version of book with topical references In many places throughout the reference chapters of Parts III and IV, you see notations directing you to the CD-ROM for a particular topic being discussed. All these topics are located in the chapters as they appear in complete Adobe Acrobat form on the CD-ROM. A single PDF file is located on the CD-ROM, and it serves as an electronic version of the entire book, complete with full topics that are listed as CD-ROM references in the printed book. For the fastest access to these topics, copy the entire PDF file for the book to your hard disk. Like any PDF document, the PDF version of the book is searchable. Recent versions of Adobe Reader should automatically load the index file (with the .pdx extension) to supply indexed search capabilities (which is much faster than Acrobat’s Find command). To begin an actual search, click the Search icon (binoculars in front of a sheet of paper). Enter the text for which you’re searching. To access the index and search facilities in future sessions, the CD-ROM must be in your CD-ROM drive — unless, of course, you’ve copied both the .pdx and .pdf files to your hard drive.
Troubleshooting If you have difficulty installing or using the CD-ROM programs, try the following solutions:
Turn off any anti-virus software that you may have running. Installers sometimes mimic virus activity and can make your computer incorrectly believe that a virus is infecting it. (Be sure to turn the anti-virus software back on later.)
Close all running programs. The more programs you’re running, the less memory is available to other programs. Installers also typically update files and programs; if you keep other programs running, installation may not work properly.
Reference the ReadMe file. Refer to the ReadMe file located at the root of the CD-ROM for the latest product information at the time of publication.
Customer Care If you have trouble with the CD-ROM, please call the Customer Support phone number at (800) 762-2974. Outside the United States, call 1(317) 572-3994. You can also contact Wiley Product Technical Support at http://support.wiley.com. John Wiley & Sons will provide technical support only for installation and other general quality control items. For technical support on the applications themselves, consult the program’s vendor or author. To place additional orders or to request information about other Wiley products, please call (877) 762-2974.
Note The property assignment event handling technique employed throughout the code in this chapter and much of the book is a deliberate simplification to make the code more readable. It is generally better to use the more modern approach of binding events using the addEventListener() (NN6+/Moz/W3C) or attachEvent() (IE5+) methods. A modern cross-browser event handling technique is explained in detail in Chapter 32, ‘‘Event Objects.’’
Even though the tag is supported by all modern browsers, its specific usage across browsers isn’t exactly standard. It’s necessary to work a little markup magic to use modern tags that operate in IE, Mozilla-based, and WebKit-based browsers. The difficulty arises in the way the browsers specify some attribute or parameter values for Java applets. Listing 47-1 reveals how to embed an applet into a document with the tag that works simultaneously in the different browsers. An important feature of the listing is a Microsoft proprietary markup feature called conditional comments (http://msdn.microsoft.com/en-us/library/ms537512%28VS.85%29.aspx). These HTML comment tags, with their special comment text, allow IE to skip over HTML markup (although if the Microsoft conditional comments are not used, IE will still render correctly; this is just a cleaner, best practices, approach). In the listing, only the first tag is rendered in WinIE; other browsers load both, but do not load the applet in the first tag because the attribute and parameter values are not in the format that they require for loading a Java applet. In addition to the tag markup differences, note that the functions controlling the applet create references to the applet object differently. Browsers other than IE have two object elements with the same name to deal with, meaning that there is an array of objects with that name; thus the script pulls a reference to the second one when two are detected.
Java applet ‘‘properties’’ The Java equivalents of JavaScript object properties can be called properties in Java as well, but in reality are public accessor and mutator methods, commonly called getters and setters. These methods allow for reading and writing the corresponding private attribute of the class. If you have access to some Java source code, you can recognize these getters and setters by their names: private String fontName; ... public String getFontName() { return fontName; } public void setFontName(String fontName) { this.fontName = fontName; }
BC528
Chapter 47: Scripting Java Applets and Plug-Ins
In the preceding code, you’ll notice that the private attribute fontName is associated with its corresponding getters and setters via a standard JavaBean naming convention: camel case. As a JavaScript programmer, you would be using these methods to indirectly access the corresponding private attribute. Getters and setters are used because the use of public instance attributes is considered a violation of object encapsulation and is seriously frowned upon by the Java programmer. Java authors must specify a method’s data type when declaring any method that returns a value. That’s why the String data type appears in the preceding example. Your scripts can access these variables with the same kind of syntax that you use to access JavaScript object properties. In order to access the fontName field, you would execute its corresponding getter and setter, as shown in the following example: var theFont = document.applets[0].getFontName(); document.applets[0].setFontName("courier");
Scripting Applets in Real Life Because the purpose of scripting an applet is to gain access to the inner sanctum of a compiled program, the program should be designed to handle such rummaging around by scripters. If you can’t acquire a copy of the source code or don’t have any other documentation about the scriptable parts of the applet, you may have a difficult time knowing what to script and how to do it.
Getting to scriptable methods If you write your own applets or are fortunate enough to have the source code for an existing applet, the safest way to modify the applet variable settings or the running processes is through applet methods. An applet designed for scriptability should have a number of methods defined that enable you to make scripted changes to private variable values. To view a sample of an applet designed for scriptability, open the Java source code file for Listing 47-2 from the CD-ROM. A portion of that program listing is shown in the following example. LISTING 47-2
Partial Listing for ScriptableClock.java import java.awt.*; import java.util.*; import java.text.*; public class ScriptableClock extends java.applet.Applet implements Runnable {
continued
BC529
Part VII: More JavaScript Programming
LISTING 47-2
(continued)
// control variables private final boolean GMT = true; private final boolean LOCALE = false; private String displayDate; private Font displayFont; private Thread thread; // parameter options private Color bgColor; private Color fgColor; private Rectangle displayArea; private String fontName; private int fontSize; private int fontStyle; private int height, width; private boolean timeZone; @Override public void init() { parseArgs(); displayFont = new Font(fontName, fontStyle, fontSize); timeZone = LOCALE; displayArea = getBounds(); height = displayArea.height; width = displayArea.width; resize(width, height); } @Override public void start() { if (thread == null) { thread = new Thread(this); thread.start(); } } @Override public void stop() { if (thread != null) { thread = null; } } public void run() { while (thread != null) { Date theDate = new Date(); DateFormat dateFormat = DateFormat.getDateTimeInstance(DateFormat. MEDIUM, DateFormat.FULL); if (timeZone) { dateFormat.setTimeZone(TimeZone.getTimeZone("GMT-0:00")); }
BC530
Chapter 47: Scripting Java Applets and Plug-Ins
displayDate = dateFormat.format(theDate); repaint(); try { Thread.sleep(1000); } catch (InterruptedException e) { } } } @Override public void paint(Graphics g) { g.setColor(bgColor); g.fillRect(0, 0, width, height); g.setColor(fgColor); g.setFont(displayFont); FontMetrics fm = getFontMetrics(getFont()); int textWidth = fm.stringWidth(displayDate); int horizOffset = (width / 2) - (textWidth / 2); g.drawString(displayDate, 5, 35); } /* Begin public methods for getting and setting data via LiveConnect */ public void setTimeZone(String zone) { stop(); timeZone = (zone.startsWith("GMT")) ? true : false; start(); } public void setFont(String newFont, String newStyle, String newSize) { stop(); if (newFont != null && newFont.length() != 0) { fontName = newFont; } if (newStyle != null && newStyle.length() != 0) { setFontStyle(newStyle); } if (newSize != null && newSize.length() != 0) { setFontSize(newSize); } displayFont = new Font(fontName, fontStyle, fontSize); start(); } public void setColor(String newbgColor, String newfgColor) { stop(); bgColor = parseColor(newbgColor); fgColor = parseColor(newfgColor); start(); }
continued
BC531
Part VII: More JavaScript Programming
LISTING 47-2
(continued)
public String getInfo() { String result = "Info about ScriptableClock.class\r\n"; result += "Version/Date: 1.0d1/2 May 1996\r\n"; result += "Author: Danny Goodman ([email protected])\r\n"; result += "Public Variables:\r\n"; result += " (None)\r\n\r\n"; result += "Public Methods:\r\n"; result += " setTimeZone(\"GMT\" | \"Locale\")\r\n"; result += " setFont(\"fontName\",\"Plain\" |\"Bold\" | \"Italic\", \"fontSize\")\r\n"; result += " setColor(\"bgColorName\", \"fgColorName\")\r\n"; result += " colors: Black, White, Red, Green, Blue, Yellow\r\n"; return result; } /* End public methods for scripted access. */ private void setFontStyle(String style) { try { if (style.equalsIgnoreCase("Plain")) { fontStyle = Font.PLAIN; } else if (style.equalsIgnoreCase("Italic")) { fontStyle = Font.ITALIC; } else { fontStyle = Font.BOLD; } } catch (Exception e) { fontStyle = Font.BOLD; } } private void setFontSize(String size) { try { fontSize = Integer.parseInt(size); } catch (Exception e) { fontSize = 24; } } private void parseArgs() { fontName = getParameter("font"); if (fontName == null) { fontName = new String("TimesRoman"); } String n = getParameter("fontSize"); setFontSize(n);
BC532
Chapter 47: Scripting Java Applets and Plug-Ins
n = getParameter("fontStyle"); setFontStyle(n); bgColor = parseColor(getParameter("bgColor")); if (bgColor == null) { bgColor = Color.white; } fgColor = parseColor(getParameter("fgColor")); if (fgColor == null) { fgColor = Color.black; } } private Color parseColor(String c) { try { if (c.equalsIgnoreCase("Black")) { return Color.black; } else if (c.equalsIgnoreCase("White")) { return Color.white; } else if (c.equalsIgnoreCase("Red")) { return Color.red; } else if (c.equalsIgnoreCase("Green")) { return Color.green; } else if (c.equalsIgnoreCase("Blue")) { return Color.blue; } else if (c.equalsIgnoreCase("Yellow")) { return Color.yellow; } else { return Color.black; } } catch (Exception e) { return null; } } }
The methods shown in Listing 47-2 are defined specifically for scripted access. In this case, they safely stop the applet thread before changing any values. The last method is one we recommend to applet authors. The method returns a small bit of documentation containing information about the kind of methods that the applet likes to have scripted and what you can have as the passed parameter values. Now that you see the amount of scriptable information in this applet, look at Listing 47-3, which takes advantage of that scriptability by providing several HTML form elements as user controls for the clock. The results are shown in Figure 47-1.
BC533
Part VII: More JavaScript Programming
LISTING 47-3
A More Fully Scripted Clock Clock with Lots o’ Widgets function setTimeZone(popup) { var choice = popup.options[popup.selectedIndex].value; var applet = (document.clock2.length) ? document.clock2[1] : document.clock2; applet.setTimeZone(choice); } function setColor(form) { var bg = form.backgroundColor.options[form.backgroundColor.selectedIndex].value; var fg = form.foregroundColor.options[form.foregroundColor.selectedIndex].value; var applet = (document.clock2.length) ? document.clock2[1] : document.clock2; applet.setColor(bg, fg); } function setFont(form) { var fontName = form.theFont.options[form.theFont.selectedIndex].value; var fontStyle = form.theStyle.options[form.theStyle.selectedIndex].value; var fontSize = form.theSize.options[form.theSize.selectedIndex].value; var applet = (document.clock2.length) ? document.clock2[1] : document.clock2; applet.setFont(fontName, fontStyle, fontSize); } function getAppletInfo(form) { var applet = (document.clock2.length) ? document.clock2[1] : document.clock2; form.details.value = applet.getInfo(); } function showSource() { var newWindow = window.open("ScriptableClock.java","", "WIDTH=450,HEIGHT=300,RESIZABLE,SCROLLBARS"); }
BC534
Chapter 47: Scripting Java Applets and Plug-Ins
Select Time Zone: Local Time Greenwich Mean Time
Select Background Color: White Black Red Green Blue Yellow Select Color Text Color: White Black Red Green Blue Yellow
Select Font: Times Roman Helvetica Courier Arial continued
BC535
Part VII: More JavaScript Programming
LISTING 47-3
(continued)
Select Font Style: Plain Bold Italic Select Font Size: 12 18 24 30
Very little of the code here controls the applet — only the handful of functions near the top. The rest of the code makes up the HTML user interface for the form element controls. After you open this document from the CD-ROM, be sure to click the Applet Info button to see the methods that you can script and the way that the parameter values from the JavaScript side match up with the parameters on the Java method side.
Applet limitations Because of concerns about security breaches via the NPAPI, Mozilla clamps down on some powers that would be nice to have via a scripted applet. The most noticeable barrier is the one that prevents applets from accessing the network under scripted control. Therefore, even though a Java applet has no difficulty reading or writing text files from the server, such capabilities — even if built into an applet of your own design — won’t be carried out if triggered by a JavaScript call to the applet. However, signed scripts (see Chapter 49) and applets can break through these security barriers after the user has given explicit permission for them to do so.
BC536
Chapter 47: Scripting Java Applets and Plug-Ins
FIGURE 47-1
Scripting more of the ScriptableClock applet.
Faceless applets Until the NPAPI came along, Java applets were generally written to show off data and graphics — to play a big role in the presentation on the page. But if you prefer to let an applet do the heavy algorithmic lifting for your pages, while the HTML form elements and images (or Dynamic HTML facilities) do the user interface, you essentially need what we call a faceless applet. The method for embedding a faceless applet into your page is the same as embedding any applet: Use the tag. For a faceless applet, specify only 1 pixel for both the height and width attributes (0 has strange side effects). This setting creates a dot on the screen, which, depending on your page’s background color, may be completely invisible to page visitors. Place it at the bottom of the page, if you like. To show how nicely this method can work, Listing 47-4 provides the Java source code for a simple applet that retrieves a specific text file, and stores the results in a Java variable available for fetching by the JavaScript shown in Listing 47-5. The HTML even automates the loading process by triggering the retrieval of the Java applet’s data from an onload event handler.
BC537
Part VII: More JavaScript Programming
LISTING 47-4
Java Applet Source Code import java.net.*; import java.io.*; public class FileReader extends java.applet.Applet implements Runnable { private private private private
public void getFile(String fileName) throws IOException { String result = null; String line = null; InputStream connection = null; DataInputStream dataStream = null; StringBuffer buffer = new StringBuffer(); try { url = new URL(getDocumentBase(), fileName); connection = url.openStream(); dataStream = new DataInputStream(new BufferedInputStream(connection)); while ((line = dataStream.readLine()) != null) { buffer.append(line + "\n"); } result = buffer.toString(); } catch (MalformedURLException e) { result = "AppletError " + e; } catch (IOException e) { result = "AppletError: " + e; } finally { if (dataStream != null) { dataStream.close(); } if (connection != null) { connection.close(); } } output = result; } public String fetchText() { return output; } @Override public void init() { }
BC538
Chapter 47: Scripting Java Applets and Plug-Ins
@Override public void start() { if (thread == null) { thread = new Thread(this); thread.start(); } } @Override public void stop() { if (thread != null) { thread = null; } } public void run() { try { getFile(fileName); } catch (IOException e) { output = "AppletError: " + e; } } }
All the work of actually retrieving the file is performed in the getFile() method (which runs immediately after the applet loads). Notice that the name of the file to be retrieved, Bill of Rights.txt, is stored as a variable near the top of the code, making it easy to change for a recompilation, if necessary. You can also modify the applet to accept the filename as an applet parameter, specified in the HTML code. Meanwhile, the only hook that JavaScript needs is the one public method called fetchText(), which merely returns the value of the output variable, which in turn holds the file’s contents. This Java source code must be compiled into a Java class file (already compiled and included on the CD-ROM as FileReader.class) and placed in the same directory as the HTML file that loads this applet. Also, no explicit pathname for the text file is supplied in the source code, so the text file is assumed to be in the same directory as the applet. LISTING 47-5
HTML Asking Applet to Read Text File Letting an Applet Do The Work function getFile(form)
continued
BC539
Part VII: More JavaScript Programming
LISTING 47-5
(continued)
{ var applet = (document.readerApplet.length) ? document.readerApplet[1] : document.readerApplet; var output = applet.fetchText(); form.fileOutput.value = output; } function autoFetch() { var applet = (document.readerApplet.length) ? document.readerApplet[1] : document.readerApplet; var output = applet.fetchText(); if (output != null) { document.forms[0].fileOutput.value = output; return; } var t = setTimeout("autoFetch()",1000); } Text from a text file...
BC540
Chapter 47: Scripting Java Applets and Plug-Ins
Because an applet is usually the last detail to finish loading in a document, you can’t use an applet to generate the page immediately. At best, an HTML document can display a pleasant welcome screen while the applet finishes loading and running whatever it does to prepare data for the page’s form elements. Fortunately for modern browsers, the page can then be dynamically constructed out of the retrieved data. Notice in Listing 47-5 that the onload event handler calls a function that checks whether the applet has supplied the requested data. If not, the same function is called repeatedly in a timer loop, until the data is ready and the textarea can be set. The tag is located at the bottom of the Body, set to 1 pixel square — invisible to the user. No user interface exists for this applet, so you have no need to clutter up the page with any placeholders or bumper stickers. Figure 47-2 shows the page generated by the HTML and the applet working together. The Get File button is merely a manual demonstration of calling the same applet method that the onload event handler calls. FIGURE 47-2
The page with text retrieved from a server file.
A faceless applet may be one way for web authors to hide what may otherwise be JavaScript code that is open to any visitor’s view. For example, if you want to deliver a small data collection lookup with a document, but don’t want the array of data to be visible in the JavaScript code, you can create the array and lookup functionality inside a faceless applet. Then, use form controls and JavaScript to act as query entry and output display devices (or to dynamically generate a table). Because the parameter values passed between JavaScript and Java applets must be string, numeric, or Boolean values, you won’t be able to pass arrays without performing some amount
BC541
Part VII: More JavaScript Programming
of conversion within either the applet or the JavaScript code (JavaScript’s string.split() and array.join() methods help a great deal here).
Data type conversions The example in this chapter does not pass any parameters to the applet’s methods, but you are free to do so. You need to pay attention to the way in which values are converted to Java data types. JavaScript strings and Boolean values are converted to Java String and Boolean objects. All JavaScript numbers, regardless of their subtype (that is, integer or floating-point number), are converted to Float objects. Therefore, if a method must accept a numeric parameter from a script, the parameter variable in the Java method must be defined as a Float type. The distinction between JavaScript string values and string objects can impact data being passed to an applet. If an applet method requires a string object as a parameter, you may have to explicitly convert a JavaScript string value (for example, a string from a text field) to a string object via the new String() constructor (see Chapter 15). You can also pass references to objects, such as form control elements. Such objects get wrapped with a JSObject type (see the discussion about this class later in the chapter). Therefore, parameter variables must be established as type JSObject (and the netscape.javascript.JSObject class must be imported into the applet).
Applet-to-Script Communication The flip side of scripted applet control is having an applet control both script and HTML content in the page. Before you undertake this avenue in page design, you must bear in mind that any calls made from the applet to the page are hard-wired for the specific scripts and HTML elements in the page. If this level of tight integration and dependence suits the application, the link up will be successful.
Note The discussion of applet-to-script communication assumes you have experience writing Java applets. We use Java jargon quite freely in this discussion.
What your applet needs Most modern browsers come with a zipped set of special class files tailored for use in the NPAPI. For Mozilla, the class files are located in an archive called -plugin.jar (Windows) or JavaPluginCocoa.bundle (Mac). Use the file search facility of the OS to locate the relevant file on your system. Microsoft versions of these class files are usually located in C:\Program Files\Java\jre6\lib. If you don’t find jre6, look for jre5. The browser must see these class files (and have both Java and JavaScript enabled in the preferences screens) for the NPAPI to work. You then need to add the plugin.jar file to the Java classpath environment variable. Following is an example of how this is accomplished at the command line: set CLASSPATH= C:\jdk1.6.0\jre\lib\plugin.jar
BC542
Chapter 47: Scripting Java Applets and Plug-Ins
Of course, your specific Java SDK installation may be different in terms of version numbering, but the command should be very similar. With the plugin.jar file available in the classpath, you’re ready to use the NPAPI objects in Java code, and build an applet. Following are the two vital classes in the netscape package (yes, even for IE), which is the Java package made available in the NPAPI ZIP file (-plugin.jar): netscape.javascript.JSObject netscape.javascript.JSException
Both classes must be imported into your applet via the Java import compiler directive: import netscape.javascript.*;
When the applet runs, the NPAPI-aware browser knows how to find the two classes, so that the user doesn’t have to do anything special as long as the supporting files are in their default locations.
What your HTML needs As a security precaution, an tag requires one extra parameter to give the applet permission to access the HTML and scripting inside the document. That parameter is mayscript, and it can go anywhere inside the tag, as follows:
Permission is not required for JavaScript to access an applet’s methods or properties, but if the applet initiates contact with the page, this attribute is required.
About the JSObject class The portal between the applet and the HTML page that contains it is the netscape. javascript.JSObject class. This object’s methods allow the applet to contact document objects and invoke JavaScript statements. Table 47-1 shows the object’s methods and one static method. Just as the window object is the top of the document object hierarchy for JavaScript references, the window object is the gateway between the applet code and the scripts and document objects. To open that gateway, use the JSObject.getWindow() method to retrieve a reference to the document window. Assign that object to a variable that you can use throughout your applet code. The following code fragment shows the start of an applet that assigns the window reference to a variable named mainwin: import netscape.javascript.*; public class myClass extends java.applet.Applet { private JSObject mainwin; @Override
Sets value of a named object belonging to a container
setSlot(int index, Object value)
Sets value of an indexed object belonging to a container
toString()
Returns string version of JSObject
If your applet will be making frequent trips to a particular object, you may want to create a variable holding a reference to that object. To accomplish this, the applet needs to make progressively deeper calls into the document object hierarchy with the getMember() method. For example, the following sequence assumes mainwin is a reference to the applet’s document window. Eventually, the statements set a form’s field object to a variable for use elsewhere in the applet: JSObject doc = (JSObject) mainwin.getMember("document"); JSObject form = (JSObject) doc.getMember("entryForm"); JSObject phonefld = (JSObject) form.getMember("phone");
Another option is to use the Java eval() method to execute an expression from the point of view of any object. For example, the following statement gets the same field object as the preceding fragment: JSObject phonefld = mainwin.eval("document.entryForm.phone");
As soon as you have a reference to an object, you can access its properties via the getMember() method, as shown in the following example, which reads the value property of the text box, and casts the value into a Java String object: String phoneNum = (String) phonefld.getMember("value");
BC544
Chapter 47: Scripting Java Applets and Plug-Ins
Two JSObject class methods let your applet execute arbitrary JavaScript expressions, and invoke object methods: the eval() and call() methods. Use these methods with any JSObject. If a value is to be returned from the executed statement, you must cast the result into the desired object type. The parameter for the eval() method is a string of the expression to be evaluated by JavaScript. Scope of the expression depends on the object attached to the eval() method. If you use the window object, the expression would exist as if it were a statement in the document script (not defined inside a function). Using the call() method is convenient for invoking JavaScript functions in the document, although it requires a little more preparation. The first parameter is a string of the function name. The second parameter is an array of arguments for the function. Parameters can be of mixed data types, in which case the array would be of type Object. If you don’t need to pass a parameter to the function call, you can define an array of a single empty string value (for example, String arg[] = {""}) and pass that array as the second parameter.
Data type conversions The strongly-typed Java language is a mismatch for loosely-typed JavaScript. As a result, with the exception of Boolean and string objects (which are converted to their respective JavaScript objects), you should be aware of the way the NPAPI adapts data types to JavaScript. Any Java object that contains numeric data is converted to a JavaScript number value. Because JavaScript numbers are IEEE doubles, they can accommodate just about everything Java can throw their way. If the applet extracts an object from the document, and then passes that JSObject type back to JavaScript, that passed object is converted to its original JavaScript object type. But objects of other classes are passed as their native objects wrapped in JavaScript ‘‘clothing.’’ JavaScript can access the applet object’s methods as if the object were a JavaScript object. Finally, Java arrays are converted to the same kind of JavaScript array created via the new Array() constructor. Elements can be accessed by integer index values (not named index values). All other JavaScript array properties and methods apply to this object as well.
Example applet-to-script application To demonstrate several techniques for communicating from an applet to both JavaScript scripts and document objects, we present an applet that displays two simple buttons (see Figure 47-3). One button generates a new window, spawned from the main window, and fills the window with dynamically-generated content from the applet.
Note Be sure to turn off pop-up window blocking temporarily to run this example. WebKit-based browsers do not handle pop-up windows in the same way as IE, Opera, and Mozilla-based browsers, so you will have problems when running this example.
BC545
Part VII: More JavaScript Programming
FIGURE 47-3
The applet displays two buttons seamlessly on the page.
The second button communicates from the applet to that second window by invoking a JavaScript function in the document. The last part of the demonstration shows the applet changing the value of a text box when the applet starts up. Listing 47-6 shows the source code for the Java applet. Because the applet generates two buttons, the code begins by importing the AWT interface builder classes. We also import the netscape.javascript package to get the JSObject class. The name of this sample class is JtoJSDemo. We declare four global variables: two for the windows, two for the applet button objects. LISTING 47-6
The applet’s init() method establishes the user interface elements for this simple applet. A white background is matched in the HTML with a white document background color, making the applet appear to blend in with the page. We use this opportunity to set the mainwin variable to the browser window that contains the applet. @Override public void init() { setBackground(Color.white); newWinButton = new Button("New Browser Window"); toggleButton = new Button("Toggle SubWindow Color"); this.add(newWinButton); this.add(toggleButton); newWinButton.addActionListener(this); toggleButton.addActionListener(this); mainwin = JSObject.getWindow(this); }
As soon as the applet starts, it changes the value property of a text box in the HTML form. Because this is a one-time access to the field, we elected to use the eval() method from the point of view of the main window, rather than build successive object references through the object hierarchy with the getMember() method. @Override public void start() { mainwin.eval("document.indicator.running.value = ‘Yes’"); }
Event handling is quite simple in this application. A click of the first button invokes doNewWindow(); a click of the second invokes toggleColor(). Both methods are defined later in the applet. public void actionPerformed(ActionEvent evt) { Button source = (Button)evt.getSource(); if (source == newWinButton) { doNewWindow(); } else if (source == toggleButton) { toggleColor(); } }
One of the applet’s buttons calls the doNewWindow() method defined here. We use the eval() method to invoke the JavaScript window.open() method. The string parameter of the eval() method is exactly like the statement that appears in the page’s JavaScript to open a new window. The window.open() method returns a reference to that subwindow, so that the statement here captures the returned value, casting it as a JSObject type for the subwin variable. That subwin variable can then be used as a reference for another eval() method that writes to that second window. Notice that the object to the left of the eval() method governs the recipient of the eval() method’s expression. The same is true for closing the writing stream to the subwindow.
BC547
Part VII: More JavaScript Programming
Note Unfortunately, earlier IE implementations of JSObject do not provide a suitable reference to the external window after it is created. Therefore, the window neither receives its content nor responds to color changes in this example. Due to other anomalies with subwindows, we advise against using NPAPI powers with multiple windows in older versions of IE.
LISTING 47-6
(continued)
Java Applet Source Code void doNewWindow() { subwin = (JSObject) mainwin.eval( "window.open(",’fromApplet’,’height=200,width=200’)"); subwin.eval("document.write(’Howdy from the applet!’)"); subwin.eval("document.close()"); }
The second button in the applet calls the toggleColor() method. In the HTML document, a JavaScript function named toggleSubWindowColor() takes a window object reference as an argument. Therefore, we first assemble a one-element array of type JSObject, consisting of the subwin object. That array is the second parameter of the call() method, following a string version of the JavaScript function name being called. void toggleColor() { if (subwin != null) { JSObject arg[] = {subwin}; mainwin.call("toggleSubWindowColor", arg); } } }
Now onto the HTML that loads the preceding applet class and receives its calls. The document is shown in Listing 47-7. One function is called by the applet. A text box in the form is initially set to ‘‘No’’ but gets changed to ‘‘Yes’’ by the applet after it has finished its initialization. The only other item of note is that the tag includes a mayscript parameter to allow the applet to communicate with the page. LISTING 47-7
HTML Document Called by Applet Java-to-JavaScript Demo
BC548
Chapter 47: Scripting Java Applets and Plug-Ins
function toggleSubWindowColor(wind) { if (wind.closed) { alert("The subwindow is closed. Can’t change it’s color."); } else { // The applet sets the color to white. // IE only works if test for hex value. // Other browsers only work if test for white. wind.document.bgColor = (wind.document.bgColor == "#ffffff" || wind.document.bgColor == "white") ? "red" : "white"; } } Here’s the applet: Is the applet running yet?
Scripting Plug-Ins Controlling a plug-in (or Windows ActiveX control in IE) from JavaScript is much like controlling a Java applet, but with more browser-specific concerns to worry about, even at the HTML level. Not all plug-ins are scriptable, of course, nor do all browsers permit such scripting, as mentioned at the start of this chapter. Yet even when you have found the right combination of
BC549
Part VII: More JavaScript Programming
browser version(s) and plug-in(s), you must also learn what the properties and/or methods of the plug-in are, so that your scripts can control them. Take a common plug-in duty, such as playing audio: the likelihood that all users will have the same audio playback plug-in installed in a particular browser brand and operating system is perhaps too small to entrust your programming to a single plug-in. If, on the other hand, you are using a plug-in that works only with a special data type, your page just needs to check that the plug-in is installed (and that it is the desired minimum version). In this section of the chapter, you’ll begin to understand the HTML issues, and then examine two separate audio playback examples. One example lets users change tunes being played back; the other arrives with five sounds, each of which is controlled by a different onscreen interface element. Both of these audio playback examples employ a library that has been designed to provide basic audio playback interfaces to the most popular scriptable audio playback plug-in, Windows Media Player, running in Internet Explorer for Windows. The main goal of the library is to act as an API (Application Programming Interface) between your scripts and the player. The API presents a simple vocabulary to let your scripts control the Windows Media Player. If you want to control an older version of the player, you can modify the details to accommodate that player’s API, while leaving your other interface code untouched.
The HTML side Although several tags have been used in the past to embed plug-ins in web pages, the modern approach involves a single tag only. With the plug-in embedded within the page (even if you don’t see it), the plug-in becomes part of the document’s object model, which means that your scripts can address it. The modern and now preferred way to get external media into the document is to load the plug-in as an object through the tag. The object element is endorsed by the W3C HTML standard, and has been supported in Internet Explorer since IE4. In many ways the tag works like the legacy tag, in that aside from specifying attributes that load the plug-in, additional nested param elements enable you to make numerous settings to the plug-in while it loads, including the name of the file to pre-load. As with a plug-in’s attributes, an object’s parameters are unique to the object and are documented (somewhere) for every object intended to be put into an HTML page. The Windows operating system has a special (that is, far from intuitive) way it refers to the plug-in program (otherwise known in Windows as an ActiveX control): through its class id (also known as a guid). You must know this long string of numbers and letters in order to embed the object into your page. The following example is an object element that loads the Windows Media Player 9.x plug-in (ActiveX control) into a page:
continued
BC647
Part VIII: Applications
LISTING 52-3
(continued)
January February March April May June July August September October November December
JavaScript: jsb52-03.js // initialize when the page has loaded addEvent(window, ‘load’, initialize); // create array of English month names var theMonths = ["January","February","March","April","May","June", "July","August","September","October","November","December"]; // global variables var oDateChooser; var oYearChooser; var oMonthChooser; var oTableHeader; var oTableBody; /******************* INITIALIZATIONS ********************/ function initialize() { // get IE4+ or W3C DOM reference for an ID // dateChooser is the form element if (document.getElementById) { oDateChooser = document.getElementById("dateChooser"); oYearChooser = document.getElementById("chooseYear"); oMonthChooser = document.getElementById("chooseMonth");
BC648
Chapter 52: Application: Tables and Calendars
oTableHeader = document.getElementById("tableHeader"); oTableBody = document.getElementById("tableBody"); } else { oDateChooser = document.dateChooser; oYearChooser = document.oDateChooser.chooseYear; oMonthChooser = document.oDateChooser.chooseMonth; oTableHeader = document.tableHeader; oTableBody = document.tableBody; } addEvent(oMonthChooser, ‘change’, populateTable); addEvent(oYearChooser, ‘change’, populateTable); // initialize year choices fillYears(); // initiialize table populateTable(oDateChooser); } // create dynamic list of year choices function fillYears() { var today = new Date(); var thisYear = today.getFullYear(); for (i = thisYear; i < thisYear + 5; i++) { oYearChooser.options[oYearChooser.options.length] = new Option(i, i); } setCurrMonth(today); } // set month choice to current month function setCurrMonth(today) { oMonthChooser.selectedIndex = today.getMonth(); } /******************* UTILITY FUNCTIONS ********************/ // day of week of month’s first day function getFirstDay(theYear, theMonth) { var firstDate = new Date(theYear,theMonth,1); return firstDate.getDay(); } // number of days in the month function getMonthLen(theYear, theMonth) { var oneHour = 1000 * 60 * 60; var oneDay = oneHour * 24;
continued
BC649
Part VIII: Applications
LISTING 52-3
(continued)
var thisMonth = new Date(theYear, theMonth, 1); var nextMonth = new Date(theYear, theMonth + 1, 1); var len = Math.ceil((nextMonth.getTime() thisMonth.getTime() - oneHour) / oneDay); return len; } /************************ DRAW CALENDAR CONTENTS *************************/ // clear and re-populate table based on form’s selections function populateTable() { var theMonth = oMonthChooser.selectedIndex; var theYear = parseInt(oYearChooser.options [oYearChooser.selectedIndex].value); // initialize date-dependent variables var firstDay = getFirstDay(theYear, theMonth); var howMany = getMonthLen(theYear, theMonth); // fill in month/year in table header while(oTableHeader.firstChild) { oTableHeader.removeChild(oTableHeader.firstChild); } oTableHeader.appendChild(document.createTextNode (theMonths[theMonth] + " " + theYear)); // initialize vars for table creation var dayCounter = 1; // clear any existing rows while (oTableBody.rows.length > 0) { oTableBody.deleteRow(0); } var newR, newC; var done=false; while (!done) { // create new row at end newR = oTableBody.insertRow(oTableBody.rows.length); for (var i = 0; i < 7; i++) { // create new cell at end of row newC = newR.insertCell(newR.cells.length); if (oTableBody.rows.length == 1 && i < firstDay) { // no content for boxes before first day while(newC.firstChild)
BC650
Chapter 52: Application: Tables and Calendars
{ newC.removeChild(newC.firstChild); } newC.appendChild(document.createTextNode("")); continue; } if (dayCounter == howMany) { // no more rows after this one done = true; } // plug in date (or empty for boxes after last day) while(newC.firstChild) { newC.removeChild(newC.firstChild); } newC.appendChild(document.createTextNode((dayCounter "9") { return false; } } return true; } // function to determine if value is in acceptable range function inRange(inputStr) { num = parseInt(inputStr); // Machines don’t need parenthesis but humans do: if (num < 1 || (num > 586 && num < 596) || (num > 599 && num < 700) || num > 728) { return false; } return true; }
The master validation controller function (named isValid() in this application) is also covered in depth in Chapter 46. A statement that wants to know if it should proceed with the lookup
BC660
Chapter 53: Application: A Lookup Table
process calls this function. If any one validation test fails, the function returns false, and the search does not proceed: // Master value validator routine function isValid(inputStr) { var msg = " 3 digit positive number"; var msgPrefix; var msgSuffix; if (isEmpty(inputStr)) { msgPrefix = "Please enter a"; msgSuffix = " into the field before clicking the button."; alert(msgPrefix + msg + msgSuffix); return false; } else { if (!isNumber(inputStr)) { msgPrefix = "Please make sure entries are"; msgSuffix = "s only."; alert(msgPrefix + msg + msgSuffix); return false; } else { if (!inRange(inputStr)) { msgPrefix = "Sorry, the number you entered is not part of our database. Try a"; msgSuffix = "."; alert(msgPrefix + msg + msgSuffix); return false; } } } return true; } // **END DATA VALIDATION FUNCTIONS**
The search() function is invoked by two different event handlers. The two direct calls come from the input field’s onchange event handler and the Search button’s onclick event handler. To search the database, the script repeatedly compares each succeeding entry of the ssn[] array against the value entered by the user. For this process to work, a little bit of preliminary work is needed. First comes an initialization of a variable, foundMatch, which comes into play later. Initially set to false, the variable is set to true only if there is a successful match — information you need later to set the value of the result text object correctly for all possible conditions: function search() { var foundMatch = false; var inputStr = stripZeros(oEntry.value);
BC661
Part VIII: Applications
if (isValid(inputStr)) { inputValue = inputStr; for (var i = 0; i < ssn.length; i++) { if (inputValue 0)
BC688
Chapter 55: Application: Outline-Style Table of Contents
As with the HTML assembly code of the first outliner, if you were to add attributes to outline elements in an OPML outline (for example, a URL for an icon to display in front of the text), it is in makeHTML() that the values would be read and applied to the HTML being created. The only other function invoked by the makeHTML() function is calcBlockState(). This function looks into one of the OPML outline’s head elements, called expansionstate. This element’s values can be set to a comma-delimited list of numbers, corresponding to nodes that are to be shown expanded when the outline is first displayed. The calcBlockState() function is invoked for each parent element. The element’s location is compared against values in the expansionstate element, if there are any, and returns the appropriate 1 or 0 value for the state string being assembled for the rendered outline: // apply default expansion state from outline’s header // info to the expanded state for one element to help // initialize currState variable function calcBlockState(n)
BC690
Chapter 55: Application: Outline-Style Table of Contents
{ var ol = xDoc.getElementsByTagName("body")[0]; var outlineLen = ol.getElementsByTagName("outline").length; // get OPML expansionState data var expandElem = xDoc.getElementsByTagName("expansionState")[0]; var expandedData = (expandElem.childNodes.length) ? expandElem.firstChild.nodeValue.split(",") : null; if (expandedData) { for (var j = 0; j < expandedData.length; j++) { if (n == expandedData[j] - 1) { return "1"; } } } return "0"; }
The final act of the initialization process is a call to the initExpand() function. This function loops through the currState global variable (whose value was written in makeHTML() with the help of calcBlockState()) and sets the display property to block for any element designed to be expanded at the outset. HTML element construction in makeHTML() is performed in such a way that each parent div has a span nested directly inside of it; and inside that span are all the child nodes. The display property of the span determines whether all of those children are seen or not. // expand items set in expansionState XML tag, if any function initExpand() { for (var i = 0; i < currState.length; i++) { if (currState.charAt(i) == 1) { document.getElementById("OLBlock" + i).style.display = "block"; } } }
By the time the initExpand() function has run — a lot of setup code that executes pretty quickly — the rendered outline is in a steady state. Users can now expand or collapse portions by clicking the widget icons.
Toggling node expansion All of the widget images in the outline have onclick event handlers assigned to them. The handlers invoke the toggle() function, passing parameters consisting of a reference to the img
BC691
Part VIII: Applications
element object receiving the event, and the serial number of the span block nested just inside the div that holds the image. With these two pieces of information, the toggle() function sets in motion the act of inverting the expanded/collapsed state of the element and the plus or minus version of the icon image. The blockNum parameter corresponds to the position within the currState string of 1s and 0s holding the flag for the expanded state of the block. With the current value retrieved from currState, the value is inverted through swapState(). Then, based on the new setting, the display property of the block is set accordingly, and widget art is changed through two special-purpose functions: // toggle an outline mother entry, storing new state value; // invoked by onclick event handlers of widget image elements function toggle(img, blockNum) { var newString = ""; var expanded, n; // modify state string based on parameters from img expanded = currState.charAt(blockNum); currState = swapState(currState, expanded, blockNum); // dynamically change display style if (expanded == "0") { document.getElementById("OLBlock" + blockNum).style.display = "block"; img.src = getExpandedWidgetState(img.src); } else { document.getElementById("OLBlock" + blockNum).style.display = "none"; img.src = getCollapsedWidgetState(img.src); } }
Swapping the state of the currState variable utilizes the same XOR operator employed by the first outliner in this chapter. The entire currState string is passed as a parameter. The indicated digit is segregated and inverted, and the string is reassembled before being returned to the calling statement in toggle(): // invert state function swapState(currState, currVal, n) { var newState = currState.substring(0,n); newState += currVal ^ 1; // Bitwise XOR item n newState += currState.substring(n+1,currState.length); return newState; }
As mentioned earlier, each of the clickable widget icons (plus and minus) can be one of three states, depending on whether the widget is at the start, middle, or end of a vertical-dotted chain. The two image-swapping functions find out (by inspecting the URLs of the images currently occupying the img element) which version is currently in place so that, for instance, a starting
BC692
Chapter 55: Application: Outline-Style Table of Contents
‘‘plus’’ (collapsed) widget is replaced with a starting ‘‘minus’’ (expanded) widget. This is a case of going the extra mile for the sake of an improved user interface: // retrieve matching version of ‘minus’ images function getExpandedWidgetState(imgURL) { if (imgURL.indexOf("Start") != -1) { return expandedWidgetStart; } if (imgURL.indexOf("End") != -1) { return expandedWidgetEnd; } return expandedWidget; } // retrieve matching version of ‘plus’ images function getCollapsedWidgetState(imgURL) { if (imgURL.indexOf("Start") != -1) { return collapsedWidgetStart; } if (imgURL.indexOf("End") != -1) { return collapsedWidgetEnd; } return collapsedWidget; } return collapsedWidget; }
Wrap up There’s no question that the amount and complexity of the code involved for the OPML version of the outliner are significant. The pain associated with developing an application such as this is all up front. After that, the outline content is easily modifiable in the OPML format (or perhaps by some future editor that produces OPML output). Even if you don’t plan to implement an OPML outline, the explanation of how this example works should drive home the importance of designing data structures that assist not only the visual design, but also the scripting that you use to manipulate the visual design.
Further Thoughts The advent of CSS and element positioning has prompted numerous JavaScripters to develop another kind of hierarchical system of pop-up or drop-down menus that don’t require as much scripting because of their reliance of CSS. You can find examples of this interface at many of the JavaScript source web sites listed in Appendix E.
BC693
Part VIII: Applications
Most of the code you find, however, will require a fair amount of tweaking to blend the functionality into the visual design that you have, or are planning, for your web site. Finding two implementations on the Web that look or behave the same way is rare. As long as you’re aware of what you’ll be getting yourself into, you are encouraged to check out these interface elements. By hiding menu choices except when needed, valuable screen real estate is preserved for more important static content.
BC694
Application: Calculations and Graphics
W
hen the scripting world had its first pre-release peeks at JavaScript (while Netscape was still calling the language LiveScript), the notion of creating interactive HTML-based calculators captured the imaginations of many page authors. Somewhere on the World Wide Web, you can find probably every kind of special-purpose calculation normally done by scientific calculators and personal computer programs — leaving only weather-modeling calculations to the supercomputers of the world. In the search for my calculator gift to the JavaScript universe, I looked around for something more graphical. Numbers, by themselves, are pretty boring; so any way the math could be enlivened was fine by me. Having been an electronics hobbyist since I was a kid, I recalled the color-coding of electronic resistor components. The values of these gizmos aren’t printed in plain numbers anywhere. You have to know the code and the meaning of the location of the colored bands to arrive at the value of each one. I think that this calculator will be fun to play with, even if you don’t know what a resistor is.
The Calculation To give you an appreciation for the calculation that goes into determining a resistor’s value, here is the way the system works. Colored bands are printed on the surface of a resistor to encode its resistance value in ohms. The first (leftmost) band is the tens digit; the second (middle) band is the ones digit. Each color has a number from 0 through 9 assigned to it (black = 0, brown = 1, and so on). Therefore, if the first band is brown and the second band
BC695
IN THIS CHAPTER Pre-cached images Math calculations CGI-like image assembly
Part VIII: Applications
is black, the number you start off with is 10. The third band is a multiplier. Each color determines the power of ten by which you multiply the first digits. For example, the red color corresponds to a multiplier of 102 , so that 10 ∞ 102 equals 1,000 ohms. A fourth band, if present, indicates the tolerance of the component — how far, plus or minus, the resistance measurement can fluctuate due to variations in the manufacturing process. Gold means a tolerance of plus-or-minus 5 percent; silver means plus-or-minus 10 percent; and no band means a 20 percent tolerance. A pinch of extra space typically appears between the main group of three-color bands and the one tolerance band.
User Interface Ideas The quick-and-dirty, non-graphical approach for a user interface was to use a single frame with four select elements defined as pop-up menus (one for each of the four color bands on a resistor), a button to trigger calculation, and a field to show the numeric results. How dull. It occurred to me that if I design the art carefully, I can have JavaScript assemble an updated image of the resistor consisting of different slices of art: static images for the resistor’s left and right ends, and variable slivers of color bands for the middle. Rather than use the brute force method of creating an image for every possible combination of colors (3,600 images total!), a far more efficient approach is to have one image file for each color (12 colors plus 1 empty) and enable JavaScript to call them from the server, as needed, in the proper order. If not for client-side JavaScript, a script on the server would have to handle this kind of intelligence and user interaction. But with this system, any dumb server can dish up the image files as called by the JavaScript script with no special server-side processing. The first generation of this resistor calculator used two frames, primarily because I needed a second frame to update the calculator’s art dynamically while keeping the pop-up color menus stationary. Images couldn’t be swapped back in those frontier days, so the lower frame had to be redrawn for each color choice. Fortunately, modern browsers enabled me to update individual image objects in a loaded document without any document reloading. Moreover, with all the images precached in memory, page users experience no (or virtually no) delay in making a change from one value to another. The design for the modern version is a simple, single-document interface (see Figure 56-1). Four pop-up menus let you match colors of a resistor, whereas the onchange event handler in each menu automatically triggers an image and calculation update. To hold the art together on the page, a table border surrounds the images on the page, whereas the numeric value of the component appears in a text field.
BC696
Chapter 56: Application: Calculations and Graphics
FIGURE 56-1
The Resistor Calculator with images inside a table border.
The Code All the action takes place in the file named resistor.html. A second document is an introductory HTML text document that explains what a resistor is and why you need a calculator to determine a component’s value. The article, called The Path of Least Resistance, can be viewed in a secondary window from a link in the main window. Here you will be looking only at resistor.html. The document begins in the traditional way without any surprises other than a CSS style to change the font of the body text. Notice that the onload event is bound to the window using the addEvent function (as described in Chapter 32, ‘‘Event Objects’’). Graphical Resistance Calculator
BC697
Part VIII: Applications
body { font-family:Arial, Helvetica, serif; } .copyright { font-size:small; } // initialize when the page has loaded addEvent(window, "load", calcOhms);
Basic arrays In calculating the resistance, the script needs to know the multiplier value for each color. If not for the last two multiplier values actually being negative multipliers (for example, 10-1 and 10-2), I could have used the index values without having to create this array. But the two out-of-sequence values at the end mean that it’s easier to work with an array than to try special-casing these instances in later calculations: // create array listing all the multiplier values var multiplier = new Array(); multiplier[0] = 0; multiplier[1] = 1; multiplier[2] = 2; multiplier[3] = 3; multiplier[4] = 4; multiplier[5] = 5; multiplier[6] = 6; multiplier[7] = 7; multiplier[8] = 8; multiplier[9] = 9; multiplier[10] = -1; multiplier[11] = -2; // create array listing all tolerance values var tolerance = new Array(); tolerance[0] = "+/-5%"; tolerance[1] = "+/-10%"; tolerance[2] = "+/-20%";
Although the script doesn’t do any calculations with the tolerance percentages, it needs to have the strings corresponding to each color for display in the pop-up menu. The tolerance array is there for that purpose. This is in contrast with the multiplier array, which contains numeric values instead of strings; the multiplier array is used to calculate the resistor value.
BC698
Chapter 56: Application: Calculations and Graphics
Calculations and formatting Before the script displays the resistance value, it needs to format the numbers into values that are meaningful to those who know about these values. Just like measures of computer storage bytes, high quantities of ohms are preceded with ‘‘kilo’’ and ‘‘meg’’ prefixes, commonly abbreviated with the ‘‘K’’ and ‘‘M’’ letters. The format() function determines the order of magnitude of the final calculation (from another function shown in the following section) and formats the results with the proper unit of measure: // format large values into kilo and meg function format(ohmage) { if (ohmage >= 1e6) { ohmage /= 1e6; return "" + ohmage + " Mohms"; } else { if (ohmage >= 1e3) { ohmage /= 1e3; return "" + ohmage + " Kohms"; } else { return "" + ohmage + " ohms"; } } }
The selections from the pop-up menus meet the calculation formulas of resistors in the calcOhms() function. Because this function is triggered indirectly by each of the select objects, sending any of their parameters to the function is a waste of effort. Moreover, the calcOhms() function is invoked by the onload event handler, which is not tied to the form or its controls. Therefore, the function obtains the reference to the form and then extracts the necessary values of the four select objects by using explicit (named) references. Each value is stored in a local variable for convenience in completing the ensuing calculation. Recalling the rules used to calculate values of the resistor bands, the first statement of the calculation multiplies the ‘‘tens’’ pop-up value times 10 to determine the tens digit, and then adds the ones digit. From there, the combined value is multiplied by the exponent value of the selected multiplier value. Notice that the expression first assembles the value as a string to concatenate the exponent factor and then evaluates it to a number. Although I try to avoid the eval() function because of its slow performance, the one call per calculation is not a performance issue. The evaluated number is passed to the format() function for proper formatting (and setting of order of magnitude). In the meantime, the tolerance value is extracted from its array, and the
BC699
Part VIII: Applications
combined string is plugged into the result text field (which is in a separate form, as described later): // calculate resistance and tolerance values function calcOhms() { var form = document.forms["input"]; var d1 = form.tensSelect.selectedIndex; var d2 = form.onesSelect.selectedIndex; var m = form.multiplierSelect.selectedIndex; var t = form.toleranceSelect.selectedIndex; var ohmage = (d1 * 10) + d2; ohmage = eval("" + ohmage + "e" + multiplier[m]); ohmage = format(ohmage); var tol = tolerance[t]; document.forms["output"].result.value = ohmage + ", " + tol; }
Preloading images As part of the script that runs when the document loads, the next group of statements precaches all possible images that can be displayed for the resistor art. For added scripting convenience, the color names are loaded into an array. With the help of that just-created array of color names, you then create another array (imageDB), which both generates Image objects for each image file, and assigns a URL to each image. Notice an important subtlety about the index values being used to create each entry of the imageDB array: Each index is a colorArray entry, which is the name of the color. As you found out in Chapter 18, ‘‘The Array Object,’’ if you create an array element with a named index, you must use that style of index to retrieve the data thereafter; you cannot switch arbitrarily between numeric indexes and names. As you see in a moment, this named index provides a critical link between the choices a user makes in the pop-up lists and the image objects being updated with the proper image file. // pre-load all color images into image cache var colorArray = new Array("Black","Blue","Brown","Gold","Gray", "Green","None","Orange","Red","Silver","Violet","White","Yellow"); var imageDB = new Array(); for (i = 0; i < colorArray.length; i++) { imageDB[colorArray[i]] = new Image(21,182); imageDB[colorArray[i]].src = colorArray[i] + ".gif"; }
The act of assigning a URL to the src property of an Image object instructs the browser to pre-load the image file into memory. This preloading happens as the document is loading, so another few seconds of delay won’t be noticed by the user.
Changing images on-the-fly The next four functions are invoked by their respective select object’s onchange event handler. For example, after a user makes a new choice in the first select object (the ‘‘tens’’ value
BC700
Chapter 56: Application: Calculations and Graphics
color selector), that select object reference is passed to the setTens() function. Its job is to extract the text of the choice and use that text as the index into the imageDB array. Alternatively, the color name can also be assigned to the value attribute of each option, and the value property read here. You need this connection to assign the src property of that array entry to the src property of the image that you see on the page (defined in the following section). This assignment is what enables the images of the resistor to be updated instantaneously — just the one image ‘‘slice’’ affected by the user’s choice in a select object: function setTens(choice) { var tensColor = choice.options[choice.selectedIndex].value; document.getElementById("tens").src = imageDB[tensColor].src; calcOhms(); } function setOnes(choice) { var onesColor = choice.options[choice.selectedIndex].value; document.getElementById("ones").src = imageDB[onesColor].src; calcOhms(); } function setMult(choice) { var multColor = choice.options[choice.selectedIndex].value; document.getElementById("mult").src = imageDB[multColor].src; calcOhms(); } function setTol(choice) { var tolColor = choice.options[choice.selectedIndex].value; document.getElementById("tol").src = imageDB[tolColor].src; calcOhms(); }
The rest of the script for the Head portion of the document merely provides the statements that open the secondary window to display the introductory document: function showIntro() { window.open("resintro.htm","","width=400,height=320, left=100,top=100"); }
Creating the select objects A comparatively lengthy part of the document is consumed with the HTML for the four select objects. Remember that the onload event was bound to the window object at the beginning of the script. This handler calculates the results of the currently selected choices whenever the document loads or reloads. If it weren’t for this event handler, you would not see the resistor
BC701
Part VIII: Applications
art when the document first appears. Also, because many browsers maintain their form controls’ settings while the page is in history, a return to the page later must display the images previously selected in the form: Calculate Resistor Values from Color Codes Black Brown Red Orange Yellow Green Blue Violet Gray White Black Brown Red Orange Yellow Green Blue Violet Gray White Black Brown Red Orange Yellow Green Blue Violet Gray White Gold Silver Gold
BC702
Chapter 56: Application: Calculations and Graphics
Silver None
Note The property assignment event handling technique in this example is a deliberate simplification to make the code more readable. It is generally better to use the more modern approach of binding events using the addEventListener() (NN6+/Moz/W3C) or attachEvent() (IE5+) methods, as was done earlier in the code for the onload event. The modern cross-browser event handling technique used earlier is explained in detail in Chapter 32.
Drawing the initial images The balance of the document, mostly in JavaScript, is devoted to creating the table and image objects whose src properties will be modified with each choice of a select object. The act of assembling the HTML for the image table occurs right after the select objects have rendered. References to those select elements are required in order to extract the currently selected values. If the form element that holds the select elements is not closed, you can’t build a valid reference to the select elements. Therefore, the page contains two forms: One for the select elements; one for the output text box inside the table: var form = document.forms["input"]; var tensDigit = form.tensSelect.selectedIndex; var tensColor = form.tensSelect.options[tensDigit].value; var onesDigit = form.onesSelect.selectedIndex; var onesColor = form.onesSelect.options[onesDigit].value; var multDigit = form.multiplierSelect.selectedIndex; var multColor = form.multiplierSelect.options[multDigit].value; var tolDigit = form.toleranceSelect.selectedIndex; var tolColor = form.toleranceSelect.options[tolDigit].value; var table ="
"; table += "
Resistance Value:"; table +="
"; table +=""; table +="
"; table +="";
BC703
Part VIII: Applications
table += " "; document.write(table); Illustration Copyright 1996 Danny Goodman. All Rights Reserved.
As you can see, the resistor images appear in one table cell (in the second row) that contains all seven image objects smashed against each other. To keep the images flush, there can be no spaces or carriage returns between tags.
Further Thoughts Although this example works quite well, annoying differences still exist among different platforms. At one point in the design process, I considered trying to align the pop-up menus with images of the resistor (or callout line images), but the differences in platform rendering of pop-up menus made that idea impractical. At best, I now separate the three left select objects from the right one by way of hard-coded spaces ( ). You should notice from this exercise that I look for ways to blend JavaScript object data structures with my own data’s structure. For example, the select objects serve multiple duties in these scripts. Not only does the text of each option point to an image file of the same name, but the index values of the same options are applied to the calculations. Things don’t always work out that nicely, but whenever your scripts bring together user interface elements and data elements, look for algorithmic connections involving names or index integers that you can leverage to create elegant, concise code. One last thought regarding this example involves the possible usage of the canvas object, which you learned about in Chapter 31, ‘‘Image, Area, Map, and Canvas Objects.’’ The canvas object makes it possible to forego images altogether and render the resistor purely through graphics methods. In other words, you could use the canvas object to draw the static parts of the resister via lines and circles, and then draw each colored stripe as a rectangle. Granted, it would be tough getting the nifty shaded 3D effect, but you could eliminate the entire issue of relying on images.
BC704
Application: Intelligent ‘‘Updated’’ Flags
I
t happens to every active web user all the time: You visit a site periodically and never know for sure what material is new since your last visit. Often, web page authors may flag items with ‘‘New’’ or ‘‘Updated’’ iconic images after they update those items themselves. But if you fail to visit the site over a few modification sessions, the only items you find flagged are those that are new as of the most recent update by the page’s author. Several new items from a few weeks back may be of vital interest to you, but you won’t have the time to look through the whole site in search of material that is more recent than your last visit. Even if the items display their modification dates, do you remember for sure the date and time of your last visit to the page? As much as we might expect a server-side program and database on a web site to keep track of my last visit, that really is asking a great deal of the web site. Besides, not every web site has the wherewithal to build such a database system — if it can even utilize server applications. Plus, some users won’t visit sites if they need to identify themselves or register. After surveying the way scriptable browsers store cookie information and how time calculations are performed under popular web browsers, I found that a feasible alternative is to build this functionality into HTML documents and let the scripting manage the feature for users. The goal is to save the date and time of the last visit to a page in the visitor’s cookie file, and then use that point as a measure against items that have an authorship time stamp in the HTML document.
The Cookie Conundrum Managing the cookie situation in this application is a bit more complicated than you may think. The reason is that you have to take into account the possible ways visitors may come and go from your site while surfing the
BC705
IN THIS CHAPTER Temporary and persistent cookies World time calculations CGI-like intelligence
Part VIII: Applications
Web. You cannot use just one cookie to store the last time a user visits the site, because you cannot predict when you should update that information with today’s date and time. For example, if you have a cookie with the previous visit in it, you eventually need to store today’s visit. But you cannot afford to overwrite the previous visit immediately (say, in onload) because your scripts need that information to compare against items on the page not only right now, but even after the visitor vectors off from a link and comes back later. That also means you cannot update that last visit cookie solely via an onunload event handler, because that, too, would overwrite information that you need when the visitor comes back a minute later. To solve the problem, I devised a system of two cookies. One is written to the cookie that is given an expiration date of some time out in the future — the hard cookie, I call it. The other is a temporary cookie — the soft cookie — which stays in cookie memory but is never written to the file. Such temporary cookies are automatically erased as the browser quits. The hard cookie stores the time stamp when a visitor first loads the page since the last launch of the browser. In other words, the hard cookie contains a time stamp of the current visit. Before the previous entry is overwritten, however, it is copied into the soft cookie. That soft cookie maintains the time stamp of the previous visit and becomes the measure against which author time stamps in the HTML document are compared. To guard against inadvertent overwriting of both cookies, a function triggered by the document’s onload event handler looks to see if the soft cookie has any data in it. If so, the function knows that the visitor has been to this page in the current session and leaves the current settings alone. Thus, the visitor can come to the site and see what’s new, vector off to some other location, come back to see the same new items flagged, and pick up from there. One potential downside to this system is that if a user never quits the browser (or if the browser quits only by crashing), the cookies will never be updated. If you discover that a great deal of your users keep their computers and browsers running all the time, you can build in a kind of timeout that invalidates the soft cookie if the hard cookie is more than, say, 12 hours old.
Time’s Not on Your Side Thanks to more than 17 years’ experience programming applications that involve tracking time, I am overly sensitive to the way computers and programming languages treat time on a global basis. This issue is a thorny one, what with the vagaries of Daylight Savings Time and time zones in some parts of the world that differ from their neighbors by increments other than whole hours. To accomplish a time tracking scheme for this application, I had to be aware of two times: the local time of the visitor and the local time of the page author. Making times match up in what can be widely disparate time zones, I use one time zone — GMT — as the reference point. When a visitor arrives at the page, the browser needs to save that moment in time so that it can be the comparison measure for the next visit. Fortunately, whenever you create a new date object in JavaScript, it does so internally as the GMT date and time. Even though the way you attempt
to read the date and time created by JavaScript shows you the results in your computer’s local time, the display is actually filtered through the time zone offset as directed by your computer’s time control panel. In other words, the millisecond value of every date object you create is maintained in memory in its GMT form. That’s fine for the visitor’s cookie value. For the page author, however, I was presented with a different problem. Rather than force the author to convert the time stamps throughout the document to GMT, I wanted to let the author enter dates and times in local time. Besides the fact that many people have trouble doing time zone conversions, it is much easier on the scripter’s side to look at an existing item in the HTML with a local time stamp and recognize when it was last updated. The problem, then, is how to let the visitor’s browser know what time the author’s time stamp is in GMT terms. To solve the issue, the author’s time stamp needs to include a reference to the author’s time zone relative to GMT. An Internet convention provides a couple of ways to do this: specifying the number of hours and minutes difference from GMT or, where supported by the browser, the abbreviation of the time zone. In JavaScript, you can create a new date object out of one of the specially formatted strings containing the date, time, and time zone. Three examples follow for the Christmas Eve dinner that starts at 6 p.m. in the Eastern Standard Time zone of North America: var myDate = new Date("24 Dec 2010 23:00:00 GMT"); var myDate = new Date("24 Dec 2010 18:00:00 GMT-0500"); var myDate = new Date("24 Dec 2010 18:00:00 EST");
The first assumes you know the Greenwich Mean Time for the date and time that you want to specify. But if you don’t, you can use the GMT designation and offset value. The syntax indicates that the date and time is in a time zone exactly five hours west of GMT (values to the east would be positive numbers) in hhmm format. Browsers also know all of the time zone abbreviations for North America (EST, EDT, CST, CDT, MST, MDT, PST, and PDT, where ‘‘S’’ is for standard time and ‘‘D’’ is for daylight time). When a user visits a page with this application embedded in it, the visitor’s browser converts the author’s time stamp to GMT (with the help of the author’s zone offset parameter), so that both the author time stamp and last visit time stamp (in the soft cookie) are comparing apples to apples.
The Application All of this discussion may make the application sound complicated. That may be true, internally. But the goal, as in most of the samples in this book, is to make the application easy to use on your site, even if you’re not sure how everything works inside. The sample page described in this chapter and on the CD-ROM (whatsnew.html) is pretty boring to look at, because the power all lies in the scripting that users don’t see (see Figure 57-1). Though this figure may be the most uninspired graphic presentation of the book, the functionality may be the most valuable addition that you make to your web site.
BC707
Part VIII: Applications
FIGURE 57-1
An item flagged as being new since my last visit to the page.
When you first open the document (do so from a copy on your hard disk so that you can modify the author time stamp in a moment), all you see are the two items on the page without any flags. Although both entries have author time stamps that pre-date the time you’re viewing the page, a soft cookie does not yet exist against which to compare those times. But the act of making the first visit to the page has created a hard cookie of the date and time.
Note Testing the sample page requires that cookies are enabled in your browser. Also, be aware that if you are testing with Google Chrome, your code will not work unless the files are coming from an HTTP server. Chrome intentionally disables cookies on file:/// documents. See Chapter 29, ‘‘The Document and Body Objects,’’ for a discussion of cookies.
Quit the browser to get that hard cookie officially written to the cookie file. Then open the whatsnew.html file in your script editor. Scroll to the bottom of the document, where you see the tag and the interlaced scripts that time stamp anything that you want on the page. This application is designed to display a special .gif image that says ‘‘NEW 4U’’ whenever an item has been updated since your last visit.
Each interlaced script looks like this: document.write(newAsOf("12 Oct 2010 13:36:00 PDT"))
The document.write() method writes to the page whatever HTML comes back from the newAsOf() function. The parameter to the newAsOf() function is what holds the author time stamp and zone offset information. The time stamp value must be in the string format, as shown in the preceding example, with the date and time following the exact order ‘‘dd mmm yyyy hh:mm:ss’’. Month abbreviations are in English (Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec). As you see in the code that follows, the newAsOf() function returns an tag with the ‘‘NEW 4U’’ image if the author time stamp (after appropriate conversion) is later than the soft cookie value. This image can be placed anywhere in a document. For example, at my web site, I sometimes place the image before a contents listing rather than at the end. This means, too, that if part of your page is written by document.write() methods, you can just insert the newAsOf() function call as a parameter to your own document.write() calls. If you want to see the author time stamping work, edit one of the time stamps in the whatsnew.html file to reflect the current time. Save the document and relaunch the browser
to view the page. The item whose author time stamp you modified should now show the bright ‘‘NEW 4U’’ image.
The Code The HTML file for the sample page is simple enough. I have you create a simple bulleted list of two entries, imaginatively called ‘‘First item’’ and ‘‘Second item.’’ Interlaced into the HTML are scripts that are ready to insert the ‘‘NEW 4U’’ image if the author time stamp is new enough: Showing What’s New
First item document.write(newAsOf("19 Jan 2010 19:55:00 PST"))
Second item document.write(newAsOf("15 Jan 2010 13:36:00 PST"))
BC709
Part VIII: Applications
The JavaScript file for the sample page starts by initializing three global variables that are used in the statements that follow. One variable is a Boolean value indicating whether the visitor has been to the page before. Another variable, lastVisit, holds the value of the soft cookie whenever the visitor is at this page: // globals var repeatCustomer = false; var lastVisit = 0; // to hold date & time of previous access in GMT milliseconds
For reading and writing cookie data, I’m including an expiration date, because I want this cookie to hang around in the cookie file for a while — at least until the next visit, whenever that may be: // shared cookie functions var mycookie = document.cookie; // read cookie data function getCookieData(name) { var label = name + "="; var labelLen = label.length; var cLen = mycookie.length; var i = 0; while (i < cLen) { var j = i + labelLen; if (mycookie.substring(i,j) == label) { var cEnd = mycookie.indexOf(";",j); if (cEnd == -1) { cEnd = mycookie.length; } return unescape(mycookie.substring(j,cEnd)); } i++; } return ""; } // write cookie data function setCookieData(name,dateData,expires) { mycookie = document.cookie = name + "=" + dateData + "; expires=" + expires; }
Notice that the setCookieData() function still maintains a level of reusability by requiring a name for the cookie to be passed as a parameter, along with the data and expiration date. I could have hard-wired the name into this function, but that goes against my philosophy of designing for reusability.
Setting the stage Functions in the next part of the script get your cookies all in a row. The first function (saveCurrentVisit()) deals with the visitor’s local time, converting it to a form that will be useful on the next visit. Although one of the local variables is called nowGMT, all the variable does is take the new date object and convert it to the GMT milliseconds value (minus any dateAdjustment value) by invoking the getTime() method of the date object. I use this name in the variable to help me remember what the value represents: // write date of current visit (in GMT time) to cookie function saveCurrentVisit() { var visitDate = new Date(); var nowGMT = visitDate.getTime(); var expires = (nowGMT + (180 * 24 * 60 * 60 *1000)); expires = new Date(expires); expires = expires.toGMTString(); setCookieData("lastVisit", nowGMT, expires); }
From the current time, I create an expiration date for the cookie. The example shows a date roughly six months (180 days, to be exact) from the current time. I leave the precise expiration date up to your conscience and how long you want the value to linger in a user’s cookie file. The final act of the saveCurrentVisit() function is to pass the relevant values to the function that actually writes the cookie data. I assign the name lastVisit to the cookie. If you want to manage this information for several different pages, assign a different cookie name for each page. This setup can be important in case a user gets to only part of your site during a visit. On the next visit, the code can point to page-specific new items. The ‘‘temporary’’ cookie also needs to set an expiration date for itself. Normally, temporary cookies disappear when the user quits the browser. But these days, it’s not uncommon for users to keep their computers and applications running for days (with fewer crashes than not too long ago). To force the browser to visit the site after awhile, as if coming fresh (to look for new flags), the nextPrevVisit cookie is set to expire one hour after it is set: // set cookie with next previous visit with one-hour expiration function saveNextPrevVisit(lastStoredVisit) { var visitDate = new Date(); var nowGMT = visitDate.getTime(); var expires = (nowGMT + (60*1000)); expires = new Date(expires);
The bulk of what happens in this application takes place in an initialization function. All the cookie swapping occurs there, as well as the setting of the repeatCustomer global variable value: // set up global variables and establish whether user is repeat customer function initialize() { var lastStoredVisit = getCookieData("lastVisit"); var nextPrevStoredVisit = getCookieData("nextPrevVisit"); if (!lastStoredVisit) { // never been here before saveCurrentVisit(); repeatCustomer = false; } else { // been here before... if (!nextPrevStoredVisit) { // but first time this session saveNextPrevVisit(lastStoredVisit); // expires in one hour lastVisit = parseFloat(lastStoredVisit); saveCurrentVisit(); repeatCustomer = true; } else { // back again during this session (perhaps reload or Back) lastVisit = parseFloat(nextPrevStoredVisit); repeatCustomer = true; } } } initialize();
The first two statements retrieve both hard (lastVisit) and soft (nextPrevVisit) cookie values. After calling the function that sets any necessary date adjustment, the script starts examining the values of the cookies to find out where the visitor stands upon coming to the page. The first test is whether the person has ever been to the page before. You do this by checking whether a hard cookie value (which would have been set in a previous visit) exists. If no such cookie value exists, the current visit time is written to the hard cookie and repeatCustomer is set to false. These actions prepare the visitor’s cookie value for the next visit. Should a user already be a repeat customer, you have to evaluate whether this visit is the user’s first visit since launching the browser. You do that by checking for a value in the soft cookie. If that value doesn’t exist, it means the user is here for the first time ‘‘today.’’ You then grab the hard cookie and drop it into the soft cookie before writing today’s visit to the hard cookie.
For repeat customers who have been here earlier in this session, you update the lastVisit global variable from the cookie value. The variable value will have been destroyed when the user left the page just a little while ago, whereas the soft cookie remains intact, enabling you to update the variable value now. Outside of the function definition, the script automatically executes the initialize() function by that single statement. This function runs every time the page loads.
The date comparison Every interlaced script in the body of the document calls the newAsOf() function to find out if the author’s time stamp is after the user’s last visit to the page. This function is where the time zone differences between visitor and author must be neutralized so that a valid comparison can be made: function newAsOf(authorDate) { authorDate = new Date(authorDate); var itemUpdated = authorDate.getTime(); return ((itemUpdated > lastVisit) && repeatCustomer) ? "" : ""; }
As you saw earlier, calls to this function require one parameter: a specially formatted date string that includes time zone information. The first task in the function is to re-cast the author’s date string to a date object. You reuse the variable name (authorDate) because its meaning is quite clear. The date object created here is stored internally in the browser in GMT time, relative to the time zone data supplied in the parameter. To assist in the comparison against the lastVisit time (stored in milliseconds), the getTime() method converts authorDate to GMT milliseconds. The last statement of the function is a conditional expression that returns the tag definition for the ‘‘NEW 4U’’ image only if the author’s time stamp is later than the soft cookie value, and the visitor has been here before. Otherwise, the function returns an empty string. Any document.write() method that calls this function and executes via this branch writes an empty string — nothing — to the page.
Further Thoughts You can, perhaps, go overboard with the way that you use this technique on a web site. Like most features in JavaScript, I recommend using it in moderation and confining the flags to high-traffic areas that repeat visitors frequent. For example, it makes a great callout for new entries in a blog, since blog updates are often time sensitive. One hazard is that you can exceed the number of cookies a browser allows if you have too many page-specific listings. Although some modern browsers (Safari and Chrome) don’t have a limit, others do. The fewest number
BC713
Part VIII: Applications
of cookies allowed on some browsers (IE6 and legacy) is 20. Other browsers allow a varying number of cookies. You can share the same cookie among documents in related frames. Copy all the functions from the head section of the script in this chapter into a head section of a framesetting document. Then, modify the call to the newAsOf() function by pointing it to the parent: document.write(parent.newAsOf("18 Nov 2006 17:40:00 PDT"));
That way, one cookie can take care of all documents that you display in that frameset.
BC714
Application: Decision Helper
T
he list of key concepts for this chapter’s application looks like the grand finale to a fireworks show. As JavaScript implementations go, this application is, in some respects, over the top, yet not out of the question for presenting a practical interactive application on a web site without any server programming.
IN THIS CHAPTER Multiple frames Multiple-document applications Multiple windows
The Application
Persistent storage (cookies)
I wanted to implement a classic application often called a decision support system. My experience with the math involved here goes back to the first days of Microsoft Excel. Rather than design a program that had limited appeal (covering only one possible decision tree), I set out to make a completely user-customizable decision helper. All the user has to do is enter values into fields on a series of screens; the program performs the calculations to let the user know how the various choices rank against each other. Although I won’t be delving too deeply into the math inside this application, you will find it helpful to understand how a user approaches this program and what the results look like. The basic scenario is a user who is trying to evaluate how well a selection of choices measure up to his or her expectations of performance. User input includes:
The name of the decision
The names of up to five alternatives (people, products, ideas, and so on)
The factors or features of concern to the user
The importance of each of the factors to the user
A user ranking of the performance of every alternative in each factor
BC715
Scripted image maps Scripted charts
Part VIII: Applications
What makes this kind of application useful is that it forces the user to rate and weigh a number of often-conflicting factors. By assigning hard numbers to these elements, the computer calculates a decision based on the rates and weights of the various factors. Results come in the form of floating-point numbers between 0 and 100. As an extra touch, I’ve added a graphical charting component to the results display.
The Design With so much user input necessary for this application, conveying the illusion of simplicity is important. Rather than lump all text objects onto a single scrolling page, I decided to break them into five pages, each consisting of its own HTML document. As an added benefit, I could embed information from early screens into the HTML of later screens, which would help to establish a more intuitive user interface. This ‘‘good idea’’ presented one opportunity and one rather large challenge. The opportunity was to turn the interface for this application into something resembling a multimedia application using multiple frames. The largest frame would contain the forms the user fills out, as well as the results page. Another frame would contain a navigation panel with arrows for moving forward and backward through the sequence of screens, plus buttons for going back to a home page and getting information about the program. I also thought a good idea would be to add a frame that provides instructions or suggestions for the users at each step. And so, the three-frame window was born, as shown in the first entry screen in Figure 58-1. Using a navigation bar also enables me to demonstrate how to script a client-side image map — not an obvious task with JavaScript. Also notice in the figure how there is a helpful text message appearing just above the navigation bar. This ‘‘tooltip’’-style message appears thanks to the use of several handy onmouseover and onmouseout event handlers, which you learn about a bit later in the chapter. On the challenge side of this design, finding a way to maintain data globally, as the user navigates from screen to screen, was necessary. Every time one of the entry pages unloads, none of its text fields is available to a script. My first attack at this problem was to store the data as global variable data (mostly arrays) in the parent document that creates the frames. Because JavaScript enables you to reference any parent document’s object, function, or variable (by preceding the reference with parent), I thought this task would be a snap. But a hazard exists in that a reload of the frameset could erase the current state of those variables. My next hope was to use the document.cookie as the storage bin for the data. A major problem I faced was that this program needs to store a total of 41 individual data points, yet no more than 20 uniquely-named cookies can be allotted to a given domain. (While some modern browsers don’t have a limit, other modern browsers and legacy browsers allow between 20 and 50 cookies.) But the cookie proved to be the primary solution for this application. (See the ‘‘Further Thoughts’’ section at the end of the chapter about a non-cookie version on the
BC716
Chapter 58: Application: Decision Helper
CD-ROM.) For some of the data points (which are related in an array-like manner), I fashioned my own data structures so that one named cookie could contain up to five related data points. That reduced my cookie demands to 17. FIGURE 58-1
The Decision Helper window consists of three frames.
Note Testing the sample application obviously requires that cookies be enabled in your browser. Be aware that if you are testing with Google Chrome, your code will not work unless the files are coming from an HTTP server. Chrome intentionally disables cookies on file:/// documents. See Chapter 29, ‘‘The Document and Body Objects,’’ for a discussion of cookies.
The Files Before I get into the code, let me explain the file structure of this application. Table 58-1 gives a rundown of the files used in the Decision Helper.
BC717
Part VIII: Applications
TABLE 58-1
Files Comprising the Decision Helper Application File
Description
index.html
Framesetting parent document
dhNav.html
Navigation bar document for the upper-left frame that contains some scripting
dhNav.gif
Image displayed in dhNav.html
dh1.html
First Decision Helper entry page
dh2.html
Second Decision Helper entry page
dh3.html
Third Decision Helper entry page
dh4.html
Fourth Decision Helper entry page
dh5.html
Results page
chart.gif
Tiny image file used to create bar charts in dh5.html
dhHelp.html
Sample data and instructions document for the lower frame
dhAbout.html
Document that loads into a second window
A great deal of interdependence exists among these files. As you see later, assigning the names to some of these files was strategic for the implementation of the image map.
The Code With so many JavaScript-enhanced HTML documents in this application, you can expect a great deal of code. To best grasp what’s going on here, first try to understand the structure and interplay of the documents, especially the way the entry pages rely on functions defined in the parent document. My goal in describing this structure is not to teach you how to implement this application, but rather how to apply the lessons I learned while building this application to the more complex ideas that may be aching to get out of your head and into JavaScript.
index.html Taking a top-down journey through the JavaScript and HTML of the Decision Helper, start at the document that loads the frames. Unlike a typical framesetting document, however, this one contains JavaScript code in its head section — code that many other documents rely on: Decision Helper
BC718
Chapter 58: Application: Decision Helper
An important consideration to remember is that in a multiple-frame environment, the title of the parent window’s document is the name that appears in the window’s title bar, no matter how many other documents are open inside its subframes. The first items of the script control a global variable, currTitle, which is set by a number of the subsidiary files as the user navigates through the application. This variable ultimately helps the navigation bar buttons do their jobs correctly. Because this application relies on the document.cookie so heavily, the cookie management functions (slightly modified versions of Bill Dortch’s cookie functions — see Chapter 29) are located in the parent document so they load only once. I simplified the cookie-writing function because this application uses default settings for pathname and expiration. With no expiration date, the cookies don’t survive the current browser session, which is perfect for this application: // global variable settings of current dh document number var currTitle = ""; function setTitleVar(titleVal) { currTitle = "" + titleVal; } function getCookieVal(offset) { var endstr = document.cookie.indexOf (";", offset); if (("" + endstr) == "" || endstr == -1) { endstr = document.cookie.length; } return unescape(document.cookie.substring(offset, endstr)); } function getCookie(name) { var arg = name + "="; var alen = arg.length; var clen = document.cookie.length; var i = 0; while (i < clen) { var j = i + alen; if (document.cookie.substring(i, j) == arg) { return getCookieVal (j); } i = document.cookie.indexOf(" ", i) + 1; if (i == 0) { break; } } return null; }
BC719
Part VIII: Applications
function setCookie(name, value) { document.cookie = name + "=" + escape (value) + ";"; }
When this application loads (or a user elects to start a new decision), it’s important to grab the cookies you need and initialize them to the basic values that the entry screens will use to fill fields when the user first visits them. All statements inside the initializeCookies() function call the setCookie() function, defined in the preceding listing. The parameters are the name of each cookie and the initial value — mostly empty strings. Before going on, study the cookie labeling structure carefully. I refer to it often in discussions of other documents in this application: function initializeCookies() { setCookie("decName",""); setCookie("alt0",""); setCookie("alt1",""); setCookie("alt2",""); setCookie("alt3",""); setCookie("alt4",""); setCookie("factor0",""); setCookie("factor1",""); setCookie("factor2",""); setCookie("factor3",""); setCookie("factor4",""); setCookie("import","0"); setCookie("perf0",""); setCookie("perf1",""); setCookie("perf2",""); setCookie("perf3",""); setCookie("perf4",""); }
The following functions should look familiar to you. They were borrowed either wholesale or with minor modification from the data-entry validation section of the Social Security number database lookup in Chapter 53, ‘‘Application: A Lookup Table.’’ I’m glad I wrote these as generic functions, making them easy to incorporate into this script. Because many of the entry fields on two screens must be integers between 1 and 100, I brought the data validation functions to the parent document rather than duplicating them in each of the subdocuments: // JavaScript sees numbers with leading zeros // as octal values, so strip zeros function stripZeros(inputStr) { var result = inputStr; while (result.substring(0,1) == "0") { result = result.substring(1,result.length); } return result; }
BC720
Chapter 58: Application: Decision Helper
// general purpose function to see if a suspected numeric // input is a positive integer function isNumber(inputStr) { for (var i = 0; i < inputStr.length; i++) { var oneChar = inputStr.substring(i, i + 1); if (oneChar < "0" || oneChar > "9") { return false; } } return true; } // function to determine if value is in acceptable // range for this application function inRange(inputStr) { num = parseInt(inputStr); if (num < 1 || num > 100) { return false; } return true; }
To control the individual data entry validation functions in the master controller, I again was able to borrow heavily from the application in Chapter 53: // Master value validator routine function isValid(inputStr) { if (inputStr != "" ) { inputStr = stripZeros(inputStr); if (!isNumber(inputStr)) { alert("Please make sure entries are numbers only."); return false; } else { if (!inRange(inputStr)) { var msg="Entries must be numbers between 1 and 100."; msg += " Try another value."; alert(msg); return false; } } } return true; }
BC721
Part VIII: Applications
Each of the documents containing entry forms retrieves and stores information in the cookie. Because all cookie functions are located in the parent document, it simplifies coding in the subordinate documents to have functions in the parent document acting as interfaces to the primary cookie functions. For each category of data stored as cookies, the parent document has a pair of functions for getting and setting data. The calling statements pass only the data to be stored when saving information; the interface functions handle the rest, such as storing or retrieving the cookie with the correct name. In the following pair of functions, the decision name (from the first entry document) is passed back and forth between the cookie and the calling statements. Not only must the script store the data, but if the user returns to that screen later for any reason, the entry field must retrieve the previously entered data: function setDecisionName(str) { setCookie("decName",str); } function getDecisionName() { return getCookie("decName"); }
The balance of the storage and retrieval pairs does the same thing for their specific cookies. Some cookies are named according to index values (factor1, factor2, and so on), so their cookie-accessing functions require parameters for determining which of the cookies to access, based on the request from the calling statement. Many of the cookie retrieval functions are called to fill in the data in tables of later screens during the user’s trip down the decision path: function setAlternative(i,str) { setCookie("alt" + i,str); } function getAlternative(i) { return getCookie("alt" + i); } function setFactor(i,str) { setCookie("factor" + i,str); } function getFactor(i) { return getCookie("factor" + i); } function setImportance(str) { setCookie("import",str); } function getImportance(i) {
BC722
Chapter 58: Application: Decision Helper
return getCookie("import"); } function setPerformance(i,str) { setCookie("perf" + i,str); } function getPerformance(i) { return getCookie("perf" + i); }
One sequence of code that runs when the parent document loads is the one that looks to see if a cookie structure is set up. If no such structure is set up (the retrieval of a designated cookie returns a null value), the script initializes all cookies via the function described earlier: if (getDecisionName() == null) { initializeCookies(); }
The last part of the script is a function that’s called if the user wants to plug in a canned example by clicking a button in the file (dh1.html) that is the first data entry screen in the upper-right frame: // plug in sample code if user wants function doSample(form) { setCookie("decName","Buying a FAX machine"); setCookie("alt0","Fax-O-Matic 1000"); setCookie("alt1","InkyFax 300"); setCookie("alt2","LazyFax LX"); setCookie("alt3","Loose Cannon M-200"); setCookie("alt4",""); setCookie("factor0","Cost"); setCookie("factor1","Size"); setCookie("factor2","Paper Handling"); setCookie("factor3","Warranty"); setCookie("factor4",""); setCookie("import","80.40.60.70.."); setCookie("perf0","60.80.40.20.."); setCookie("perf1","80.60.50.30.."); setCookie("perf2","80.55.75.70.."); setCookie("perf3","70.70.80.70.."); setCookie("perf4",""); parent.entryForms.document.forms[0].decName.value = "Buying a FAX machine"; }
The balance of the parent document source code defines the frameset for the browser window. It establishes some hard-wired pixel sizes for the navigation panel. This ensures that the entire
BC723
Part VIII: Applications
.gif file is visible whenever the frameset loads, without a ton of unwanted white space if the browser window is large: It’s really cool... ...but only if your browser handles frames Back
It’s worth pointing out that some older browsers do not respond to changes in framesetting size attributes through a simple reload of the page. Modern browsers appear to have resolved this problem; however if you seem to be making changes, but reloading the frameset doesn’t make the changes appear, try reopening the browser window or — as a last resort — restarting the browser.
dhNav.html Because of its crucial role in controlling the activity around this program, look into the navigation bar’s document next. To accomplish the look and feel of a multimedia program, this document was designed as a client-side image map that has four regions scripted, corresponding to the locations of the four buttons (see Figure 58-1). The trick to the tooltip mechanism is the showing and hiding of a div element that contains the text to be displayed. This element has its own style class, tipStyle, which is responsible for establishing the white rectangular text box with a thin black border. Navigation Bar body { background-color:white; } .tipStyle { position:absolute;
One function is connected to each button. The first function is linked to the graphical Home button. For the listing here, I just present an alert dialog box replicating the action of navigating back to a real web site’s home page: function goHome() { alert("Navigate back to home page on a real site."); }
Each of the arrow navigation buttons brings the user to the next or previous entry screen in the sequence. To facilitate this without building tables of document titles and names, you call upon the currTitle global variable in the parent document. This value contains an integer in the range between 1 and 5, corresponding to the main content documents dh1.html, dh2.html, and so on. As long as the offset number is no higher than the next-to-last document in the sequence, the goNext() function increments the index value by one and concatenates a new location for the frame. At the same time, the script advances the help document (in the bottom frame) to the anchor corresponding to the chosen entry screen by setting the location.hash property of that frame. Similar action navigates to the previous screen of the sequence through the goPrev() function. This time, the index value is decremented by one, and an alert warns the user if the current page is already the first in the sequence: function goNext() { var currOffset = parseInt(parent.currTitle); if (currOffset 1)
Clicking the Info button displays a smaller window containing typical About-box data for the program (see Figure 58-2): function goInfo() { var newWindow = window.open("dhAbout.html","","height=250,width=380"); }
FIGURE 58-2
The About Decision Helper screen appears in a separate window.
The last pair of functions, showTip() and hideTip(), are used to show and hide, respectively, the tooltip text that appears when the mouse hovers over one of the navigation buttons. The showTip() function accepts the text to be shown in the tooltip as its only argument: function showTip(tipMsg) { var obj = document.getElementById("tip"); obj.style.visibility = "visible";
BC726
Chapter 58: Application: Decision Helper
while(obj.firstChild) obj.removeChild(obj.firstChild); obj.appendChild(document.createTextNode(tipMsg)); } function hideTip() { var obj = document.getElementById("tip"); obj.style.visibility = "hidden"; }
The body of the navigation document contains the part that enables you to script a client-side image map. Mouse click events weren’t available to area elements in legacy browsers and are not available in all modern browsers, so to inject a bit of backward compatibility, mouse action is converted to script action by assigning a javascript: pseudo-URL to the HREF attribute for each area element. Instead of pointing to an entirely new URL (as area elements usually work), the attributes point to the JavaScript functions defined in the head portion of this document. After a user clicks the rectangle specified by an tag, the browser invokes the function instead.
Revealed here is the other component of the tooltip feature you learned about earlier (revisit the upper-left corner of Figure 58-1). Each area element within the image map has two mouse event handlers that take care of showing and hiding the tooltip text, based upon the mouse hovering above the navigation area.
BC727
Part VIII: Applications
Note The property assignment event handling technique used throughout this example is a deliberate simplification to make the code more readable. It is generally better to use the more modern approach of binding events using the addEventListener() (NN6+/Moz/W3C) or attachEvent() (IE5+) methods. A modern cross-browser event handling technique is explained in detail in Chapter 32.
dh1.html Of the five documents that display in the main frame, dh1.html is the simplest (refer to Figure 58-1). It contains a single entry field in which the user is invited to enter the name for the decision. The function loadDecisionName summons one of the cookie interface functions in the parent window. A test is located here in case there is a problem with initializing the cookies. Rather than show null in the field, the conditional expression substitutes an empty string: DH1 body { font-family:Arial, Helvetica, serif; } h2 { font-size:18px; } h4 { font-size:14px; } .form { text-align:center; } // initialize when the page has loaded addEvent(window, "load", initialize); function initialize() { parent.setTitleVar(1); loadDecisionName(); document.forms[0].decName.focus(); } function loadDecisionName()
BC728
Chapter 58: Application: Decision Helper
{ var result = parent.getDecisionName(); result = (result == null) ? "" : result; document.forms[0].decName.value = result; }
After the document loads, it performs three tasks (in the onload event handler bound to the window object in the first part of the script). The first task is to set the global variable in the parent to let it know which number of the five main documents is currently loaded. Next, the script must fill the field with the decision name stored in the cookie. This task is important because users will want to come back to this screen to review what they entered previously. A third statement sets the focus of the entire browser window to the one text object. This task is especially important in a multi-frame environment, such as this design. After a user clicks on the navigation panel, that frame has the focus. To begin typing into the field, the user has to tab (repeatedly) or click the text box to give it focus for typing. By setting the focus in the script when the document loads, you save the user time and aggravation: The Decision Helper Step 1 of 5: Type the name of the decision you’re making. Then click the "Next" arrow.
In the text field itself, an onchange event handler saves the value of the field in the parent’s cookie for the decision name. No special Save button or other instruction is necessary here because any navigation that the user does via the navigation bar automatically causes the text field to lose focus and triggers the onchange event handler: Decision Name:
The balance of this file has a (commented out) textarea object that you can use for debugging cookie data. This is followed by a button that, when clicked, calls a function in the parent (index.html). This allows the user to choose to plug in sample data:
// un-comment next lines to show textarea that // monitors cookie values // document.write("" // + parent.document.cookie // + "");
BC729
Part VIII: Applications
dh2.html For the second data entry screen (shown in Figure 58-3), five fields invite the user to enter descriptions of the alternatives under consideration. As with the decision name screen, the scripting for this page must both retrieve and save data displayed or entered in the fields. FIGURE 58-3
The second data entry screen.
In one function, the script retrieves the alternative cookies (five total) and stuffs them into their respective text fields (as long as their values are not null). This function uses a for loop to cycle through all five items — a common process throughout this application. Whenever a cookie is one of a set of five, the parent function has been written (in the following example) to
BC730
Chapter 58: Application: Decision Helper
store or extract a single cookie, based on the index value. Text objects holding like data (defined in the following listing) are all assigned the same name, so that JavaScript lets you treat them as array objects — greatly simplifying the placement of values into those fields inside a for loop: DH2 body { font-family:Arial, Helvetica, serif; } h2 { font-size:18px; } h4 { font-size:14px; } .form { text-align:center; } // initialize when the page has loaded addEvent(window, "load", initialize); function initialize() { parent.setTitleVar(2); loadAlternatives(); document.forms[0].alternative[0].focus(); } function loadAlternatives() { for (var i = 0; i < 5; i++) { var result = parent.getAlternative(i); result = (result == null) ? "" : result; document.forms[0].alternative[i].value = result; } }
After the document loads, the onload event (bound to the window object at the beginning of the script) does three things: the document number is sent to the parent’s global variable, its
BC731
Part VIII: Applications
fields are filled by the function defined in the head, and the first field is handed the focus to assist the user in entering data the first time. Any change that a user makes to a field is stored in the corresponding cookie. Each onchange event handler passes its indexed value (relative to all like-named fields), plus the value entered by the user, as parameters to the parent’s cookie-saving function: The Decision Helper Step 2 of 5: Type up to five alternatives you are considering. Alternative 1: Alternative 2: Alternative 3: Alternative 4: Alternative 5:
dh3.html With the third screen, the complexity increases a bit. Two factors contribute to this increase in difficulty. One is that the limitation on the number of cookies available for a single domain forces you to combine into one cookie the data that might normally be distributed among five cookies. Second, with the number of text objects on the page (see Figure 58-4), it becomes more efficient (from the standpoint of tedious HTML writing) to let JavaScript deploy the fields. The fact that two sets of five related fields exist facilitates using for loops to lay out and populate them.
BC732
Chapter 58: Application: Decision Helper
FIGURE 58-4
Screen for entering decision factors and their weights.
The onload event is bound to the window object. The only tasks that the onload event handler needs to do are to update the parent global variable about the document number, and to set the focus on the first entry field of the form. The getdh3Factor() function is reminiscent of head functions in previous entry screens. This function retrieves a single factor cookie from the set of five cookies: DH3 body { font-family:Arial, Helvetica, serif; }
BC733
Part VIII: Applications
h2 { font-size:18px; } h4 { font-size:14px; } // initialize when the page has loaded addEvent(window, "load", initialize); function initialize() { parent.setTitleVar(3); document.forms[0].factor[0].focus(); } function getdh3Factor(i) { var result = parent.getFactor(i); if (result == null) { return ""; } return result; }
Values for the five possible weight entries are stored together in a single cookie. To make this work, I had to determine a data structure for the five ‘‘fields’’ of a single cookie ‘‘record.’’ Because all entries are integers, any nonnumeric character would work. I arbitrarily selected the period: function setdh3Importance() { var oneRecord = ""; for (var i = 0; i < 5; i++) { var dataPoint = document.forms[0].importance[i].value; if (!parent.isValid(dataPoint)) { document.forms[0].importance[i].focus(); document.forms[0].importance[i].select(); return; } oneRecord += dataPoint + "."; } parent.setImportance(oneRecord); return; }
BC734
Chapter 58: Application: Decision Helper
The purpose of the setdh3Importance() function is to assemble all five values from the five Weight entry fields (named importance ) into a period-delimited record that is ultimately sent to the cookie for safekeeping. Another of the many for loops in this application cycles through each of the fields, checking for validity and then appending the value with its trailing period to the variable (oneRecord) that holds the accumulated data. As soon as the loop finishes, the entire record is sent to the parent function for storage. Although the function shows two return statements, the calling statement does not truly expect any values to be returned. Instead, I use the return statement inside the for loop as a way to break out of the for loop without any further execution whenever an invalid entry is found. Just prior to that, the script sets the focus and select to the field containing the invalid entry. JavaScript, however, is sensitive to the fact that a function with a return statement in one possible outcome doesn’t have a return statement for other outcomes (an error message to this effect appears in some browsers if you try the function without balanced returns). By putting a return statement at the end of the function, all other possibilities are covered to the browser’s satisfaction. The inverse of storing the weight entries is retrieving them. Because the parent. getImportance() function returns the entire period-delimited record, this function must break apart the pieces and distribute them into their corresponding Weight fields. A combination of string methods determines the offset of the period and how far the data extraction should go into the complete record. Before the for loop repeats each time, it is shortened by one ‘‘field’s’’ data. In other words, as the for loop executes, the copy of the cookie data returned to this function is pared down one entry at a time, as each entry is stuffed into its text object for display: function getdh3Importance() { var oneRecord = parent.getImportance(); if (oneRecord != null) { for (var i = 0; i < 5; i++) { var recLen = oneRecord.length; var offset = oneRecord.indexOf("."); var dataPoint = (offset >= 0 ) ? oneRecord.substring(0,offset) : ""; document.forms[0].importance[i].value = dataPoint; oneRecord = oneRecord.substring(offset+1,recLen); } } }
Assembling the HTML for the form and its 10 data entry fields needs only a few lines of JavaScript code. Performed inside a for loop, the script assembles each line of the form, which consists of a label for the Factor (and its number), the factor input field, the importance input
BC735
Part VIII: Applications
field, and the label for the Weight (and its number). A document.write() method writes each line to the document: The Decision Helper Step 3 of 5: List the factors that will influence your decision, and assign a weight (from 1 to 100) to signify the importance of each factor in your decision.
var output = ""; for (i = 0; i < 5; i++) { output += "Factor " + (i+1) + "-->"; output += ""; output += ""; document.write(output); } demo(); // runs as document loads document.write(hisDog + " belongs to " + aBoy + ".");
5. The application uses three parallel arrays and is structured very much like the solution to question 1. Learn to reuse code whenever you can. var planets = new Array(4); planets[0] = "Mercury"; planets[1] = "Venus"; planets[2] = "Earth"; planets[3] = "Mars"; var distance = new Array(4); distance[0] = "36 million miles"; distance[1] = "67 million miles"; distance[2] = "93 million miles"; distance[3] = "141 million miles"; var diameter = new Array(4); diameter[0] = "3100 miles";
BC809
Part IX: Appendixes
diameter[1] = "7700 miles"; diameter[2] = "7920 miles"; diameter[3] = "4200 miles"; function getPlanetData() { var selectedPlanet = document.getElementById("entry").value; for ( var i = 0; i < planets.length; i++) { if (planets[i] == selectedPlanet) { break; } } var msg = planets[i] + " is " + distance[i]; msg += " from the Sun and "; msg += diameter[i] + " in diameter."; document.getElementById("output").value = msg; } Enter the name of a planet:
Chapter 10 Answers 1. a. Close, but no cigar. Array references are always plural: window.document.forms[0] b. Not valid: self refers to a window and entryForm must refer to a form. Where’s the document? It should be self.document.entryForm.entryField.value. c. Valid. This reference points to the name property of the third form in the document. d. Not valid. The uppercase ‘‘D’’ in the method name is incorrect. e. Valid, assuming that newWindow is a variable holding a reference to a subwindow. 2. window.alert("Welcome to my Web page."); 3. document.write("Welcome to my Web page."); 4. A script in the body portion invokes a function that returns the text entered in a prompt() dialog box. function askName() { var name = prompt("What is your name, please?","");
BC810
Appendix D: Answers to Tutorial Exercises
return name; } document.write("Welcome to my web page, " + askName() + ".");
5. The URL can be derived from the href property of the location object. function showLocation() { alert("This page is at: " + location.href); } Blah, blah, blah.
Chapter 11 Answers 1. For Listing 11-2, pass the text input element object because that’s the only object involved in the entire transaction. Text Object value Property function upperMe(field) { field.value = field.value.toUpperCase(); }
For Listing 11-3, the button invokes a function that communicates with a different element in the form. Pass the form object.
BC811
Part IX: Appendixes
Checkbox Inspector function inspectBox(form) { if (form.checkThis.checked) { alert("The box is checked."); } else { alert("The box is not checked at the moment."); } } Check here
For Listing 11-4, again the button invokes a function that looks at other elements in the form. Pass the form object. Extracting Highlighted Radio Button function fullName(form) { for (var i = 0; i < form.stooges.length; i++) { if (form.stooges[i].checked) { break; } } alert("You chose " + form.stooges[i].value + "."); }
Select your favorite Stooge: Moe Larry Curly
For Listing 11-5, all action is triggered by and confined to the select object. Pass only that object to the function.
BC812
Appendix D: Answers to Tutorial Exercises
Select Navigation function goThere(list) { location = list.options[list.selectedIndex].value; } Choose a place to go: Home Page Shop Our Store Shipping Policies Search the Web
2. Here are the most likely ways to reference the text box object: document.getElementById("email") document.forms[0].elements[0] document.forms["subscription"].elements[0] document.subscription.elements[0] document.forms[0].elements["email"] document.forms["subscription"].elements["email"] document.subscription.elements["email"] document.forms[0].email document.forms["subscription"].email document.subscription.email
The reference document.all.email (or any reference starting with document.all) works only in Internet Explorer and other browsers that emulate IE, but not in Mozilla or Safari. Other valid references may include the W3C DOM getElementsByTagName() method. Since the question indicates that there is only one form on the page, the text box is the first input element in the page, indicating that document.body.getElementsByTagName("input")[0] would be valid for this page. 3. The this keyword refers to the text input object, so that this.value refers to the value property of that object. function showText(txt) {
5. The select object invokes a function that does the job. Color Changer function setColor(list) { var newColor = list.options[list.selectedIndex].value; document.bgColor = newColor; } Select a background color: Stop Caution Go
Chapter 12 Answers 1. Use string.indexOf() to see if the field contains the ‘‘@’’ symbol. E-mail @ Validator function checkAddress(form) { if (form.email.value.indexOf("@") == -1) { alert("Check the e-mail address for accuracy.");
BC814
Appendix D: Answers to Tutorial Exercises
return false; } return true; } Enter your e-mail address:
2. Remember that the substring goes up to, but does not include, the index of the second parameter. Spaces count as characters. myString.substring(0,3) myString.substring(11,17) myString.substring(5,12)
// result = "Int" // result = "plorer" // result = "net Exp"
3. The indexOf() function returns a -1 if the character is not found. The substring() function will extract a substring starting at the indexed position +1. If there are no spaces in stringA, firstSpace will be = -1. Adding a 1 to that yields 0. Strings start at position 0, so excerpt will return the entire stringA. 4. The missing for loop is in boldface. You could also use the increment operator on the count variable (++count) to add 1 to it for each letter ‘‘e.’’ function countE(form) { var count = 0; var inputString = form.mainstring.value.toLowerCase(); for (var i = 0; i < inputString.length; i++) { if (inputString.charAt(i) == "e") { count += 1; } } var msg = "The string has " + count; msg += " instances of the letter e."; alert(msg); }
5. The formula for the random throw of one die is in the chapter. Roll the Dice function roll(form) { form.die1.value = Math.floor(Math.random() * 6) + 1
6. If you used the Math.round() method in your calculations, that is fine given your current exposure to the Math object. Another method, Math.ceil(), may be more valuable because it rounds up any fractional value. Waiting for Santa function daysToXMAS() { var oneDay = 1000 * 60 * 60 * 24; var today = new Date(); var XMAS = new Date("December 25, 2001"); var diff = XMAS.getTime() - today.getTime(); return Math.ceil(diff/oneDay); } document.write(daysToXMAS() + " days until Christmas.");
3. All three frames are siblings, so references include the parent. parent.mechanics.location.href = "french201M.html"; parent.description.location.href = "french201D.html";
4. A script in one of the documents is attempting to reference the selector object in one of the frames but the document has not fully loaded, causing the object to not yet be in the browser’s object model. Rearrange the script so that it fires in response to the onload event handler of the framesetting document. 5. From the subwindow, the opener property refers back to the frame containing the window.open() method. To extend the reference to the frame’s parent, the reference includes both pieces: opener.parent.location.
Chapter 14 Answers 1. As the document loads, the tag creates a document image object. A memory image object is created with the new Image() constructor. Both objects have the same properties, and assigning a URL to the src property of a memory object loads the image into the browser’s image cache. 2. var janeImg = new Image(100,120); janeImg.src = "jane.jpg";
3. document.images["people"].src = janeImg.src; 4. Surround tags with link () tags, and use the link’s onclick, onmouseover, and onmouseout event handlers. Set the image’s border attribute to zero if you don’t want the link highlight to appear around the image. 5. The following works in all W3C DOM-compatible browsers. The order of the first two statements may be swapped without affecting the script. var newElem = document.createElement("a"); var newText = document.createTextNode("Next Page"); newElem.href = "page4.html"; newElem.appendChild(newText); document.getElementById("forwardLink").appendChild(newElem);
BC817
JavaScript and DOM Internet Resources
A
s an online technology, JavaScript has plenty of support online for scripters. Items recommended here were taken as a snapshot of Internet offerings in early 2010. But beware! Sites tend to change. URLs can change too. Be prepared to hunt around for these items if the information provided here is updated or moved around by the time you read this.
Support and Updates for This Book The most up-to-date list of errata and other notes of interest pertaining to this edition of JavaScript Bible can be found at the book’s web site, located at: http://www.wiley.com/WileyCDA/WileyTitle/productCd0470526912.html
FAQs One situation that arises with a popular and accessible technology, such as JavaScript and DHTML authoring, is that the same questions get asked over and over, as newcomers arrive on the scene daily. Rather than invoke the ire of newsgroup users, look through existing FAQ files to see if your concern has already been raised and answered. Here are some of the best JavaScript FAQ sites: http://javascript.faqts.com http://javascripter.net/faq/index.htm
BC818
Appendix E: JavaScript and DOM Internet Resources
For less-frequently asked questions — but previously asked and answered in a public form — use the Google Groups search, described later in this appendix under Newsgroups.
Online Documentation Locations of web sites that dispense official documentation for one browser or another are extremely fluid. Therefore, the following information contains links only to top-level areas of appropriate web sites, along with tips on what to look for after you are at the site. Microsoft has condensed its developer documentation into a massive site called MSDN (Microsoft Developer Network). The place to begin is: http://msdn.microsoft.com/library/
This page is the portal to many technologies, but the one most applicable to JavaScript and client-side scripting is one labeled ‘‘Library.’’ Within the MSDN Library, you can then click ‘‘Web Development’’ to access information related to JavaScript and other Web development technologies. Inside the Web Development area of the library you’ll find a section named ‘‘Scripting.’’ Here you’ll find plenty of documentation and technical articles for Microsoft scripting technologies, including JScript (Microsoft’s flavor of JavaScript). For Mozilla-based browser technologies, start at: http://www.mozilla.org/docs/web-developer/
Finally, you can read the industry standards for HTML, CSS, and ECMAScript technologies online. Be aware that these documents are primarily intended for developers of tools that we use — browsers, WYSIWYG editors, and so forth — to direct them on how their products should respond to tags, style sheets, scripts, and so on. Reading these documents has frequently been cited as a cure for insomnia. That said, however, you can still glean a lot of useful information about scripting, HTML code, and CSS code from them. http://www.ecma-international.org/publications/standards/Ecma-262.htm http://www.w3.org/TR/html401/ http://www.w3.org/TR/html5/ http://www.w3.org/TR/xhtml1/ http://www.w3.org/TR/xhtml2/ http://www.w3.org/standards/techs/css http://www.w3.org/DOM/ http://www.w3.org/TR/xml/ http://www.w3.org/TR/
Please note that just because a particular item is described in an industry standard doesn’t mean that it is implemented in any or all browsers. In the real world, we must develop for the way the technologies are actually implemented in browsers.
BC819
Part IX: Appendixes
World Wide Web The number of web sites devoted to JavaScript tips and tricks is mind-boggling. Many sites come and go in the middle of the night, leaving no trace of their former existence. If you are looking for more example code for applications not covered in this book, perhaps the best place to begin your journey is through the traditional search engines. Narrowing your search through careful keyword choice is vital. In addition to the Mozilla and (heavily Windows-oriented) Microsoft developer web sites (plus numerous online articles of mine listed at http://www.dannyg.com/pubs/index.html), a few other venerable sites are: http://www.javascript.com/ http://www.w3schools.com/js/ http://www.webreference.com/js/ http://en.wikipedia.org/wiki/Javascript https://wiki.mozilla.org/JavaScript http://javascript.internet.com/ http://www.d.umn.edu/itss/support/Training/Online/webdesign/javascript.html http://www2.webkit.org/perf/sunspider-0.9/sunspider.html
Feeds and Blogs The current way to read news and articles about JavaScript (or any subject for that matter) is via RSS feeds, Atom feeds, and blogs. Typically, these feeds are read in a dedicated RSS feed reader program, email client, or browser. Google provides a free reader, called Google Reader. The following links can be added as subscriptions to any of the feed readers: http://www.alistapart.com/site/rss http://z.about.com/6/g/javascript/b/rss2.xml?r=9F http://z.about.com/6/o/m/javascript_t2.xml?r=9F http://accessify.com/rss/accessify_rss.xml http://feeds.feedburner.com/deanedwards/weblog http://groups.google.com/group/firefoxpow/feed/rss_v2_0_msgs.xml http://feeds2.feedburner.com/blogspot/Egta http://blogs.msdn.com/ie/rss.xml http://www.javascript.com/jss.rdf http://www.webreference.com/js/tips/channels/last1512.rdf http://labs.opera.com/rss.dml http://www.feedzilla.com/rss/programming/javascript http://feeds.feedburner.com/scriptaculous http://feeds.feedburner.com/vitaminmasterfeed http://webkit.org/blog/feed/ http://meyerweb.com/eric/thoughts/category/tech/rss2/full http://www.d.umn.edu/itss/support/Training/Online/webdesign/webdesign.xml http://www.webreference.com/webreference.rdf
BC820
Appendix E: JavaScript and DOM Internet Resources
Some blog sites allow you to post questions and get answers, although usually you can only comment on an article or respond to other comments. Hosts for RSS feeds and blogs are still evolving and competing for mind-share. Bloggers will frequently change hosts, so if you can’t find a blogger at a link above, just do a search for the title or author to find the new host. Sometimes a blogger will leave a terminal message.
Newsgroups and Forums The time-honored places to get quick answers to your pressing questions are online newsgroups and forums. To use newsgroups, you will need a newsgroup reader. Most browsers have dropped support for newsfeeds. Some email clients (such as Thunderbird) know how to do this. Newsgroups don’t charge fees, but some of the NNTP servers do. You can use your search engine to look for a free NNTP reader. Here are the top JavaScript-related newsgroups: On most news servers: comp.lang.javascript
On news://msnews.microsoft.com: microsoft.public.scripting.jscript microsoft.public.inetsdk.programming.scripting.jscript microsoft.public.inetsdk.programming.dhtml_editing microsoft.public.inetexplorer.scripting microsoft.public.dotnet.languages.jscript
On news://news.mozilla.org: mozilla.dev.tech.javascript mozilla.dev.tech.js-engine mozilla.dev.tech.js-engine.rhino mozilla.dev.apps.js-debugger
Forums today, on the other hand, are primarily browser-based. Here are some of the top JavaScript-related forums: http://en.wikipedia.org/wiki/Internet_forum http://www.ajaxtalk.com/ http://groups.google.com/group/firefoxpow/ http://tech.groups.yahoo.com/group/ydn-javascript/ http://old.nabble.com/forum/Search.jtp?query=javascript&page=0&fsearch=y
Before you post a question to a newsgroup or forum, read about FAQs discussed earlier in this chapter and also use the extremely valuable newsgroup archive search facility of Google Groups. Visit the Google Groups search page at: http://groups.google.com/
BC821
Part IX: Appendixes
Enter the keyword or phrase into the top text box, but then also try to narrow your search by limiting the newsgroup(s) to search. For example, if you have a question about weird behavior you are experiencing with the borderCollapse style property in IE, enter borderCollapse into the search field, and then try narrowing the search to a specific newsgroup (forum) such as comp.lang.javascript. If you post a question to a newsgroup or forum, you will most likely get a quick and intelligent response if you also provide either some sample code that’s giving you a problem, or a link to a temporary file on your server that others can check out. Visualizing a problem you’ve spent days on is very hard for others. Be as specific as possible, including the browser(s) versions(s) and operating system(s) on which the code must run and the nature of the problem.
Final Thoughts These sites are by no means the only worthwhile JavaScript and DHTML destinations on the Web. Sometimes having too many sources is as terrifying as having not enough. The links and newsgroups described in this appendix should take you a long way.
BC822
Wiley Publishing, Inc. End-User License Agreement READ THIS. You should carefully read these terms and conditions before opening the software packet(s) included with this book ‘‘Book’’. This is a license agreement ‘‘Agreement’’ between you and Wiley Publishing, Inc. ‘‘WPI’’. By opening the accompanying software packet(s), you acknowledge that you have read and accept the following terms and conditions. If you do not agree and do not want to be bound by such terms and conditions, promptly return the Book and the unopened software packet(s) to the place you obtained them for a full refund. 1. License Grant. WPI grants to you (either an individual or entity) a nonexclusive license to use one copy of the enclosed software program(s) (collectively, the ‘‘Software,’’ solely for your own personal or business purposes on a single computer (whether a standard computer or a workstation component of a multi-user network). The Software is in use on a computer when it is loaded into temporary memory (RAM) or installed into permanent memory (hard disk, CD-ROM, or other storage device). WPI reserves all rights not expressly granted herein. 2. Ownership. WPI is the owner of all right, title, and interest, including copyright, in and to the compilation of the Software recorded on the physical packet included with this Book ‘‘Software Media’’. Copyright to the individual programs recorded on the Software Media is owned by the author or other authorized copyright owner of each program. Ownership of the Software and all proprietary rights relating thereto remain with WPI and its licensers. 3. Restrictions On Use and Transfer. (a) You may only (i) make one copy of the Software for backup or archival purposes, or (ii) transfer the Software to a single hard disk, provided that you keep the original for backup or archival purposes. You may not (i) rent or lease the Software, (ii) copy or reproduce the Software through a LAN or other network system or through any computer subscriber system or bulletin-board system, or (iii) modify, adapt, or create derivative works based on the Software. (b) You may not reverse engineer, decompile, or disassemble the Software. You may transfer the Software and user documentation on a permanent basis, provided that the transferee agrees to accept the terms and conditions of this Agreement and you retain no copies. If the Software is an update or has been updated, any transfer must include the most recent update and all prior versions. 4. Restrictions on Use of Individual Programs. You must follow the individual requirements and restrictions detailed for each individual program in the About the CD-ROM appendix of this Book or on the Software Media. These limitations are also contained in the individual license agreements recorded on the Software Media. These limitations may include a requirement that after using the program for a specified period of time, the user must pay a registration fee or discontinue use. By opening the Software packet(s), you will be agreeing to abide by the licenses and restrictions for these individual programs that are detailed in the About the CD-ROM appendix and/or on the Software Media. None of the material on this Software Media or listed in this Book may ever be redistributed, in original or modified form, for commercial purposes. 5. Limited Warranty. (a) WPI warrants that the Software and Software Media are free from defects in materials and workmanship under normal use for a period of sixty (60) days from the date of purchase
of this Book. If WPI receives notification within the warranty period of defects in materials or workmanship, WPI will replace the defective Software Media. (b) WPI AND THE AUTHOR(S) OF THE BOOK DISCLAIM ALL OTHER WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE SOFTWARE, THE PROGRAMS, THE SOURCE CODE CONTAINED THEREIN, AND/OR THE TECHNIQUES DESCRIBED IN THIS BOOK. WPI DOES NOT WARRANT THAT THE FUNCTIONS CONTAINED IN THE SOFTWARE WILL MEET YOUR REQUIREMENTS OR THAT THE OPERATION OF THE SOFTWARE WILL BE ERROR FREE. (c) This limited warranty gives you specific legal rights, and you may have other rights that vary from jurisdiction to jurisdiction. 6. Remedies. (a) WPI’s entire liability and your exclusive remedy for defects in materials and workmanship shall be limited to replacement of the Software Media, which may be returned to WPI with a copy of your receipt at the following address: Software Media Fulfillment Department, Attn.: JavaScript Bible, 7e, Wiley Publishing, Inc., 10475 Crosspoint Blvd., Indianapolis, IN 46256, or call 1-800-762-2974. Please allow four to six weeks for delivery. This Limited Warranty is void if failure of the Software Media has resulted from accident, abuse, or misapplication. Any replacement Software Media will be warranted for the remainder of the original warranty period or thirty (30) days, whichever is longer. (b) In no event shall WPI or the author be liable for any damages whatsoever (including without limitation damages for loss of business profits, business interruption, loss of business information, or any other pecuniary loss) arising from the use of or inability to use the Book or the Software, even if WPI has been advised of the possibility of such damages. (c) Because some jurisdictions do not allow the exclusion or limitation of liability for consequential or incidental damages, the above limitation or exclusion may not apply to you. 7. U.S. Government Restricted Rights. Use, duplication, or disclosure of the Software for or on behalf of the United States of America, its agencies and/or instrumentalities ‘‘U.S. Government’’ is subject to restrictions as stated in paragraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause of DFARS 252.227-7013, or subparagraphs (c) (1) and (2) of the Commercial Computer Software - Restricted Rights clause at FAR 52.227-19, and in similar clauses in the NASA FAR supplement, as applicable. 8. General. This Agreement constitutes the entire understanding of the parties and revokes and supersedes all prior agreements, oral or written, between them and may not be modified or amended except in a writing signed by both parties hereto that specifically refers to this Agreement. This Agreement shall take precedence over any other documents that may be in conflict herewith. If any one or more provisions contained in this Agreement are held by any court or tribunal to be invalid, illegal, or otherwise unenforceable, each and every other provision shall remain in full force and effect.
