Christian web host - 386Part IIIDocument Objects ReferenceoffscreenBufferingValue:Boolean or string.Read/WriteCompatibility:WinIE4+, MacIE4+, NN-,
386Part IIIDocument Objects ReferenceoffscreenBufferingValue:Boolean or string.Read/WriteCompatibility:WinIE4+, MacIE4+, NN-, Moz-, Safari- IE4+ by default initially renders a page in a buffer (a chunk of memory) before it is blasted tothe video screen. You can control this behavior explicitly by modifying thewindow.offscreenBufferingproperty. The default value of the property is the string auto. You can also assign Boolean trueorfalseto the property to override IE s normal automatic handling of this behavior. ExampleIf you want to turn off buffering for an entire page, include the following statement at thebeginning of your script statements: window.offscreenBuffering = false; onerrorValue:Function. Read/WriteCompatibility:WinIE4+, MacIE4+, NN3+, Moz1+, Safari- The onerrorproperty is an exception to the rule of this book to not describe event handlersas properties within object reference sections. The reason is that the onerrorevent bringsalong some special properties that are useful to control by setting the event handler propertyin scripts. Recent browsers (IE5+, NN4+, and W3C) are designed to prevent script errors from beingintrusive if a user encounters a script error while loading or interacting with a page. Even so, even the subtle hints about problems (messages or icons in the status bar) can be confusingfor users who have no idea what JavaScript is. JavaScript lets you turn off the display ofscript error windows or messages as someone executes a script on your page. The questionis: When should you turn off these messages? Script errors generally mean that something is wrong with your script. The error may be theresult of a coding mistake or, conceivably, a bug in JavaScript (perhaps on a platform versionof the browser that you haven t been able to test). If such errors occur, often the script won tcontinue to do what you intended. Hiding the script error from yourself during developmentwould be foolhardy, because you d never know whether unseen errors are lurking in yourcode. It can be equally dangerous to turn off error dialog boxes for users who may believethat the page is operating normally, when, in fact, it s not. Some data values may not be calcu- lated or displayed correctly. That said, I can see some limited instances of when you may want to keep such dialog boxwindows from appearing. For example, if you know for a fact that a platform-specific bug tripsthe error message without harming the execution of the script, you may want to prevent thaterror alert dialog box from appearing in the files posted to your Web site. You should do thisonly after extensive testing to ensure that the script ultimately behaves correctly, even withthe bug or error. IE fires the onerrorevent 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 onerroreventdoesn t fire, and you cannot trap that error message. Moreover, if the user has the IE scriptdebugger installed, any code you use to prevent browser error messages from appearing willnot work. NotewindowObject.offscreenBuffering