- From: Al Gilman <asgilman@iamdigex.net>
- Date: Wed, 30 Jun 1999 07:37:39 -0400
- To: www-talk@w3.org
At 09:23 AM 6/30/99 +1000, Grahame Grieve wrote: > >>It's not clear to me what is the right thing to do in this situation. > >It should be up to the author. It's OK for the author to define the default, but the mechanisms have to be in place for the user to exercise ultimate control. This becomes obvious when uncontrolled server-precipitated changes break the usability of web content for people with disabilities, but it is actually the right answer across the board to establish the right terms of engagement for a dialog with the user. We went through this with the reversal in the precedence (author vs. user) in the !important meta-markup in CSS2. The same goes for the flow of changes to objects in the user's domain as for the details of type size and color. Al > The spec is nearly right, except >that the author (=server) cannot influence the browsers behaviour. >There's a number of methods to prevent cache's and browser's >from caching your page, which is right, but none to prevent >this back behaviour. Koen's original proposal would've dealt >with that situation nicely. Oh well. > >Grahame >
Received on Wednesday, 30 June 1999 07:31:57 UTC