I'm sure its already been reported, but drupal.org looks all wrong in IE7 beta 2. The top tabs are all on the left side of the screen stacked up on top of each other rather than side by side. And that also makes it impossible to press links on the same level as them elsewhere on the page, e.g. the search box top right.

Comments

sepeck’s picture

The beta went public today. I believe that the recommended fix was to remove all the hacks that allowed IE6 to work.

-sp
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

Shane Birley’s picture

...a difficult transition. The adoption rate may be quicker this time, but the IE 5 -> IE 6 change took a while to do.

Also, with IE 6 the hacks are imperative to have working sites right now - and one would think there would be some "IE 6" backport compatibility automagic stuff going on. But, we will really know the full story when the product exits beta.

---
Shane Birley
Vicious Bunny Creative
http://www.vbcreative.com

---
Shane Birley
Left Right Minds
https://www.leftrightminds.com

kong’s picture

that is IE7's problem, not drupal.org's. Here's a quoted comments from PC Magazine:

The Microsoft crew that showed us the latest IE emphasized that Redmond completely rewrote the code for its rendering engine. The new engine had a lot of glitches, though, and hampered our browsing abilities in some cases. While main pages for most Web sites loaded just fine, you'll notice that some specialty applications, blogs, and tools might be rendered incorrectly. For instance, the browser had problems when it rendered—or rather didn't render–the text within our own PCMag.com forums application. The browser lost all our formatting controls and also shrank the text box. And using the quote feature made the posts virtually illegible due to all the raw HTML code filling the window.

source: Internet Explorer 7 beta 2 review by PC Magazine

roly’s picture

Unfortunately I don't think we can just say it is IE7's problem (although I know we would like to). The reason for this is that users of web sites WILL move to IE7 from IE6 (noting that the user base for IE is still around 85%). The adoption rate from IE6 to IE7 is likely to be much faster for 3 reasons:
1. It has tab browsing
2. MS has a huge marketing strategy encouraging users to upgrade
3. Most new PC's will be shipped with IE7 (once released).

My view is that we carefully watch the take up of IE7 and when sufficient numbers are evident then implement a solution. Unfortunately I can not see the IE7 guys doing anything on their side to help us. :(

q0rban’s picture

Unfortunately I can not see the IE7 guys doing anything on their side to help us. :(

c'mon.. Are you saying that Microsoft doesn't care about my feelings? I don't think the blue screen of death is blue by coincidence. It is clearly a highly complex AE (read Artificial Empathy) engine.

BryanSD’s picture

I took a quick look at IE7 at work. I hate to admit this, but some of its Firefox features (tabbed browsing and RSS Feeds) have actually been improved (IMHO) in IE on what Firefox/Opera started. There really is some neat features in there from a user-only perspective. It will be hard for Mozilla to persuade those Windows users who have not yet moved to Firefox to do it now. Unless of course, the Mozilla gang has some tricks up their sleeve with Firefox 2.0.

Drupal Sites Coming Soon:
CMSReport

andre75’s picture

I always thought the main reason for people to switch is that they get hammered by spyware and viruses caught by IE. Guess I was wrong.
I guess that means back to CSS design for most of us (end endless hours of poking around for me, since I don't know CSS).

Andre

-------------------------------------------------
http://www.aguntherphotography.com

BryanSD’s picture

To be honest, from a sysadmin point of view, I've seen just as many security patches/concerns with Firefox as I have with IE. I haven't looked into IE7 too deeply, but it's also suppose to follow the same path as other browsers and get it's freaken code out of the Windows OS as much as possible. If that happens there is less incentive to provide Firefox on the desktops within my office.

I led a team within my organization for migrating our primary e-mail client to Mozilla Thunderbird. I'm a HUGE Mozilla fan. Quite frankly though, from a sysadmin perspective neither Thunderbird nor Firefox are as easy to manage on a Windows network as the MS counterparts. There are a few more hoops you have to go through with Firefox and Thunderbird to deploy on the network (like still having to build your own MSI packages unless you're willing to use the nightlies).

-Bryan

andre75’s picture

If you configure everything correctly, maybe you are right. Most Users are not even capable to disable ActiveX support in IE.
Every Browser has some weakness, but the most critical one for me on IE is the exploit that lets people manipulate the URL shown in the address bar. I get tons of emails from "paypal" and "ebay".
While common wisdom tells me to ignore them, some ebay auctions now have fraudulent links in them. They are easy to recognize by looking at the URL (if your browser shows it correctly).

-------------------------------------------------
http://www.aguntherphotography.com

kkobashi’s picture

This is not Microsoft's problem. It is our problem. You cannot point the finger and place blame on Microsoft when you are not in control over the browser that is used by 90% of your website visitors. What they ship, you have to live with.

The Drupal community needs to formulate a team of testers and developers to start addressing IE 7 compatability. These individuals need to stay on top of IE 7 on a continual basis.

This suggests that the next major release of Drupal should be frozen several months prior to Windows Vista to allow for that release to settle. Then, say, around August 2006 create a new release dubbed "MrSoftie IE 7" with *ONLY* IE 7 changes. By keeping code changes only to IE 7, the Drupal community can wrap their hands around the beast, and place it within our control.

No changes should be made now to the existing code base to address IE 7 bugs. The reasons are:

1) Microsoft could make more changes, negating Drupal fixes
2) Microsoft could make more changes, resulting in more Drupal problems
3) You dont want to dirty the existing code base and mix the MrSoftie IE 7 with Drupal's current project release. Keep them separate or we will have a hell of a time rolling back.

