|
Posted by David Stone on June 7, 2006, 7:41 am
Please log in for more thread options
> On Tue, 6 Jun 2006, David Stone wrote:
>
> >
> > > Been trying to specify text alignment within specific
> > > columns in an html 4 strict page. According to the
> > > w3c specs,
> >
> > Never mind - after poking around the bugzilla pages, it appears
> > to be the case that NONE of the Mozilla-based browsers implement
> > COLGROUP and COL as per html 4.01 specs.
>
> Indeed. It was discussed on usenet only a few days ago, and is
> reportedly the oldest non-fixed bug in Moz-family browsers. Hmmm, ok,
> the discussion was in alt.html
>
> > This is one of the things where IE follows the standard, and
> /few\
> > Mozilla/Firefox/etc don't.
See my earlier post about applying a border to an object (in my
case, a Flash object). That doesn't work correctly in Moz-family
browsers either.
> OK so far...
>
> > So if you want entries in a column to be centred, and you want
> > that to be rendered in Mozilla-based browsers, you have to
> > apply the alignment to each cell individually _regardless_ of
> > whether you use html/css or just plain html.
>
> Not quite true. Since Mozilla-based browsers understand enough of
> CSS2, you can do this via a stylesheet, as was recently discussed
> http://groups.google.co.uk/group/alt.html/browse_thread/thread/e4b2a487ec8e02b
> 4
I looked at that. It's a bit more work than I care for with my particular
table instance. Curiously enough, the background colour of a COLGROUP
is one of the things that has supposedly been fixed, at least for the
current build. (Well, as near as I can understand what bugzilla seems
to be saying: https://bugzilla.mozilla.org/show_bug.cgi?id=4510)
I ended up adding a class declaration to each td that needed
special formatting. One of the articles in the cited thread suggests
selecting the entire column in dreamweaver and then setting the
desired attributes. When I tried this, dreamweaver inserted a styled
div into each td which, IMO, is even worse.
>
> > The next time someone tells me I should be standards-compliant,
> > I think I shall just blow a big fat raspberry at them :P
>
> Nevertheless, it doesn't pay off in the long-term to keep relying on
> browser bugs. In this case, you just need two sets of
> specification-conforming settings, and you'll pretty much cover the
> field.
I don't see how I'm "relying on browser bugs"? I found a standards-
compliant solution that works on all the browsers I tested. My biggest
beef is that I wasted over 3 hours trying to figure why FF wouldn't do
what it was supposedly meant to do...
| 
XML Sitemap