Okay, for those of us who remember my question about styling columns here is
the solution I came up with (for my current project anyway). It takes advantage
of the fact that Firefox *does* allow for the background of columns to be
styled while still keeping everything very tight (notice that no
> It's possible, and pretty simple. You just use the solution from the
> wiki, where you style the COL and IE picks it up, and use adjacent
> siblings for standards-complient browsers.
This is what I'm trying to avoid, since I would rather not style for
individual browsers, which means it would be
On 11/10/05, CJ Larson <[EMAIL PROTECTED]> wrote:
> I have a feature table in which I have 5 total columns: ID, Name,
> Description, Cost, and Activated. On my main feature page, I wish to
> display the Name, Desc, and Cost fields in that order. On my "manage
> your features" page, I wish to disp
Thursday, November 10, 2005, 1:59:25 PM, Dan Kletter wrote:
> Drawback is colgroup is only supported by IE and limited to width,
> border, background and visibility styles.
Thanks to it's non-standard layout engine IE doesn't have these limitations
on styling via COL. Nor do CSS2 browsers styling
> Have you tried it?
> http://css-discuss.incutio.com/?page=StylingColumns (Combination
> method)
(Sorry you get this twice Steve; I sent it off list accidentally the
first time.)
I was referring to colgroup as specified in the original post, not
work-around methods (that consequently don't work
CJ Larson wrote:
"I think the problem posed is that *every* td has the same thing, the
same thing, the same thing, so why should a class have to specified 40
times (number pulled from a hat) to style this one type of td? Now, if
only one city td needed to be special, a class there would be differe
Drawback is colgroup is only supported by IE and limited to width,
border, background and visibility styles. (I know the original poster
was designing for IE, but still...)
I think Eric Meyer had the right idea. I wouldn't advise using
adjacent sibling selectors. It's not very efficient.
Ideally,
Thursday, November 10, 2005, 1:27:55 PM, CJ Larson wrote:
> Making a colgroup for this city *one* time and being done with it is the
> intuitive thing to do, but since it doesn't work... "problem".
Have you tried it?
http://css-discuss.incutio.com/?page=StylingColumns (Combination method)
> The extra classes have
> relevant names, so you shouldn't feel that they are obstructing your
quest
> for purity.
I think the problem posed is that *every* td has the same thing, the
same thing, the same thing, so why should a class have to specified 40
times (number pulled from a hat) to style
> Thanks, Eric. It was just so nice when I had stripped away a ton of code
> and had all these cells with no classes assigned or inline styling or
> anything (literally just: X, whereas the old version that
> somebody else coded looked like bgcolor="E1E4E4">X) and it worked, and worked
> beautiful
10 Nov 2005 09:46:38 -0500
Subject: Re: [css-d] Styling COL and COLGROUP
At 8:32 PM -0500 11/9/05, [EMAIL PROTECTED] wrote:
>So the only way to bold and center all the text in every cell of a
>particular column is to add those rules to every cell? (Sounds like bad
>coding to me
Wednesday, November 9, 2005, 10:01:21 PM, Philippe Wittenbergh wrote:
> .myclass {text-align: center}
> td:first-child+td+td {text-align: center} /* the 3rd column */
> ***But***, and here IE is buggy again, you *cannot* group those
> selector, else IE doesn't recognise the .myclass selector.
I
At 8:32 PM -0500 11/9/05, [EMAIL PROTECTED] wrote:
>So the only way to bold and center all the text in every cell of a
>particular column is to add those rules to every cell? (Sounds like bad
>coding to me.) Or to pretend that they are header cells when they
>aren't? (Sounds like bad coding to me.
On 11/9/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> I don't hardly ever use these tags but I found they came in handy in my
> current assignment. However, in IE (not my favorite browser but I have
> to admit it's doing what I want to in this instance) everything
> displayed the way I intuiti
On 10 Nov 2005, at 11:13 am, James Bennett wrote:
>
> I once read through a long and protracted Mozilla bug report on this
> which I'm currently unable to locate; IIRC the problem, conceptually,
> is that individual table cells are not actually children of the
> COLGROUP or COL; as a result, they
On 11/9/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> I don't hardly ever use these tags but I found they came in handy in my
> current assignment. However, in IE (not my favorite browser but I have
> to admit it's doing what I want to in this instance) everything
> displayed the way I intuiti
> > I don't hardly ever use these tags but I found they came in handy
in my
> > current assignment. However, in IE (not my favorite browser but I
have
> > to admit it's doing what I want to in this instance) everything
> > displayed the way I intuitively imagined it would after adding
style
> >
On 10 Nov 2005, at 9:21 am, [EMAIL PROTECTED] wrote:
> I don't hardly ever use these tags but I found they came in handy in my
> current assignment. However, in IE (not my favorite browser but I have
> to admit it's doing what I want to in this instance) everything
> displayed the way I intuitive
I don't hardly ever use these tags but I found they came in handy in my
current assignment. However, in IE (not my favorite browser but I have
to admit it's doing what I want to in this instance) everything
displayed the way I intuitively imagined it would after adding style
rules to these two
19 matches
Mail list logo
