- From: Ian Jacobs <ij@w3.org>
- Date: Thu, 08 Mar 2001 10:27:18 -0500
- To: Charles McCathieNevile <charles@w3.org>
- CC: w3c-wai-ua@w3.org
Charles McCathieNevile wrote: > > I don't see that there is a problem using the method Aaron suggested. It > would enable a user agent to seperately queue the changes to a document that > gets updated on the fly, which seems like a good thing since they could be > offered to the user who had asked for a page to stay still, as a seperate > item. It might be helpful to have this available, and I can't see that it > breaks anything we need. > > So I would propose to instead add this as a technique. Would you object to the editorial change? _ Ian > Reference document 24 Feb 2001 draft [1]. > > 1) Checkpoints 3.5/3.5 > > 3.5 Allow configuration so that client-side content refreshes > (i.e., those initiated by the user agent, not the server) > do not change content except on explicit user request. > > Aaron suggested that this might be interpreted as meaning > "compare and see if the refresh changed the content or not". > > Proposed change: > > Allow configuration so that the user agent does not > perform client-side content refreshes (i.e., those > initiated by the user agent, not the server) > except on explicit user request. > > I propose the same type of change to checkpoint 3.6: > > [snip] -- Ian Jacobs (jacobs@w3.org) http://www.w3.org/People/Jacobs Tel: +1 831 457-2842 Cell: +1 917 450-8783
Received on Thursday, 8 March 2001 10:27:20 UTC