Re: Pixels 'n points (CSS1 browser test)
> * Following their original web design, tables do not inherit styles
> from the surrounding text or style sheet.
> (quoted from the Navigator 4.0 release notes)
I think they're wrong on this. They should inherit based on the
document structure, and thus inherit in reasonable way. But note that
very few properties are really inherited in CSS, mostly fonts and
> both browsers-- different things for each browser, of course-- but I think
> *correct* support for float on all elements would be a huge step.
> Navigator at least supports float, but breaks when you start associating
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 have other complaints, like N4's lack of support for the anchor
pseudoclasses. I told a Netscape person (not to be named) about my
support for changing geometry on anchor activation and the person was
horrified, even though the spec. is *not* ambiguous over this.
I think some properties actually *are* problematic, for example
vertical-align applied to textual objects in paragraph flows really make
only modest sense. The definition of vertical-align also doesn't
correspond to common practice, started with Mosaic, of carrying the
top and bottom text limits for the line as the line is formatted from
left to right. Thus vertical-align can lead to circular dependencies,
which is not good, IMO.
Doug Rand email@example.com
Silicon Graphics/Silicon Desktop http://reality.sgi.com/drand
Disclaimer: These are my views, SGI's views are in 3D