Heather Stern writes:
> It looks fine in lynx,
Hey, thanks for testing this, and the reference to the Lynx-View tester.
I noticed one problem - the Add Message button should have text but
it doesn't. It is generated with the following code:
if ($gifsOK) {
print "
<INPUT TYPE=\"image\" NAME=\"add\"
SRC=\"$hniconsURL/add.gif\"
BORDER=0 ALT=\"Add Message\" WIDTH=80 HEIGHT=24>";
}
else {
print "
<INPUT TYPE=\"submit\" NAME=\"add\"
VALUE=\"Add Message\"\">";
}
So there is either ALT text for an image button, or just the VALUE
text if gifs have not been requested. Is this a bug in the Lynx-View
converter?
> I think a text-only version would be neat,
If you mean that if a user wants to turn off images, they can't do
it very well with Netscape because of the no-image icons, yeah, this
is a problem. Maybe part of the problem is that the test for gifsOK
is:
$gifsOK = $ENV{'HTTP_ACCEPT'} =~ m,(image/gif)|(\*/\*),;
So the */* case, which many browsers will include by default, will
still make HyperNews think that gifs are OK.
Another part of the problem is that we were not even using the gifsOK
test in several places. Namely the relation icons and
new/newer/newest icons. I just added those tests.
> I'd prefer a less-frills option since nearly all the buttons are
> representing text. Certainly it sounds possible to zap all the
> text-buttons in source if you were installing your own. But I kinda like
> the prefix icons.
More selective per-user customization of the display will require a different
strategy. The customization really should be done on the client side,
and we plan to use JavaScript for that. I've already got a working test
of the concept at:
http://union.ncsa.uiuc.edu/hn/top.html
> I say submit an enhance request to your graphic browser company to let
> you not have a broken-image gizmo when image loading is off.
Sometimes you want to selectively display some images, but not all of
them though. So this alt-text instead of broken-image feature should
be an option.
dan
|