Hey guys, I have been having a weird problem with IE7 (surprise!), check this screen from FF3
This is from the Blog4Umbraco package, it creates the blog-item divs as children of the content div. So far so good, but with IE7, this is what happens (according to firebug lite)
The hml is rendered differently and of course disturbing everything up. It had happened before and I had to re-write the xslt, but with Blog4Umbraco I had to stop my horses. Any ideas?
It's not alway you can rely on firebug I think. It does not make sense that the DOM looks different in one browser and not another browser.
Does the HTML source look ok when you use "view source"? And what is the problem on the rendered page visually? Maybe there is an unclosed element somewhere that makes the other elements collapse or something like that?
Yeah, it was something like that, I am circumscribing the bodyText length to a certain ammount as a teaser of the blog item in front page, it turns out that it was chopping a <p> tag right in the middle so it was causing havoc, I changed the ammount that that did it. thanks.
IE7 rendering html differently
Hey guys, I have been having a weird problem with IE7 (surprise!), check this screen from FF3
This is from the Blog4Umbraco package, it creates the blog-item divs as children of the content div. So far so good, but with IE7, this is what happens (according to firebug lite)
The hml is rendered differently and of course disturbing everything up. It had happened before and I had to re-write the xslt, but with Blog4Umbraco I had to stop my horses. Any ideas?
Hi AntonioMX
It's not alway you can rely on firebug I think. It does not make sense that the DOM looks different in one browser and not another browser.
Does the HTML source look ok when you use "view source"? And what is the problem on the rendered page visually? Maybe there is an unclosed element somewhere that makes the other elements collapse or something like that?
/Jan
Yeah, it was something like that, I am circumscribing the bodyText length to a certain ammount as a teaser of the blog item in front page, it turns out that it was chopping a <p> tag right in the middle so it was causing havoc, I changed the ammount that that did it. thanks.
is working on a reply...