Re: HTML 3.2 PR

Peter Flynn (
19 Jan 1997 22:18:24 +0000 (GMT)

Date: 19 Jan 1997 22:18:24 +0000 (GMT)
From: Peter Flynn <>
Subject: Re: HTML 3.2 PR
In-reply-to: <> (message from John
Message-id: <>

John Luke wrote:

   1. Have a date function to show the browser exactly what date and time =
   they are viewing the page

Nothing to do with HTML, though: this is a browser function matter.

   2. Provide a right justify capability without having to use a table

Already exists: <P ALIGN=RIGHT>...but many browsers don't obey it.

   3. Provide for pagination controls in output (where will page breaks =
   occur, of course this depends but the <P></P> pagagraph markers are a =
   good start).

This is an old chestnut: stylesheets have fixed this. There is nothing
meaningful that HTML can do here, as page size and font size are
beyond the control of the author.

It is not to the credit of browsers that their default typographic
output is disastrously bad, even splitting headings off from the para
that follows...

   4. Provide an easy method for assigning passwords to pages.

Already exists, btu it's a server function, not an HTML one.

   5. Incorporate the <MARQUEE></MARQUEE> tag

Already in HTML Pro.

   6. Create a parser for HTML and stop worrying about incorporating

Why bother, when SGML parsers already do the job perfectly?

   7. Allow users to substitute the bullet in <UL> by adding a =
   specification <UL img src=3D3D"bullet.jpg"> rather than having to use =
   the image command on every line.

Already in it. UL/OL have had DINGBAT and SRC since HTML3, but
as usual, most browsers ignore it.

   8. Allow music to play even after switching pages and put a button on =
   the browser to allow the user to control its playing or stopping.

I think you can already do this if the soundcontrol widget is
downloaded offpage. One of the problems with current browser
implementations of ActiveX sound controls is that they are tied to the
page -- deliberately. But this isn't anything to do with HTML: it's
specifically a browser problem.

   9. Provide an easy inclusion to log access locations and persons.

Do you mean access to your own server logs (that's a matter between
you and your ISP and/or computer center)? Or do you mean you want a
log of where _you_ have visited (taht's in your history file, but I
agree it would be better kept in a more accessible fashion). But I
don't see how HTML can do anything for this.

   10. Reinstate the <HTML Version =3D3D "3.2"> tag along with the doctype =
   for compatibility and identification of source.

They never left. I agree 100% people should use them, though.