>But there's no applet involved at all! Apparently all the
>"regular" button do is fetch an URL <g> Dropping to external
>editor (hitting F4 in Arachne), and replacing the buttons
>entirely with two simple links do the trick just fine:
>
>>> <input onclick="location='daftarkan.html'" type="button"
>> value="SETUJU">
>>> <input onclick="location='/'" type="button" value="TIDAK
>> SETUJU">
>
>can be replaced with:
>
> <a href="daftarkan.html">SETUJU</a>
> <a href="/">TIDAK SETUJU</a>
<snip>
>(Seriously, it could be either bad practice or an emerged common
>practice, as it's uncommon nowadays to browse the web without IE
>or at least NS ;-)
Yep, no JavaScript BUT an external process (calling those other pages).
>From what I understand the input type="button" indicates that the form
is not immediately sent for processing. Similarly, style tags such as
<em> and <strong> may convey more meaning to future browsers than <i>
and <b>, though as page content they look the same.
Jake, Wymondham, England
