Not signed in (Sign In)
SkillShare - A place to discuss Web Standards and Web Design topics
Categories
Vanilla 1.1.9 is a product of Lussumo. More Information: Documentation, Community Support.
- Friends
-
I'm currently developing a new design for a site, but got some stupid issues with IE :/
http://www.andrzejk.info/caractere/carDetails_VwLupo.php
The right column with dom tabs -> In FF it all looks fine. But when I open it in IE the container div of the tabs gets a 1px margin from the left.
Tried everything. Still comes up.. :/
Maybe anyone has an idea? :/ -
- CommentAuthorseth.aldridge
- CommentTimeJul 27th 2006
This may be something that could work:
*html .tab {
margin-left:1px;
}
I'm not sure it that will work or not, but I've seen people use the "*html" before to fix IE issues.
Hope it works. -
The *html hack is ok for addressing IE issues, as long as you're not fussed about validating your css.
I work for a company that insits we validate all stylesheets so we can't use *html. -
I work for a company that insits we validate all stylesheets so we can't use *html.
* html isn't invalid code (at least, not according to the w3c validator), just illogical. -
- CommentAuthorseth.aldridge
- CommentTimeJul 27th 2006
you could also create a seperate style sheet for IE and have two but that can be a pain in the ... -
Nifkin
I should have checked before I made that statement, shouldn't i. :(
It came from another developer . That will teach me for not actually checking myself.
I don't use it, but thank-you for pointing out i was incorrect. -
One may also use the 'child selector' hack, such as: html>body.
This hack hides from IE 5/6 and lower, but has the advantage of being read by compliant browsers and the recent IE 7 (...which is still beta) and it validates. Just be sure there is no whitespace before or after the child selector.
It is a sort of reverse hack in that you set the initial declarations for non-compliance, then set the compliant declarations under the child selector. As subsequent versions of IE become more compliant, one does not have to return to the code to eliminate the hack as it is valid.
This, and many other nifty codings, can be found in Andy Budd's book 'CSS Mastery', which is one of my many 'bibles'. -
I don't use it, but thank-you for pointing out i was incorrect.
I wasn't trying to be mean about it. :)
Once you said something about it I did start to wonder and had to go hit the validator to find out. Long story short, be careful which web-nerd's information you trust. -
One place I always start with when I look at incompatibilities between browsers is the box model, because it's the root of alot of inconsistencies. If you never use the padding and width declarations on the same element, you'll have a very good start towards ie/firefox compatibility. I've run into a couple of occaisons where it was more trouble to do it that way, but most of the time you've got a parent element and series of children. If you apply your layout to the parent, and your spacing to the child, it will turn out good for you.
-
I wasn't trying to be mean about it. :)
I know you weren't ;->
1 to 10 of 10