In this article I will show you how browsers respond to Active Client Pages. In particular, we will focus on the question of whether different browsers respond to all the features of Active Client Pages as they should. Recall that browsers do not implement all the features in the HTML, JavaScript and DOM specifications. So we need to ask this question.
How Browsers Respond to Active Client Pages (Page 1 of 4 )
In case you do not know what Active Client Pages mean, they are defined as the production of HTML pages at the client computer by the browser using web technology. The abbreviation for Active Client Pages is ACP. I have written three series about this new method of web development. The titles of the series are: Active Client Pages: Script Approach, Active Client Pages: Ajax Approach and Active Client Pages: Chrys's Approach. I strongly advise you to read those series before you read this one.
In this short series I explain how browsers respond to ACP. The browsers I use are Internet Explorer 6, Mozilla Firefox 2, Netscape 8, Opera 9 and Safari 3.
I will give you an ACP example. We shall use this example to see to what extent each browser responds to ACP. At the end of the series, I will give you recommendations on how to work with the browsers, depending on the extents to which they respond to ACP.
There are three approaches to ACP with one of them having two phases. I start by giving you the summaries of the three different approaches.
You need basic knowledge in HTML, JavaScript and Perl to understand this short (five-part) series.
HTML 
Wrapping Up Chrys`s Approach to Active Client Pages
