how to use an iframe as a link (make the whole iframe clickable)

On 2008-05-21, dorayme <doraymeRidThis (AT) optusnet (DOT) com.au> wrote:

In article <slrng382on.710.spamspam (AT) bowser (DOT) marioworld>,
Ben C <spamspam (AT) spam (DOT) eggs> wrote:

On 2008-05-21, dorayme <doraymeRidThis (AT) optusnet (DOT) com.au> wrote:
In article <slrng37ief.5h7.spamspam (AT) bowser (DOT) marioworld>,
Ben C <spamspam (AT) spam (DOT) eggs> wrote:
[...]
Which viewport?


How many viewports are there per browser? I have not completed my deep
investigations into root theory as yet - in which viewports take up
starring roles - but I have a rough working hypothesis that there is
just one per browser that I was seeing this morning. <g

Usually one per browser, but each frame or iframe starts a new viewport
(and things that are like iframes-- you can OBJECT for example).

Ah! Of course, you are right. Where frames are concerned, there are at
least* as many viewports as there are frames + 1. Safari and FF were
differing in the viewports they were attending to in relation to borders
and things...

Not exactly. None of the browsers were trying to put the border around
the viewport inside the iframe (that would have been a useful but
incorrect place to put it).

Firefox was putting it around the main viewport because it didn't like a
table cell as a containing block for positioned descendents. So it
skipped past it and went up to the next candidate, which happened to be
the root containing block, which is the (main) viewport.

The border was supposed to coincide with the edges of the anonymous
table cell which should have had the same size and position as the
outside of the iframe (i.e. outside its scroll bars).