RE: [Q] META "Refresh" deprecated ?

[ I could be wasting my time offering this URL, but then again, it
  just might help: http://www.deja.com/=dnc/getdoc.xp?AN=564975310 ]

On Tue, 22 Feb 2000, Piers Williams wrote:

> > (For instance, Opera allows the Refresh idiocy to be disabled.)

> Opera also allows you to disable Javascript, CSS and a variety of
> other features, but I don't see you baying for them to be dropped.

It would help if you followed the thread a bit more carefully, and
refrained from changing your argument just to get a rejoinder in. 

(If there's anything I would argue that should be dropped, it would be
the HTTP-EQUIV attribute.  Contending with Refresh specifically is a
separate issue; that I'm able to do something about it seems to have
met with your disapproval.)

> You've made my point for me - at the end of the day all feature
> implimentation is in the hands of the user, either directly (via
> settings on browser) or indirectly (by using a different browser).

If that was your point, suggesting the use of the back button didn't
go very far towards making it.  But if you'd like to claim my point as
yours, you're welcome:)

> So there's no problem implimenting features that _might_ in some
> circumstances have a potential accessabilty problem, as the user
> can just not enable them [etc]

I think you've missed the basic point about this "feature".  Read
Jonny Axelsson's and Patrice Calve's comments.  It's a question of the
*user* being in control of what he browses.  Saying that such and such
a "demographic" can figure whatnot out is like saying that there is a
demographic to whom it's okay to sell cars where they have to figure
out how to get the brakes working.


Arjun

Received on Tuesday, 22 February 2000 10:10:46 UTC