Kenny Graham napisał(a):
I cant seem to find anything
Div is generic block.. not generic block of text.
Agreed, I worded it badly. It can contain non-text, but doesn't have to.
In most cases it groups block elements as for grouping inline there are
other dedicated elements as span which
On Sat, Dec 16, 2006 at 09:48:58PM -0800, Paul Novitski wrote:
I believe the reason it's an ie-only hack is that standards-compliant
browers won't apply the selector .ie-only.foo to any element because
no element has both classes ie-only and foo
div class=foo ie-only
This element has both
David Dorward wrote:
On Sat, Dec 16, 2006 at 09:48:58PM -0800, Paul Novitski wrote:
I believe the reason it's an ie-only hack is that standards-compliant
browers won't apply the selector .ie-only.foo to any element because
no element has both classes ie-only and foo
div class=foo ie-only
Wow! Never seen this list so busy. You dthink it was Xmas or something. :)
Good to hear warnings. If it is not too much trouble, could you expound
on that statement a little?
Not too much. Simply that the learning curve is often quite steep and that
proprietary templating engines don't
Paul Noone wrote:
Wow! Never seen this list so busy. You dthink it was Xmas or something. :)
Hehe, yeah, it is nice to see some action. :)
Not too much. Simply that the learning curve is often quite steep and
that proprietary templating engines don't help this.
Ah, I see. Thanks for
At 12/17/2006 01:17 PM, Thierry Koblentz wrote:
David Dorward wrote:
On Sat, Dec 16, 2006 at 09:48:58PM -0800, Paul Novitski wrote:
I believe the reason it's an ie-only hack is that standards-compliant
browers won't apply the selector .ie-only.foo to any element because
no element has both
Thierry Koblentz wrote:
Erwin Heiser wrote:
!--[if gt IE 6]
link rel=stylesheet href=ie7.css media=screen ![endif]--
!--[if lte IE 6] link rel=stylesheet href=ie6.css
media=screen ![endif]--
Why not going with !--[if IE 7] rather than !--[if gt IE 6]
That way you don't have to
On 12/18/06, Geoff Pack [EMAIL PROTECTED] wrote:
This is precisely the problem with conditional comments: You don't know
in advance if any given bug will be fixed in IE8, so you can't know
which conditional you will need.
If you get it wrong, and the bug fix is still needed in IE8 (or is not