Kerry Kobashi

BryanSD’s picture

I would suspect one of the reasons we're seeing problems with IE7 at Drupal.org has very little to do with the Drupal core, but an issue with either the XHTML or CSS within the theme being used at Drupal.org. Since past versions of IE have not always followed standards a number of tweaks have been made to themes so they display better in IE. I wouldn't be too surprised if these "fixes" are what is causing problems with IE7 rendering pages properly. In other words, doing exactly what you suggest...tweaking for a specific browser instead of following coding standards...may have caused this problem in the first place.

I was going confirm my suspicians and see if anything in the CSS or XHTML of the theme being used for Drupal.org was causing the problem. But after looking at ./themes/bluebeach/style.css it looks like I would be forbidden to display the actual code in order to discuss fixing it, so why bother. :-(

This theme is NOT for public use. No copying of CSS, XHTML or images is allowed without permission.

Back to my point...I think tweaking code for a specific browser is a bad idea. What we need to do is make sure we follow the standards. One of Microsoft's goal with IE7 is to follow standards better than it has in the past. These standards include CSS 2.1 and XJAX which "addresses many of the major inconsistencies that can cause web developers problems when producing visually rich, interactive webpages". In other words Microsoft is putting IE 7 on the same path as Firefox and trying to follow open standards. Our time is best spent worrying that our sites/themes follow the standards and point out to Microsoft when their browser doesn't render properly coded pages correctly. After all, this is a Beta...and I think they would rather address the problems with their browser instead of forcing more work-arounds for their browser.

-Bryan

Drupal Sites Coming Soon:
CMSReport

Drupal Blog (on WordPress) at:
Like that Idea

sepeck’s picture

huh?

it looks like I would be forbidden to display the actual code in order to discuss fixing it,

what are you talking about? If you think you know ho wthis can be fixed, then feel free to open an issue against the Drupal infrastruture and report the fix. If you look at the project issue tracker you will see this is an already reported issue
http://drupal.org/node/47873

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

BryanSD’s picture

Sepeck,

I don't want to get sucked into a GPL/OpenSource debate, but the style.css in the theme being used by Drupal.org is not fully GPL ( http://drupal.org/themes/bluebeach/style.css ). As I mentioned before, the sytle.css specifically restricts the copying of code and displaying it publicly.

This theme is NOT for public use. No copying of CSS, XHTML or images is allowed without permission.

I'm not a lawyer and will be happy that I'm somehow misreading this. Are you saying that permission has been granted for all Drupal users to use and modify the Theme as needed? Now if I have been given permission to fix the coding in the theme but I can't copy the code to my own site...I don't see the personal incentive to why I would do that.

To be honest I'm surprised that Drupal.org (the site not the CMS) is using a theme that is not fully under the GPL. I understand why users may need to protect the style.css to a license outside the GPL, but I'm not sure why Drupal.org would need or want to do this.

Before this discussion gets any more heated, remember...there may be nothing wrong with the CSS or XHTML code in the theme and it's a bugs in the IE7 Beta. While I suspect that the tweaks for the previous versions of IE is what is causing the problems for IE7, I really can't say without looking. When I took a peak at the style.css...I was caught off guard that Drupal.org's theme is NOT fully under the GPL. The icons themselves are also under the MPL and LGPL. A little unclear to under what license the CSS is under.

-Bryan

sepeck’s picture

I am seriously tired of all the misrepresenation and FUD about this crap being spread around the forums by some people and getting everyone upset. The reason is we are protecting Drupal.org's look and feel is because over half of the 'new' sites announced in the new sites section, are blue beach theme. That was the former theme for Drupal.org. It caused confusion and difficulty finding and identifying Drupal.org from all the other sites. It made all of them look like Drupal.org. The fact that drupal.org is making itself unique to be identifiable is important. There is an explanation of this in the handbook.

Blue Beach is a very very site specific theme. It has things very specific to Drupal.org. The same author using much of the same code/techniques released Friends Electric for people to use and modify as they see fit.

My sites page.tpl.php is available, but I spent some time learning css and like to only see my site look like mine, issue's and all.

Blue Beach style.css may not be used elsewhere. That is what it means. If you believe that you can help fix it for IE7 then feel free to help. There is an issue open for people to help maintain drupal.org in the Infrastrucutre issues. If you don't feel that you can help fix/correct it, then don't. If you can, then great please post it there in the issue tracker. Drupal.org's Blue Beach theme is protected undercopyright to protect the look and feel of the main site. This is a seperate issue from GPL. CSS is not created by or displayed by php. It merely controls the display output. I would be seriously upset to see hundreds of sites that look like Drupal.org. It would dillute it.

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

BryanSD’s picture

There is an issue open for people to help maintain drupal.org in the Infrastrucutre issues. If you don't feel that you can help fix/correct it, then don't. If you can, then great please post it there in the issue tracker. Drupal.org's Blue Beach theme is protected under copyright to protect the look and feel of the main site.

And that was my whole point...because there was a restriction on copying/displaying the code...I was uncertain where I had permission to display the code in hopes of helping to fix it. I respect Drupal's wishes to protect it's look and feel and didn't want to violate any copyright/trademark issues by posting it in the general public forums.

I agree there has been a lot of FUD, but some of that FUD has originated from the lack of clarification and not the questions or interpretations being seen in the forum. Perhaps if the style.css in specifying "no copying" of the CSS was allowed without permission...it should have specified where permission was granted (i.e. within the Infrastructure issue to assist in resolving issues)? You know such clarifications are needed or you wouldn't be finding yourself working so hard with the handbooks.

On a side note (and ending hopefully a good note) thanks for all the good changes you've made lately with the handbooks. The work is appreciated and getting easier each day to navigate through.

-Bryan

BryanSD’s picture

Sepeck,

Using the link to the issue provided, I saw that drupal.css also has some issues. If I get a chance and if no one beats me to it, I'll take a look at that file since there is no question that it is under the GPL.

By the way, for those folks that are wanting more information to what has changed between IE6 and IE7 (regarding page design) a couple places I'm starting to read. Their long links so you'll need to
click here for information regarding CSS changes
and click here for additional information.

kkobashi’s picture

Thank you BryanSD for your help into this. I am glad there are people out there such as yourself taking this issue on with seriousness.

Kerry Kobashi

kkobashi’s picture

Don't get me wrong. Standards are a good thing, but a product's adherence to standards is only as good as the implementation. Taking the stance that software is always written correctly and to standard is a leap of faith. More so when someone holds the bulk of the browser market, and uses it to their competitive advantage.

There's a big difference between the idealistic "what should be", and the realistic "what is". When 90% of the traffic to my websites come to visit via IE, am I going to tell them "Sorry, I can't support you IE 7 user because Microsoft isn't following web standards"?

I don't know about you, but I got better things to do than fix CMS bugs.

Kerry Kobashi
Kobashi Computing

sepeck’s picture

The display problem is NOT A CMS BUG! It is a theme issue with some specific css in use on Drupal.org's Blue Beach theme. This issue was brought to light earlier already in the issue tracker and the HOW of the fix is being looked at. Have you bothered to look at some of the other themes in IE7? I have looked at several of them and they display just fine. (not all, been busy)

Your incredibly wild jump to conclusion to condem all CMS's without bothering to do basic research is incredible. Simply incredible.

If you have better things to do than contribute to the Open Source CMS that you use, then please feel free to go use SharePoint or SharePointServices because all of us volunteers have better things to do than help you! As you don't have time to help us, I shall make a note to remember your stance on this issue in future. My assistence in helping people is based on the assumption that some percentage will take time out of their busy day to help the next person in line. I make no money off Drupal or Drupal services.

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

kkobashi’s picture

You have lost it. Get a grip.

In my defense, I too have spent my free time helping people on these forums. But unlike you, I don't go around insulting and yelling at people like some unstable crazy fool deserving preferential treatment just because you are a "Drupal documentation coordinator".

Your really scary man. Do me a favor and don't respond to any of my messages.

Kerry Kobashi

sepeck’s picture

This means it's not done yet.

We were aleady aware of the issue. It will be addressed. It is not a 'Drupal' issue, it is a theme issue on Drupal.org. The causes are in fact theme hacks designed to help make IE6 work.

Your little aside about waiting or releasing based of Microsoft's OS is completely off topic and demonstrates you fail to understand the nature of the problem. My site works fine in IE7.

The only thing that needs to be done in regards to the tabs is fix some theme issues with the Blue Beach theme that existed to deal with theme issues in ie6. As IE7 is still in early beta, there's not even any hurry. It'll get done.

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

kkobashi’s picture

Why the defensive stance? Your post reads like sour grapes. Chill out.

"It works for my site" doesn't cut it. I run multi sites with hundreds of thousands of visitors every month with different flavors of Drupal, themes, modules, etc. If you think every Drupal user is going to rest their fate on your word, your wrong. A sample of one data point isn't sufficient in my book.

IE 7 support is my concern. Whether Drupal breaks or not under IE 7 isn't the issue because I have full confidence the community and myself will solve problems as they arise. Your sending the wrong message by shoving the issue under rug until the time arrives. That is wrong and irresponsible.

Drupal users should start testing their sites against IE 7 NOW and give feedback to the community up until IE 7 ships in Vista. It is a message of simple awareness and one that needs to be stressed:

"Dear Drupal users,

As you know, Internet Explorer is the most often used browser when visiting your Drupal website. IE 7 is currenty in public beta test. This means now is the time to start testing your existing sites with IE 7 until Windows Vista ships. This will provide us with valuable feedback on any potential compatability problems as we move forward. While we won't fix them now, we will do so later on in the year. Please kindly provide us a description of your problem along with Drupal and IE 7 release numbers.

- The Drupul Community"

How is that a wrong message to send?

Given that the release of IE 6 was in 2001 and IE 7 is a major release with rendering implications, many people are going to want to know how extensive IE 7 testing was before upgrading. Also consider the opposite: If Microsoft breaks something, how will that affect all previous releases of Drupal.

Drupal alone holds little weight in Microsoft's eyes. Don't think you will be able to bang on their door crying and demanding fixes. Like I said, you have to live with it and roll with it.

Further, your missing the message here. And NO, it is not off topic since this is the only forum post on the subject and its fresh. Nor is it "stupid".

Kerry Kobashi

BryanSD’s picture

Ok...I think everyone needs to settle down a bit. How much energy have we wasted on these type of discussions?

Kkobashi, Sepeck is likely correct that this is not so much of a Drupal problem as it is to specific coding within the theme being used at Drupal.org (this site...not the CMS). For all intensive purposes, Drupal.org's theme is "propriety" in that it is not available for download or for public use. In other words...there isn't anything to change within the Drupal CMS because the problem you're seeing at Drupal.org is likely not within Drupal Core or Themes that are available for download.

Now this isn't to say that the theme being used by Drupal.org shouldn't be corrected or tweaked for IE7. I think there should be some looking into the code within the theme to see if it's prudent to do anything at this point. Sepeck's point though is that if the display problem is actually due to a bug within IE7 beta and changes were to be made now to Drupal.org...this "shoot from the hip" fix now may make things worse for future versions of IE7 that would address this bug. Since Microsoft intends for the browser to follow standards (something new to them), if this is a bug then they will likely be fixing it very soon within IE7. I think everyone agrees that they want Drupal.org's theme to work well in IE7...it's a question of timing that seems to be causing this "conflict".

-Bryan

Drupal Sites Coming Soon:
CMSReport

Drupal Blog (on WordPress) at:
Like that Idea

kkobashi’s picture

The only one who needs to settle down is Sepeck because for some reason, he has it out for me and is taking this on personally.

For your information, I was directed to this thread after someone told me that the same problem I found was mentioned here. I fully understood the problem AND solution with IE 7 and Drupal.org.

My first message (read it carefully and where it exists in the hiearchy) was more general. It is about a push for compatability testing moving forward into IE 7 final release. It hasn't been since October 2001 that the last major version of IE was released. With hundreds of thousands of existing Drupal sites having the bulk of their visitors using IE, I would think that there should be some validation testing needed from the community, strict standards as we are or not. Backwards compatability is important and it *could* cause problems for older installations. People need to be aware, test, and provide feedback just in case sh*t exists.

That was where I was coming from and even suggested a plan
on how to do this. Somehow, this message got lost in the shuffle, having been pissed on by Mr. Peck.

I have no idea why Steven Peck went on a rampage acting in a pissy manner spitting on every one of my posts. To show how much vengeance he had towards me, my message "RE: Follow Standards" was in response to BryanSD's message. Look very carefully of how the message was nested in the hierarchy. I was simply agreeing with BryanSD's assessment that our time is best spent worrying that our sites/themes follow the standards.

Sepeck owes me a public apology for his completely wrong behavior. I was taught to respect people when I grew up, not act towards them in a condescending manner.

Kerry Kobashi

Martin Frank’s picture

I agree 100% with Kerry Kobashi.

Webmasters want their websites to display, display, display, to any user, with any browser. What's the use of a website which doesn't show?

Whatever the reason, it doesn't advance drupal that it's main website doesn't display correctly in the IE 7 Beta. In fact, nearly nothing of it displays; you cannot use IE 7 to access drupal.org's handbook, forum, downloads, or support.

IE 7 is so much better than earlier versions of IE that many people are already updating. I use IE 7 Beta every day, and have not encountered ONE other website which didn't display. Most of the drupaler themes seem to display correctly or with small flaws (fancy theme). MY drupal websites all display without (IE 7) problems. drupal.org obvioulsly is not a global drupal problem. it is a local drupal.org theme problem.

drupal.org is the main help, handbook and support site for drupal users. I fail to grasp why the necessary changes to make the website display without problems, should not be made immediately. EVEN if the cool beauty of the theme would have to be compromised.

It remembers me sadly of the login problem: TWO YEARS have been spent discussing an issue and still we have this war between webmasters going up the walls because suddenly one morning, their users cannot login, and drupalniks meditating on the cathedral like beauty of their core code... But then, I wouldn't use drupal, if I wouldn't believe that the drupalniks haven't built a great, slightly gothic, CMS code cathedral.

I guess, we have to be thankful for what they did for us and hope that the differnt piper they are following will whistle it to them in time.

Love

Martin

homepage and website of the gay swiss
writer martin frank

ByteDreams’s picture

IE 7 is no longer a beta. It's a release candidate. I i hope things get fixed soon -- it wasn't today. I just tried to view drupal.org today, and the only page that worked was the main page, so I had to get out of IE 7 and open up Firefox. Okay, so that's not a difficult thing to do, but it was annoying. The drupal site should work in all browsers. Every day that it doesn't could have an effect on the number of new Drupal users, not to mention attracting bad PR

ByteDreams

roly’s picture

Just read a report that IE7 will be released before 27 Oct via download and a few weeks after that via AU (automatic update) facility. Here is a link to an article:
http://www.internetnews.com/security/article.php/3637681

I hope drupal.org will be fixed soon too as I am concerned about the bad PR that it is likely to generate. Such as great 'product' and bad PR could have a major impact.

FiReaNGeL’s picture

The only bad PR it would generate is IE7 not being standard enough to display webpages, AGAIN, forcing web developers to just throught hoops / implement hacks to make it render on the most used browser. Extra points if you can point to WHY is IE the most used browser despite not being standard (hint: monopoly lawsuits against MS).

BryanSD’s picture

If this was a few years ago, using your argument we shouldn't have designed Web pages for Netscape 6 and/or Mozilla 1.0. Those were horrible days for those of us that had added so many tweaks to Netscape 4.7 and then when migrating to Netscape 6 and Mozilla found they (Netscape, Mozilla, Open Source) still didn't get it quite right! It really wasn't until Netscape 7 and later versions of Mozilla 1.x that they got it right.

In a lot of ways IE7 is a lot like Mozilla 1.0. It is a first attempt to correct the mistakes of the past. Is it fully CSS compliant without bugs? No...but at least Microsoft is finally moving in the right direction. As an open source community we have been rightly critical of Microsoft not following Web standards. Microsoft however, in my opinion, has made genuine efforts with IE7 to abide by the standards, something they really didn't do in the past. It seems disingenuous to me if we as a community who have been critical of IE6 reject the much more CSS compliant IE7 simply because it's from Microsoft.

Hopefully those defending IE6 code have actually taken a look at some of the IE6 CSS bugs that have been corrected in IE7?

Though you won’t see (most of) these until Beta 2, we have already fixed the following bugs from PositionIsEverything and Quirksmode:

* Peekaboo bug
* Guillotine bug
* Duplicate Character bug
* Border Chaos
* No Scroll bug
* 3 Pixel Text Jog
* Magic Creeping Text bug
* Bottom Margin bug on Hover
* Losing the ability to highlight text under the top border
* IE/Win Line-height bug
* Double Float Margin Bug
* Quirky Percentages in IE
* Duplicate indent
* Moving viewport scrollbar outside HTML borders
* 1 px border style
* Disappearing List-background
* Fix width:auto

In addition we’ve added support for the following

* HTML 4.01 ABBR tag
* Improved (though not yet perfect)

fallback * CSS 2.1 Selector support (child, adjacent, attribute, first-child etc.) * CSS 2.1 Fixed positioning * Alpha channel in PNG images * Fix :hover on all elements * Background-attachment: fixed on all elements not just body
Bryan CMSReport
BryanSD’s picture

Wow...the code in the bluebeach theme needs some work. First of all, with regards to the primary links (blue tabs)...it's an issue of the width not being specified that is causing the problem. If I place some width: 100px for the tabs where needed things display correctly in IE7. I also validated through W3C's CSS Validator that the BlueBeach style.css does not validate to standards. However, I did run into a problem trying to validate the front page of Drupal.org which contains a XHTML error...although the error is minor, the W3C CSS Validator refuses to validate until it is fixed. So I went ahead and just validated against the opening handbook page. Below is some of the errors I received showing that part of the problem is that the primary link tabs as written doesn't comply with CSS standards.

URI : http://drupal.org/themes/bluebeach/style.css

* Line: 76 Context : ul#primary-links li

Property _width doesn't exist : 0

Now here is the kicker...fixing the CSS still may not solve the problem for IE7. As I mentioned, specifiying a particular width of say 100px will fix this problem. However, the theme currently specifies the height of the tabs as 'auto' so that it changes dynamically with the size of font being used in the tabs. There is no reason that setting the width dynamically isn't also needed for difference in the number of characters needed to spell the word. From my understanding this is perfectly acceptable in CSS 2.1, BUT THE IE7 TEAM HAS YET TO INTRODUCE THIS FEATURE INTO IE7. Remember folks IE7 is still under development! From the MS developers themselves:

If you have dynamic content that requires changes to your box size on the fly. This can happen if you insert content dynamically, or you did not specify a font size and the user changes it as part of the user settings...We are currently working on implementing these but until they become available you can use a script solution similar to the one shown in the following code sample.

While, MS is offering a workaround...IMHO it's best to wait until a newer Beta of IE7 is released and fixes this. Implementing the workarounds could just get us into trouble with later versions. Of course that's just my opinion and I'll let the powers that be make those decisions.

What should be done IMO is start looking at fixing the CSS errors that we know are not true to standard. In the process of fixing the CSS errors in the theme's style.css there could be a chance that it fixes the display problems in IE7. However, according to Microsoft's own documentation it isn't likely.

On a sidebar...I can't believe IE7 is written by Microsoft. It really has a lot of promising features and when finished is likely to be just as compliant to CSS and XHTML standards as other browsers. I say this as I'm using Firefox 1.5.

-Bryan

Drupal Sites Coming Eventually:
CMSReport

Drupal Blog (on WordPress) at:
Like that Idea

roly’s picture

Just wanted to let you all know that IE7 (due 4th quarter) will be released via Automatic updates. This is likely to mean a huge uptake of IE7 in a small period of time. At the moment some of the content on drupal.org is not visible in IE7 (eg modules page).

I know this is a 'theming' issue but it may affect many sites out there where the audience has a high IE use.

Here is an article on this issue:

http://www.computerworld.com/action/article.do?command=viewArticleBasic&...