Generally, I like to add a style rule for regular TRs and then a class for
either TR.odd or TR.even (whichever you'd like).
tr{
background-color: #eee;
}
tr.odd{
background-color: #ccc;
}
This way, you only need to print out the 'class="odd"' on the odd rows,
which makes your pages smaller
Ah, that method will work, Mark - but I would argue against using the
javascript pseudo-protocol for a production site.
The reason has to do with usability. Often times, embedding the javascript
pseudo protocol in a link will prevent users from being able to right click
and open the link in a new
Russ:
Though this is more of a javascript/html dom question, I'll answer anyway.
You must return false in the 'onclick' method of the link you're using to
fire this javascript event. This will prevent the browser from following the
href attribute.
So your markup should look like:
Truth
In Savin
This article is a handy reference for running multiple versions of IE:
http://www.positioniseverything.net/articles/multiIE.html
I've recently installed the package with installers (by *Yousif Al Saif) and
have had no problems with it.
Good luck,
Andy
*
___
The syntax you've shown (input.text) is a class selector, not an attribute
selector.
The rule:
input.text{...}
would match the following markup:
Yes - this is generally the way to use Conditional Comments to filter CSS
rules to IE.
Here's a snippet of code to illustrate the point:
...
...
So generally, you'd add all the normal rules in the first style sheet,
theme.css, then override them specifically for IE in the IE-only style
sheet,
The best practice method for conditionally filtering CSS rules to IE is a
proprietary microsoft technology called Conditional Comments.
http://msdn.microsoft.com/workshop/author/dhtml/overview/ccomment_ovw.asp
Andy
__
css-discuss
OK, got this working.
There are multiple problems here - so I'd really suggest you start by
validating your HTML.
The problem you're seeing in Safari has to do with the nested DIV inside of
your div#theImages container. The problem is you're defining a height on
this container that is less than
You would probably want to toggle style.display = 'none' and style.display =
'' or block/inline accordingly.
Changing visibility will cause these 'hidden' contains to still occupy their
space in the flow of the document.
Andy
On 12/6/06, Mark J. Reed <[EMAIL PROTECTED]> wrote:
>
> On 12/6/06, Ma
If you're seeing a problem in certain versions of IE, please be sure to
include the build number of the IE version you're experiencing the problem.
To see the build number, in IE's toolbar - hit help, about internet
explorer.
I see no problem in my build (6.0.2900 SP2)
Andy*
*
For example, go to
Jeralyn:
Replace your H1 and H1 A selector rules with the following:
#header h1 {
position: relative;
top:43px;
margin:0;
width: 260px; height: 60px;
}
#header h1 a {
position:absolute;
top:0;left:0;
display: block;
background: url('images/sc_logo.jpg') no-repeat right top;
height:100%; width:100
The problem you are seeing is a result of not properly containing the image
floated to the left (.imgbedside)
You need to either add markup to clear the element (with for example) or implement a no-markup clearing
solution.
References
- http://www.complexspiral.com/publications/containing-float
Mark:
This is quite an interesting case. Aparrently, applying "hasLayout" to the
#header_right element is causing a rendering bug in IE that is adding extra
space between the #header_left and #header_right elements. See the reference
below for a description of "hasLayout" and its effects in IE.
S
13 matches
Mail list logo
