Getting uniform layout in both IE7 & IE8 with form elements - html

It would seem that IE7 puts an extra 1px of spacing above and beneath form elements.
IE8, FF3.5, Chrome 2 & Opera 9.5 correctly renders these elements without the spacing.
What I want though, is for the display to be the same in IE7, so is there some kind of workaround to get IE7 to correctly render the elements?
It doesn't appear to matter whether or not the form element (eg Input Boxes) are placed within 's or 's, nor does it seem to matter about padding, margins & spacing settings. (setting them all to zero still has a 1px space around the input boxes)

I ran into this a while back and to be honest, I'm not totally sure I remember the fix. I seem to recall it has something to do with IE adding padding on the inside and outside of the input box, thus making it impossible to fix. It was either that or borders. Try either of these, together and separately:
input {
border: 0;
font-size: .9em;
}
If either of those offer what you need, I'd go with a conditional comment like:
<!--[if lte IE 7]>
input {
border: 0;
font-size: .9em;
}
<![endif]-->

Unfortunately, browsers render form elements with inconsistent heights and widths.
Fortunately, your two problem children are IE6 and IE7, both of which are easy to target using conditional comments. Without seeing them it's hard to say what the exact fix would be, but it might look something like this:
<!--[if lte IE 7]>
<style type="text/css">
input{ padding-top: 3px; ) /* 1px less than other browsers */
</style>
<![endif]-->

Related

IE box model error

I have a footer, below a textarea, containing a list and two buttons (all inline) within a div with the id #share-something. For some reason it is placed differently in Internet Explorer. I want it to look the same in IE as it does in Chrome. What am I doing wrong? http://jsfiddle.net/h3twR/
Oddly enough, IE7 seems to be fine for me, but 8 & 9 are off. If you have an IE-only stylesheet (using conditional comments), you can add this:
#share-something-container textarea {
margin-bottom: 5px;
}
*:first-child+html #share-something-container textarea {
margin-bottom: 0px; /* targets ie7 and undoes the margin above, as IE7 is okay */
}
This doesn't explain why 8 & 9 behave differently, but I've long since given up looking for logic and reason in IE.
There seems to be some kind of difference between IE8/9 and the other browsers and how they're rendering TEXTAREA.
It looks like you just have to set TEXTAREA to display block. It seems some browsers behave differently in this situation as they will see all elements as inline and generate extra white space. However, setting it to display:inline doesn't seem to have the reverse effect, so it's weird like that.
Here's a solution:
http://jsfiddle.net/h3twR/2/
I simply added this:
#share-something-container textarea {
...
display:block;
margin-bottom:5px;
}
And it appeared to render more consistently. IE7 seems to be off a little bit more. But hopefully this helps a little.
Cheers!

How can I override "display:inline-block" with "display: block" in IE7?

