Comparing Browser Response to Active Client Pages

The window at the fourth level in the example, displays the value of a variable residing in its opener (window). Recall that the opener actually has two documents. The variable happens to be in the second document in the opener. All you need is a reference to the opener to access this variable; you do not need a reference to the document.

The specification does not provide for this feature. So, in which document in the opener should this variable be? If you put the variable in the first document in the example, the call will not work. So I advise you to avoid calls from the window phase into the document phase and vice versa.

Caution with Forward Button

In ACP, when one document opens another document or when one window opens another window, data can be sent into the objects or elements of the opened page. When you use the Back button and then use the Forward button, you may not have the result you had before in the “Forward” page. After using the Back Button, if you want the required result in the “Forward” page, click the button that generated the Forward page, and not the Forward button.

Response of Browsers to the Document Phase of ACP

Here, I want to say how browsers respond when the session is made up of only the Document Phase of Chrys’s Approach to ACP. Internet Explorer 6 responds without any problem. Mozilla FireFox 2 responds without any problem. Netscape does not respond (does not give you any satisfactory results). Opera 9 gives you the expected results, but the Back and Forward buttons may not be enabled. Safari 3 doe not respond (does not give you any satisfactory results).