【正文】
教師評(píng)語(yǔ): 簽字: 年 月 日 英語(yǔ)原文: Document Object Model and Dynamic HTML The term Dynamic HTML,often abbreviated DHTML,refers to the technique of making Web pages dynamic by clientside scripting to manipulate the document content and pages can be made more lively,dynamic,or interactive by DHTML techniques. With DHTML,you can prescribe actions triggered by browser events to make the page more lively and actions may alter the content and appearance of any parts of the changes are fast and efficient because they are made by the browser without having to work with any ,the clientside scripting is written in JavaScript and basic techniques for making Web pages dynamic. Contrary to what the name may suggest,DHTML is not a markup language or a software is a technique to make Web pages dynamic through clientside the past,DHTML relied on browserand vendorspecific such pages work for all browsers requires much effort,testing,and unnecessarily long programs. Standardization efforts at W3C and elsewhere are making it possible to write standardbased DHTML that works for all pliant DHTML involves three aspects. —for crossbrowser scripting(Chapter9) Style Sheets(CSS)—for style and presentation control (Chapter6) Object Model(DOM)—for a uniform programming interface to access and manipulate the Web page as a document When these three aspects are bined,you get the ability to program changes in Web pages in reaction to useror browsergenerated ,you can make HTML pages more dynamic. Popular with Web developers,supported by all major browsers,and standardized,JavaScript provides the ability to program browser actions in response to have true crossplatform DHTML,we still need a uniform way for JavaScript to access and manipulate Web brings us to the DOM. What is DOM? The objective of unit and integration testing was to ensure that the code implemented the design properly。that is,that the programmers wrote code to do what the designers system testing,we have a very different objective:to ensure that the system does what the customer wants it to understand how to meet this objective,we first must understand where faults in the system e from. Recall that a software fault causes a failure only when acpanied by the right is,a fault may exist in the code,but if the code is never executed,or if the code is not executed long enough or in the appropriate configuration to cause a problem,we may never see the software testing cannot exercise every possible condition,we keep as our goal the discovery of faults,hoping that in the process we eliminate all faults that might lead to failures during actual system usage. Software faults can be inserted in a requirement,design,or code ponent,or in the documentation,at any point during development or illustrates the l