Comparing Browser Response to Active Client Pages
(Page 1 of 5 )
In this part of the series we look at the actual response of browsers to the technology of Active Client Pages. I shall also give you some recommendations for how to use Active Client Pages. This is the fifth and last part of the series.
I will start by giving you the response to the simple example from the following browsers: Internet Explorer 6, Mozilla Firefox 2, Netscape 8, Opera 9 and Safari 3. The test for each browser is simple. We open two descending chains and then click some buttons on the way. From the result of each browser, we shall look at recommendations that will guide you when you are doing web development with Active Client Pages.
Internet Explorer 6
Opening the Windows
The Descending Chain N0, N1, N20 and N30
I typed http://localhost/windowPhaseSimpleExample.htm in the address bar of Internet Explorer 6 and I reached the master page; there was no problem here.
I clicked the button labeled “Open page 1” and the page of node N1 opened. There is no problem here.
To get to node N20, you have to click the button labeled “Open Window 2_1.” I clicked this and I reached the page for node N20.
I then clicked the button labeled “Open Page 3 Win” and the page of node 30 opened. There was no problem here.
That is it for the chain with N0, N1, N20 and N30.
The Descending Chain N1, N21 N31, N32 and N4
I opened the pages for Node N0 and N1 as I described above. Of course there was no problem.
The page of node N1 has the button labeled “Open Window 2_2.” I clicked this button and the page for node N21 opened. There was no problem here.
The page of the node N21 has a button labeled “Open Page 3 Doc 0.” I clicked this button and the window of node N31 opened. According to the code, this window is supposed to have a tool bar; the tool bar was noticed. There was no problem here.
Now you can only go from node N31 to N32 since these two nodes represent documents of the same window. I clicked the button labeled “load Doc 1” and the document at node N32 opened in the same window as the previous document. The Back button was now enabled; this is what we expect, so that worked. At this point we have two documents in the same window. You can use the Back and Forward buttons to go to either of them. I tried this successfully.
The page for node N32 has a button labeled “Open a Page 4.” I clicked this button and the page for node N4 opened. This is the last page in the descending chain. There was no problem here.
Clicking the Buttons
I started with the master page and opened the nodes N0, N1, N20 and N30. I clicked the button labeled “Show the Value in Master Page” on the page of N30 and an alert box displayed “It worked!”. This was fine. This is what we expected. This displayed value is from a JavaScript variable in the master page (N0).
I started with the master page again and opened the nodes N0, N1, N21, N31 and N32. I clicked the button labeled “Show the Value in Page 2_2” on the page for N32; an alert box displayed “I am 2_2.” That is fine. That is what we expected. This displayed value is from a JavaScript variable in the page for node N21.
I carried on to open the page for node N4. I clicked the button labeled “Show the Value in Page 3_1.” An alert box appeared displaying “I am 3_1.” This displayed value is from a JavaScript variable in the page for node N31.
Apparently Internet Explorer 6 has responded without any errors. However, Internet Explorer 6 does not respond completely to ACP as I will explain below. Know that its response is very good; in fact, it's better than those of the other browsers.
Next: Mozilla Firefox 2 >>
More HTML Articles
More By Chrysanthus Forcha
