Looks like some IE CSS rendering bugs are actually "fixes"
-
I've been sitting here testing some stuff in IE, Safari and Opera earler today where i needed to set exact pixel sizes for nested divs and tables, and found that the IE idiosyncracy of stretching a div around the "overflowing content" may actually be a quick fix implemented after some kind soul working on the project noticed that there's no way to have cross-browser compatible pages with their current rendering technique. With IE, when you set a div to be 50 by 50 px with a 1 px border, if you want to nest another div in it with no border and can't rely on width:100%, you subtract 2 px, one px for each side, making the div 48 by 48 px. But Opera and Konqueror/Safari approach the matter differently and the same no-border div will actually be the same 50 by 50 px. That's where the stretching div "bug" comes in, compensating for the difference in approach. I'm actually thinking this has been around since the Netscape days, but i have no way of verifying Roswell :)
"Angelinos -- excuse me. There will be civility today."
Antonio VillaRaigosa
City Mayor, Los Angeles, CA -
I've been sitting here testing some stuff in IE, Safari and Opera earler today where i needed to set exact pixel sizes for nested divs and tables, and found that the IE idiosyncracy of stretching a div around the "overflowing content" may actually be a quick fix implemented after some kind soul working on the project noticed that there's no way to have cross-browser compatible pages with their current rendering technique. With IE, when you set a div to be 50 by 50 px with a 1 px border, if you want to nest another div in it with no border and can't rely on width:100%, you subtract 2 px, one px for each side, making the div 48 by 48 px. But Opera and Konqueror/Safari approach the matter differently and the same no-border div will actually be the same 50 by 50 px. That's where the stretching div "bug" comes in, compensating for the difference in approach. I'm actually thinking this has been around since the Netscape days, but i have no way of verifying Roswell :)
"Angelinos -- excuse me. There will be civility today."
Antonio VillaRaigosa
City Mayor, Los Angeles, CA:laugh::laugh: I feel your pain. Have you tried divs in a table? Browser's really have different opinions on that.
- S 50 cups of coffee and you know it's on!
Rock the Vote: John Simmons / outlaw programmer for '08. -
I've been sitting here testing some stuff in IE, Safari and Opera earler today where i needed to set exact pixel sizes for nested divs and tables, and found that the IE idiosyncracy of stretching a div around the "overflowing content" may actually be a quick fix implemented after some kind soul working on the project noticed that there's no way to have cross-browser compatible pages with their current rendering technique. With IE, when you set a div to be 50 by 50 px with a 1 px border, if you want to nest another div in it with no border and can't rely on width:100%, you subtract 2 px, one px for each side, making the div 48 by 48 px. But Opera and Konqueror/Safari approach the matter differently and the same no-border div will actually be the same 50 by 50 px. That's where the stretching div "bug" comes in, compensating for the difference in approach. I'm actually thinking this has been around since the Netscape days, but i have no way of verifying Roswell :)
"Angelinos -- excuse me. There will be civility today."
Antonio VillaRaigosa
City Mayor, Los Angeles, CAAh, the wonderful world of cross-browser hacks... I wrote a number of rich DHTML controls a while back, and there were a number of cases where I had to use IE bugs as fixes for other IE bugs. :sigh:
--Justin, Microsoft MVP, C#
C# / DHTML / VG.net / MyXaml expert available for consulting work[^] Get Quality Portraits Drawn From Your Photos[^]
-
:laugh::laugh: I feel your pain. Have you tried divs in a table? Browser's really have different opinions on that.
- S 50 cups of coffee and you know it's on!
Rock the Vote: John Simmons / outlaw programmer for '08.Steve Echols wrote:
divs in a table
Tables are getting outdated right since it is slowing down the rendering. Our web designer is crazy of DIVs and giving as much granular cross-browser compatible stylesheet to make it work across the browsers.
Vasudevan Deepak Kumar Personal Homepage Tech Gossips
-
Ah, the wonderful world of cross-browser hacks... I wrote a number of rich DHTML controls a while back, and there were a number of cases where I had to use IE bugs as fixes for other IE bugs. :sigh:
--Justin, Microsoft MVP, C#
C# / DHTML / VG.net / MyXaml expert available for consulting work[^] Get Quality Portraits Drawn From Your Photos[^]
J. Dunlap wrote:
where I had to use IE bugs as fixes
Two good ones: 1)
window.close()without prompt by hijacking the opener property. 2)ExecWB ActiveXto manage through a promptless print.Vasudevan Deepak Kumar Personal Homepage Tech Gossips
