Re: Pixels 'n points (CSS1 browser test)

On Fri, 27 Jun 1997, Douglas Rand wrote:

> It really isn't that difficult,  I do it in our browser.  The code which
> builds the rendering structure checks for displayFLOAT for inline or
> block elements (my internal value for the property) and sticks the
> content in a floater container.  It's relatively simple and few lines of
> code,  et voila,  I can put a paragraph off to the left (and I did for
> my public demo at SGI's developer's forum).  Every capable browser
> already does such things for IMG and TABLE replaced elements.

I really don't get it. NS and MS have the programmers to break down a
(usually defective) document into a concise object tree, interpret snippets
of code in several different languages, have elements perform triple
sommersaults and morris dance all over your screen, yet when it comes to
applying a simple, clear standard for document presentation, that makes oh
so much sense to any programmer reading it, that practically tells you the
code you need to write in itself, they choke. (next thing you know the W3C
will be publishing C source with their specs - Whoops! They are! that's what
libwww is!). And as if that wasn't enough, the release notes for Netscape
Communicator 4.0 beta had several pages noting with concise detail, as
*BUGS* in the beta, all the deviations of the implementation from the CSS
spec. I was happy. At least the developers knew what they had to fix. But
out comes the release version, this huge list has vanished into oblivion and
it seems that Netscape is content with supporting only a small handful of
what itself voted as a W3C Recomendation. It boggles the mind.

And the Linux release has been shelved. No bother. I love Amaya.

Stephanos "Pippis" Piperoglou - http://users.hol.gr/~spip/index.html
  "Life's not fair, but the root password helps" - Simon the BOFH