- From: Charles McCathieNevile <charlesn@sunrise.srl.rmit.edu.au>
- Date: Tue, 6 Oct 1998 06:04:04 +1000 (EST)
- To: w3c-wai-ua@w3.org
- cc: WAI PF group <w3c-wai-pf@w3.org>
This is true. What interests me is the question of whether, rather than an ID identifying the elements which are dynamic, we can put it on the script author (or the user agent to automagically extract the information from the script) to declare which elements they act on. (Is this a page authoring thing? or not yet?) This information combined with a knowledge of which properties (or classes of properties) are affected could be used to sort out which events are important for the user to be able to predict in advance, and which need not be worried about. Charles McCN On Mon, 5 Oct 1998, Jon Gunderson wrote: > We cannot think of Dynamic HTML as only operating on current HTML elements. > Dyanmic HTML needs to be though of as an application interface, that will > create and modify the HTML content on the screen based on user actions and > portential interactions with application servers. Only the simpliest uses > of DHTML can we think of it like a style sheet which only affects the > rendering of static HTML elements. > > Jon > >
Received on Monday, 5 October 1998 16:29:38 UTC