Here's some code to illustrate the problem I'm running into. jsFiddle Demo
<div class="normal">
Test
Test longer
</div>
<div class="ib blockbyclass">
Test
Test longer
</div>
<div class="ib">
Test
Test longer
</div>
body{background-color: gray;}
div{float:left; margin: 5px;}
a {background-color: black; color: white;}
div.ib a {display: inline-block;}
div.normal > a {display: block;}
div.blockbyclass> a {display: block; }
I have a certain type of link that under most circumstances needs to be rendered as inline-block, but in a certain case needs to be rendered as block elements. Specifically, I want them to each appear on their own line and take up the entire area of the containing div. In this particular case, the div containing the links is set to float, so it will resize itself based on the largest of the links inside it. IE8, IE9, Firefox and Chrome render these links correctly, but no matter what I do IE7 refuses to forget the display: inline-block rule.
How can I make IE7 show these elements in "block" mode?
Acording with this article display:inline-block has a similar behavior that display:inline in IE7, so you can make a litte change only to support IE7 (with a simple hack for IE):
div.ib a {
display: inline-block;
*display: inline; /* IE7 and below */
}
I hope this works as you expected.
EDIT:
Ok. The problem are with the property hasLayout explaining here. Both zoom:1 and height:any_value activates the hasLayout, so meanwhile display:inline-block; *display:inline works to overwrite the next display:block declarations, putting a height:30px (for example) returns the property hasLayout. So the thing to do is remove the hasLayout as it says in this article.
I have this demo to show how works. Because height is practically untouchable I using padding-bottom and font-size to simulate the height in other browsers. Note that the width of the widest element is maintained.
EDIT2:
Have you are considerate jQuery solutions? (Only giving the elements different widths in IE7)
Update: moved from comments here:
The problem is on div floating. When you float an element, that will be outside of pages normal stream, so, IE will take for it width:0; height:0; and when you put some elements in it, they will create their own height and width and the floated-element will be rendered how can push them (my English is really bad, so sorry). First step, A is inline-block so its height is for example x. when you make it block it should fill its parent, but, in IE mind, its parent has width:0. so you should remove the first inline-block attribute from div.ib a OR you can create a fixed-width attribute for floated div element.
div { float: left; margin: 5px; width: 80px; }
also, insofar as I know, W3C recommends that floated elements should have a fixed-width. - IE 6 needs a fixed height too to work correctly!!!
The another way -if you can and your solution allows you- is that change the first inline-block to inline just for IE:
display: inline-block;
*display: inline;
But the width solution (for div) is more standard and flexible.
END UPDATE
However, for overriding a css-attribute just in IE, you have 3 optional way to do:
The first way is using conditional comment that makes it's content visible to IE only. A full example is something like this:
<!-- visible to IE less that 7 (6, 5, etc) -->
<!--[if lt IE 7]> <link href="/Content/ie6.css" rel="stylesheet" type="text/css" /> <![endif]-->
<!-- visible to IE 7 only -->
<!--[if IE 7]> <link href="/Content/ie7.css" rel="stylesheet" type="text/css" /> <![endif]-->
<!-- visible to IE 8 only -->
<!--[if IE 8]> <link href="/Content/ie8.css" rel="stylesheet" type="text/css" /> <![endif]-->
<!-- visible to IE 9 and above and also visible to other browsers -->
<!--[if gt IE 8]><!--> <link href="/Content/normal.css" rel="stylesheet" type="text/css" /> <!--<![endif]-->
As you can see, you have many options to use conditional comment.
The other way is using CSS specially selectors that make some selectors visible to IE and hide them from other browsers. A full example is:
/* normal */
your-selector{
}
/* visible to IE 6 only */
* html your-selector{
}
/* visible to IE 7 only */
*:first-child + html your-selector{
}
/* visible to IE 7 and above */
html > body your-selector{
}
/* visible to IE 8 and above */
html > /**/ body your-selector{
}
The third way that I know is using IE specialized css-properties:
/* normal selector */
your-selector{
/* normal property, visible to all browsers */
color: #FF0;
padding: 20px auto 35px;
/* use special properties in name/value for IE */
/* visible to ie 6 only */
_color: #FF0;
_padding: 15px auto 30px;
/* visible to ie 7 and below (7, 6, 5, ...) */
*color:#FF0;
*padding: 15px auto 30px;
}
Let me know if you have any questions or need clarifications on any part.
Your problem is a hasLayout trigger by the inline-block setting. To quote http://www.satzansatz.de/cssd/onhavinglayout.html (my emphasis added):
"The display-property differs: while 'inline-block' sets haslayout = true, the flag will not be reset to false later on by overriding the value with 'block' or 'inline' in another rule set."
This is unlike most hasLayout triggers that can be reset. Therefore, I think to fix your problem, you need to think in reverse. You need to have block be your default for the a tag and then add a class to get your inline-block when you need it.
Sort of like http://jsfiddle.net/mmpX3/33/ where blockbyclass I replaced with inlinebyclass (which is really inline-block).
Updated Explanation: You probably noticed that when you switched to block after going from inline-block that it "sort of worked" (the lines of text still move down). That is because it is displaying as a block, but one that hasLayout as opposed to one that does not. I don't know your particular situation, but if you can set a width on the containing div then a secondary solution to that I proposed above of "thinking in reverse" is to then set a width: 100% in conjunction with your "resetting" to block, like so: http://jsfiddle.net/mmpX3/64/.
Updated Caution: I don't know if you have other css you plan to apply to the a tags, but if any of that triggers hasLayout then you will need to watch out for that (and perhaps find a different method). See for example this fiddle http://jsfiddle.net/mmpX3/69/ in which everything is set to block but because I put a min-height on the a tag, it still has the same issues as your original problem.
You can put styles for IE7 in a separate CSS and use a conditional comment to include it only for IE7.
<!--[if IE 7]>
<link ...your IE7 specific stylesheet goes here ... >
<![endif]-->
Make sure this piece of code is below the link to the regular css file.
display: inline-block
for IE7 looks like:
*display: inline;
zoom: 1
display: inline-block is not compatible in IE7 for elements which are not inline by default so IE will ignore this rule for DIVs. If you change the DIV to a SPAN for example then this example should work.
Here's the thing: If you need the a tag anchors to render on their own lines, they are block elements, not inline... In fact, there's nothing about what you're saying that indicates a need for an inline-block. Your divs are floating, so they'll stack to the left, in a line (but not inline; they are outside the flow of the document, thus float).
Try this... let's strip it all down. Here's the HTML you gave us:
<div class="normal">
Test
Test longer
</div>
<div class="ib blockbyclass">
Test
Test longer
</div>
<div class="ib">
Test
Test longer
</div>
With the CSS you provided, in Safari and Firefox, I see three blocks with two links each, each on their own line. What you're seeing in IE7, however, isn't two inline-block elements, but just two inline elements – the reason for this is that inline-block is not supported in IE7 because of a hasLayout error (something Microsoft created to overcomplicate a simple issue). In other words, it can't forget inline-block because it simply doesn't understand inline-block (which you've misunderstood as necessary), and is treating a by its default display behavior (i.e. inline).
If they need to be on separate lines and take up the width of the container, all you have to do is this (demonstrated on .ib a, completely ignoring blockbyclass which seems to just be a red herring in this case):
.ib a {display:block;}
TADA! Width is inherited from the parent container, the a takes the default a stylings, and everything is happy. So take a look at this:
<div class="ib">
Test
Test longer
</div>
This, in this case, becomes redundant, and therefore unnecessary. You're already making those elements block.
<div class="ib">
Test
Test longer
</div>
You're simply overcomplicating something really very simple.
Here's a fiddle: http://jsfiddle.net/dhYjZ/1/
It appears that float is to blame here. It is not that IE7 does not mark the item as block, I think it is due to the div float not having a width. This can be seen here:
http://jsfiddle.net/mmpX3/129/
Typically, when working with older browsers, I have found that floated elements in <= IE7 tend to need a fixed width setting to avoid issues.
In your case, I would suggest adding a fixed width as the JS Fiddle, or remove the float if it is not needed. If I can see the use case for the floated div, I may be able to come up with an alternative.
Why a combination of float and display:inline-block stops display:block from being re-instanted, I don't know. It sounds like a typical IE7 bug that can be worked around.
I'm not quite sure what is the end-result that you are after. Are you trying to make the black background to be a whole rectangle that encapsulates both links instead of 2 rectangles (1 for each link)?
If so, why not apply the background to the DIV instead of the links?
EDIT:
It seems that there's a bug with IE7 that makes it display elements in a mixture of block and inline-block when one of the rules that applies to the element has display: inline-block even if another value for display takes precedence.
If you see http://jsfiddle.net/P2N5c/16/ , it doesn't matter if the rule that has display: block is the first one (like the one using the #blocky rule) or if it's the last one.
So far I'm not sure how to prevent this bug, but you could bypass it by avoid giving the links both ib and blockbyclass and just giving it the classes that make them blocks. I.e. don't give them ib. Instead of adding a class to toggle the states for the DIV, replace one class for the other.
Simply put, I replace all of my display:inline-block; usages with display:inline;, and I also do so conditionally, as with the answers provided above.
With your example, I find success with the following:
body{background-color: gray;}
div{float:left; margin: 5px;}
a {background-color: black; color: white;display:block;}
Jsfiddle: http://jsfiddle.net/zL3Ea/
Seems like jobs done.
I am fork your code, try it: http://jsfiddle.net/Lkwzx/1/
Secret in this line: div.ib a { display: inline-block; *display: inline; }

why does the page display differently in IE than google chrome?

Certain pages display terribly in IE generally, what is the best approach to solving these issues?
You forgot to add a doctype, so your page is in Quirks Mode.
Add this (the HTML5 doctype) as the very first line:
<!DOCTYPE html>
and it should look better.
Although, changing the Document Mode manually (using Developer Tools; hit F12), it still doesn't look right. There are evidently other problems with the page.
The most pertinent problem (after escaping Quirks Mode) is this:
<body style="margin: 0; padding; 0;background-color: 4DA2CA;">
Internet Explorer is not showing any background colour because you forgot the # before the colour. (And you have padding; 0, with a ; instead of :)
This will work:
<body style="margin: 0; padding: 0; background-color: #4DA2CA">
But you shouldn't be using inline styles in the first place..
This would be better:
<body>
with CSS in your stylesheet:
body {
margin: 0;
padding: 0;
background-color: #4DA2CA
}
you mean that in IE the Div's are smaller.Thats because in IE css border,margin are included in the width declared.So, if you have given a div width of 100px and a margin of 10px both sides then in IE the actual visible width of this div will be 100-10-10=80px.To solve the problem you can use child css decleration.
Considering our example if you want to show this div 100px width in both the browsers do the following
.mydiv{ /*This deceleration will be understood by all the browsers*/
margin:10px;
width:120px;
}
html>body .mydiv{ /*This deceleration will not be understood by IE browsers so other will override the width*/
width:100px;
}
Using this you can uniform the width of your Divs across both IE and non-ie browsers
Instead of pointing out the reason for each element's different way of rendering in IE, I would strongly recommend not re-inventing the wheel each time you create a new page element.
Even in modern standards-complaint browsers, CSS can be very unpredictable, so it's better to use bullet-proof snippets of code from trusted sources such as
CSS the Missing Manual
CSS the Definitive Guide
CSS Cookbook
Start out with working blocks of HTML/CSS and modify them to your liking and test cross-browser from there. The whole process will be much less frustrating.

What did I do wrong in this CSS Layout?

I did this layout here: http://www.2xfun.com/
It uses some css3 effects and stuff which are not supported in every browser, but if they dont work its fine.
The thing is that i really tried to keep the essentials working in old browsers.
I didnt use any negativ margins, which i know of make problems in IE 6 etc
But if i look at it in IE 6 the layout gets messy. The elements are completely garbled.
Where did I fail so terribly? I don't need an analysis of all my errors because i know its by far not perfect. But what positioning css directives are so wrong that they cause IE6 to mess everything up?
So my question is:
What properties or combination of properties do cause such legacy incompatibility
are there any good work arounds (css resets, javascript fixes) ?
addendum:
this is how the page looks like in ie6
and after Šime Vidas's javascript fix
and this is how it should look like and looks like in modern browsers
Everything that has position: absolute, put both top and left positions, not just top. Everything that has float AND margin, set to display: inline. That will at least fix many problems. I'd also recommend a reset styling, like Meyer's. Your code looks a bit underdefined for IE6, it's a picky one.
Put this on the page:
<!--[if lt IE 9]>
<script src="http://ie7-js.googlecode.com/svn/version/2.1(beta4)/IE9.js"></script>
<![endif]-->
How does the page look in IE6 now?
Project homepage: http://code.google.com/p/ie7-js/
Getting started: http://www.charlescooke.me.uk/web/lab_notes/ie7_script.html
Here we go..
Add a rule to this effect to your normal stylesheet - #neXib was correct:
.headcontainer, .headbar {
left:0
}
Without that, your site has problems even in IE7.
The above snippet, combined with adding this voodoo magic dust I created fixes the pressing IE6 issues:
<!--[if IE 6]>
<style type="text/css">
.headbar-spacer {
width: 169px
}
.content div.right {
padding-right: 0
}
.content h2 {
margin: -30px 0 0 106px;
width: 535px;
padding: 0 0 12px 0
}
</style>
<![endif]-->
I commented out this:
<script type="text/javascript" src="http://s7.addthis.com/js/250/addthis_widget.js#username=xa-4c90156b67654829"></script>
It seemed to somehow make IE6 jump the white video container to the top of the window. So wrap that in a conditional comment if need be.
Your site looks like this with the above changes in IE6 (ignoring the low color depth of this image):
Much better!
Improvements you could make:
Try out DD_belatedPNG to fix your .png transparency issues.
Make an image version of the CSS gradient you have on .headbar. At the moment, IE8 does not have a gradient. IE has support for it's own special kind of gradient, you might consider providing those rules (-ms-filter/filter + gradient?).
Redundant point: fix Notice: Undefined index: jsfix in /home/2xfun/html/application/views/vanilla.php on line 13. Obviously you just put that in for testing. I recommend suppressing the PHP error by prefixing the line with #.
Kick IE6 in the face. Twice.

Is conditional comments the way to go really? And how does it work?

This previous Q about a div positioning problem in IE gave several answers where they told me to use conditional commenting.
How come this relative positioned div is displayed differently in IE?
How does it work, I mean how do I implement conditional comments?
Ex:
<div class="normal"></div>
<!--[if IE 6]>
<div class="IE6"></div>
<![endif]-->
IF it is explorer 6, will this then override the first div with class="normal"?
Because if it wont, then there will be two divs in explorer 6 right...
What could possibly be the problem of this positioning?
I have even tried creating a new html document with a hello world text, and put it inside a div with relative pos, and in IE it behaves differently, about 3px further down than in other browsers...
Thanks
This is normally used to load an extra bit of CSS that "fixes" various issues due to IE6 bugs/lack of features.
eg. the top of our site looks a bit like this...
<link rel="STYLESHEET" type="text/css" href="/css/common.css" />
<!--[if IE 6]>
<link rel="STYLESHEET" type="text/css" href="/css/ie.css">
<![endif]-->
This loads our normal stylesheet first. Next IE6 (only IE6) loads the second stylesheet, which override a couple of definitions that cause problems for IE.
If you need different content, you could include both sets of content (normal content and IE content) and have the IE content hidden by default via your standard CSS (display:none), and simply overide this in the IE6 css stylesheet.
No, it isn't the way to go really.
They're non-standard, they're proprietary, they set a bad example, and they're absolutely unnecessary.
whatever {
foo: bar !important; /* for non-IE6 */
foo: baz; /* for IE6 */
}
child { /* for IE6 */ }
parent > child { /* for non-IE6 */ }