Nick Fitzsimons" <[EMAIL PROTECTED]> > On Tue, March 11, 2008 6:54 pm, Alan Gresley wrote: > > So anyone who has empty declarations blocks in there style sheets will > > have to remove them now. > > Or they could do the obvious thing and report the bug to Microsoft, or > vote for it if it's already been reported, and it will undoubtedly be > fixed in the next beta.
Precisely. Anyway it not as simply triggered as I thought. I think the empty declarations blocks must be following an import. Test Case. http://css-class.com/test/bugs/ie/8/empty-declaration-hides-next-ruleset.htm > I have to say once again that I am completely baffled as to why people are > acting as if this is a final release. It's the first public Beta of a > piece of software which, if the same process with IE7 is any guide, will > not be released in a final form for maybe another six months. I expect we > will see at least two more Betas before seeing even a Release Candidate. I personally not acting in any manner. That's why I leave my pages broken in IE8. I have just seen one scenario. Since the rule set with empty declaration must appear between an import and the the following rule set. This could be for the html or body element. I dare say that if someone did have such a empty rule set between an import and body, they may report to MS that there site is broken because all the basic style has been lost. That would be a misguided bug reporting, one which MS doesn't need. > If you find a bug, report it, but don't suggest that people will have to > fix anything - the only people with anything to fix at this stage are the > IE team, and the only useful contribution one can make to the web > development community is to inform them of these issues. > > <http://blogs.msdn.com/ie/archive/2008/03/05/ie8-beta-feedback.aspx> > > Regards, > > Nick. And this is why I am reporting it here. The more people that are aware of the bug early on, the more people that will vote on the bug. I myself am waiting for mail to arrived so I can join TechBeta. I can assure you that some in the IE team are aware of this bug or others that I have found since my pages have regular visits from Redmond. I have seen a page break not due to a bug in IE8 but more because IE8 was using a hack meant for IE7. *:first-child+html E {display:inline} /* common IE7 fix */ These rules meant for fixing a buggy IE7 may cause a page to break in IE8 which is a much more standard complaint browser. IE8 is needing the regular style rules that the other browser are using. I can't really refer to these other browser as the better browser now because IE8 in most cases is equaling or bettering these other browsers. Listing another good scenario. <http://css-class.com/test/css/backgrounds/multiple-backgrounds.htm> The CSS is: background: url(normal.jpg); background: url(one.png), url(two.png); Since IE8 is actuality parsing the last declaration it will try to download this. domain.com/images/one.png,two.png instead of this. domain.com/images/one.png MS doesn't need reports from people that IE8 is not showing header/banner images where the real problem is that IE8 is parsing a declaration that it doesn't understand, thus should drop it and use the normal.jpg. It was good that I was using a dummy image in a multiple background to serve Safari the better image or I would never had discovered the real bug. I have now corrected this so now Safari and Opera now use the better image. :-) So in summing up, no need to get into frizzle. Just sit back down calmly, meditate, and then peacefully clean up your style sheets. For those who have the knowledge to, remove those IE7 targeting hacks from the main style sheet and import IE7 style from another style sheet. The rest of you can simply not use hacks, they are dangerous. :-) Isn't CSS fun! Alan http://css-class.com/test/ ______________________________________________________________________ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
