Re: Keeping HTML Simple & Format negotiation between Browser & Server

Marc Andreessen (marca@ncsa.uiuc.edu)
Fri, 28 May 93 20:21:18 -0500

Pei Y. Wei writes:
> However, one could think of lots of other applications where it would
> be easier and more appropriate to use area-overlay-buttons. Just look at
> the numerous HyperCard stackwares that use ``invisible fields'' to
> implement highly neat effects. This approach, however hard-coded but
> no more than ``HREF='' is hard-coded, has the benefits of no necessary
> dependence on a server.

I agree.

> An example of invisible/see-thru buttons overlaying an image -- face.gif
> is visible, and has two invisible area oriented anchors pointing to
> eyes.gif and mouth.gif respectively. Probably unnecessary, but WIDTH &
> HEIGHT could be specified to handle scaling. Also, perhaps <FIGA> should
> simply be <A>. :
>
> <FIGURE SRC="http://sesame-st.org/whatis/face.gif" TYPE="image/gif"
> WIDTH=100 HEIGHT=100>
> <FIGA HREF="http://sesame-st.org/whatis/eyes.gif" TYPE="image/gif"
> x0=20 y0=10 x1=80 y1=30>
> <FIGA HREF="http://sesame-st.org/whatis/mouth.gif" TYPE="image/gif"
> x0=40 y0=70 x1=60 y1=80>
> <FIGCAP>Spy a face</FIGCAP>
> </FIGURE>

Looks good to me. Two comments: my gut feeling is that coordinates
should be in pixel space, and that if the browser scales the image it
should readjust any transmitted coordinates to match when the user
actually selects something. And, I think it should be possible
to specify more than one rectangle per "FIGA" (e.g...

<FIGA HREF="http://sesame-st.org/whatis/mouth.gif" TYPE="image/gif"
COORDS="40-60,70-80;90-100,120-130">

...or something similar).

Cheers,
Marc