- From: Daniel Dardailler <danield@w3.org>
- Date: Tue, 06 Oct 1998 09:23:01 +0200
- To: Al Gilman <asgilman@access.digex.net>
- cc: w3c-wai-er-ig@w3.org
> Some page authors have static information inserted in their code > through initialization code which runs independently from any > input from the user. This may make their pages unusable with > scripts turned off even 'though the needed information is static > and not truly computed. You mean something like "onload" performs some document.write("<BODY>...") Yes this is really bad, and people are doing it. > The repair tool concept is a tool that would interpret scripts > and move static information into the HTML from the script. To me, a "repair" tool is one that is used by the page author (or maintainer), so what you describe is a possible repair tool, although I'm not sure it is feasible (i.e. how does it determine the "onload" leads to idempotent/unvariable bits) What's certainly feasible is a "proxy" tool, doing the "onload" (and all other non-interactive events) dynamically on behalf of the final user-agent.
Received on Tuesday, 6 October 1998 03:23:07 UTC