Ye' old general discussion board. Basically, for everything that isn't covered elsewhere. Come here to shoot the breeze, shoot your mouth off, or whatever suits your fancy. This forum is not for asking programming related questions.
Sorry, I just had to get that off my chest. MSIE bugs been biting me all day - how am I supposed to make "nice" W3 standard (XHTML 1.1) compliant layouts with such a ridiculous amount of bugs I can't physically do anything about?!
Two things been affecting me today. PNG-24 transparency (but the (Microsoft **** fix) filter doesn't help here unless I make a large image).
The Box model!!! All I want is for my div's to stop stretching and just spill over the edge and from what I've read this is not fixable
It really annoys me when I make a really nice layout and then it breaks in IE so I have to start adding Propreitary MS code which starts breaking standards unless I use something even more MS like conditional comments - thus making me look bad. There's really no end to the MS specific code we need to use. How the hell can such a huge company not fix these issues asap?
Hmm... well I've partially worked around the issue of the expanding divs by using a cleverly designed background image (the overlapping divs I wanted was purely for visual effect) so it *looks* the same in IE even if the (invisible) boxes are doing different things.
At this point I should probably move this thread to client side but anyway...
Does anybody know how to fix this issue *without* javascript.... ?
If I use the MS filters I can't physically access the content on the div anymore The PNG is a background image that fills the div and what I think is happening is that IE is effectively turning my div into an image! I can see the text clear as mud but I can't click it (the cursor just sits as "default" so I can't select text or click links).
Any clues? quirksmode.org doesn't seem to offer a solution.
I find myself more and more agreeing with the opinion that currently with so many IE users it just takes too much time and effort to write nice XHTML 1.1 which would produce THE SAME result in IE as in other browsers. You will never learn all those 'hacks' and it's just not worth the trouble in my opinion. I'd rather write HTML transitional instead of 'hacks'.
Ree wrote:I find myself more and more agreeing with the opinion that currently with so many IE users it just takes too much time and effort to write nice XHTML 1.1 which would produce THE SAME result in IE as in other browsers. You will never learn all those 'hacks' and it's just not worth the trouble in my opinion. I'd rather write HTML transitional instead of 'hacks'.
I have days when I write XHTML + CSS to 1.1 compliancy very happily and I'm so familiar with the *little* bugs that I work around them without even thinking about it. The filter for PNG-24 aplha transparency usually works fine but since this is a background image it's causing me grief. Today has been one of my worst days coding and hitting constant IE bugs I think due to the nature of the particular layout I'm using.
Note: I do finish with valid XHTML and CSS eventually even if it does involve conditional comments - I just pull hairs out in the process. All those underscored css attributes get moved into IE specific parts of the template at the end - I just put them in the code while I'm developing so that I can see what's going on quicker.
It's nice to see the after effects of the Firefox releases... Be even nicer if IE maintains compliance after IE7 and doesn't another nap for a few decades until it received another shock to its unquestioned dominance...