Re: Anchored rendering of TABLE head/foot

Murray Maloney (murray@sco.COM)
Thu, 15 Dec 94 10:35:47 EST

> >There seemed to be wide appreciation for (even consensus?) for my
> >suggestion at the IETF that online rendering of tables should, in the
> >best browsers, anchor the table heading and footing while scrolling table
> >rows. I wanted to raise it here again so it is documented and others may
> >help refine the idea.

Well, I wasn't at the recent IETF meeting, but I sure like the idea.

> I, for one, would find that behaviour distracting at least, and
> probably quite bothersome. If it ever is implemented, it should be
> possible to disable this.

While I don't agree with the first points, I do agree that this
behaviour should be user-controllable.
> In addition, given the huge number of possible window heights/widths,
> and browser technologies, I would say that this will be difficult to
> implement well (to say the least). Also, this is a presentational
> issue, and as much as possible, presentation should be kept out of
> HTML. It *might* be reasonable to propose this to people defining
> stylesheet mechanisms (ie. I need a way to make text "sticky").

I don't think that the suggestion had much to do with HTML per se.
It seems to be a suggestion about rendering. If browser developers
can do it, then why not? Certainly this will affect how style
sheets might be written -- or not -- but I don't think that the
style sheet design should preclude any browser implementation
from adding such an obviously useful feature.

> I would not like to see this part of any standard until an
> implementation has proven it's value.

I don't see how it could be part of any standard -- unless someone
follows through on periodic suggestions to develop a standard
for browsers. The value is immediately obvious to the author
of the suggestion and seemingly to others, including me, as well.
-- And if there ever were a browser standard, I assert that it
could only define the minimum set of behaviours and characteristics
that a browser must support to be conforming, and beyond that
only suggestions as to what a browser might do. Beyond that,
browser developers must be free to differentiate their products.


Murray C. Maloney Internet:
Technical Publications Writer/Architect Uucp: ...uunet!sco!murray
SCO Canada, Inc. My Phone: (416) 960-4031
130 Bloor Street West, 10th Floor Fax: (416) 922-2704
Toronto, Ontario, Canada M5S 1N5 SCO Phone: (416) 922-1937
Disclaimer: I'm speaking for myself. 'T ain't nobody else to blame but me.
Sponsor member of Davenport Group (
Member of IETF HTML Working Group (
Member of SGML Open Internet and WWW Technical Committee